All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: linux-kernel@vger.kernel.org
Cc: andy@spylog.ru
Subject: Re: 2.4.19pre10aa3
Date: Thu, 20 Jun 2002 19:03:40 +0200	[thread overview]
Message-ID: <20020620170340.GC1134@dualathlon.random> (raw)
In-Reply-To: <20020620131951.GD10718@dualathlon.random>

On Thu, Jun 20, 2002 at 03:19:51PM +0200, Andrea Arcangeli wrote:
> On Thu, Jun 20, 2002 at 03:44:59PM +0400, Andrey Nekrasov wrote:
> > Hello Andrea Arcangeli,
> > 
> > 
> > Kernel 2.4.19pre10aa3 + hidden_arp (from LVS)
> > 
> > 
> > 
> > ...
> > Intel(R) PRO/100 Fast Ethernet Adapter - Loadable driver, ver 1.8.38
> > Copyright (c) 2002 Intel Corporation
> > 
> > eth0: Intel(R) 8255x-based Ethernet Adapter
> >   Mem:0xfb101000  IRQ:18  Speed:100 Mbps  Dx:Full
> >   Hardware receive checksums enabled
> >   cpu cycle saver enabled
> > ...
> > 
> > ...
> > eth0 e100_wait_exec_cmd: Wait failed.
> > hw tcp v4 csum failed
> > hw tcp v4 csum failed
> > hw tcp v4 csum failed
> > hw tcp v4 csum failed
> > hw tcp v4 csum failed
> > hw tcp v4 csum failed
> > hw tcp v4 csum failed
> > ...
> > 
> > 
> > Than this message is caused? It something serious also can be problems?
> 
> probably a driver issue with hw checksum. btw interestingly the stack
> computes the cksum by hand for every tcp incoming packet (unless
> ip_summed is set by the driver to CHECKSUM_UNNECESSARY), this is how it
> noticed the hw checksum was wrong. I guess it's either an e100 driver
> issue, or an hardware issue. Maybe it's setting DF_CSUM_OFFLOAD for your
> card despite your hardware doesn't support that feature, or maybe
> there's something wrong in the logic that sets the skb->csum.

you may want to try again with aa4, it has a newer e100 driver taken
from jam2 that might make difference here.

Andrea

  reply	other threads:[~2002-06-20 17:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20  5:59 2.4.19pre10aa3 Andrea Arcangeli
2002-06-20  6:04 ` 2.4.19pre10aa3 David S. Miller
2002-06-20  6:30   ` 2.4.19pre10aa3 Andrea Arcangeli
2002-06-20 11:44 ` 2.4.19pre10aa3 Andrey Nekrasov
2002-06-20 13:19   ` 2.4.19pre10aa3 Andrea Arcangeli
2002-06-20 17:03     ` Andrea Arcangeli [this message]
2002-06-20 13:05 ` 2.4.19pre10aa3 J.A. Magallon
2002-06-20 13:32   ` 2.4.19pre10aa3 Andrea Arcangeli
2002-06-20 14:07     ` 2.4.19pre10aa3 Andrea Arcangeli
2002-06-20 14:05 ` 2.4.19pre10aa3 Ingo Molnar
2002-06-20 14:40   ` 2.4.19pre10aa3 Andrea Arcangeli
2002-06-20 14:44     ` 2.4.19pre10aa3 Andrea Arcangeli
2002-06-20 15:40 ` 2.4.19pre10aa3 Heinz Diehl
2002-06-20 22:48 ` 2.4.19pre10aa3 J.A. Magallon
2002-06-21  4:31   ` 2.4.19pre10aa3 Andrea Arcangeli

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=20020620170340.GC1134@dualathlon.random \
    --to=andrea@suse.de \
    --cc=andy@spylog.ru \
    --cc=linux-kernel@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 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.