Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: amd64 current kernel crashes w/ rw_vector_enter: locking against myself

On Aug,Wednesday 19 2009, at 11:43 PM, Kurt Schreiner wrote:

On Wed, Aug 19, 2009 at 11:14:09PM +0200, David Laight wrote:
On Wed, Aug 19, 2009 at 10:52:02PM +0200, Kurt Schreiner wrote:

trying to boot a kernel compiled from -current sources cvs updated
Aug 19 20:57 MEST results in an early crash. Doesn't matter if I
try booting a GENERIC kernel (as shown below) or a customized one.
This is on a Sun Ultra24 w/ an Intel Q6600 and 8GB Ram...

I'd try building a kernel with 'tail-call' optimisation disabled.
It might give a better looking traceback.
Just added -fno-optimize-sibling-calls to COPTS. Crash is the same,
but trace looks slightly "better".


boot netbsd.gen_090819
booting hd0a:netbsd.gen_090819
10720224+543680+722240 [764040+501597]=0xda48e8
Reader / writer lock error: rw_vector_enter: locking against myself

lock address : 0xffffffff80d0d368
current cpu  :                  0
current lwp  : 0xffffffff80c9c940
owner/count  : 0xffffffff80c9c940 flags    : 0x0000000000000004

AFAIK there should be address of last holder in LOCKDEBUG print. x/i address will get you name
of a function which locked first.



Home | Main Index | Thread Index | Old Index