Messages in this thread | | | Date | Sun, 26 Nov 2000 10:49:50 +1100 | From | Andrew Morton <> | Subject | Re: PROBLEM: crashing kernels |
| |
Nice report. Wish they were all like that.
Look:
"Mr. Big" wrote: > > I thought that the khttpd is guilty, I won't use it anymore. Next morning > it crashed again, now without khttpd, without high load, without high > memory usage, just the 3Com driver said: > kernel: eth0: Interrupt posted but not delivered -- IRQ blocked by another device? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is caused by the APIC(s) forgetting how to deliver interrupts for a particular IRQ. Normally, reloading the driver doesn't help. But in your case it did. This is odd.
It looks like the same thing is happening with the eepro NIC as well. But the eepro diagnostics aren't as informative when this happens.
This can normally be prevented by booting with the `noapic' option on the LILO command line.
So I suggest you stick with the 3c905C and boot with `noapic'. Try the eepro as well - it may well work fine with the APIC disabled.
You may also get some benefit from running:
# echo "512 1024 1536" > /proc/sys/vm/freepages
after booting. The default values are a little too low for applications which are very network intensive. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
| |