From: Auke Kok <sofar@foo-projects.org>
To: Dave Jones <davej@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: E1000 stopped transmitting in rc3.
Date: Thu, 27 Apr 2006 18:54:28 -0700 [thread overview]
Message-ID: <445175D4.8010209@foo-projects.org> (raw)
In-Reply-To: <20060428001352.GA3319@redhat.com>
Dave Jones wrote:
> With 2.6.17-rc3, my E1000 won't get a dhcp lease.
> Looking at tcpdump and ifconfig output, it's easy to see why.
> It's recieving packets, but the packets transmitted field
> of ifconfig never increases.
>
> The last version I have built that worked ok was 2.6.17rc2-git3
*puzzled*
the only patch between 2.6.17rc2 and 2.6.17rc3 contains an rx-path patch, but
nothing that affects tx. All the other patches sent earlier are queued for
2.6.18 so they don't apply.
Auke
next prev parent reply other threads:[~2006-04-28 1:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 0:13 E1000 stopped transmitting in rc3 Dave Jones
2006-04-28 1:54 ` Auke Kok [this message]
2006-04-28 7:14 ` David S. Miller
[not found] ` <39fa70c7844cbb7240b98446e0940de7@localhost>
2006-04-29 6:46 ` Jim McCullough
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=445175D4.8010209@foo-projects.org \
--to=sofar@foo-projects.org \
--cc=davej@redhat.com \
--cc=netdev@vger.kernel.org \
/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).