From: Ricardo Galli <gallir@uib.es>
To: Martin Schlemmer <azarah@gentoo.org>
Cc: Mirko Lindner <mlindner@syskonnect.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test3+sk98lin driver with hardware bug make eth unusable
Date: Tue, 12 Aug 2003 14:40:50 +0200 [thread overview]
Message-ID: <200308121440.50395.gallir@uib.es> (raw)
In-Reply-To: <1060689676.13254.172.camel@workshop.saharacpt.lan>
On Tuesday 12 August 2003 14:01, Martin Schlemmer shaped the electrons to
shout:
> On Tue, 2003-08-12 at 13:01, Ricardo Galli wrote:
> > I've already reported this problem to syskonnect few weeks ago (without
> > success as I see).
> >
> > There is a ASIC bug in several popular motherboards (including ASUS ones)
> > related to TX hardware checksum.
> >
> > For packets smaller that 56 bytes (payload), as UDP dns queries, the asic
> > generates a bad checksum making the drivers unusable for "normal"
> > Internet usage:
>
> <snip>
>
> > The only solution is to comment out
> > #define USE_SK_TX_CHECKSUM
> > in skge.c
>
> Known issue.
>
> Mirko will have a look as soon as he have time.
Thanks, I just sent a Kconfig patch as a workaround:
http://lkml.org/lkml/2003/8/12/83
BTW, I'm testing it in a ASUS P4800 Deluxe motherboard, which has the asic
bug:
gallir@antoli:~$ lspci
00:00.0 Host bridge: Intel Corp.: Unknown device 2578 (rev 02)
00:01.0 PCI bridge: Intel Corp.: Unknown device 2579 (rev 02)
00:1d.0 USB Controller: Intel Corp.: Unknown device 24d2 (rev 02)
00:1d.1 USB Controller: Intel Corp.: Unknown device 24d4 (rev 02)
00:1d.2 USB Controller: Intel Corp.: Unknown device 24d7 (rev 02)
00:1d.3 USB Controller: Intel Corp.: Unknown device 24de (rev 02)
00:1d.7 USB Controller: Intel Corp.: Unknown device 24dd (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corp.: Unknown device 24d0 (rev 02)
00:1f.1 IDE interface: Intel Corp.: Unknown device 24db (rev 02)
00:1f.2 IDE interface: Intel Corp.: Unknown device 24d1 (rev 02)
00:1f.3 SMBus: Intel Corp.: Unknown device 24d3 (rev 02)
00:1f.5 Multimedia audio controller: Intel Corp.: Unknown device 24d5 (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti 4200]
(rev a3)
02:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller
(rev 80)
02:05.0 Ethernet controller: 3Com Corporation: Unknown device 1700 (rev 12)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
02:0c.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
02:0c.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev
07)
02:0d.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev
78)
Cheers,
--
ricardo galli GPG id C8114D34
http://mnm.uib.es/~gallir/
next prev parent reply other threads:[~2003-08-12 12:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-12 11:01 2.6.0-test3+sk98lin driver with hardware bug make eth unusable Ricardo Galli
2003-08-12 12:01 ` Martin Schlemmer
2003-08-12 12:40 ` Ricardo Galli [this message]
2003-08-23 18:35 ` Martin Schlemmer
2003-08-24 12:27 ` Martin Schlemmer
2003-08-28 10:24 ` [PATCH 2.6.0-test4][sk98lin] sk98lin " Mirko Lindner
2003-08-28 10:39 ` Martin Schlemmer
2003-09-04 21:55 ` Martin Schlemmer
2008-09-05 8:26 ` Mirko Lindner
2003-08-24 16:28 ` 2.6.0-test3+sk98lin " Ricardo Galli
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=200308121440.50395.gallir@uib.es \
--to=gallir@uib.es \
--cc=azarah@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlindner@syskonnect.de \
/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;
as well as URLs for NNTP newsgroup(s).