Re: kern/38273 panic: LOCKDEBUG, "lockdebug_barrier: spin lock held", from ld_ataraid_start_raid0()

["Juan Romero Pardines" <xtraeme%gmail.com@localhost>]

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>
Cc: 
Subject: Re: kern/38273 panic: LOCKDEBUG, "lockdebug_barrier: spin lock held", 
from ld_ataraid_start_raid0()
Date: Wed, 17 Sep 2008 21:22:38 +0200

 2008/9/17 Greg A. Woods; Planix, Inc. <woods%planix.ca@localhost>:
 >
 > On 17-Sep-08, at 2:40 PM, Greg A. Woods wrote:
 >>
 >> Well now at least it immediately dumps during boot:
 >>
 >> ataraid0: found 1 RAID volume
 >> ld0 at ataraid0 vendtype 1 unit 0: Adaptec ATA RAID-1 array
 >> ld0: ld_ataraid_attach(): ld unit 0 (ld->sc_dv =3D 0xd187064c)
 >> ld0: ldattach(): unit 0
 >> ld0: 186 GB, 24321 cyl, 255 head, 63 sec, 512 bytes/sect x 390721536
 >> sectors
 >> rnd: ld0 attached as an entropy source (collecting)
 >> Mutex error: mutex_vector_exit: exiting unheld spin mutex
 >>
 >> lock address : 0x00000000d18706ac type     :               spin
 >> initialized  : 0x00000000c01f46f9
 >> shared holds :                  0 exclusive:                  0
 >> shares wanted:                  0 exclusive:                  0
 >> current cpu  :                  1 last held:                  1
 >> current lwp  : 0x00000000c0b349e0 last held: 000000000000000000
 >> last locked  : 0x00000000c01f411b unlocked : 0x00000000c01f4160
 >> owner field  : 0x0000000000000600 wait/spin:                0/1
 >>
 >> panic: LOCKDEBUG
 >
 >
 > FYI, "current lwp" there appears to be the swapper thread, according to "ps
 > /l"
 
 Do you have any local changes in ld.c? I'd like to know why the mutex hasn't
 been acquired in ldstart().