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 Message-ID: <19970623212115.CY37600@uriah.heep.sax.de> In-Reply-To: <199706231004.NAA15233@shadows.aeon.net>; from mika ruohotie on Jun 23, 1997 13:04:48 %2B0300 References: <19970605223427.LN28350@uriah.heep.sax.de> <199706231004.NAA15233@shadows.aeon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970623212115.CY37600>