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: Mon, 20 Aug 2007 11:25:56 +0200 [thread overview]
Message-ID: <be1b757c0708200225r1de32a9pc06f3af0e98c0b9@mail.gmail.com> (raw)
In-Reply-To: <20070816141122.GA6625@electric-eye.fr.zoreil.com>
The error exists from patch 2 on. I did some network testing with
patch 1 and currently use it and have no errors so far.
>From my experiences up to now patch 1 should be error free.
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-20 9:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 11:35 Karl Meyer
2007-08-13 16:58 ` Francois Romieu
2007-08-13 17:27 ` Karl Meyer
2007-08-14 7:09 ` Francois Romieu
2007-08-14 15:47 ` Karl Meyer
2007-08-14 16:47 ` Karl Meyer
2007-08-14 21:25 ` Karl Meyer
2007-08-14 22:46 ` Francois Romieu
2007-08-16 14:11 ` Francois Romieu
2007-08-16 21:03 ` Karl Meyer
2007-08-20 9:25 ` Karl Meyer [this message]
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=be1b757c0708200225r1de32a9pc06f3af0e98c0b9@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
all inboxes | Powered by JetHome®