From owner-freebsd-bugs  Thu Sep 18 12:03:29 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id MAA28397
          for bugs-outgoing; Thu, 18 Sep 1997 12:03:29 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA28386
          for <freebsd-bugs@freebsd.org>; Thu, 18 Sep 1997 12:03:24 -0700 (PDT)
Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1])
	by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id VAA10970;
	Thu, 18 Sep 1997 21:02:19 +0200 (CEST)
To: joerg_wunsch@interface-business.de (Joerg Wunsch)
cc: freebsd-bugs@freebsd.org
Subject: Re: My 2.2-stable panic reproduced 
In-reply-to: Your message of "Thu, 18 Sep 1997 20:05:21 +0200."
             <19970918200521.RX41144@ida.interface-business.de> 
Date: Thu, 18 Sep 1997 21:02:19 +0200
Message-ID: <10968.874609339@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


>$5 = {i_chain = {0x0, 0x0}, i_vnode = 0x87654321, i_devvp = 0x0, 
>
>So what?  Replace the VREF by a VGET?  The i_vnode value of 0x87654321
>sounds terribly interesting.  See this bug report:
>
>Fatal trap 12: page fault while in kernel mode
>fault virtual address   = 0x87654371
>fault code              = supervisor read, page not present
>instruction pointer     = 0x8:0xf013476f
>stack pointer           = 0x10:0xefbffdb0
>
>Exactly the same bogus value.  So who the heck is dumping 0x87654321's
>all over my memory???

Yes, something is weird here.

It is a very weird value.. Could you do me the favour of 

	od -X /kernel | grep 8765

and see if it is present anywhere in you kernel ?  I don't see it
in mine, and if you don't have it either I pressume we're looking
at a device driver doing something weird...

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."