From: "Karl Meyer" <adhocrocker@gmail.com>
To: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
Cc: "Francois Romieu" <romieu@fr.zoreil.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"
Date: Mon, 3 Sep 2007 00:21:50 +0200 [thread overview]
Message-ID: <be1b757c0709021521q850f2bdq3f88c24c02c26b1b@mail.gmail.com> (raw)
In-Reply-To: <6bffcb0e0709021515v586f078cjce04f877e2f27aa2@mail.gmail.com>
Hi,
am am looking for this issue for some time now, but there where no
errors in 2.6.22-r2 (gentoo speak, I guess this is 2.6.22.2
officially), I also ran git-bisect (for more information see the older
messages in this thread).
2007/9/3, Michal Piotrowski <michal.k.k.piotrowski@gmail.com>:
> Hi,
>
> On 01/09/07, Karl Meyer <adhocrocker@gmail.com> wrote:
> > This is what happened today:
> >
> > Sep 1 21:08:01 frege NETDEV WATCHDOG: eth0: transmit timed out
> > frege ~ # uname -r
> > 2.6.22.5-cfs-v20.5
>
> Can you reproduce this on 2.6.22 (not 2.6.22.x - it might be a -stable
> regression)?
>
> Regards,
> Michal
>
> --
> LOG
> http://www.stardust.webpages.pl/log/
>
next prev parent reply other threads:[~2007-09-02 22:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <be1b757c0708130435y689b9dd8raf9ac9f9c0fcc976@mail.gmail.com>
2007-08-13 16:58 ` PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out" Francois Romieu
[not found] ` <be1b757c0708131027v5c57822as2d9bd3190fd19b71@mail.gmail.com>
[not found] ` <20070814070901.GA14693@electric-eye.fr.zoreil.com>
[not found] ` <be1b757c0708141425qd887581n3922702b84a21758@mail.gmail.com>
[not found] ` <20070814224629.GB3495@electric-eye.fr.zoreil.com>
2007-08-16 14:11 ` Francois Romieu
2007-08-16 21:03 ` Karl Meyer
2007-08-20 9:25 ` Karl Meyer
2007-08-21 10:56 ` Karl Meyer
2007-08-27 12:50 ` Jarek Poplawski
2007-09-01 19:24 ` Karl Meyer
2007-09-02 22:15 ` Michal Piotrowski
2007-09-02 22:21 ` Karl Meyer [this message]
2007-09-12 20:50 ` Francois Romieu
2007-09-26 9:07 ` Karl Meyer
2007-10-01 11:42 ` Karl Meyer
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=be1b757c0709021521q850f2bdq3f88c24c02c26b1b@mail.gmail.com \
--to=adhocrocker@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--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).