On Wed, Apr 03, 2002 at 10:38:57AM -0500, David Z Maze wrote:
> David Z. Maze <[EMAIL PROTECTED]> writes:
> > (2) The machine spontaneously reboots in Linux after it's been up
> > for a minute or two. Booting into Windows and then rebooting
> > seems to help; booting the ACPI kernel seems to hurt.
>
> ...and it's doing it again this morning. Which is really irritating,
> since it makes the machine completely unusable. I've purged all
> vestiges of the ACPI-enabled 2.4.18 kernel, so all I'm using is an
> APM-enabled 2.4.17 kernel right now (still with sid). Booting to
> Windows isn't helping, either. Any hints? Any way to kick it into
> submission?
Maybe you could set panic= so that it doesn't reboot, but just stops.
Then, at least, you might be able to read what the panic message *is*...
Since kernels are interchangeable between distros, I'd try the "stock"
kernels of several types, and see if they all exhibit this behavior,
now that it's gotten ugly and reproducible.
If any of them do not, take a look at the .config offered by that distro's
kernel source package. Likely you need the options set in some special
way.
To give some best shots, I've had hardware with the following misbehaviors
where I could workaround it in the kernel:
An SMP motherboard not willing to talk to its second CPU for some reason.
"stock" SMP kernels of all varieties make the single CPU hang up too.
"stock" normal kernels not terribly stable.
workaround: disable APIC support on a uniprocessor kernel build.
Machine seems okay, first time the disk gets heavy use, system hangs:
could be DMA. The following items normally use DMA, but most
systems have very few DMA channels to go around, with symptoms
similar to IRQ conflicts:
parallel sound(sometimes wants two) hard disks
Some APM oddities:
workaround: "interrupts" options under the APM section set.
in this case it's really worth your while to use
make menuconfig
or make xconfig
so that you can read the help that goes with the various APM opts.
You may consider a 2.2.x kernel and see if it's any better or worse.
You may consider a 2.5.x kernel and see if this part is any better though
other things are bound to be worse. (save early, save often, save extras,
make backups a lot.)
Finally - you might try going for the pre19 patches... and if you find a
"good" kernel from 2.2.x but 2.4.x cannot be convinced, I'd definitely
prepare a complaint to the linux-kernel mailing list, so they can fix
whatever it is.
* Heather Stern * star@ many places...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
