From: moffe@amagerkollegiet.dk (Rasmus Bøg Hansen)
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: Hugo Mills <hugo-lkml@carfax.org.uk>,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: e100 driver
Date: Thu, 22 May 2003 02:12:20 +0200 [thread overview]
Message-ID: <87wugjsuu3.fsf@grignard.amagerkollegiet.dk> (raw)
In-Reply-To: <20030521233220.GA20622@fargo> ( =?iso-8859-1?q?David_G=F3mez's_message_of?= "Thu, 22 May 2003 01:32:20 +0200")
David Gómez <david@pleyades.net> writes:
> Hi Scott,
>
>> > I reloaded again the e100 module with this parameter. Let's
>> > see how it performs. Thanks for the advice ;)
>> >
>> > I'll let you know if checksum errors doesn't show anymore.
>>
>> There are several new reports of this problem, so we're trying to repro now...
>
> Indeed disabling hardware receive hecksums made the problem go away, it's been
> more that a day with no errors in my logs. If you want to know more about my
> hardware/software configuration, let me know.
I have had some of these too but never paid them any attention
(2.4.21-rc2).
I too tried disabling hardware checksums - now I don't see anything in
the logs...
00:0c.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
Subsystem: Intel Corp. EtherExpress PRO/100+ Management Adapter
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (2000ns min, 14000ns max), cache line size 08
Interrupt: pin A routed to IRQ 11
Region 0: Memory at d5000000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at a000 [size=64]
Region 2: Memory at d4800000 (32-bit, non-prefetchable) [size=1M]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
00: 86 80 29 12 17 00 90 02 08 00 00 02 08 20 00 00
10: 00 00 00 d5 01 a0 00 00 00 00 80 d4 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 0c 00
30: 00 00 00 00 dc 00 00 00 00 00 00 00 0b 01 08 38
I disabled the PXE function on the boot rom using the DOS intel tool;
otherwise I haven't messed with the firmware.
/Rasmus
--
-- [ Rasmus "Møffe" Bøg Hansen ] ---------------------------------------
Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot.
-- Microsoft help desk
----------------------------------[ moffe at amagerkollegiet dot dk ] --
next prev parent reply other threads:[~2003-05-21 23:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 22:12 Feldman, Scott
2003-05-21 23:32 ` David Gómez
2003-05-22 0:12 ` Rasmus Bøg Hansen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-20 19:31 Feldman, Scott
2003-05-20 22:02 ` David Gómez
2003-05-19 21:12 David Gómez
2003-05-19 21:33 ` Hugo Mills
2003-05-19 22:20 ` David Gómez
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=87wugjsuu3.fsf@grignard.amagerkollegiet.dk \
--to=moffe@amagerkollegiet.dk \
--cc=hugo-lkml@carfax.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.feldman@intel.com \
/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®