The following reply was made to PR kernel/6638; it has been noted by GNATS.

From: Ted Unangst <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: kernel/6638: panic: dklk: lock not shared
Date: Mon, 20 Jun 2011 13:57:01 -0400

 On Mon, Jun 20, 2011 at 1:54 PM, Ted Unangst <[email protected]> wrote:
 > On Mon, Jun 20, 2011 at 12:14 PM,  <[email protected]> wrote:
 >
 >> panic: dklk: lock not shared
 >> Stopped at      Debugger+0x5:   leave
 >> RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS
 PANIC!
 >> IF RUNNING SMP, USE 'mach ddbcpu <#>' AND 'trace' ON OTHER PROCESSORS,
 TOO.
 >> DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
 >> ddb{0}> trace
 >> Debugger() at Debugger+0x5
 >> panic() at panic+0xe4
 >> rw_assert_rdlock() at rw_assert_rdlock+0x28
 >> rw_exit() at rw_exit+0x46
 >> vndioctl() at vndioctl+0x81e
 >
 > Looks like something trashed the sc.  That's supposed to be a write lock.
 
 Indeed.  disk_attach calls disk_construct which calls rw_init.

Reply via email to