Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
The word is that there is a problem but it is a software problem. For some reason the virtual hub gives an IOERROR, but I haven't had the time or seen the need to figure that one out. It seems to be harmless though. nick > And what is the word on thise IOERROR's given by my kernel when its init'ing > its usb stack. > > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhub0: port 1 power on failed, IOERROR > uhub0: port 2 power on failed, IOERROR > > ? > > -Steve > > -- > Stephan van Beerschoten[EMAIL PROTECTED] > PGP fingerprint: 4557 9761 B212 FB4C 778D 3529 C42A 2D27 >"This email was brought to you by your local pop server" > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
On Fri, Jul 28, 2000 at 02:17:31PM -0700, Andrey A. Chernov wrote: > I too. The only way I can avoid this panic is > > 1) Remove /erc/rc.shutdown (which write files) > 2) Do several syns manually before reboot. > > In all other situations I got this panic. Just another way (suggested by a friend of my) is to shutdown into the single user mode, umount every filesystem, forcibly remount / into read-only mode - and then reboot. Gonna try putting this into /etc/rc.shutdown. -- /Voland Vadim Belman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
On Fri, Jul 28, 2000 at 11:36:26AM -0700, Scott Flatman wrote: > On Fri, 28 Jul 2000, Brian Fundakowski Feldman wrote: > > > I havne't been able to reproduce this, but this case is going to have > > more to do with analysis of the code than with "debugging", I think. > > By chance are you running with softupdates enabled on /? If I can > > reproduce it here, I will spend a while inspecting all the state to > > figure this one out as best as possible. > > I get the same panic 100% of the time upon reboot. So I can quite > easily reproduce it. :) I too. The only way I can avoid this panic is 1) Remove /erc/rc.shutdown (which write files) 2) Do several syns manually before reboot. In all other situations I got this panic. -- Andrey A. Chernov <[EMAIL PROTECTED]> http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
On Fri, 28 Jul 2000, Brian Fundakowski Feldman wrote: > I havne't been able to reproduce this, but this case is going to have > more to do with analysis of the code than with "debugging", I think. > By chance are you running with softupdates enabled on /? If I can > reproduce it here, I will spend a while inspecting all the state to > figure this one out as best as possible. I get the same panic 100% of the time upon reboot. So I can quite easily reproduce it. :) I tried turning off softupdates on all partitions. Same panic. It also caused umount to hang the machine. I don't have softupdates on / either way. I rebuilt a kernel today, about 1 hour ago. Still panics either way, with or without softupdates. Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
I'm running with softupdates on /, and it has happened to me several times. On Fri, 28 Jul 2000, Brian Fundakowski Feldman wrote: > On Fri, 28 Jul 2000, Sheldon Hearn wrote: > > > > > Just a quick note to let you two gentlement know that the problem > > persists with rev 1.107 of buf.h. > > > > Brian, these are realy easy for me to reproduce on my own box here. Do > > you want to send me the stuff for maintaining the queues that you said > > would help you figure out what's going on? Or are you able to reproduce > > this yourself? > > I havne't been able to reproduce this, but this case is going to have > more to do with analysis of the code than with "debugging", I think. > By chance are you running with softupdates enabled on /? If I can > reproduce it here, I will spend a while inspecting all the state to > figure this one out as best as possible. > > > Ciao, > > Sheldon. > > -- > Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / > [EMAIL PROTECTED]`--' > > > > 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: lockmgr: pid 5, not exclusive lock holder 0 unlocking
On Fri, 28 Jul 2000, Sheldon Hearn wrote: > > Just a quick note to let you two gentlement know that the problem > persists with rev 1.107 of buf.h. > > Brian, these are realy easy for me to reproduce on my own box here. Do > you want to send me the stuff for maintaining the queues that you said > would help you figure out what's going on? Or are you able to reproduce > this yourself? I havne't been able to reproduce this, but this case is going to have more to do with analysis of the code than with "debugging", I think. By chance are you running with softupdates enabled on /? If I can reproduce it here, I will spend a while inspecting all the state to figure this one out as best as possible. > Ciao, > Sheldon. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
On Wed, 26 Jul 2000 16:43:04 MST, Kirk McKusick wrote:
> I have had a number of complaints of this sort which seem to be
> somehow related to recursive buffer locks. Since the recursive
> locks are only needed to prevent deadlock when mounting snapshots
> I decided to back out the use of recursive locks for now. When I
> have had a chance to investigate why they are causing problems,
> I will try reenabling them. Let me know if this problem persists
> once you have upgraded to version 1.107 of buf.h.
Just a quick note to let you two gentlement know that the problem
persists with rev 1.107 of buf.h.
Brian, these are realy easy for me to reproduce on my own box here. Do
you want to send me the stuff for maintaining the queues that you said
would help you figure out what's going on? Or are you able to reproduce
this yourself?
Ciao,
Sheldon.
Script started on Fri Jul 28 14:25:46 2000
[root@axl] ~AXL # gdb -k -c /var/crash/vmcore.3 kernel.debug
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
IdlePTD 2826240
initial pcb at 244080
panicstr: lockmgr: pid 1, not exclusive lock holder 0 unlocking
panic messages:
---
---
#0 boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:303
303 dumppcb.pcb_cr3 = rcr3();
(kgdb) bt
#0 boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:303
#1 0xc01462c1 in panic (fmt=0xc02044a0 "lockmgr: pid %d, not %s %d unlocking")
at /usr/src/sys/kern/kern_shutdown.c:553
#2 0xc0140fdc in lockmgr (lkp=0xc0da4400, flags=6, interlkp=0xc8f08dec,
p=0xc84bfe00) at /usr/src/sys/kern/kern_lock.c:382
#3 0xc01747b3 in vop_stdunlock (ap=0xc84c5e48)
at /usr/src/sys/kern/vfs_default.c:255
#4 0xc01b4285 in ufs_vnoperate (ap=0xc84c5e48)
at /usr/src/sys/ufs/ufs/ufs_vnops.c:2285
#5 0xc01af163 in ufs_inactive (ap=0xc84c5e78) at vnode_if.h:865
#6 0xc01b4285 in ufs_vnoperate (ap=0xc84c5e78)
at /usr/src/sys/ufs/ufs/ufs_vnops.c:2285
#7 0xc017752e in vput (vp=0xc8f08d80) at vnode_if.h:794
#8 0xc01ac43f in ffs_sync (mp=0xc0c35a00, waitfor=2, cred=0xc0721780,
p=0xc02569e0) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:955
#9 0xc01794b1 in sync (p=0xc02569e0, uap=0x0)
at /usr/src/sys/kern/vfs_syscalls.c:551
#10 0xc0145cf7 in boot (howto=0) at /usr/src/sys/kern/kern_shutdown.c:225
#11 0xc0145af8 in reboot (p=0xc84bfe00, uap=0xc84c5f80)
at /usr/src/sys/kern/kern_shutdown.c:146
#12 0xc01eb239 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = -1077936612, tf_esi = -1077936624, tf_ebp = -1077936836,
tf_isp = -934518828, tf_ebx = -1077936732, tf_edx = -1, tf_ecx = 4,
---Type to continue, or q to quit---
tf_eax = 55, tf_trapno = 7, tf_err = 2, tf_eip = 134536452, tf_cs = 31,
tf_eflags = 643, tf_esp = -1077937056, tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:1128
#13 0xc01dff45 in Xint0x80_syscall ()
#14 0x80486ee in ?? ()
#15 0x8048478 in ?? ()
#16 0x8048139 in ?? ()
(kgdb) quit
[root@axl] ~AXL # exit
Script done on Fri Jul 28 14:26:19 2000
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
On Wed, 26 Jul 2000, Sheldon Hearn wrote: > > Hi Kirk, > > On Tue, 25 Jul 2000 11:28:47 MST, Kirk McKusick wrote: > > > Modified files: > > sys/kern vfs_bio.c > > Log: > > Now that buffer locks can be recursive, we need to delete the panics > > that complain about them. > > This looks related. I get it pretty consistently on shutdown, provided > the machine did some work subsequent to going multi-user. [Script cut] Yeah, several people are noticing that one. Robert Watson and I were trying to debug it, but it was really late at night so personally I gave up on it until I could reproduce it here. I got a different one. I'd like to track it down but it hasn't repeated itself (yet?). My call stack was (disregarding ATA's call stack mostly): panic() bufdone() checking that B_DONE's not set (which it is) cluster_callback() calling bp->b_iodone() biodone() calling bufdone() ad_interrupt() calling biodone() I implemented a little circular buffer which holds (calling function, bp) pairs for bufdone(), but so far I have had no crash yet (yay? :-/). When I do, the circular buffer (thanks, Greg!) will help me out to actually debug this instead of just wondering why B_DONE was set. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
Hi Kirk,
On Tue, 25 Jul 2000 11:28:47 MST, Kirk McKusick wrote:
> Modified files:
> sys/kern vfs_bio.c
> Log:
> Now that buffer locks can be recursive, we need to delete the panics
> that complain about them.
This looks related. I get it pretty consistently on shutdown, provided
the machine did some work subsequent to going multi-user.
Ciao,
Sheldon.
Script started on Wed Jul 26 13:20:40 2000
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
IdlePTD 2842624
initial pcb at 247480
panicstr: lockmgr: pid 1, not exclusive lock holder 0 unlocking
panic messages:
---
---
#0 boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:303
303 dumppcb.pcb_cr3 = rcr3();
(kgdb) back
#0 boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:303
#1 0xc0146bb5 in panic (fmt=0xc02072a0 "lockmgr: pid %d, not %s %d unlocking")
at /usr/src/sys/kern/kern_shutdown.c:553
#2 0xc01418d0 in lockmgr (lkp=0xc0ea3c00, flags=6, interlkp=0xc8f8842c,
p=0xc84bfe00) at /usr/src/sys/kern/kern_lock.c:382
#3 0xc017509f in vop_stdunlock (ap=0xc84c5e48)
at /usr/src/sys/kern/vfs_default.c:255
#4 0xc01b6eed in ufs_vnoperate (ap=0xc84c5e48)
at /usr/src/sys/ufs/ufs/ufs_vnops.c:2275
#5 0xc01b1e4f in ufs_inactive (ap=0xc84c5e78) at vnode_if.h:865
#6 0xc01b6eed in ufs_vnoperate (ap=0xc84c5e78)
at /usr/src/sys/ufs/ufs/ufs_vnops.c:2275
#7 0xc0177e1a in vput (vp=0xc8f883c0) at vnode_if.h:794
#8 0xc01af12b in ffs_sync (mp=0xc0c65200, waitfor=2, cred=0xc0721780,
p=0xc0259de0) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:955
#9 0xc0179d9d in sync (p=0xc0259de0, uap=0x0)
at /usr/src/sys/kern/vfs_syscalls.c:551
#10 0xc01465eb in boot (howto=0) at /usr/src/sys/kern/kern_shutdown.c:225
#11 0xc01463ec in reboot (p=0xc84bfe00, uap=0xc84c5f80)
at /usr/src/sys/kern/kern_shutdown.c:146
#12 0xc01edea9 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = -1077936612, tf_esi = -1077936624, tf_ebp = -1077936836,
tf_isp = -934518828, tf_ebx = -1077936732, tf_edx = -1, tf_ecx = 4,
tf_eax = 55, tf_trapno = 7, tf_err = 2, tf_eip = 134536452, tf_cs = 31,
tf_eflags = 643, tf_esp = -1077937056, tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:1128
#13 0xc01e2bb5 in Xint0x80_syscall ()
#14 0x80486ee in ?? ()
#15 0x8048478 in ?? ()
#16 0x8048139 in ?? ()
(kgdb) quit
Script done on Wed Jul 26 13:20:49 2000
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
Wilko Bulte wrote: > On Tue, Jul 25, 2000 at 12:12:20PM -0700, Mike Smith wrote: > > > Stephan van Beerschoten wrote: > > > > > > > > And what is the word on thise IOERROR's given by my kernel when its init'ing > > > > its usb stack. > > > > > > > > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > > > uhub0: 2 ports with 2 removable, self powered > > > > uhub0: port 1 power on failed, IOERROR > > > > uhub0: port 2 power on failed, IOERROR > > > > > > > > > > Funny you should mention that :-) I asked the same question to N. Hibma > > > a while ago (I get the same problem on my Intel OR840), but so far > > > haven't had an answer. > > > > That's because the message is completely harmless; ignore it. > > True.. but flagging completely harmless messages with "failed" and "IOERROR" > is bound to generate lots and lots of questions. If it does not tell the > world anything useful let's please get rid of it. Agreed. If they are harmless and meaningless, please axe them. They are a flood of -questions questions waiting to happen. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/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: lockmgr: pid 5, not exclusive lock holder 0 unlocking
On Tue, Jul 25, 2000 at 12:12:20PM -0700, Mike Smith wrote: > > Stephan van Beerschoten wrote: > > > > > > And what is the word on thise IOERROR's given by my kernel when its init'ing > > > its usb stack. > > > > > > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > > uhub0: 2 ports with 2 removable, self powered > > > uhub0: port 1 power on failed, IOERROR > > > uhub0: port 2 power on failed, IOERROR > > > > > > > Funny you should mention that :-) I asked the same question to N. Hibma > > a while ago (I get the same problem on my Intel OR840), but so far > > haven't had an answer. > > That's because the message is completely harmless; ignore it. True.. but flagging completely harmless messages with "failed" and "IOERROR" is bound to generate lots and lots of questions. If it does not tell the world anything useful let's please get rid of it. Or? -- Wilko Bulte http://www.freebsd.org [EMAIL PROTECTED] http://www.nlfug.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
> Stephan van Beerschoten wrote: > > > > And what is the word on thise IOERROR's given by my kernel when its init'ing > > its usb stack. > > > > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > uhub0: 2 ports with 2 removable, self powered > > uhub0: port 1 power on failed, IOERROR > > uhub0: port 2 power on failed, IOERROR > > > > Funny you should mention that :-) I asked the same question to N. Hibma > a while ago (I get the same problem on my Intel OR840), but so far > haven't had an answer. That's because the message is completely harmless; ignore it. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
Stephan van Beerschoten wrote: > > And what is the word on thise IOERROR's given by my kernel when its init'ing > its usb stack. > > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhub0: port 1 power on failed, IOERROR > uhub0: port 2 power on failed, IOERROR > Funny you should mention that :-) I asked the same question to N. Hibma a while ago (I get the same problem on my Intel OR840), but so far haven't had an answer. Regards, PYD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
On Tue, 25 Jul 2000, Ollivier Robert wrote: > According to Brian Fundakowski Feldman: > > Actually, I'm pretty certain this is the fix: > > Well it won't panic but isn't it putting the problem under the carpet? I > agree the panic seems to be here temporarely but... No, I'm really certain this isn't the case. You see, struct buf has a b_lock that until recently was a plain, exclusive lockmgr lock. In Kirk's last round of changes, he converted b_lock to be LK_CANRECURSE, which means that the lock, while still an exclusive lock, may be relocked multiple times by the same caller. The panics are plain wrong. What's left is to determine what is the proper thing to do in each of these cases, which I'm certain that many people already know already (you see, I'm still a bit green ;). What I am _almost_ sure about is that the right thing is just to remove one of the locks and let it get freed back up the call chain. I'm almost certain this is the case because if you are grabbing exclusive locks and recursing upon them, your call chain is the only consumer and in a recursive-locking-callchain, you will have multiple symmetric lock and unlock pairs. Anything else horribly complicates things, and this makes me a good 95% certain that this is exactly the right fix, not that it's sweeping any true bugs under the carpet. Allowing recursive locks is pretty much the only way to solve many of the problems here because it's simply not possible to support all code paths without allowing for this recursion. The code would either be horribly complicated or non-functional. I'm certain Kirk may be able to back me up here. It seems that the cleanup is meant to make the locks recursive mostly to facilitate correct/proper call chains, and that's consistent with my understand at least :) Indeed, if you look at the comment in brelse() from the delta, you will see that the intention of allowing this very situation to occur and simply BUF_UNLOCK() was planned for and the panic()s were for debugging during the previous time that b_locks weren't LK_CANRECURSE. As always, take what I say with a grain of salt since I'm definitely not a VFS guru in any manner; I just happen to think I understand this one :) > -- > Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- [EMAIL PROTECTED] > The Postman hits! The Postman hits! You have new mail. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
According to Stephan van Beerschoten: > But indeed.. isn't removing the panic cal just shifting the problem in > stead of taking care of the panic-originator ? That's what is bothering me :-) > And what is the word on thise IOERROR's given by my kernel when its init'ing > its usb stack. It started a few months but doesn't seem to stop my USB mouse from working... -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- [EMAIL PROTECTED] The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
On Tue, 25 Jul 2000, Brian Fundakowski Feldman wrote: > Actually, I'm pretty certain this is the fix: > I have removed the panic-calls. I'll see if my system gets otherwise unstable.. For now i'll be happy if I get enough time for my make world to complete before my system hangt itself again :) But indeed.. isn't removing the panic cal just shifting the problem in stead of taking care of the panic-originator ? And what is the word on thise IOERROR's given by my kernel when its init'ing its usb stack. uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port 1 power on failed, IOERROR uhub0: port 2 power on failed, IOERROR ? -Steve -- Stephan van Beerschoten[EMAIL PROTECTED] PGP fingerprint: 4557 9761 B212 FB4C 778D 3529 C42A 2D27 "This email was brought to you by your local pop server" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
According to Brian Fundakowski Feldman: > Actually, I'm pretty certain this is the fix: Well it won't panic but isn't it putting the problem under the carpet? I agree the panic seems to be here temporarely but... -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- [EMAIL PROTECTED] The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
Actually, I'm pretty certain this is the fix:
Index: vfs_bio.c
===
RCS file: /usr2/ncvs/src/sys/kern/vfs_bio.c,v
retrieving revision 1.260
diff -u -r1.260 vfs_bio.c
--- vfs_bio.c 2000/07/11 22:07:43 1.260
+++ vfs_bio.c 2000/07/25 14:24:26
@@ -1067,9 +1067,6 @@
if (bp->b_qindex != QUEUE_NONE)
panic("brelse: free buffer onto another queue???");
if (BUF_REFCNT(bp) > 1) {
- /* Temporary panic to verify exclusive locking */
- /* This panic goes away when we allow shared refs */
- panic("brelse: multiple refs");
/* do not release to free list */
BUF_UNLOCK(bp);
splx(s);
@@ -1192,7 +1189,6 @@
panic("bqrelse: free buffer onto another queue???");
if (BUF_REFCNT(bp) > 1) {
/* do not release to free list */
- panic("bqrelse: multiple refs");
BUF_UNLOCK(bp);
splx(s);
return;
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[EMAIL PROTECTED]`--'
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
On Tue, 25 Jul 2000, Ollivier Robert wrote:
> I just got two panics tonight, the same each time. Current from yesterday,
> after the latest round of patch from Kirk. The second panic is exactly the
> same including the trace.
Welp, I didn't get em before, but I do now. I'll see what I can do to figure
this one out, but don't know at all if I'll be able to solve it. My
backtrace is similar. The important par about the backtrace is the
part before the panic:
#9 0xc0164695 in panic (fmt=0xc02662eb "bqrelse: multiple refs") at
../../kern/kern_shutdown.c:553
#10 0xc018f3b5 in bqrelse (bp=0xc373e100) at ../../kern/vfs_bio.c:1195
#11 0xc018e9b9 in vfs_backgroundwritedone (bp=0xc37812e0) at ../../kern/vfs_bio.c:696
#12 0xc0190fbd in bufdone (bp=0xc37812e0) at ../../kern/vfs_bio.c:2666
#13 0xc0190f06 in bufdonebio (bp=0xc37812e0) at ../../kern/vfs_bio.c:2617
#14 0xc0221258 in ad_interrupt (request=0xc10f43c0) at ../../sys/bio.h:103
#15 0xc021f756 in ata_intr (data=0xc0c7ff80) at ../../dev/ata/ata-all.c:1126
#16 0xc024b747 in splx (ipl=0xc018e41a) at ../../i386/isa/ipl_funcs.c:181
#17 0xc018e41a in bread (vp=0xcf889600, blkno=0x260030, size=0x1800, cred=0x0,
bpp=0xd0476ad0)
at ../../kern/vfs_bio.c:459
#18 0xc01fa070 in ffs_blkfree (ip=0xd0476b58, bno=0x1373c8, size=0x2000) at
../../ufs/ffs/ffs_alloc.c:1346
#19 0xc0201153 in indir_trunc (ip=0xd0476b58, dbn=0x24cf40, level=0x0, lbn=0xc,
countp=0xd0476b48)
at ../../ufs/ffs/ffs_softdep.c:2098
#20 0xc0200f29 in handle_workitem_freeblocks (freeblks=0xc0ce9200) at
../../ufs/ffs/ffs_softdep.c:2002
#21 0xc02009b0 in softdep_setup_freeblocks (ip=0xc0f4ac00, length=0x0) at
../../ufs/ffs/ffs_softdep.c:1710
#22 0xc01fbac6 in ffs_truncate (vp=0xd036a800, length=0x0, flags=0x0, cred=0xc0ce9080,
p=0xd0c0)
at ../../ufs/ffs/ffs_inode.c:196
#23 0xc020bc12 in ufs_setattr (ap=0xd0476e44) at ../../ufs/ufs/ufs_vnops.c:498
#24 0xc020dedd in ufs_vnoperate (ap=0xd0476e44) at ../../ufs/ufs/ufs_vnops.c:2291
#25 0xc0199cb8 in open (p=0xd0c0, uap=0xd0476f80) at vnode_if.h:305
#26 0xc02479d1 in syscall2 (frame={tf_fs = 0x2f, tf_es = 0x2f, tf_ds = 0x2f, tf_edi =
0xbfbff9f0, tf_esi = 0xbfbff9d8,
tf_ebp = 0xbfbff964, tf_isp = 0xd0476fd4, tf_ebx = 0xbfbff9d8, tf_edx = 0x7,
tf_ecx = 0x7, tf_eax = 0x5,
tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0x804d788, tf_cs = 0x1f, tf_eflags =
0x246, tf_esp = 0xbfbff928,
tf_ss = 0x2f}) at ../../i386/i386/trap.c:1128
#27 0xc023bab5 in Xint0x80_syscall ()
#28 0x8048ec2 in ?? ()
#29 0x8048139 in ?? ()
At frame 10, the lock is held in multiple:
(kgdb) p bp->b_lock
$1 = {
lk_interlock = {
lock_data = 0x0
},
lk_flags = 0x440,
lk_sharecount = 0x0,
lk_waitcount = 0x0,
lk_exclusivecount = 0x2,
lk_prio = 0x14,
lk_wmesg = 0xc0265fe4 "bufwait",
lk_timo = 0x0,
lk_lockholder = 0x752f
}
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[EMAIL PROTECTED]`--'
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
On Tue, 25 Jul 2000, Jun Kuriyama wrote: > At 25 Jul 2000 07:37:43 GMT, > Ollivier Robert <[EMAIL PROTECTED]> wrote: > > I just got two panics tonight, the same each time. Current from yesterday, > > after the latest round of patch from Kirk. The second panic is exactly the > > same including the trace. > > It seems I've got same panics. But sometimes my box cannot panic and > rebooted suddenly. > > # My box rebooted 4 times today. :-( here too (about the panics and the spontanious boots). I don't know what the problem is.. I have recompiled the kernel again after some cvs updates, but it's still the same. So if its not the kernel it must be a userland tool, but I don't have enough time to build myself a new world, because everytime I start the process and I come back after a while, I find my machine rebooted. Right now I'm trying again while i stay present at the machine itself to see what it could be. btw, I have some big problems with the new version of mtree .. it seems that the -L flag has been abandoned.. which results in almost every port I try to install failing.. I have recompiled mtree from the tree and installed in manually (because at first my world failed as wel). Almost all 'make install's fail on mtree using -L option. Am I missing something about the mtree replacement that I should have to know ? -Steve -- Stephan van Beerschoten[EMAIL PROTECTED] PGP fingerprint: 4557 9761 B212 FB4C 778D 3529 C42A 2D27 "This email was brought to you by your local pop server" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
At 25 Jul 2000 07:37:43 GMT, Ollivier Robert <[EMAIL PROTECTED]> wrote: > I just got two panics tonight, the same each time. Current from yesterday, > after the latest round of patch from Kirk. The second panic is exactly the > same including the trace. It seems I've got same panics. But sometimes my box cannot panic and rebooted suddenly. # My box rebooted 4 times today. :-( -- Jun Kuriyama <[EMAIL PROTECTED]> // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
I just got two panics tonight, the same each time. Current from yesterday, after the latest round of patch from Kirk. The second panic is exactly the same including the trace. -=-=- (kgdb) exec-file /var/crash/kernel.7 (kgdb) core-file /var/crash/vmcore.7 IdlePTD 3661824 initial pcb at 2e5100 panicstr: lockmgr: pid 5, not exclusive lock holder 0 unlocking panic messages: --- panic: bqrelse: multiple refs syncing disks... panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking Uptime: 1h34m18s iconv_mod_handler #0 boot (howto=260) at ../../kern/kern_shutdown.c:303 #1 0xc016eb78 in poweroff_wait (junk=0xc02733a0, howto=5) at ../../kern/kern_shutdown.c:553 #2 0xc0169940 in lockmgr (lkp=0xc116bc00, flags=6, interlkp=0xccea97ac, p=0xcb92f780) at ../../kern/kern_lock.c:382 #3 0xc019cb2b in vop_stdunlock (ap=0xcb93d674) at ../../kern/vfs_default.c:255 #4 0xc0218e55 in ufs_vnoperate (ap=0xcb93d674) at ../../ufs/ufs/ufs_vnops.c:2291 #5 0xc0213db7 in ufs_inactive (ap=0xcb93d6a4) at vnode_if.h:865 #6 0xc0218e55 in ufs_vnoperate (ap=0xcb93d6a4) at ../../ufs/ufs/ufs_vnops.c:2291 #7 0xc019f8a6 in vput (vp=0xccea9740) at vnode_if.h:794 #8 0xc0211093 in ffs_sync (mp=0xc0e39200, waitfor=2, cred=0xc0a2b700, p=0xc0304940) at ../../ufs/ffs/ffs_vfsops.c:955 #9 0xc01a1785 in sync (p=0xc0304940, uap=0x0) at ../../kern/vfs_syscalls.c:551 #10 0xc016e5c7 in boot (howto=256) at ../../kern/kern_shutdown.c:225 #11 0xc016eb78 in poweroff_wait (junk=0xc027758b, howto=-972358720) at ../../kern/kern_shutdown.c:553 #12 0xc0197f2d in bqrelse (bp=0xc60afbc0) at ../../kern/vfs_bio.c:1195 #13 0xc01975a1 in vfs_backgroundwritedone (bp=0xc60dde20) at ../../kern/vfs_bio.c:696 #14 0xc0199a4d in bufdone (bp=0xc60dde20) at ../../kern/vfs_bio.c:2666 #15 0xc01999f6 in bufdonebio (bp=0xc60dde20) at ../../kern/vfs_bio.c:2617 #16 0xc012cc70 in dadone (periph=0xc0e00c00, done_ccb=0xc0e09c00) at ../../sys/bio.h:103 #17 0xc01271e7 in camisr (queue=0xc02e0bf0) at ../../cam/cam_xpt.c:6328 #18 0xc0126ff9 in swi_cambio () at ../../cam/cam_xpt.c:6231 #19 0xc0243370 in splz_swi () #20 0xc0197016 in bread (vp=0xcb929600, blkno=262208, size=12288, cred=0x0, bpp=0xcb93dbac) at ../../kern/vfs_bio.c:459 #21 0xc0205100 in ffs_blkfree (ip=0xcb93dc34, bno=90760, size=16384) at ../../ufs/ffs/ffs_alloc.c:1346 #22 0xc020c1e3 in indir_trunc (ip=0xcb93dc34, dbn=306752, level=0, lbn=12, countp=0xcb93dc24) at ../../ufs/ffs/ffs_softdep.c:2098 #23 0xc020bfb9 in handle_workitem_freeblocks (freeblks=0xc1059d80) at ../../ufs/ffs/ffs_softdep.c:2002 #24 0xc020ba40 in softdep_setup_freeblocks (ip=0xc10e4a00, length=0) at ../../ufs/ffs/ffs_softdep.c:1710 #25 0xc0206b56 in ffs_truncate (vp=0xccea92c0, length=0, flags=0, cred=0x0, p=0xcb92f780) at ../../ufs/ffs/ffs_inode.c:196 #26 0xc0213d0f in ufs_inactive (ap=0xcb93df00) at ../../ufs/ufs/ufs_inode.c:88 #27 0xc0218e55 in ufs_vnoperate (ap=0xcb93df00) at ../../ufs/ufs/ufs_vnops.c:2291 #28 0xc019f8a6 in vput (vp=0xccea92c0) at vnode_if.h:794 #29 0xc020cdd8 in handle_workitem_remove (dirrem=0xc0fc7aa0) at ../../ufs/ffs/ffs_softdep.c:2702 #30 0xc020a3e0 in softdep_process_worklist (matchmnt=0x0) at ../../ufs/ffs/ffs_softdep.c:556 #31 0xc019f134 in sched_sync () at ../../kern/vfs_subr.c:1017 #32 0xc0241edc in fork_trampoline () Cannot access memory at address 0x8000. -=-=- -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- [EMAIL PROTECTED] The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
