Skip to contentSkip to conversation

e100 driver

DISCUSSION David Gómez 2 participants 3 messages May 19, 2003

lore
Share & tools
lore
#0 lore raw

Hi all,

Is there some known problem in 2.4.20 with the e100 driver? I've been seen lately a lot of errors in my kernel logs, with the messages:

<31>May 19 09:05:42 kernel: hw tcp v4 csum failed
<31>May 19 09:11:11 kernel: icmp v4 hw csum failure

repeated several times. I've switched back to the eepro100 driver and the checksum errors messages seems to go away...

Thanks,

Signature · 4 lines
David Gómez

"The question of whether computers can think is just like the question of
 whether submarines can swim." -- Edsger W. Dijkstra
#1 lore raw
Quoted 8 lines · David Gómez

Is there some known problem in 2.4.20 with the e100 driver? I've been seen lately a lot of errors in my kernel logs, with the messages:

<31>May 19 09:05:42 kernel: hw tcp v4 csum failed
<31>May 19 09:11:11 kernel: icmp v4 hw csum failure

repeated several times. I've switched back to the eepro100 driver and the checksum errors messages seems to go away...

I get this, too, on two recently-purchased machines. I suspect that
the new revs of the chips are the cause -- my kernel doesn't seem to know about many of the device IDs on this board:

hrm@cader:~$ lspci
00:00.0 Host bridge: Intel Corp.: Unknown device 2560 (rev 03)
00:02.0 VGA compatible controller: Intel Corp.: Unknown device 2562 (rev 03)
00:1d.0 USB Controller: Intel Corp.: Unknown device 24c2 (rev 02)
00:1d.1 USB Controller: Intel Corp.: Unknown device 24c4 (rev 02)
00:1d.2 USB Controller: Intel Corp.: Unknown device 24c7 (rev 02)
00:1d.7 USB Controller: Intel Corp.: Unknown device 24cd (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82820 820 (Camino 2) Chipset PCI (rev 82)
00:1f.0 ISA bridge: Intel Corp.: Unknown device 24c0 (rev 02)
00:1f.1 IDE interface: Intel Corp.: Unknown device 24cb (rev 02)
00:1f.3 SMBus: Intel Corp.: Unknown device 24c3 (rev 02)
00:1f.5 Multimedia audio controller: Intel Corp.: Unknown device 24c5 (rev 02)
01:08.0 Ethernet controller: Intel Corp.: Unknown device 1039 (rev 82)

Other than the odd csum failures (average of 1-2 a day on each
box), it all seems to work perfectly.

Hugo.

Signature · 4 lines
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
          --- ...  one ping(1) to rule them all, and in the ---          
                         darkness bind(2) them.                          
#2 lore raw

Hi Hugo,

Quoted 6 lines · Hugo Mills
Quoted 2 lines
<31>May 19 09:05:42 kernel: hw tcp v4 csum failed
<31>May 19 09:11:11 kernel: icmp v4 hw csum failure

I get this, too, on two recently-purchased machines. I suspect that
the new revs of the chips are the cause -- my kernel doesn't seem to know about many of the device IDs on this board:

Not in my case :(, i'm using a not very recent intel ethernet card:

00:0c.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 08)

Quoted 2 lines

Other than the odd csum failures (average of 1-2 a day on each
box), it all seems to work perfectly.

I was getting a lot more, look:

[huma@fargo] [~] % grep csum /var/log/messages|grep "May 19"| wc -l

    443
[huma@fargo] [~] % grep csum /var/log/messages|grep "May 18"| wc -l
    486
[huma@fargo] [~] % grep csum /var/log/messages|grep "May 17"| wc -l
    425
[huma@fargo] [~] % grep csum /var/log/messages|grep "May 16"| wc -l
    953
[huma@fargo] [~] % grep csum /var/log/messages|grep "May 15"| wc -l
   1023
[huma@fargo] [~] % grep csum /var/log/messages|grep "May 14"| wc -l
    911

I've been a long time without noticing this problem, but looking casually for another reason at the logs get me to finding these checksum errors hell ;))

Signature · 4 lines
David Gómez

"The question of whether computers can think is just like the question of
 whether submarines can swim." -- Edsger W. Dijkstra