RE: panic (witness_destroy+0x237) after booting today's -CURRENT
On 31-May-01 David Wolfskill wrote: Once I saw that I had a real hostname, I hit ^D at the shell prompt, put my fingers in position to hit Alt+F9, and kernel: type 12 trap, code=0 Stopped at witness_destroy+0x237: cmpl%esi,0xc(%edx) db trace witness_destroy(ce7e211c,ce7e211c,ce894f3c,c01ce297,ce7e211c) at witness_destroy+0x237 mtx_destroy(ce7e211c,ce7e2000,ce7e277c,ce7e2660,4) at mtx_destroy+0x73 wait1(ce7e2660,ce894f80,0,ce894fa0,c036e899) at wait1+0x897 wait4(ce7e2660,ce894f80,bfbfb8dc,2,2)) at wait4+0x10 syscall(2f,2f,2f,2,2) at syscall+0x71d syscall_with_err_pushed() at syscall_with_err_pushed+0x1b db Did you get any other messages, such as a faulting virtual address, etc.? Is %edx 0? -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: panic (witness_destroy+0x237) after booting today's -CURRENT
Date: Thu, 31 May 2001 13:46:01 -0700 (PDT) From: John Baldwin [EMAIL PROTECTED] Did you get any other messages, such as a faulting virtual address, etc.? I had been using vty1; when the panic ocurred, I was (forcibly) switched to vty0. There are no faulting virtual address-flavored messages on vty0. If there were on vty1, I didn't see them quickly enough. Is %edx 0? [Checks man ddb...] Yes, it is. Anything else that might be of interest? I'm about to head into a meeting, but I'll leave the crashed system crashed as long as I can if it might be useful to poke around in there. Thanks, david -- David H. Wolfskill [EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: panic (witness_destroy+0x237) after booting today's -CURRENT
On 31-May-01 David Wolfskill wrote: Date: Thu, 31 May 2001 13:46:01 -0700 (PDT) From: John Baldwin [EMAIL PROTECTED] Did you get any other messages, such as a faulting virtual address, etc.? I had been using vty1; when the panic ocurred, I was (forcibly) switched to vty0. There are no faulting virtual address-flavored messages on vty0. If there were on vty1, I didn't see them quickly enough. Is %edx 0? [Checks man ddb...] Yes, it is. Anything else that might be of interest? I'm about to head into a meeting, but I'll leave the crashed system crashed as long as I can if it might be useful to poke around in there. Hmm, not that I can think of atm. It looks like the SLIST of all lock in the system got corrupted somehow. :( -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
