t; 2.6.14 crash
> 2.6.12.6 crash "NMI watchdog detected LOCKUP"
> 2.6.6crash "NMI watchdog detected LOCKUP on CPU1 eip c02500aa, registers:"
> 2.6.1would not boot
It is definately a 3com 3c905b problem: I swapped that card yesterday
with an adapter from a
didn't mention whether that card work OK under earlier 2.6
> kernels. If it does, a bit of bisection searching would really help.
2.6.15 crash
2.6.14.4 crash
2.6.14 crash
2.6.12.6 crash "NMI watchdog detected L
romiscues mode".
> > Did you confirm that the NMI counters in /proc/interrupts are incrementing?
> Yes:
> [EMAIL PROTECTED]:/home/folkert# for i in `seq 1 5` ; do cat /proc/interrupts
> | grep NMI ; sleep 1 ; done
> NMI:69490806949067
> NMI: 69491826949169
NMI counters in /proc/interrupts are incrementing?
Yes:
[EMAIL PROTECTED]:/home/folkert# for i in `seq 1 5` ; do cat /proc/interrupts
| grep NMI ; sleep 1 ; done
NMI:69490806949067
NMI:69491826949169
NMI:69492846949271
NMI:69493866949373
NMI:6949488694947
lilo config.
> Am now compiling the kernel.
No change. Well, that is: the last message on the console now is
"setting eth1 to promiscues mode".
Folkert van Heusden
--
Try MultiTail! Multiple windows with logfiles, filtered with regular
expressions, color
ne, make sure that the NMI line
> of /proc/interrupts is incrementing.
I'll give it a try. I've added it to the append-line in the lilo config.
Am now compiling the kernel.
Folkert van Heusden
--
Try MultiTail! Multiple windows with logfiles, filtered with regular
expressions,
92265 73603 IO-APIC-level Intel ICH5
NMI: 0 0
LOC: 75664 75663
ERR: 0
MIS: 10
Folkert van Heusden
--
Try MultiTail! Multiple windows with logfiles, filtered with regular
expre
> okay, thanks for the report, adding netdev
> On 10/29/05, Folkert van Heusden <[EMAIL PROTECTED]> wrote:
> > Reproducable i get a kernel panic when inserting the e1000 module on my
> > system. Kernel 2.6.13.3.
> > It is P4 with hyperthreading enabled. 1GB ram.
>
