search for: 000000c6

...00 00 00 00-00 00 00 00 00 00 00 00 ss:eip=2b 00 00 00 33 00 00 00-00 0c 04 00 5f ad 08 04 00 00 00 00 0f 00 00 00-00 00 00 00 24 1c 06 00 BTX halted If I break to the loader prompt and try 'ls /boot', I get this backtrace: int=00000006 err=00000000 efl=00010203 eip=00040c08 eax=000000c6 ebx=00000008 ecx=eb000000 edx=000000c6 esi=00000004 edi=000000c2 ebp=00000000 esp=0008f8b4 cs=002b ds=0033 es=002b fs=0033 gs=0033 ss=0033 cs:eip=8f 49 40 00 94 49 00 cb-00 00 04 00 00 00 fc 07 80 00 00 00 04 00 00 00-94 49 00 00 00 00 00 00 ss:eip=00 00 00 00 00 00 00 00-00 00...

I've updated the win32 icecast2 binary on my site to reflect current CVS (as of now - March 19, 2003).... It's available here for anyone interested : http://www.oddsock.org/tools/icecast2/ <p>oddsock <p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to

...39;XXXXXX' on channel 0/22, span 1 Executing [XXXXXX at outgoing:1] NoOp("DAHDI/22-1", """ <XXXXXX>") in new stack Executing [XXXXXX at outgoing:2] Dial("DAHDI/22-1", "SIP/XXXXXX at ITSP1") in new stack Called XXXXXX at ITSP1 SIP/ITSP1-000000c6 is circuit-busy (This result is because the ITSP1 account is blocked for testing) Everyone is busy/congested at this time (1:0/1/0) ITSP2: Executing [XXXXXX at outgoing:3] Dial("DAHDI/22-1", "SIP/XXXXXX at ITSP2") in new stack Called XXXXXX at ITSP2...

...0000003f -1 00000056 -1 00000054 -1 000000b2 -1 0000003c -1 00000093 -1 00000029 -1 00000098 -1 00000076 -1 000000c9 -1 00000092 -1 00000036 -1 0000001c -1 000000de -1 000000c4 -1 0000009b -1 000000cd -1 0000009a -1 000000da -1 0000008e -1 000000c6 -1 00000025 -1 000000d6 -1 00000064 -1 00000072 -1 000000d3 -1 00000094 -1 00000062 -1 00000052 -1 00000055 -1 00000073 -1 00000059 -1 00000024 -1 0000000b -1 0000001a -1 000000c0 -1 0000006f -1 00000057 -1 00000015 -1 000000a8 -1 00000058...

...EL_I386_REL32 _setGlobal > bd: 89 e0 movl %esp, %eax > bf: c7 00 00 00 00 00 movl $0, (%eax) > 000000c1: IMAGE_REL_I386_DIR32 _foo > c5: e8 00 00 00 00 calll 0 <_setfoo+0xC6> > 000000c6: IMAGE_REL_I386_REL32 _debugPointer > ca: b9 d5 00 00 00 movl $213, %ecx > cf: 8b 74 24 2c movl 44(%esp), %esi > d3: 89 44 24 10 movl %eax, 16(%esp) > d7: 89 f0 movl %esi, %eax > d9: 89 54 24 0c m...

...bd: 89 e0 movl %esp, %eax >>> bf: c7 00 00 00 00 00 movl $0, (%eax) >>> 000000c1: IMAGE_REL_I386_DIR32 _foo >>> c5: e8 00 00 00 00 calll 0 <_setfoo+0xC6> >>> 000000c6: IMAGE_REL_I386_REL32 _debugPointer >>> ca: b9 d5 00 00 00 movl $213, %ecx >>> cf: 8b 74 24 2c movl 44(%esp), %esi >>> d3: 89 44 24 10 movl %eax, 16(%esp) >>> d7: 89 f0 movl %esi, %eax >&g...

On Mon, Jun 5, 2017 at 1:34 PM, Nikodemus Siivola < nikodemus at random-state.net> wrote: > Uh. Turns out that if I hide the pointer to @foo from LLVM by passing it > through an opaque identity function ... then everything works fine. > > Is this a bug in LLVM or is there some magic involving globals I'm > misunderstanding? > This looks like a bug in the handling of

https://bugs.freedesktop.org/show_bug.cgi?id=100567 Bug ID: 100567 Summary: Nouveau system freeze fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau