[lkml]   [2000]   [Nov]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: PROBLEM: crashing kernels

> > In the afternoon we decided to put back the original mainboard+ram+cpu.
> > We booted the kernel described above.
> With `noapic', I assume?
Yes, of course

> It could be hardware or a driver or whatever. Suggest you
> go to a more recent kernel and if the problems persist,
> swap hardware out. Power supply, memory, CPUs, etc.
> We don't know. It doesn't correlate with any particular chipset.
> Could be a hardware bug, a Linux bug or a chip errata which we don't
> know about.

Another crash, and error message in this topic:
Kernel Panic: skput:over: a00f8d9b: 1526 put: 66 dev: eth1
In interrupt handler - not syncing

Because we have the SysRQ compiled, we tried the SysRQ + ALT + u
combination, to umount the partitions at least. After a big dump of hexa
numbers we got this:
Aiee, killing interrupt handler
Unable to handle kernel NULL pointer dereference

The eth1 is a dlink card, we use a driver from the cards developer. We use
this type of card with another computer since months ago, with the same
(2.2.14) kernel, and we didn't experience any problems yet. Of course I've
compiled the modul on the same computer where it's been run, and where
also the kernel has ben compiled and run.

The two cards in the two computers also have the same load (because they
are connected with a crosslink cable ;)

So I suppose it's not the fault of the network driver this time. I still
believe is somewhere around the apic.

I hope I could give You some more informations

| Nagy Attila |
| |

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:47    [W:0.020 / U:1.676 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site