*BSD News Article 91388


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!comp.vuw.ac.nz!news.hn.netlink.co.nz!southern.co.nz!cure.southern.co.nz!cure.southern.co.nz!calvin
From: calvin@cure.southern.co.nz (Calvin I Varney)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: panic: page fault
Date: 19 Mar 1997 07:04:03 GMT
Organization: The Cure
Lines: 34
Message-ID: <5go353$6j@cure.southern.co.nz>
NNTP-Posting-Host: cure.southern.co.nz
X-Newsreader: TIN [version 1.2 PL2]
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:37288

hi,

I recently upgraded my hardware from an old 486dx33 with an ultra 34f scsi 
system to a IBM 6x86-2V2P166GE (rev 3.7) on a FYI Intel 82430 (Intel VX based)
motherboard using an NCR 53C810 pci scsi host controller.

I rebuilt the kernel to account for the new hardware but every 1 or 2 days I 
receive the following system panic (virtual address, instruction pointer and
current process vary):

Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x74
fault code              = supervisor read, page not present
instruction pointer     = 0x8:0xf012d36d
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 311 (sendmail)
interrupt mask          =
panic: page fault


I'm still using FreeBSD 2.1R which has been extremely stable on the 486 for 
over a year.

Before I hit the books to to figure out how to debug a kernel (lots of learning
to do here) is any one able to speculate as to what may be causing such page 
faults. Is it likely to be caused by hardware or are there known problems 
with 2.1 using such hardware?

thanks for any assistance,

Calvin.