Date: Sun, 26 May 1996 19:33:59 +0200 (MET DST) From: grog@lemis.de (Greg Lehey) To: bubba@mymachine.com (Just call me Bubba) Cc: freebsd-questions@freebsd.org Subject: Re: I had a Kernel panic and was wondering if anyone could figure out y Message-ID: <199605261733.TAA00408@allegro.lemis.de> In-Reply-To: <Pine.LNX.3.91.960524235231.27861A-100000@server1.netpath.net> from "Just call me Bubba" at May 24, 96 11:59:36 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Just call me Bubba writes:
>
> I am not shure what could cause this, but heres what it said.
>
> fatal trap 12 page fault while in kernel mode
> fault virtual address 0x0
> fault code =supervisor read, page not present
> instruction pointer 0x8:0xf01a5b26
> stack pointer 0x10:0xefbffe34
> frame pointer 0x10:0xefbffe80
> code segment base 0x0, limit 0xfffff, type 0x1b
> DPL 0, pres 1, def 32 1, gran 1
> processor flags interrupt enabled, resume IOPL=0
> current process 321 (pkg_add)
> interrupt mask ufs
> panic page fault
I'm afraid that the system's not sure either. Most panic messages the
result of some test made by the kernel. It checks something and finds
it incorrect. In such cases, it prints out a more or less
intelligible message about what has gone wrong. In this case, the
kernel has surprised itself. This panic message basically says
"something has gone seriously wrong. The kernel has attempted to
access non-existent memory".
The only real way to analyze this problem is to look at a panic dump.
Unfortunately, you probably don't have one. Look at pages 80 and 81
of "Installing and Running FreeBSD" for the full details, but here's
an overview:
1. Uncomment the line in /etc/sysconfig saying
dumpdev /dev/wd0s1b
If you have SCSI disks, it'll be /dev/sd0s1b. This is your swap
partition, and that's where the kernel writes its dump after a
panic.
2. Create the directory /var/crash. This is where the system startup
routines write the dump after the system has restarted.
You can find details of how to analyze a dump in the on-line
handbook. In this particular case, it probably won't help much, but
if you post a stack trace, it might give somebody an idea.
Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605261733.TAA00408>