On Friday 16 December 2005 04:13 am, Goran Gajic wrote: > On Thu, 15 Dec 2005, John Baldwin wrote: > > If you are in X this is probably a panic (currently the kernel doesn't > > create a coredump while you are in X which is a bug). Can you hook up a > > serial console and use that to get the panic message? > > Yes, here is capture from minicom: > > drm0: <ATI Radeon RV280 9200 SE> port 0xc000-0xc0ff mem > 0xe8000000-0xefffffff,0xff8f0000-0xff8fffff irq 16 at device 0.0 on pci1 > info: [drm] AGP at 0xf8000000 64MB > info: [drm] Initialized radeon 1.19.0 20050911 > info: [drm] Loading R200 Microcode > lock order reversal: > 1st 0xc366e21c vnode interlock (vnode interlock) _at_ kern/vfs_vnops.c:791 > 2nd 0xc3b8fb44 process lock (process lock) _at_ i386/i386/trap.c:742 > KDB: stack backtrace: > kdb_backtrace(0,ffffffff,c0975450,c0975900,c0927544) at kdb_backtrace+0x29 > witness_checkorder(c3b8fb44,9,c08be5a5,2e6) at witness_checkorder+0x580 > _mtx_lock_flags(c3b8fb44,0,c08be59c,2e6,c3b91780) at _mtx_lock_flags+0x5b > trap_pfault(dbc9da28,0,3) at trap_pfault+0xb2 > trap(dbc90008,c0680028,c09b0028,c3b91780,dbc9da84) at trap+0x3cd > calltrap() at calltrap+0x5 > --- trap 0xc, eip = 0xc081799c, esp = 0xdbc9da68, ebp = 0xdbc9da70 --- > stack_save(dbc9da84) at stack_save+0x1c Ah, I think the stack_save() stuff in 6.0 is buggy. I think there's a fix in HEAD. I would just turn those DEBUG options off for now. -- John Baldwin <jhb_at_FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.orgReceived on Fri Dec 16 2005 - 19:25:10 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:49 UTC