jerome lacoste schrieb:
On 8/23/05, Tomasz Chmielewski <[email protected]> wrote:
(...)
We are running four more machines like that, the only difference is the
kernel they are running (2.6.11.4).
On some of them, there are serious problems with a network, and they
usually happen when the traffic is bigger than usual (i.e., some big
software deployment to several workstations, remote backup, etc.).
The syslog is then full of entries like that:
Aug 21 04:04:30 SERVER-B-HS kernel: NETDEV WATCHDOG: eth0: transmit
timed out
Aug 21 04:04:30 SERVER-B-HS kernel: 0000:00:06.0: tulip_stop_rxtx() failed
I am seeing thousands of tulip_stop_rxtx() failed messages as well
with 2.6.11. No regular network failure though.
See http://kerneltrap.org/mailarchive/1/message/110291/flat
This may have something to do with this patch, introduced with 2.6.10
(see the ChangeLog-2.6.10).
It would explain why I had no problems on ~20 machines with 2.6.8.1
kernel, and I have this issue on the machines with 2.6.11.5 kernel.
[PATCH] tulip: make tulip_stop_rxtx() wait for DMA to fully stop
From: "John W. Linville" <[email protected]>
tulip_stop_rxtx() doesn't wait for DMA to fully stop like the function
call name implies.
This was submitted through my employer -- I am not the original author
of this patch. However, I passed it by Jeff Garizk and he expressed
interest in having it upstream.
--
Tomek
http://wpkg.org
-
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]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |