From owner-freebsd-current Mon Jul 16 14:39:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 1C46237B406; Mon, 16 Jul 2001 14:39:21 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (mjacob@beppo [192.67.166.79]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6GLdHS20127; Mon, 16 Jul 2001 14:39:17 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Mon, 16 Jul 2001 14:39:17 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Wilko Bulte Cc: John Baldwin , Alexander Langer , current@FreeBSD.ORG Subject: Re: netstat kernel panic In-Reply-To: <20010716233655.A2457@freebie.xs4all.nl> Message-ID: 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 On Mon, 16 Jul 2001, Wilko Bulte wrote: > On Mon, Jul 16, 2001 at 02:30:47PM -0700, Matthew Jacob wrote: > > > I've seen this panic many times on my alpha SMP testbox. It seems that the vm > > > object returned by vm_map_lookup via the fs.first_object variable is actually > > > NULL, resulting in a NULL pointer deref when calling vm_object_pip_add() (note > > > object=0x0). I haven't seen this on UP or x86 before, but it seems the bug > > > wasn't alpha specific now. :( > > > > > > > No.... "Yay!" > > "Thou shall not enjoy the misery of thou fellow committers" > > But it sure helps if things are broken on x86 as well as on alpha.. > > :-) :-) > It just means it might get fixed quicker! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message