[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 Romero Pardines" <xtraeme%gmail.com@localhost>
To: "NetBSD GNATS" <gnats-bugs%netbsd.org@localhost>
Subject: Re: kern/38273 panic: LOCKDEBUG, "lockdebug_barrier: spin lock held",
Date: Wed, 17 Sep 2008 22:01:36 +0200
2008/9/17 Greg A. Woods <woods%planix.com@localhost>:
> At Wed, 17 Sep 2008 19:25:02 +0000 (UTC), Juan Romero Pardines wrote:
> Subject: Re: kern/38273 panic: LOCKDEBUG, "lockdebug_barrier: spin lock
> held", from ld_ataraid_start_raid0()
>> Do you have any local changes in ld.c? I'd like to know why the mutex
>> been acquired in ldstart().
> Indeed I do. I have the following changes, the meat of which were
> suggested on August 25 by Juergen Hannken-Illjes in response to this PR,
> but in private mail.
> As I recall they changed the behaviour from a panic to then just causing
> the newfs process to hang, so they sort of improved things, but not really.
> I'll try reverting them now and see what happens, but to my naive eyes
> they do look logical and proper.
That explained why my patch caused this panic. Try it without those changes
and let me know if you have any problem.
Main Index |
Thread Index |