From: "Karl Meyer" <adhocrocker@gmail.com>
To: "Francois Romieu" <romieu@fr.zoreil.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"
Date: Thu, 16 Aug 2007 23:03:35 +0200 [thread overview]
Message-ID: <be1b757c0708161403r3faa7190wd74ac1ecc8aa8f45@mail.gmail.com> (raw)
In-Reply-To: <20070816141122.GA6625@electric-eye.fr.zoreil.com>
I did some testing today and found that the error occurs after
applying some of the patches. However I did not figure out the exact
patch in which the error "starts" since it sometimes occurs immediatly
when moving some data over the net and sometimes it takes 30 min till
I get the transmit timeout. I will be away till sunday and do some
more testing then.
2007/8/16, Francois Romieu <romieu@fr.zoreil.com>:
> (please do not remove the netdev Cc:)
>
> Francois Romieu <romieu@fr.zoreil.com> :
> [...]
> > If it does not work I'll dissect 0e4851502f846b13b29b7f88f1250c980d57e944
> > tomorrow.
>
> You will find a tgz archive in attachment which contains a serie of patches
> (0001-... to 0005-...) to walk from 6dccd16b7c2703e8bbf8bca62b5cf248332afbe2
> to 0e4851502f846b13b29b7f88f1250c980d57e944 in smaller steps.
>
> Please apply 0001 on top of 6dccd16b7c2703e8bbf8bca62b5cf248332afbe2. If it
> still works, apply 0002 on top of 0001, etc.
>
> --
> Ueimor
>
>
next prev parent reply other threads:[~2007-08-16 21:03 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 [this message]
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
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=be1b757c0708161403r3faa7190wd74ac1ecc8aa8f45@mail.gmail.com \
--to=adhocrocker@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).