From owner-freebsd-current  Mon Jun 23 12:23:02 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id MAA23881
          for current-outgoing; Mon, 23 Jun 1997 12:23:02 -0700 (PDT)
Received: from sax.sax.de (sax.sax.de [193.175.26.33])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA23862
          for <current@FreeBSD.ORG>; Mon, 23 Jun 1997 12:22:49 -0700 (PDT)
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA10231; Mon, 23 Jun 1997 21:22:36 +0200
Received: (from j@localhost)
	by uriah.heep.sax.de (8.8.5/8.8.5) id VAA28200;
	Mon, 23 Jun 1997 21:21:16 +0200 (MET DST)
Message-ID: <19970623212115.CY37600@uriah.heep.sax.de>
Date: Mon, 23 Jun 1997 21:21:15 +0200
From: j@uriah.heep.sax.de (J Wunsch)
To: current@FreeBSD.ORG
Cc: bsdcur@shadows.aeon.net (mika ruohotie)
Subject: Re: page fault
References: <19970605223427.LN28350@uriah.heep.sax.de> <199706231004.NAA15233@shadows.aeon.net>
X-Mailer: Mutt 0.60_p2-3,5,8-9
Mime-Version: 1.0
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199706231004.NAA15233@shadows.aeon.net>; from mika ruohotie on Jun 23, 1997 13:04:48 +0300
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

As mika ruohotie wrote:

> #6  0x1d45d8f5 in ?? ()
> Cannot access memory at address 0x21bd40f4.
> (kgdb) frame 5
> #5  0xf0103f71 in cd9660_getattr (ap=0x210620f0)
>     at ../../isofs/cd9660/cd9660_vnops.c:286
> 286             vap->va_type    = vp->v_type;
> 
> 
> this is again as much as it was listing, nothing more.
> 
> and it's NOT the first time i see that particular memory address in
> a crashing message. (0x21bd40f4)
> 
> it's hardware, right?

No, probably not.  But from the above trace, it's not guessable what
has been the reason why your memory is trashed (nor is it intelligible
for why the cd9660 code has been called at all).

Anyway, if you're seeing it with the same failing address, it's not
likely hardware.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)