Re: Assertion faild at kern_mutex.c
Date: Thu, 28 Feb 2002 22:51:02 +0900 From: Jun Kuriyama [EMAIL PROTECTED] Sorry, I forgot to get kernel core for this (today's -current)... panic: Assertion td-td_proc-p_stat == SRUN || td-td_proc-p_stat == SZOMB || td-td_proc-p_stat == SSTOP failed at ../../../kern/kern_mutex.c:126 I have yet to see this, running either: freebeast(5.0-C)[1] uname -a FreeBSD freebeast.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Thu Feb 28 07:41:32 PST 2002 [EMAIL PROTECTED]:/common/S4/obj/usr/src/sys/FREEBEAST i386 (SMP build machine) or g1-7(5.0-C)[1] uname -a FreeBSD g1-7.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #85: Thu Feb 28 08:31:56 PST 2002 [EMAIL PROTECTED]:/common/S3/obj/usr/src/sys/LAPTOP_30W i386 (laptop) with sources updated as of: freebeast(5.0-C)[2] tail /var/log/cvsup-history.log CVSup begin from cvsup14.freebsd.org at Mon Feb 25 03:47:02 PST 2002 CVSup ended from cvsup14.freebsd.org at Mon Feb 25 03:53:57 PST 2002 CVSup begin from cvsup14.freebsd.org at Mon Feb 25 10:01:00 PST 2002 CVSup ended from cvsup14.freebsd.org at Mon Feb 25 10:07:56 PST 2002 CVSup begin from cvsup14.freebsd.org at Tue Feb 26 03:47:03 PST 2002 CVSup ended from cvsup14.freebsd.org at Tue Feb 26 03:53:30 PST 2002 CVSup begin from cvsup14.freebsd.org at Wed Feb 27 03:47:02 PST 2002 CVSup ended from cvsup14.freebsd.org at Wed Feb 27 03:53:38 PST 2002 CVSup begin from cvsup14.freebsd.org at Thu Feb 28 03:47:02 PST 2002 CVSup ended from cvsup14.freebsd.org at Thu Feb 28 03:53:56 PST 2002 Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill [EMAIL PROTECTED] I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Assertion faild at kern_mutex.c
At Thu, 28 Feb 2002 17:10:25 + (UTC), David Wolfskill wrote: Sorry, I forgot to get kernel core for this (today's -current)... panic: Assertion td-td_proc-p_stat == SRUN || td-td_proc-p_stat == SZOMB || td-td_proc-p_stat == SSTOP failed at ../../../kern/kern_mutex.c:126 I have yet to see this, running either: I cannot reproduce this assertion failure. I'll try to get core if I got this failure next time. -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Assertion faild at kern_mutex.c
At Fri, 1 Mar 2002 01:34:17 + (UTC), John Baldwin wrote: That's bad juju panic. :) Are you using witness? If so, did you get a printf about sleeping with a lock held? I think I did not get lock warning just before this assertion failure. But on my environment, I got this lock order reversal everytime I booted. lock order reversal 1st 0xc036afc0 allproc @ ../../../kern/vfs_syscalls.c:452 2nd 0xc7ecce34 filedesc structure @ ../../../kern/vfs_syscalls.c:457 -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Assertion faild at kern_mutex.c
Date: Fri, 01 Mar 2002 10:47:09 +0900 From: Jun Kuriyama [EMAIL PROTECTED] At Fri, 1 Mar 2002 01:34:17 + (UTC), John Baldwin wrote: That's bad juju panic. :) Are you using witness? If so, did you get a printf about sleeping with a lock held? I think I did not get lock warning just before this assertion failure. But on my environment, I got this lock order reversal everytime I booted. lock order reversal 1st 0xc036afc0 allproc @ ../../../kern/vfs_syscalls.c:452 2nd 0xc7ecce34 filedesc structure @ ../../../kern/vfs_syscalls.c:457 Although I did not get the reported panic, I have also had a very similar lock order reversal reported since (at least) the -CURRENT of 22 Feb. (which as far back as I presently keep the message log). I'm skeptical that there is a significant relationship between the panic the lock order reversal. Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill [EMAIL PROTECTED] I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Assertion faild at kern_mutex.c
David Wolfskill wrote: Date: Fri, 01 Mar 2002 10:47:09 +0900 From: Jun Kuriyama [EMAIL PROTECTED] At Fri, 1 Mar 2002 01:34:17 + (UTC), John Baldwin wrote: That's bad juju panic. :) Are you using witness? If so, did you get a printf about sleeping with a lock held? I think I did not get lock warning just before this assertion failure. But on my environment, I got this lock order reversal everytime I booted. lock order reversal 1st 0xc036afc0 allproc @ ../../../kern/vfs_syscalls.c:452 2nd 0xc7ecce34 filedesc structure @ ../../../kern/vfs_syscalls.c:457 Although I did not get the reported panic, I have also had a very similar lock order reversal reported since (at least) the -CURRENT of 22 Feb. (which as far back as I presently keep the message log). I reported that particular LOR on this list on Feb 7th. -- Michael Nottebrock To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Assertion faild at kern_mutex.c
At Fri, 1 Mar 2002 01:34:17 + (UTC), John Baldwin wrote: That's bad juju panic. :) Are you using witness? If so, did you get a printf about sleeping with a lock held? I forgot to mention, I'm using WITNESS and WITNESS_SKIPSPIN options. -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Assertion faild at kern_mutex.c
On 01-Mar-02 David Wolfskill wrote: Date: Fri, 01 Mar 2002 10:47:09 +0900 From: Jun Kuriyama [EMAIL PROTECTED] At Fri, 1 Mar 2002 01:34:17 + (UTC), John Baldwin wrote: That's bad juju panic. :) Are you using witness? If so, did you get a printf about sleeping with a lock held? I think I did not get lock warning just before this assertion failure. But on my environment, I got this lock order reversal everytime I booted. lock order reversal 1st 0xc036afc0 allproc @ ../../../kern/vfs_syscalls.c:452 2nd 0xc7ecce34 filedesc structure @ ../../../kern/vfs_syscalls.c:457 Although I did not get the reported panic, I have also had a very similar lock order reversal reported since (at least) the -CURRENT of 22 Feb. (which as far back as I presently keep the message log). I'm skeptical that there is a significant relationship between the panic the lock order reversal. There's not. The panic is due to some process being asleep or something while holding a mutex. That reversal is a known problem that involves redoing select a bit. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ 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
