Re: panic: lock (sleep mutex) vnode interlock on Alpga
On Tue, 25 Sep 2001, Wilko Bulte wrote: I'm not sure if this is new, but anyway on -current as of yesterday evening: Mounting root from ufs:/dev/da1a panic: lock (sleep mutex) vnode interlock not locked @ /usr/src/sys/kern/vfs_default.c:460 panic Is this problem solved ? Can anyone give a 'go' on this one ? I'm waiting for this bug to be solved so that I can upgrade one of my 4.4-RELEASE machines to -CURRENT. :) -Steve -- Stephan van Beerschoten [SVB21-RIPE] [EMAIL PROTECTED] PGP fingerprint: 4557 9761 B212 FB4C 778D 3529 C42A 2D27 To err is human, to forgive is Not Company Policy To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic: lock (sleep mutex) vnode interlock on Alpga
On Sat, Sep 29, 2001 at 10:45:22AM +0200, Stephan van Beerschoten wrote: On Tue, 25 Sep 2001, Wilko Bulte wrote: I'm not sure if this is new, but anyway on -current as of yesterday evening: Mounting root from ufs:/dev/da1a panic: lock (sleep mutex) vnode interlock not locked @ /usr/src/sys/kern/vfs_default.c:460 panic Is this problem solved ? Can anyone give a 'go' on this one ? I'm waiting for this bug to be solved so that I can upgrade one of my 4.4-RELEASE machines to -CURRENT. :) I think yes. John committed a fix IIRC. At least my Alpha stopped panicing. -- | / o / /_ _ email: [EMAIL PROTECTED] |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic: lock (sleep mutex) vnode interlock on Alpga
On Wed, 26 Sep 2001, Wilko Bulte wrote: FWIW: the kernel that shows this behaviour was built using make buildkernel just after a make buildworld. That should ensure a make depend. But I'll try your suggestions and see what happens next. I have the same problem as described earlier in this thread. I installed a 4.4 RELEASE (cdrom) system and then cvsupped my way to -CURRENT. After that basically I did a /usr/src# make update buildworld buidkernel KERNCONF=GENERIC and a /usr/src# make installworld installkernel KERNCONF=GENERIC I ran mergemaster and agreed to pretty much everything; I booted, and I ended up with the problem. I did this several times (at least 3) trying out different minor things. None helped obviously. I thought I did something wrong while upgrading from 4.x to 5.x that resuled in this. -- Stephan van Beerschoten [SVB21-RIPE] [EMAIL PROTECTED] PGP fingerprint: 4557 9761 B212 FB4C 778D 3529 C42A 2D27 To err is human, to forgive is Not Company Policy To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
panic: lock (sleep mutex) vnode interlock on Alpga
I'm not sure if this is new, but anyway on -current as of yesterday evening: acd0: CDROM TOSHIBA CD-ROM XM-6302B at ata0-master PIO4 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da1a panic: lock (sleep mutex) vnode interlock not locked @ /usr/src/sys/kern/vfs_default.c:460 panic Stopped at Debugger+0x34: zapnot v0,#0xf,a0 v0=0x0,a0=0x6 db trace Debugger() at Debugger+0x34 panic() at panic+0x100 witness_unlock() at witness_unlock+0x2a4 _mtx_unlock_flags() at _mtx_unlock_flags+0x98 vop_nolock() at vop_nolock+0x38 vop_defaultop() at vop_defaultop+0x2c vn_lock() at vn_lock+0x15c ffs_mountfs() at ffs_mountfs+0xd8 ffs_mount() at ffs_mount+0x9c vfs_mountroot_try() at vfs_mountroot_try+0x200 vfs_mountroot() at vfs_mountroot+0x9c mi_startup() at mi_startup+0x154 locorestart() at locorestart+0x68 --- root of call graph --- db -- | / o / /_ _ email: [EMAIL PROTECTED] |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic: lock (sleep mutex) vnode interlock on Alpga
I'm getting the same thing from a kernel I built this morning on i386. Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services On Tue, 25 Sep 2001, Wilko Bulte wrote: I'm not sure if this is new, but anyway on -current as of yesterday evening: acd0: CDROM TOSHIBA CD-ROM XM-6302B at ata0-master PIO4 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da1a panic: lock (sleep mutex) vnode interlock not locked @ /usr/src/sys/kern/vfs_default.c:460 panic Stopped at Debugger+0x34: zapnot v0,#0xf,a0 v0=0x0,a0=0x6 db trace Debugger() at Debugger+0x34 panic() at panic+0x100 witness_unlock() at witness_unlock+0x2a4 _mtx_unlock_flags() at _mtx_unlock_flags+0x98 vop_nolock() at vop_nolock+0x38 vop_defaultop() at vop_defaultop+0x2c vn_lock() at vn_lock+0x15c ffs_mountfs() at ffs_mountfs+0xd8 ffs_mount() at ffs_mount+0x9c vfs_mountroot_try() at vfs_mountroot_try+0x200 vfs_mountroot() at vfs_mountroot+0x9c mi_startup() at mi_startup+0x154 locorestart() at locorestart+0x68 --- root of call graph --- db -- | / o / /_ _ email: [EMAIL PROTECTED] |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic: lock (sleep mutex) vnode interlock on Alpga
On Tue, Sep 25, 2001 at 07:25:04PM +0200, Wilko Bulte wrote: I'm not sure if this is new, but anyway on -current as of yesterday evening: acd0: CDROM TOSHIBA CD-ROM XM-6302B at ata0-master PIO4 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da1a panic: lock (sleep mutex) vnode interlock not locked @ /usr/src/sys/kern/vfs_default.c:460 panic Stopped at Debugger+0x34: zapnot v0,#0xf,a0 v0=0x0,a0=0x6 db trace Debugger() at Debugger+0x34 panic() at panic+0x100 witness_unlock() at witness_unlock+0x2a4 _mtx_unlock_flags() at _mtx_unlock_flags+0x98 vop_nolock() at vop_nolock+0x38 vop_defaultop() at vop_defaultop+0x2c vn_lock() at vn_lock+0x15c ffs_mountfs() at ffs_mountfs+0xd8 ffs_mount() at ffs_mount+0x9c vfs_mountroot_try() at vfs_mountroot_try+0x200 vfs_mountroot() at vfs_mountroot+0x9c mi_startup() at mi_startup+0x154 locorestart() at locorestart+0x68 --- root of call graph --- db Yep, I get exactly the same problem here. -- Simon Dick [EMAIL PROTECTED] Why do I get this urge to go bowling everytime I see Tux? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: panic: lock (sleep mutex) vnode interlock on Alpga
On 25-Sep-01 Wilko Bulte wrote: I'm not sure if this is new, but anyway on -current as of yesterday evening: Ok, can you try building a new kernel from scratch and see if you still have the same problem? If so, can you back out my latest set of changes to kern_mutex.c and sys/mutex.h and see if that fixes things? It looks like witness is somehow getting out of sync. One cause could be stale .o files that aren't being recompiled. Perhaps you haven't run make depend in a while? -- 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: lock (sleep mutex) vnode interlock on Alpga
John/all: For what it's worth... I started experiencing this panic problem as described .. After a make depend and then building/installing the kernel the problem is gone. This was from a cvsup ~9:30 EST 9/25/01 --mikej Michael Jung [EMAIL PROTECTED] On 25-Sep-01 Wilko Bulte wrote: I'm not sure if this is new, but anyway on -current as of yesterday evening: Ok, can you try building a new kernel from scratch and see if you still have the same problem? If so, can you back out my latest set of changes to kern_mutex.c and sys/mutex.h and see if that fixes things? It looks like witness is somehow getting out of sync. One cause could be stale .o files that aren't being recompiled. Perhaps you haven't run make depend in a while? -- 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 [EMAIL PROTECTED] ../mailto.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic: lock (sleep mutex) vnode interlock on Alpga
On Tue, Sep 25, 2001 at 02:49:41PM -0700, John Baldwin wrote: On 25-Sep-01 Wilko Bulte wrote: I'm not sure if this is new, but anyway on -current as of yesterday evening: Ok, can you try building a new kernel from scratch and see if you still have the same problem? If so, can you back out my latest set of changes to kern_mutex.c and sys/mutex.h and see if that fixes things? It looks like witness is somehow getting out of sync. One cause could be stale .o files that aren't being recompiled. Perhaps you haven't run make depend in a while? FWIW: the kernel that shows this behaviour was built using make buildkernel just after a make buildworld. That should ensure a make depend. But I'll try your suggestions and see what happens next. -- | / o / /_ _ email: [EMAIL PROTECTED] |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
