mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Knut Petersen <Knut_Petersen@t-online.de>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [BUG] sky2 broken for Yukon PCI-E Gigabit Ethernet Controller 11ab:4362 (rev 19)
Date: Mon, 23 Jan 2006 10:15:38 -0800	[thread overview]
Message-ID: <20060123101538.14d21bf4@dxpl.pdx.osdl.net> (raw)
In-Reply-To: <43D1C99E.2000506@t-online.de>

O
> 
> It seems that the SuSE Firewall locked something ....
> 
> I started with kernel 2.6.15-git7, tried 2.6.15.1 and 2.6.16-rc1*.
> At the moment I do use a kernel 2.6.15-git7 patched with an updated sky2 
> (v.013).
> I could not find a single working sky2 configuration.
> 

Are you using the full kernel.org kernel, or are you putting sky2 driver into
the SUSE kernel? There are a number of bug fixes related to hardware checksumming
that are in the kernel.org kernel (2.6.15 or later).  There was one in ICMP.
These fixes relate to places in the code where a protocol decides to trim a
packet by removing bytes. I am not familiar with the SuSE Firewall. Is it just
standard netfilter modules or additional code?

-- 
Stephen Hemminger <shemminger@osdl.org>
OSDL http://developer.osdl.org/~shemminger

  reply	other threads:[~2006-01-23 18:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-21  5:41 Knut Petersen
2006-01-23 18:15 ` Stephen Hemminger [this message]
2006-01-23 19:20   ` Knut Petersen
2006-01-23 19:27     ` Stephen Hemminger
2006-01-24  9:43       ` Knut Petersen
2006-01-24 17:54         ` Stephen Hemminger
2006-01-24 20:32         ` Herbert Xu
2006-01-27  6:07           ` Knut Petersen
2006-01-27 12:22             ` Herbert Xu
2006-01-27 15:28               ` Patrick McHardy
2006-01-27 16:04               ` Knut Petersen
2006-02-04 10:32               ` Knut Petersen
2006-01-21 12:11 Knut Petersen

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=20060123101538.14d21bf4@dxpl.pdx.osdl.net \
    --to=shemminger@osdl.org \
    --cc=Knut_Petersen@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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®