> -----Original Message-----
> From: email@example.com
> [mailto:firstname.lastname@example.org]On Behalf Of Alan Cox
> Sent: Thursday, June 15, 2000 4:29 AM
> To: George Sexton
> Cc: Andrea Arcangeli; email@example.com
> Subject: Re: Stability (2.2.14/15/16/17pre1)
> > OOPs generated from the kernel. I hooked up a serial console and it just
> > catches nothing. Magic-Sysrq doesn't work. I tried using Ingo
> Molnar's NMI
> > Oopser and it didn't seem to generate an oops either.
> If even the NMI oopsing tools are not generating anything I'd start to be
> somewhat concerned. An NMI is not ignorable so cannot be blocked out..
Perhaps I did it wrong. I set the IRQ to 1 (Keyboard). The keyboard did not
work when this kernel was in place and it crashed after less than 1 hour. I
went to the machine and pounded on the keyboard, but no oops message. I
might re-try this by hooking IRQ 12 for the PS/2 mouse. At least I could use
the keyboard then....
> Do you do something specific in those time periods such as backups.
There does not seem to be a discernible pattern of times or activities.
> Does it work with "noapic" as a boot option
I have not tried this. On the next crash I will test it.
> Does it work single processor
One machine with a kernel compiled Uni-Processor would still exhibit the
lock-ups with the 2.2.14 series. I have never tried physically removing a
processor to see if the problem went away.
FWIW, I have a 3rd machine that has been running NT 4.0 with the same MOBO
that hasn't crashed in a year.
> What chipset
MH Software, Inc.
Voice: 303 438 9585
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jun 23 2000 - 21:00:10 EST