From owner-freebsd-current Thu Jan 18 10:42: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id AD97337B699 for ; Thu, 18 Jan 2001 10:41:41 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp150.geekhouse.net [192.168.1.150]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f0IIjYs68443; Thu, 18 Jan 2001 10:45:35 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <5.0.2.1.0.20010118152851.00a52ec0@tfrsolcom> Date: Thu, 18 Jan 2001 10:41:28 -0800 (PST) From: John Baldwin To: Rogier Mulhuijzen Subject: RE: Panic w/crash dump (looks like atomic.h problem) Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Jan-01 Rogier Mulhuijzen wrote: > Got a nice crash while running XMMS under X11 and running a 'make world -j > 128 -DNOCLEAN' on ttyv0 > > Current was cvsupped on the 17th in the morning (Central European Time) IIRC. > > Attached: script(1) output of gdb kernel trace > Kernel config file > dmesg(8) output > > I'm not an expert on tracing panics, I just followed the instructions in > the FAQ, so feel free to ask me to look at stuff. > > DocWilco If you look at the traceback, vref() was called with a NULL vnode as its parameter, so the panic is due to dereferencing a NULL pointer, not a bug in the atomic ops. :) As to why the kernel was vref()'ing a NULL pointer, I have no idea. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message