From owner-freebsd-current Mon Jul 16 13:21:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id CC11037B405; Mon, 16 Jul 2001 13:21:51 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from zerogravity.kawo2.rwth-aachen.de (zerogravity.kawo2.rwth-aachen.de [134.130.181.28]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id WAA02489; Mon, 16 Jul 2001 22:21:51 +0200 Received: by zerogravity.kawo2.rwth-aachen.de (Postfix, from userid 1001) id 871BA14DAB; Mon, 16 Jul 2001 22:21:48 +0200 (CEST) Date: Mon, 16 Jul 2001 22:21:48 +0200 From: Alexander Langer To: John Baldwin Cc: current@FreeBSD.org Subject: Re: netstat kernel panic Message-ID: <20010716222148.A8002@zerogravity.kawo2.rwth-aachen.d> Mail-Followup-To: Alexander Langer , John Baldwin , current@FreeBSD.org References: <20010715120317.A99869@fump.kawo2.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Mon, Jul 16, 2001 at 01:03:34PM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. 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 Thus spake John Baldwin (jhb@FreeBSD.org): > > tf_eip = -1070822146, tf_cs = 8, tf_eflags = 66118, > > tf_esp = -1069680480, tf_ss = 1}) at /usr/src/sys/i386/i386/trap.c:405 > >#11 0xc02c8cfe in vm_object_pip_add (object=0x0, i=1) > > 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. :( I had it on two different machines (both _UP_ x86). (just to verify). Thanks Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message