Date: Sun, 20 Aug 1995 15:43:03 +0800 (CST) From: Brian Tao <taob@gate.sinica.edu.tw> To: FREEBSD-HACKERS-L <freebsd-hackers@freebsd.org> Subject: Page fault caused by... Pine? Message-ID: <Pine.BSI.3.91.950820153634.17751y-100000@aries>
next in thread | raw e-mail | index | archive | help
I had a strange kernel panic today... the boss was just reading
her mail in Pine 3.91 in an xterm when the machine simply locked up
and rebooted itself. Pine has worked flawlessly on all other machines
and on her particular one up until the panic, so I'm lead to believe
it was caused by a hardware problem.
The case on that computer was opened up today to install a new DX4
chip, but the motherboard can't take one, so no changes were made. It
is still running its original DX2/66 CPU. I didn't see any obvious
signs of damage or loose bits on the motherboard, but I swapped her
machine for one of our other DX4/100's in the meantime. The DX2/66
hasn't behaved strangely since then. Any ideas? Or should I chalk
this one up to a stray cosmic ray?
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x38
fault code = supervisor read, page not present
instruction pointer = 0x8:0xf012aad1
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 = 207 (pine)
interrupt mask =
panic: page fault
syncing disks... 3 3 done
Automatic reboot in 15 seconds - press a key on the console to abort
Rebooting...
--
Brian ("Though this be madness, yet there is method in't") Tao
taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.91.950820153634.17751y-100000>