From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michal Piotrowski" Subject: Re: 2.6.23-rc3 and SKY2 driver issue Date: Thu, 16 Aug 2007 10:25:45 +0200 Message-ID: <6bffcb0e0708160125v56f3d0f3l865574bdd56bd6ad@mail.gmail.com> References: <663186.13204.qm@web90403.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, Netdev , "Stephen Hemminger" To: "James Corey" Return-path: Received: from wa-out-1112.google.com ([209.85.146.177]:20688 "EHLO wa-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751679AbXHPIZq (ORCPT ); Thu, 16 Aug 2007 04:25:46 -0400 Received: by wa-out-1112.google.com with SMTP id v27so205983wah for ; Thu, 16 Aug 2007 01:25:45 -0700 (PDT) In-Reply-To: <663186.13204.qm@web90403.mail.mud.yahoo.com> Content-Disposition: inline Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org [Adding Stephen and netdev to CC] On 15/08/07, James Corey 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: > [] > __skb_checksum_complete_head+0x46/0x5f > [] __skb_checksum_complete+0xc/0x11 > [] tcp_v4_rcv+0x157/0x810 > [] dev_queue_xmit+0x237/0x260 > [] find_busiest_group+0x252/0x684 > [] ip_local_deliver+0xca/0x14c > [] ip_rcv+0x478/0x4ba > [] sky2_poll+0x6f9/0x9b9 > [] > run_rebalance_domains+0x13e/0x408 > [] net_rx_action+0xa8/0x166 > [] __do_softirq+0x55/0xc3 > [] call_softirq+0x1c/0x28 > [] do_softirq+0x2c/0x7d > [] do_IRQ+0x13e/0x15f > [] mwait_idle+0x0/0x46 > [] ret_from_intr+0x0/0xa > [] mwait_idle+0x42/0x46 > [] cpu_idle+0x8c/0xaf > [] start_kernel+0x2ac/0x2b8 > [] _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: > [] > __skb_checksum_complete_head+0x43/0x56 > [] __skb_checksum_complete+0xc/0x11 > [] tcp_v4_rcv+0x14e/0x801 > [] ip_local_deliver+0xca/0x14c > [] ip_rcv+0x46c/0x4ae > [] :sky2:sky2_poll+0x72b/0x9c7 > [] net_rx_action+0xa8/0x166 > [] __do_softirq+0x55/0xc4 > [] call_softirq+0x1c/0x28 > [] do_softirq+0x2c/0x7d > [] do_IRQ+0x13e/0x15f > [] mwait_idle+0x0/0x48 > [] ret_from_intr+0x0/0xa > [] > :sky2:sky2_xmit_frame+0x0/0x41d > [] mwait_idle+0x42/0x48 > [] cpu_idle+0xbd/0xe0 > [] start_kernel+0x2ac/0x2b8 > [] _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 -- LOG http://www.stardust.webpages.pl/log/