From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org
Subject: Re: 3.4-rc: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
Date: Sat, 4 Aug 2012 14:22:37 +0200 [thread overview]
Message-ID: <20120804142237.44060164@stein> (raw)
In-Reply-To: <20120602111335.0b94fb59@stein>
On Jun 02 Stefan Richter wrote:
> I haven't had time to look further into it yet. Just two minor findings:
>
> (a) After update from 3.4-rc5 to 3.4, the problem persisted.
>
> (b) Later I noticed that silent file corruptions on FireWire disks happened
> and happen under 3.4-rc5 and 3.4, so I reverted into 3.3.1 which fixed
> that issue. Furthermore, since 6 days uptime of 3.3.1, the eth0 (r8169)
> transmit queue time-out did never occur.
After a month uptime of 3.3.1 without any problems, I rebooted into 3.5
six days ago. The frequent "r8169 0000:0b:00.0: eth0: link up" messages
which I got with 3.4-rc5 and 3.4 no longer happen. Whatever was wrong
with my system, it no longer is. Either 3.5 fixed it or it was an issue
external to the kernel or even external to the PC.
--
Stefan Richter
-=====-===-- =--- --=--
http://arcgraph.de/sr/
prev parent reply other threads:[~2012-08-04 12:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 16:24 3.4-rc: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out Stefan Richter
2012-05-01 17:27 ` Francois Romieu
2012-05-01 18:04 ` Stefan Richter
2012-05-01 20:04 ` Francois Romieu
2012-05-03 18:48 ` Stefan Richter
2012-06-02 9:13 ` Stefan Richter
2012-06-11 15:55 ` Tomas Papan
2012-06-11 20:49 ` Francois Romieu
2012-06-11 21:04 ` Tomas Papan
2012-06-11 21:52 ` Francois Romieu
2012-06-12 5:12 ` Tomas Papan
2012-06-12 5:26 ` Francois Romieu
2012-06-12 6:51 ` Tomas Papan
2012-06-12 14:34 ` Tomas Papan
2012-06-25 16:13 ` Tomas Papan
2012-06-25 20:25 ` Francois Romieu
2012-08-04 12:22 ` Stefan Richter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120804142237.44060164@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).