Skip to contentSkip to conversation

E1000 stopped transmitting in rc3.

DISCUSSION Dave Jones 4 participants 4 messages Apr 28, 2006 – Apr 29, 2006 1 message not in the archive

Subsystems (2)
lore
Share & tools
lore

Dave Jones

author
#0 lore raw

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

Signature · 1 line
http://www.codemonkey.org.uk
#1 lore raw
Quoted 6 lines · 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

*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

maintainer
#2 lore raw

From: Auke Kok <[email protected]>
Date: Thu, 27 Apr 2006 18:54:28 -0700

Quoted 6 lines
Quoted 5 lines · 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.

Quoted 7 lines
Quoted 1 line

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.

A message that is not in the archive (sent off-list or not yet received): 39fa70c7844cbb7240b98446e0940de7@localhost

#4 lore raw
Quoted 1 line

From what I have seen currently, the issue is resolved. Based on a

test across multiple systems on x86-64, i386, and ia64 builds.

Quoted 25 lines · Auke Kok
Quoted 22 lines · David S. Miller

From: Auke Kok <[email protected]>
Date: Thu, 27 Apr 2006 18:54:28 -0700

Quoted 11 lines
Quoted 6 lines · 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

*puzzled*

the only patch between 2.6.17rc2 and 2.6.17rc3 contains an rx-path

patch, but

Quoted 1 line

nothing that affects tx. All the other patches sent earlier are queued

for

Quoted 1 line

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.

Quoted 10 lines
Quoted 1 line

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