Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 16 Jul 2002 08:52:39 -0400 (EDT)
From:      Andrew Gallatin <gallatin@cs.duke.edu>
To:        Dag-Erling Smorgrav <des@ofug.org>
Cc:        alpha@FreeBSD.ORG, current@FreeBSD.ORG
Subject:   Re: VOP_GETATTR panic on Alpha
Message-ID:  <15668.5911.639776.253419@grasshopper.cs.duke.edu>
In-Reply-To: <xzpele33kq0.fsf@flood.ping.uio.no>
References:  <xzpele33kq0.fsf@flood.ping.uio.no>

next in thread | previous in thread | raw e-mail | index | archive | help

Dag-Erling Smorgrav writes:
 > The following panic is 100% reproducable - it happens whenever I boot
 > a recent kernel on Alpha, just before init(8) starts getty(8) on the
 > console:
 > 
 > VOP_GETATTR: 0xfffffe00019e7220 is not locked but should be
 > Lock violation.
 > 
 > Stopped at      Debugger+0x34:  zapnot  v0,#0xf,v0      <v0=0x0>
 > db> trace
 > Debugger() at Debugger+0x34
 > vn_stat() at vn_stat+0xd8
 > vn_statfile() at vn_statfile+0x58
 > fstat() at fstat+0x80
 > syscall() at syscall+0x364
 > XentSys() at XentSys+0x64
 > --- syscall (189, FreeBSD ELF, fstat) ---
 > --- user mode ---
 > 
 > Dumps don't seem to work, so I can't get much more than this.
 > 

Welcome to hell.   

If you clear panicstr, you have a chance of getting a dump.

Drew

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?15668.5911.639776.253419>