Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!newsfeed.internetmci.com!news-was.dfn.de!news-fra1.dfn.de!news-ber1.dfn.de!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Problem with 2.2.1 Install !!! Date: 16 Jun 1997 20:29:15 GMT Organization: Private BSD site, Dresden Lines: 39 Message-ID: <5o47mr$e49@uriah.heep.sax.de> References: <33A2659D.41C67EA6@silas.cc.monash.edu.au> <33A282BD.31DFF4F5@freebsd.org> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 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 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:42911 "Jordan K. Hubbard" <jkh@FreeBSD.org> wrote: > > Straight after the ed0 probe (which should probe the 3Com board) I > > Only one type of 3Com card (the 3c503) - the more generally encountered > 3Com products actually probe with the ep driver. Are you sure of this > one? Well, there are even more 3Com drivers :) (vx, eg, el), but he wrote about a 3C503, so the ed0 is correct. > > received the following rather large (and awe inspiring/scary) message. > > > > Fatal trap 12 : page fault while in kernel mode > > fault virtual address = 0xefc00000 > > fault code = supervisor read, page not present > > Hmmm. That's definitely weird - it sure would be nice to know exactly > which driver triggers this. Right after ed0, the probe should continue with ed1. The fault is inside function kvtop(), a very short function converting a KVA (kernel virtual address) into a physical address, or simpler call it a page map read. (It's actually in the inlined call to pmap_kextract().) This means the page tables on your machine are corrupted. Oh well, i don't say it's not the os's fault, but it's not unlikely a memory problem either. At any rate, it will require serious investigation before it's possible to spot this (since the time when the page table is corrupted and the spot where the crash happens might be very different). -- 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. ;-)