From owner-freebsd-current Tue Jul 16 5:53:15 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 5B64B37B400; Tue, 16 Jul 2002 05:53:11 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 847A943E4A; Tue, 16 Jul 2002 05:53:10 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id IAA09769; Tue, 16 Jul 2002 08:53:09 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g6GCqdB51617; Tue, 16 Jul 2002 08:52:39 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15668.5911.639776.253419@grasshopper.cs.duke.edu> Date: Tue, 16 Jul 2002 08:52:39 -0400 (EDT) To: Dag-Erling Smorgrav Cc: alpha@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: VOP_GETATTR panic on Alpha In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid 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 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 > 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