Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 7 Jul 2002 02:03:01 -0700 (PDT)
From:      Don Lewis <dl-freebsd@catspoiler.org>
To:        jroberson@chesapeake.net
Cc:        current@FreeBSD.ORG
Subject:   Re: cvs commit: src/sys/tools vnode_if.awk
Message-ID:  <200207070904.g6793v0M022279@gw.catspoiler.org>
In-Reply-To: <20020707024045.J25604-100000@mail.chesapeake.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On  7 Jul, Jeff Roberson wrote:
> On Sat, 6 Jul 2002, Jeff Roberson wrote:

>>    - Use 'options DEBUG_VFS_LOCKS' instead of the DEBUG_ALL_VFS_LOCKS
>>      environment variable to enable the lock verifiction code.

> This was previously disabled because our locking was so bad that we could
> not boot with this option enabled.  I can now boot, compile a kernel, and
> reboot without catching any locking asserts.  This means that we are safe
> at our current level of debugging, but we are certainly not out of the
> woods wrt VFS locking yet.
> 
> If you have a crash test box I would appreciate it if you would enable
> this kernel option.  If it catches any errors you will be droped into the
> debugger where you can get a backtrace (type: tr) and mail it to me &&
> current@ to avoid dups.

It wasn't able to sucessfully boot with this enabled.  I'm hand
transcribing this, so apologies for any typos:

[fsck finishes]
Doing initial network setup: host.conf hostname.
VOP_READ: 0xc6737800 is not locked but should be
Debugger("Lock violation.
")


Debugger(c0420fe4) at Debugger+0x45
vn_rdwr(0,c6737800,c6425000,55ac,0,0,1,8,c22c7200,df241aec,c22cc0c0) at
vn_rdwr+0x18d
linker_hints_lookup(c04750a0,c,c62df000,5,0) at
linker_hints_lookup+0x2d9
linker_search_module(c62df000,5,0,0,c0415120) at
linker_search_module+0x43
linker_load_module(0,c62df000,0,0,df241cdc) at linker_load_module+0x72
kldload(c22cc0c0,df241d14,1,0,296) at kldload+0xc3
syscall(...)


If I disable the panic and continue the boot process, I see the
following in dmesg:


da0 at ahc0 bus 0 target 0 lun 0
da0: <SEAGATE ST336706LW 010A> Fixed Direct Access SCSI-3 device 
da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enable
d
da0: 35003MB (71687370 512 byte sectors: 255H 63S/T 4462C)
/usr/src/sys/vm/uma_core.c:1332: could sleep with "kernel linker" locked from /u
sr/src/sys/kern/kern_linker.c:1798
VOP_READ: 0xc6737800 is not locked but should be
VOP_GETVOBJECT: 0xc6737800 is not locked but should be
VOP_GETVOBJECT: 0xc6737800 is not locked but should be
VOP_BMAP: 0xc6737800 is not locked but should be
VOP_GETVOBJECT: 0xc6737800 is not locked but should be
VOP_GETVOBJECT: 0xc6737800 is not locked but should be
VOP_READ: 0xc6737800 is not locked but should be
VOP_READ: 0xc6737800 is not locked but should be
VOP_READ: 0xc6737800 is not locked but should be





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200207070904.g6793v0M022279>