From: laakkone@klaava.Helsinki.FI (Tero Laakkonen) Subject: 0.99.8 kernel panic ... Date: Wed, 21 Apr 1993 12:54:10 GMT
hi, i built 0.99.8 about a week ago using my old 2.2.2 libraries and
it's been working perfectly.
the other day i accidentally deleted my 2.2.2 libs and so i had to build
0.99.8 again with 4.3.3 dlls without tcp/ip. that too worked perfectly.
today i built 0.99.8 with 4.3.3 dlls and tcp/ip (under 0.99.8 with 4.3.3
dlls without tcp/ip), coz i wanted my newly installed X (which was a
bitch to install, i installed X last summer and it wasn't nearly as
messed up) to work more nicely.
i did this just before lunch time and booted my new (0.99.8 with 4.3.3
dlls and tcp/ip) kernel. when
i came back to my machine after lunch, the screen was full of general
protection faults and messages from the swapper about not being able to
free something.
when i tried to do some fsck's, it said uhhoh, got a DMI ...
i tried to do a couple of boots, even with my non-tcp kernel, it still
got DMI's/general protection errors ... even got a SYSTEM HALTED ...
my DOS-side seems to be working ok, implying to me that what i have is
probably not a hardware fault.
what i need right now is a quick answer: will #'ing 'swapon' out of my
/etc/rc make my system usable again? if so i could use my hj-bootroot
disk to get into my /etc/rc to edit out the wicked line.
on the long run, do i need to mkswap my swap partition again? i
mkswapped it the first time in july last year, perhaps the swap
partition format has changed? or perhaps i should just buy a new
motherboard which is guaranteed not to have any hardware bugs, so i know
if something messes up it's not the hardware ...
i'm all at sea. this is the first time this kind of thing has happened
to me with linux. tell me it's an easy-to-fix hardware bug.
-tero