mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ion Badulescu <ionut@badula.org>
To: Hendrik Visage <hvjunk@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Starfire (Adaptec) kernel 2.6.13+ panics on AMD64 NFS server
Date: Fri, 30 Sep 2005 12:46:01 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.61.0509301226140.13733@ionlinux.tower-research.com> (raw)
In-Reply-To: <d93f04c70509300114i1757cde1x42d9fe7c453a8bbd@mail.gmail.com>

Hi Henrik,

On Fri, 30 Sep 2005, Hendrik Visage wrote:

> Will do, but check perhaps for some 64bit uncleanes in the scatter gather stuff
> that got enabled in 2.6.13 because of the GPL'd Adaptec firmware, as I
> recalled some skb related stuff.

There is an easy way to disable the firmware and pretty much all the 
changes that went into 2.6.13: load the starfire with enable_hw_cksum=0. 
If you can easily reproduce this problem, try doing the above and see if 
you can still hit it. Maybe it's a newly introduced problem in the upper 
layer's SG--your other network driver simply isn't using SG so it's 
not affected.

It's very suspicious that the bug would be in skb_checksum_help(), since 
the starfire driver doesn't do anything with the skb before handing it 
over to skb_checksum_help(). It would mean that the upper layer handed an 
invalid skb to the driver, or that we have some random memory corruption 
somewhere.

Thanks,
Ion

-- 
   It is better to keep your mouth shut and be thought a fool,
             than to open it and remove all doubt.

  reply	other threads:[~2005-09-30 16:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30  3:36 Hendrik Visage
2005-09-30  4:16 ` Andrew Morton
2005-09-30  8:14   ` Hendrik Visage
2005-09-30 16:46     ` Ion Badulescu [this message]
2005-09-30 16:01   ` Hendrik Visage
2005-09-30 17:40     ` Andrew Morton
2005-09-30 20:10       ` Hendrik Visage
2005-09-30 20:55         ` Ion Badulescu
2005-09-30 22:39         ` Herbert Xu
2005-10-01 19:21           ` Hendrik Visage

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.61.0509301226140.13733@ionlinux.tower-research.com \
    --to=ionut@badula.org \
    --cc=akpm@osdl.org \
    --cc=hvjunk@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®