From: Michal Piotrowski <hidden> Date: 2007-08-16 08:26:09
[Adding Stephen and netdev to CC]
On 15/08/07, James Corey [off-list ref] wrote:
I tried running a D-link gig card on kernel 2.6.21.1
and it came up fine, but when I did a sftp of
an linux dvd ISO to it, the interface would lock
up hard with the error
eth1: hw csum failure.
Call Trace:
<IRQ> [<ffffffff804d3e31>]
__skb_checksum_complete_head+0x46/0x5f
[<ffffffff804d3e56>] __skb_checksum_complete+0xc/0x11
[<ffffffff805046c7>] tcp_v4_rcv+0x157/0x810
[<ffffffff804d8a6f>] dev_queue_xmit+0x237/0x260
[<ffffffff80229990>] find_busiest_group+0x252/0x684
[<ffffffff804ead50>] ip_local_deliver+0xca/0x14c
[<ffffffff804eb24a>] ip_rcv+0x478/0x4ba
[<ffffffff803ec7d3>] sky2_poll+0x6f9/0x9b9
[<ffffffff8022bd5d>]
run_rebalance_domains+0x13e/0x408
[<ffffffff804d877a>] net_rx_action+0xa8/0x166
[<ffffffff80235d62>] __do_softirq+0x55/0xc3
[<ffffffff8020a4ec>] call_softirq+0x1c/0x28
[<ffffffff8020b611>] do_softirq+0x2c/0x7d
[<ffffffff8020b8cf>] do_IRQ+0x13e/0x15f
[<ffffffff802086ce>] mwait_idle+0x0/0x46
[<ffffffff80209871>] ret_from_intr+0x0/0xa
<EOI> [<ffffffff80208710>] mwait_idle+0x42/0x46
[<ffffffff80208666>] cpu_idle+0x8c/0xaf
[<ffffffff8078174e>] start_kernel+0x2ac/0x2b8
[<ffffffff80781140>] _sinittext+0x140/0x144
So I tried running the latest snapshot 2.6.23-rc3
and the almost the same thing happens. Only
difference is that now the entire box locks up.
The error is almost the same
eth1: hw csum failure.
Call Trace:
<IRQ> [<ffffffff804779b6>]
__skb_checksum_complete_head+0x43/0x56
[<ffffffff804779d5>] __skb_checksum_complete+0xc/0x11
[<ffffffff804a989d>] tcp_v4_rcv+0x14e/0x801
[<ffffffff8048ff84>] ip_local_deliver+0xca/0x14c
[<ffffffff80490472>] ip_rcv+0x46c/0x4ae
[<ffffffff880060f9>] :sky2:sky2_poll+0x72b/0x9c7
[<ffffffff8047c934>] net_rx_action+0xa8/0x166
[<ffffffff80235ced>] __do_softirq+0x55/0xc4
[<ffffffff8020c5cc>] call_softirq+0x1c/0x28
[<ffffffff8020d6fd>] do_softirq+0x2c/0x7d
[<ffffffff8020d9bb>] do_IRQ+0x13e/0x15f
[<ffffffff8020a780>] mwait_idle+0x0/0x48
[<ffffffff8020b951>] ret_from_intr+0x0/0xa
<EOI> [<ffffffff880063e7>]
:sky2:sky2_xmit_frame+0x0/0x41d
[<ffffffff8020a7c2>] mwait_idle+0x42/0x48
[<ffffffff8020a718>] cpu_idle+0xbd/0xe0
[<ffffffff80704a5a>] start_kernel+0x2ac/0x2b8
[<ffffffff80704140>] _sinittext+0x140/0x144
I see that the new kernel includes some sort of
SKY2 DEBUG stuff. I would be happy to rerun
the test with that turned on, given some minor
direction.
From: Stephen Hemminger <hidden> Date: 2007-08-16 13:06:09
On Thu, 16 Aug 2007 10:25:45 +0200
"Michal Piotrowski" [off-list ref] wrote:
[Adding Stephen and netdev to CC]
On 15/08/07, James Corey [off-list ref] wrote:
quoted
I tried running a D-link gig card on kernel 2.6.21.1
and it came up fine, but when I did a sftp of
an linux dvd ISO to it, the interface would lock
up hard with the error
eth1: hw csum failure.
Call Trace:
<IRQ> [<ffffffff804d3e31>]
__skb_checksum_complete_head+0x46/0x5f
[<ffffffff804d3e56>] __skb_checksum_complete+0xc/0x11
[<ffffffff805046c7>] tcp_v4_rcv+0x157/0x810
[<ffffffff804d8a6f>] dev_queue_xmit+0x237/0x260
[<ffffffff80229990>] find_busiest_group+0x252/0x684
[<ffffffff804ead50>] ip_local_deliver+0xca/0x14c
[<ffffffff804eb24a>] ip_rcv+0x478/0x4ba
[<ffffffff803ec7d3>] sky2_poll+0x6f9/0x9b9
[<ffffffff8022bd5d>]
run_rebalance_domains+0x13e/0x408
[<ffffffff804d877a>] net_rx_action+0xa8/0x166
[<ffffffff80235d62>] __do_softirq+0x55/0xc3
[<ffffffff8020a4ec>] call_softirq+0x1c/0x28
[<ffffffff8020b611>] do_softirq+0x2c/0x7d
[<ffffffff8020b8cf>] do_IRQ+0x13e/0x15f
[<ffffffff802086ce>] mwait_idle+0x0/0x46
[<ffffffff80209871>] ret_from_intr+0x0/0xa
<EOI> [<ffffffff80208710>] mwait_idle+0x42/0x46
[<ffffffff80208666>] cpu_idle+0x8c/0xaf
[<ffffffff8078174e>] start_kernel+0x2ac/0x2b8
[<ffffffff80781140>] _sinittext+0x140/0x144
So I tried running the latest snapshot 2.6.23-rc3
and the almost the same thing happens. Only
difference is that now the entire box locks up.
The error is almost the same
eth1: hw csum failure.
Call Trace:
<IRQ> [<ffffffff804779b6>]
__skb_checksum_complete_head+0x43/0x56
[<ffffffff804779d5>] __skb_checksum_complete+0xc/0x11
[<ffffffff804a989d>] tcp_v4_rcv+0x14e/0x801
[<ffffffff8048ff84>] ip_local_deliver+0xca/0x14c
[<ffffffff80490472>] ip_rcv+0x46c/0x4ae
[<ffffffff880060f9>] :sky2:sky2_poll+0x72b/0x9c7
[<ffffffff8047c934>] net_rx_action+0xa8/0x166
[<ffffffff80235ced>] __do_softirq+0x55/0xc4
[<ffffffff8020c5cc>] call_softirq+0x1c/0x28
[<ffffffff8020d6fd>] do_softirq+0x2c/0x7d
[<ffffffff8020d9bb>] do_IRQ+0x13e/0x15f
[<ffffffff8020a780>] mwait_idle+0x0/0x48
[<ffffffff8020b951>] ret_from_intr+0x0/0xa
<EOI> [<ffffffff880063e7>]
:sky2:sky2_xmit_frame+0x0/0x41d
[<ffffffff8020a7c2>] mwait_idle+0x42/0x48
[<ffffffff8020a718>] cpu_idle+0xbd/0xe0
[<ffffffff80704a5a>] start_kernel+0x2ac/0x2b8
[<ffffffff80704140>] _sinittext+0x140/0x144
I see that the new kernel includes some sort of
SKY2 DEBUG stuff. I would be happy to rerun
the test with that turned on, given some minor
direction.
From: James Corey <hidden> Date: 2007-08-20 15:42:33
--- Stephen Hemminger
[off-list ref] wrote:
On Thu, 16 Aug 2007 10:25:45 +0200
"Michal Piotrowski"
[off-list ref] wrote:
quoted
[Adding Stephen and netdev to CC]
On 15/08/07, James Corey [off-list ref]
wrote:
quoted
quoted
I tried running a D-link gig card on kernel
2.6.21.1
quoted
quoted
and it came up fine, but when I did a sftp of
an linux dvd ISO to it, the interface would lock
up hard with the error
eth1: hw csum failure.
Call Trace:
<IRQ> [<ffffffff804d3e31>]
__skb_checksum_complete_head+0x46/0x5f
[<ffffffff804d3e56>]
[<ffffffff80208666>] cpu_idle+0x8c/0xaf
[<ffffffff8078174e>] start_kernel+0x2ac/0x2b8
[<ffffffff80781140>] _sinittext+0x140/0x144
So I tried running the latest snapshot
2.6.23-rc3
quoted
quoted
and the almost the same thing happens. Only
difference is that now the entire box locks up.
The error is almost the same
eth1: hw csum failure.
Call Trace:
<IRQ> [<ffffffff804779b6>]
__skb_checksum_complete_head+0x43/0x56
[<ffffffff804779d5>]
[<ffffffff8047c934>] net_rx_action+0xa8/0x166
[<ffffffff80235ced>] __do_softirq+0x55/0xc4
[<ffffffff8020c5cc>] call_softirq+0x1c/0x28
[<ffffffff8020d6fd>] do_softirq+0x2c/0x7d
[<ffffffff8020d9bb>] do_IRQ+0x13e/0x15f
[<ffffffff8020a780>] mwait_idle+0x0/0x48
[<ffffffff8020b951>] ret_from_intr+0x0/0xa
<EOI> [<ffffffff880063e7>]
:sky2:sky2_xmit_frame+0x0/0x41d
[<ffffffff8020a7c2>] mwait_idle+0x42/0x48
[<ffffffff8020a718>] cpu_idle+0xbd/0xe0
[<ffffffff80704a5a>] start_kernel+0x2ac/0x2b8
[<ffffffff80704140>] _sinittext+0x140/0x144
I see that the new kernel includes some sort of
SKY2 DEBUG stuff. I would be happy to rerun
the test with that turned on, given some minor
direction.
Regards,
Michal
Please reproduce with a more recent kernel?
Um, I thought 2.6.23rc WAS pretty recent. :-)
I'll check if there is something newer in the
repository now.
-J
____________________________________________________________________________________
Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more.
http://mobile.yahoo.com/go?refer=1GNXIC
From: Stephen Hemminger <hidden> Date: 2007-08-20 16:48:18
On Mon, 20 Aug 2007 09:23:46 -0700 (PDT)
James Corey [off-list ref] wrote:
quoted hunk
--- Stephen Hemminger
[off-list ref] wrote:
quoted
On Mon, 20 Aug 2007 08:42:21 -0700 (PDT)
James Corey [off-list ref] wrote:
quoted
--- Stephen Hemminger
[off-list ref] wrote:
quoted
On Thu, 16 Aug 2007 10:25:45 +0200
"Michal Piotrowski"
quoted
Please reproduce with a more recent kernel?
Um, I thought 2.6.23rc WAS pretty recent. :-)
I'll check if there is something newer in the
repository now.
What is the chip version? Please send console log:
"dmesg | grep sky2"
--
Stephen Hemminger [off-list ref]
Ah ... details.
Machine:
Dell Optiplex 745
Kernel:
2.6.23-rc3 #1 SMP Tue Aug 14 19:44:07 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux
Card:
D-Link DGE-550SX
# dmesg | grep sky2
sky2 0000:04:00.0: v1.16 addr 0xdf9fc000 irq 16
Yukon-XL (0xb3) rev 3
sky2 eth1: addr 00:17:9a:73:87:60
sky2 eth1: enabling interface
sky2 eth1: ram buffer 96K
sky2 eth1: Link is up at 1000 Mbps, full duplex, flow
control none
Okay, this is a fiber based card. Does the error happen right away (ie all packets
have bad sum), or is it sporadic (ie some magic packet or race in hardware).
Also are you using regular (1500) or jumbo (9000) mtu?
--
Stephen Hemminger [off-list ref]