[ale] final plea for help (more kernel panic info)

[Greg]

For the hardware it is easy -
	Check all connections and replace cables if you suspect them (I have had
them go bad)
	Test hardware in another PC and vice versa. Test only one component at a
time.
	Can you put Windows 98 on it ? (windows is sometimes more forgiving)
	Can you put OpenBSD on it (I try it like windows - sometimes it tells me
what is bad during the install)
	Have you googled for problems ?
	If you are using a RAID through BIOS controller then you are destined for
problems.  I have both normal and RAID controllers on my board.  Linux does
not support the RAID yet.
	Have you tested your memory ?  It seems that it might be bad.  I am
assuming that you are using ddr memory ? (doesn't your board take that type
? I thought that I read it somewhere.)

For the software
	Could your install medium be bad ?
	I am just assuming that there is no possibility of virii
	Have you tried removing every single thing and trying it ?  I think that I
also noticed that your board has 2 eeprom bios chips (for backup - though I
have never had a BIOS go bad)

	Good Luck,
	Greg Canter


> -----Original Message-----
> From: ale-admin at ale.org [mailto:ale-admin at ale.org]On Behalf Of J.M.
> Taylor
> Sent: Saturday, January 04, 2003 3:59 AM
> To: ale at ale.org
> Subject: [ale] final plea for help (more kernel panic info)
>
>
> It's not just fsck, it's pretty much anything I try to do. I can run at
> the console for awhile (10 - 30 minutes) but if I try to do much of
> anything, it gives me a cannot handle null pointer, a kernel oops, and a
> long list of things that don't make much sense to me.
>
> I don't think it's a hard drive or IDE controller thing, my gut feeling is
> that it's memory or CPU.  I say this b/c I can do normal disk IO and
> everything is OK (and fsck, when I can get it to run, says my hdds are
> fine. they've been fine for two years, i would be very startled if they
> both suddenly went bad). But if I try to do anything that utilises system
> resources: cp -r, mv, untar a large archive, I get kernel panics. The "EIP
> is at so-and-so" messages have varied widely throughout the night, I would
> think if it was an IDE controller it would complain about that every
> single time.
>
> I'm trying to update my kernel, but I can't build a new one (can't untar
> the archive, or copy an untarr'd archive from much of anywhere) and I
> can't even update with an RPM (kernel panic).
>
> How, at this point, can I diagnose whether it's hardware or software? Any
> help, feedback, or assistance in understanding what I'm looking at when
> the kernel panics and spits out two screens of long numbers will be
> welcomed gratefully.
>
> thanks
> jenn,
> tired and dejected
>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
>
>

_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale