linux-kernel - Re: NETDEV WATCHDOG, tulip, 2.6.18

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20070419114641.C61052@shell.msen.com>
Date:	Thu, 19 Apr 2007 12:55:00 -0400 (EDT)
From:	Lou Poppler <lwp@...l.msen.com>
To:	Tomasz Chmielewski <mangoo@...g.org>
cc:	linux-kernel@...r.kernel.org, 419950@...s.debian.org
Subject: Re: NETDEV WATCHDOG, tulip, 2.6.18

On Thu, 19 Apr 2007, Tomasz Chmielewski wrote:

>> I also have recurrent problems with
>> NETDEV WATCHDOG: eth0: transmit timed out

> If you search the list, you'll find several similar reports about the tulip 
> driver (NETDEV WATCHDOG: eth0: transmit timed out).
>
> Adding nopaic/nolapic/noacpi options to the kernel command line helped in my 
> case.

Yes, I've looked at many similar complaints on this list and on Debian's
BTS, going back several years.  It seems that it happens with more drivers
than just tulip, all with basicly the same symptoms.  The pattern seems to
be: (1) a period of problem-free operation, minutes to days duration;
(2) something bad happens, probably APIC or APCI related, probably
interfering with seeing an interrupt; (3) the kernel doesn't ever
completely recover from the bad event, and the affected interface
remains crippled until reboot.

I will continue to experiment with noapic,nolapic,acpi=off,pci=routeirq
plus variations of BIOS setup options.  This is slow experimentation,
since it can take days to see the problem -- but luckily this machine
is not critical to anything now, and I don't mind taking some time
to try to figure this out.  When I find some settings that avoid the
problem, I think this will mean we have avoided the "something bad"
in step (2) above, possibly by disabling some functionality of the
hardware.  The possibility remains that some part of the kernel could
be coping better with whatever this is, and recovering the normal
operation of the interface after the "something bad".  I think I
remember other peoples' NETDEV WATCHDOG trouble reports where they
say their setup used to work OK under some earlier 2.4 (or 2.2 ?)
kernels, or even under other OSes.

Any other suggestions for boot options I should try are welcome,
as are any requests for other specific info about this system
while it is still in failure mode.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/