[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/38273 panic: LOCKDEBUG, "lockdebug_barrier: spin lock held", from ld_ataraid_start_raid0()
The following reply was made to PR kern/38273; it has been noted by GNATS.
From: Juan RP <xtraeme%gmail.com@localhost>
To: NetBSD GNATS <gnats-bugs%NetBSD.org@localhost>
Subject: Re: kern/38273 panic: LOCKDEBUG,
"lockdebug_barrier: spin lock held", from ld_ataraid_start_raid0()
Date: Thu, 18 Sep 2008 22:07:13 +0200
On Thu, 18 Sep 2008 15:51:39 -0400
"Greg A. Woods" <woods%planix.com@localhost> wrote:
> Done, with no apparent change in behaviour.... Again this was some ways
> into the "newfs /dev/rld0a"
I'm out of ideas then. No idea how we will fix this if we are calling
buf_init() with the ld's spin lock held!
Or ldstart() is wrong and it should not acquire the spin lock there
(AFAIK is the correct way) or the only option is to release/reacquire
the spin lock as I had done in the patch.
Also as the spin lock is held, acquiring the adaptive mutex from v_interlock
will also cause another "spin lock held" panic later on (which I addressed
with the softint(9)).
Main Index |
Thread Index |