> > > > > > > Have you tried enabling the NMI watchdog? Enable CONFIG_X86_LOCAL_APIC and
> > > > > > > boot with `nmi_watchdog=1' on the command line, 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.
> > > > > No change. Well, that is: the last message on the console now is
> > > > > "setting eth1 to promiscues mode".
> > > > Did you confirm that the NMI counters in /proc/interrupts are incrementing?
> > > Yes:
> > > root@muur:/home/folkert# for i in `seq 1 5` ; do cat /proc/interrupts | grep NMI ; sleep 1 ; done
> > > NMI: 6949080 6949067
...
> > > NMI: 6949488 6949475
> >
> > Is there anything else I can try?
> argh. I haven't forgotten. Hopefully after -rc1 I'll have more time...
Sorry :-)
> Your report 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 LOCKUP"
2.6.6 crash "NMI watchdog detected LOCKUP on CPU1 eip c02500aa, registers:"
2.6.1 would not boot
Folkert van Heusden
--
Try MultiTail! Multiple windows with logfiles, filtered with regular
expressions, colored output, etc. etc. www.vanheusden.com/multitail/
----------------------------------------------------------------------
Get your PGP/GPG key signed at www.biglumber.com!
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
