On Sun, 02 May 1999, Gevaerts Frank wrote:
>
> Anyway, next time you get an Oops, write everything down and read
> /usr/src/linux/Documentation/oops-tracing.txt. Once you have followed its
> instructions you have something the kernel developpers can analyse, in
> case you have a real kernel bug.
>
> Frank
>
Um, he can't boot. How would he read /usr/src/Documentation/oops-tracing.txt?
=) The best bet would be to start checking all of the hardware. You wouldn't
have the same problem with so many kernel versions if it were a kernel bug,
because of the difference in the abilities to be triggered and so on.
THe only probable cause I can think of is that there is some truely buggy
hardware.
----------------------------------------------------------------
Michael B. Trausch
President of Linux Operations, ADK Computers
----------------------------------------------------------------
ADK Computers, Walbridge Office Phone: 419.838.8104
5375 Keller Road Main Office: 419.882.7435
Walbridge, OH 43465 E-Mail: [EMAIL PROTECTED]
----------------------------------------------------------------
Sunday, May 02, 1999
Don't break my heart, my achy-breakyeaargh!uyIo~NO CARRIER
