Xref: utzoo comp.sys.att:8753 unix-pc.general:4799
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!mailrus!usenet.ins.cwru.edu!cwjcc!neoucom!wtm
From: wtm@neoucom.UUCP (Bill Mayhew)
Newsgroups: comp.sys.att,unix-pc.general
Subject: Re: Fixdisk problems?
Summary: I got mine to crash
Message-ID: <1896@neoucom.UUCP>
Date: 10 Feb 90 15:12:31 GMT
References: <111@spirit.UUCP> <301@mtune.ATT.COM>
Distribution: na
Organization: Northeastern Ohio Universities College of Medicine
Lines: 49


After having read Frank's article, I thought I'd try
dd </dev/fp002 >/dev/null to see if I might be able to catch some
bad blocks on my disk (yes, I know, I could use the diagnostics
disk).  I ran the command in the background as root, and then
returned to ksh to do some other work such as reading mail.

A few minutes later, I got a page fault from the 3.51m kernel.  I
wasn't doing anything extraordinary that I haven't done many times
before, other than the dd command.

I have a very plain machine with 2 meg RAM, miniscribe 6085, and
the stock disk controller.  No 2010s or hardware modifications.  I
was in ksh, and the metermaid display was on.  Just before the
crash, metermaid look normal.  The %serial buffers was ~100%,
%clists ~90%, %ram pages ~ 50%, %CPU idle ~0%, %CPU user ~40%, %CPU
kernel ~60%, %CPU wait ~0%, printer selected and no errors.

This is what the panic message looked like.  The panic scribbled
over the metermaid and some of the other stuff on the screen, so it
was a bit tough to read.  Seems somewhat elusive because I tried to
duplicate the conditions again and have not been able to get the
crash.

type = 0x02, pid = 17144, pc = 0x6C09, rps = 0x2000, .... 0x4BB5C
GSR = 8D00, BSR0 = 7C07, BSR1 = 2400 PHYSPF = 0
D0 = ff, D1 = 6030, D2 = 301, D3 = 5
D4 = 52, D5 = 400, D6 C000, D7 = 400
A0 = 30300, A1 = 72400, A2 = 4BB5C, A3 = 70E08
A4 = 70884, A5 = 413B8, A6 = 70820, userA7=2FF138/kernA7=707C4
KI-RAM@6BC:000422D8 51C8FFFC 4E75227C 004000E0
KS-RAM@707C4:
 000101C6 000302FC 00072400 00000400 000270EC 00000000 00000034 08000007
 0B560000 13312002 00051052 000001F4 00400602 00000000 00000001 FFFB7C30


panic: page fault in kernel


I'm not sure what goes in the space where the .... is above.  The
display was too cluttered to make it out.  Also the last number on
the first line might be 0x4BB50 isntead of 0x4BB5C.

Anybody have any ideas?


Bill Mayhew  (wtm@neoucom.edu)
North Eastern Ohio Universites College of Medicine
Rootstown, OH  44272-9995       ph:  216-235-2511