In the last episode (Apr 02), Jeff Roberson said: > On Wed, 2 Apr 2003, Gordon Tetlow wrote: > > > I think it was a libthr linked app after I killed it: > > Yeah, this is a problem with the thread single exit and suspend code. > I haven't fixed it yet. Thanks for the report. I get the same LOR message on my machine, but it is always immediately followed by a panic. libthr also seems to only work with WITNESS. Without it the machine locks up hard (serial debugger doesn't even respond) when you start any libthr-linked app. Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = 03000000 fault virtual address = 0xa0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc03a1f72 stack pointer = 0x10:0xdff75c58 frame pointer = 0x10:0xdff75c84 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle trap number = 12 panic: page fault cpuid = 0; lapic.id = 03000000 Stack backtrace: panic(c03d95fc,c0406ad0,1,1,1) at panic+0x11b trap_fatal(dff75c18,a0,c043d120,c047df20,c40da850) at trap_fatal+0x28d trap_pfault(dff75c18,0,a0,c40d7d88,a0) at trap_pfault+0x17a trap(c40d0018,c40d0010,dff70010,c40d7d88,0) at trap+0x3e5 calltrap() at calltrap+0x5 --- trap 0xc, eip = 0xc03a1f72, esp = 0xdff75c58, ebp = 0xdff75c84 --- cpu_throw(c40d7d20,0,c03f0e89,7a9,c03f140a) at cpu_throw+0x12 thread_suspend_check(0,0,c03f2a5b,68,c40d7d88) at thread_suspend_check+0xd8 userret(c40da850,dff75d48,0,404,3) at userret+0x24b syscall(2f,2f,2f,0,82f8000) at syscall+0x167 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (0), eip = 0x28250e43, esp = 0xbfafee90, ebp = 0xbfafef2c --- -- Dan Nelson dnelson_at_allantgroup.comReceived on Fri Apr 04 2003 - 12:31:07 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:02 UTC