All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Hannes Schulz <schulz@schwaar.com>
Cc: shemminger@osdl.org, scott.feldman@intel.com, jgarzik@pobox.com,
	linux-net@vger.kernel.org, bridge@osdl.org
Subject: [Bridge] Re: [more info] Re: [2.4.22] bad interaction between e100 and bridge: BUG at dev.c:991!
Date: Sat, 30 Aug 2003 19:01:00 -0700	[thread overview]
Message-ID: <20030830190100.4eac4504.davem@redhat.com> (raw)
In-Reply-To: <p05111b00bb740b63506b@[10.96.96.13]>

On Thu, 28 Aug 2003 22:24:52 +0200
Hannes Schulz <schulz@schwaar.com> wrote:

> >Could the problem be that the e100 can do IP receive checksumming on 
> >the board,
> >but the eepro driver doesn't enable it.  When the board is doing checksum
> >offload, then the csum field isn't set.
> >
> >Please try disabling receive checksumming on the e100 driver
> >
> >	modprobe e100 XsumRX=0
> >
> >If this is the problem, it exists both 2.4 and 2.6.
> 
> Indeed: with  XsumRX=0,0 the BUG doesn't happen. I put some debugging 
> code in dev.c:

Looks like bridging is taking an input packet, transmitting it but not
initializing skb->csum, skb->ip_summed, and other fields before doing
so.

Definitely a bridging bug.

  reply	other threads:[~2003-08-31  2:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <p05111b01bb728bc8972e@[10.96.96.13]>
2003-08-27 20:28 ` [Bridge] Re: [2.4.22] bad interaction between e100 and bridge: BUG at dev.c:991! Stephen Hemminger
2003-08-28 20:24   ` [Bridge] [more info] " Hannes Schulz
2003-08-31  2:01     ` David S. Miller [this message]
2003-09-02 17:45       ` [Bridge] " Stephen Hemminger
2003-09-02 18:23         ` Bart De Schuymer
2003-09-02 18:17           ` David S. Miller
2003-09-05 18:30       ` [Bridge] [PATCH 2.4] bridging and hw checksum fix Stephen Hemminger
2003-09-03 14:56   ` [Bridge] Re: [2.4.22] bad interaction between e100 and bridge: BUG at dev.c:991! Hannes Schulz
2003-09-03 15:38     ` Stephen Hemminger
2003-09-03 16:49     ` Bart De Schuymer

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=20030830190100.4eac4504.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=bridge@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-net@vger.kernel.org \
    --cc=schulz@schwaar.com \
    --cc=scott.feldman@intel.com \
    --cc=shemminger@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.