Andrew Morton wrote:
> 1: Include `magic sysrq' support in the kernel and use ALT-SYSRQ-T and S
> when it has locked up. If you get some traces then please feed them
> into `ksymoops -m System.map' and report back.
That was locked as well, AFAIK.
> 2: If the above doesn't work, add `nmi_watchdog=1' to the kernel boot
> options. That may catch the lockup.
>
> 3: Replace the NIC with another eepro100. If the problem goes away then
> chuck the old one.
>
> 4: Replace the NIC with one of a different type (ie: swap with the other
> machine). If that fixes it we look at the ethernet driver. Otherwise
> we look at, umm, the rest of the kernel.
I'd love to do some of this, but since the box is now being shipped to a
colo facility in New York, I don't really have a choice in the matter.
Hopefully someone here doing SMP + EEPro100 can see if they can reproduce
the issue (2.4.5 kernel).
--
www.kuro5hin.org -- technology and culture, from the trenches.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
