From owner-freebsd-current Tue Jul 16 5:45:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CD0337B401; Tue, 16 Jul 2002 05:45:17 -0700 (PDT) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED2C443E58; Tue, 16 Jul 2002 05:45:15 -0700 (PDT) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id BB07B534A; Tue, 16 Jul 2002 14:45:12 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: alpha@freebsd.org, current@freebsd.org Subject: VOP_GETATTR panic on Alpha From: Dag-Erling Smorgrav Date: 16 Jul 2002 14:45:11 +0200 Message-ID: Lines: 23 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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 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. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message