Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!cs.utexas.edu!news.sprintlink.net!dispatch.news.demon.net!demon!tank.news.pipex.net!pipex!oleane!jussieu.fr!univ-lyon1.fr!swidir.switch.ch!scsing.switch.ch!news.belwue.de!News.Uni-Marburg.DE!news.th-darmstadt.de!fauern!lrz-muenchen.de!news.informatik.uni-muenchen.de!news.muc.de!news.space.net!roka.net!news.bocad.com!kruener From: kruener@bocad12.bocad.com (Heiner) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: 950726 Page Fault in Kernel Date: 30 Aug 1995 16:17:51 GMT Organization: BOCAD Software GmbH Lines: 40 Message-ID: <4222vf$l1c@bocad.com> References: <SAKAI.95Aug22002915@csle59.csl.cl.nec.co.jp> <41rs0h$poa@bonnie.tcd-dresden.de> NNTP-Posting-Host: bocad.com X-Newsreader: TIN [version 1.2 PL2] On 28 Aug 1995 09:42:09 +0200 J Wunsch (j@bonnie.heep.sax.de) wrote: : Junji SAKAI <sakai@csle59.csl.cl.nec.co.jp> wrote: : > Fatal trap 12: page fault while in kernel mode : > fault virtual address = 0xf53cb708 (*) : > fault code = supervisor read, page not present : > instruction pointer = 0x8:0xf0121378 (*) : > 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 = 1189 (cc1) (*) : > interrupt mask = bio (*) : > panic: page fault : > syncing disks... 22 22 22 22 ...... give up : Normally, i'd say extract the name list and look for the symbols : around the faulting instruction pointer, but... : >Items with asterisk(*) vary case by case, but others are the same : >in all case. This panic happens almost every time I compile something. : >I don't know why these page fault traps occur. : ...this rather smells like a hardware problem. Try relaxing the : conditions for your RAM/cache (or EDO) RAM etc., or try to make the : cache write-through. There are ASUS boards known to have a broken : chipset, but i've forgot which one. : I assume every memory-expensive program would cause this, the compiler : is only just the best known expample. Try troffing a large .ms file, : i guess you'll experience the same. I'm afraid I got the same error, once in nfsd, in rm and in Idle. All during heavy nfs traffic to and from the machine. Copying to that machine over nfs either using cp over nfs or rcp for hours did not reveal this error, but after copying from that machine crashed after ~5 hours. The fault was always in malloc (from kern_malloc). Every time it kernel-panic'd and tried to reboot. Machine: 486/40 VLB w 32M running the same test under Linux 1.2.13 for two days until I stopped the machine. Heiner