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, 2 Jun 2012 11:13:35 +0200 [thread overview]
Message-ID: <20120602111335.0b94fb59@stein> (raw)
In-Reply-To: <20120503204813.65468df7@stein>
On May 03 Stefan Richter wrote:
> On May 01 Francois Romieu wrote:
> [...]
> > Can you apply the patch below on top of current ethtool
> > (git://git.kernel.org/pub/scm/network/ethtool/ethtool.git) and see
> > if it is enough to compare the register dumps (ethtool -d eth0).
> [...]
> > This is a firmware free chipset anyway. Nothing strange in the interface
> > stats (ethtool -S eth0) ?
> >
> > You may have to narrow things. Can you check if the r8169.c at
> > 036dafa28da1e2565a8529de2ae663c37b7a0060 behaves the same ?
>
> I will follow up on this eventually, but it may take quite some time due
> to interfering work.
>
> Thank you for looking into it and giving directions,
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.
I have no idea whether the FireWire and networking issues might be somehow
connected, and I still lack time to investigate these issues (using Linux
only at home, not at work), but I will eventually get back to it.
--
Stefan Richter
-=====-===-- -==- ---=-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2012-06-02 9:13 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 [this message]
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
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=20120602111335.0b94fb59@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.