E1000 stopped transmitting in rc3.

E1000 stopped transmitting in rc3.

[Dave Jones]

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

NIC is ..
03:0e.0 Ethernet controller: Intel Corporation 82545GM Gigabit Ethernet Controller (rev 04)
(8086:1026)

		Dave

-- 
http://www.codemonkey.org.uk

Re: E1000 stopped transmitting in rc3.

[Auke Kok]

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

Re: E1000 stopped transmitting in rc3.

[David S. Miller]

From: Auke Kok <sofar@foo-projects.org>
Date: Thu, 27 Apr 2006 18:54:28 -0700

> 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.

If the rx path is corrupting the packets or providing bad
checksums, there will be nothing to transmit back.

So RX changes could explain the behavior.

Re: E1000 stopped transmitting in rc3.

[Jim McCullough]

>From what I have seen currently, the issue is resolved.  Based on a
test across  multiple systems on x86-64, i386,  and ia64 builds.

On 4/28/06, Auke Kok <sofar@foo-projects.org> wrote:
>
>
> On Fri, 28 Apr 2006 00:14:40 -0700 (PDT), "David S. Miller" <davem@davemloft.net> wrote:
> > From: Auke Kok <sofar@foo-projects.org>
> > Date: Thu, 27 Apr 2006 18:54:28 -0700
> >
> >> 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.
> >
> > If the rx path is corrupting the packets or providing bad
> > checksums, there will be nothing to transmit back.
> >
> > So RX changes could explain the behavior.
>
> Jim sent me a private message that his colleagues messed up the build, and that it is working correctly now, right Jim?
>
> Cheers,
>
> Auke
>
>
>


--
Jim McCullough