Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.hawaii.edu!ames!usenet.kornet.nm.kr!usenet.hana.nm.kr!usenet.seri.re.kr!news.imnet.ad.jp!lab!wsclark!gemini!k-sato
From: k-sato@res.otaru-uc.ac.jp (Kou Sato)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: fatal trap 12
Date: 19 Jan 1996 05:59:50 GMT
Organization: Otaru University of Commerce, Otaru 047, Japan
Lines: 84
Message-ID: <4dnc0m$5hl@gemini.res.otaru-uc.ac.jp>
References: <4dja87$gvr@nntp5.u.washington.edu>
NNTP-Posting-Host: canal.res.otaru-uc.ac.jp
X-Newsreader: mnews [version 1.18PL3] 1994-08/01(Mon)
caleb@crl.com (S. Paul) writes:
> fatal trap 12:page fault while in kernel mode
> fault vertual address =0x0
> fault code =supervisor read,page not present
> instruction pointer =0x8:0xf0105413
> code segment =base 0x0, limit 0xfffff, type 0x1b
> =DPL 0,pres1, def32 1,gran 1
> processor cflags =interupt enabled, resumed, IOPL=0
> currect process =5(init)
> interrupt mask =
> panic page fault
>
> could someone please tell me what each of the above lines mean or where to
> look for the infomation and discription of the above messages
I also had a similar problem. It was a general protection fault
(trap 9) and its profile is:
instruction pointer =0x8:0xf01976ca (almost always this value)
code segment =base 0x0, limit 0xfffff, type 0x1b
=DPL 0,pres1, def32 1,gran 1
processor eflags =interupt enabled, resumed, IOPL=0
currect process = sh, ls, ...
interrupt mask = net, bio, tty. (as I remember correctly...)
It always happend just after "fsck -p" while it was booting,
and after I removed the cdrom drive, it stopped just after "fsck -p"
as before, but allowed me to run the shell (although "/" was mounted
in read-only mode). But running "fsck -p" or "ls" had caused the
same problems (the value of the instr. ptr. was the same). It was
curious that "ls" had not always caused the problem, but running
"ls" several times always coused the problem. (Running "fsck" had
always caused the problem although.)
The version of the system is 2.0.5-950622-SNAP, it had been working
well on my machine (with i486DX2, ISA, 16MB RAM, 128K cache, aha1542cf
and conner's 1030MB HDD) until a week ago, although a little bit unstable
while it was booting (suddenly repeated rebooting). Linux 0.99 had run
without any problems on the same machine with an IDE drive, but since
I appended a SCSI drive and installed Linux 1.3, it some times repeated
to reboot while it was booting, but I thought it was OK because it worked
pretty fine once it booted after retrying booting a couple of times.
However I found that I prefer BSD (FreeBSD have been running without
any problems for almost an years on the machine at my office which has
same cpu, same SCSI HDD that my machine has, but has aha1522), so
I replaced Linux with BSD 2 months ago and it had worked well as I wrote.
So I thought there must be problems in the hardwares and ran diagnostic
programs. They said there are no problems in the memories, cashe, CPU,
FPU, IRQcontrolers, HDD, etc. I formatted (low level) the HDD, and
installed the BSD again, but got the same problem. Maybe the diagnostic
programs run in virtural 86 mode and do not test MMU, but I am not sure
that is the problem.
Could someone tell me what is the problem? CPU? HDD? SCSI interface?
or else? Or will you tell me how to find which instruction is at
0x8:0xf01976ca in (virtual?) memory space while I could not boot my
system? Any suggestions would be appreciated. Thank you.
-
Koh Sato
k-sato@res.canal.otaru-uc.ac.jp
Otaru University of Commerce