[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.1.10.0901230802180.10635@p34.internal.lan>
Date: Fri, 23 Jan 2009 08:06:40 -0500 (EST)
From: Justin Piszcz <jpiszcz@...idpixels.com>
To: Doug Bazarnic <kernel@...arnic.net>
cc: 'Francois Romieu' <romieu@...zoreil.com>,
'Andrew Morton' <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, 'Alan Piszcz' <ap@...arrain.com>,
netdev@...r.kernel.org
Subject: RE: 2.6.28: r8169: NETDEV WATCHDOG: eth0 (r8169): transmit timed
out
On Fri, 23 Jan 2009, Doug Bazarnic wrote:
> I've just setup a lab in the office to test out IPVS, and I'm using an Asus
> p5q-ws MB with dual r8169 nics on board. This machine is acting as a load
> balancer, and it's just directing packets to the web servers. Lots of
> requests...
>
> Justin Piszcz <jpiszcz@...idpixels.com> :
> [...]
>> It is the first time I have ever seen it on this system, while running
>> 2.6.28. I have never seen the error in the past (at least not that I can
>> remember/no log entries) for 2.6.27 or below.
>
> Does it translate into a temporary network hiccup, say a few seconds,
> or does it mean a final loss of networking ?
That is what it seemed like, enough to kill a DVD burn.
>
> Given the timestamp, the driver seemed to worked for some amount of time
> before breaking, did it not ? It would thus be different from the usual
> "no link at startup" problem.
Yes it did.
>
> Can you send a complete dmesg, including the r8169 XID line ?
# grep -i 8169 dmesg
[ 0.428875] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 0.428968] r8169 0000:05:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 0.429060] r8169 0000:05:00.0: setting latency timer to 64
[ 0.429132] r8169 0000:05:00.0: irq 378 for MSI/MSI-X
[ 20.267767] r8169: eth0: link up
[ 20.267846] r8169: eth0: link up
http://home.comcast.net/~jpiszcz/20090123/dmesg.txt
Justin.
--
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/
Powered by blists - more mailing lists