From: "Robbert Kouprie" <robbert@radium.jvb.tudelft.nl>
To: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>, "'John Gluck'" <jgluckca@home.com>
Subject: RE: eepro100.c bug on 10Mbit half duplex (kernels 2.4.5 / 2.4.10 / 2.4.11pre6 / 2.4.11 / 2.4.10ac11)
Date: Thu, 11 Oct 2001 19:29:20 +0200 [thread overview]
Message-ID: <002701c1527a$42bec1d0$020da8c0@nitemare> (raw)
In-Reply-To: <E15rjR4-000400-00@the-village.bc.nu>
I assume that should print out a message at bootup? That didn't happen:
Oct 7 18:29:18 radium eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
Oct 7 18:29:18 radium eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified
by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
Oct 7 18:29:18 radium eth0: OEM i82557/i82558 10/100 Ethernet,
00:D0:B7:E8:A2:02, IRQ 17.
Oct 7 18:29:18 radium Board assembly 749658-005, Physical connectors
present: RJ45
Oct 7 18:29:18 radium Primary interface chip i82555 PHY #1.
Oct 7 18:29:18 radium General self-test: passed.
Oct 7 18:29:18 radium Serial sub-system self-test: passed.
Oct 7 18:29:18 radium Internal registers self-test: passed.
Oct 7 18:29:18 radium ROM checksum self-test: passed (0xdbd8681d).
- Robbert
> -----Original Message-----
> From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk]
> Sent: donderdag 11 oktober 2001 19:16
> To: Robbert Kouprie
> Cc: 'John Gluck'; linux-kernel@vger.kernel.org
> Subject: Re: eepro100.c bug on 10Mbit half duplex (kernels
> 2.4.5 / 2.4.10 / 2.4.11pre6 / 2.4.11 / 2.4.10ac11)
>
>
> > files. It would always lockup after said amount of traffic,
> but only in
> > 10 Mbit half duplex mode. Also, I have the 82557, not the
> 82558 chip.
> >
> > The problem looks a lot like what should be fixed in this
> changelog line
> > from 2.4.9-ac13:
>
> Check the workaround is being activated for your eepro100..
>
next prev parent reply other threads:[~2001-10-11 17:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 12:29 eepro100.c bug on 10Mbit half duplex (kernels 2.4.5 / 2.4.10 / 2.4.11pre6 / 2.4.11 / 2.4.10ac11) Robbert Kouprie
2001-10-11 16:27 ` John Gluck
2001-10-11 16:52 ` Robbert Kouprie
2001-10-11 17:15 ` Alan Cox
2001-10-11 17:29 ` Robbert Kouprie [this message]
2001-10-11 19:19 ` Robbert Kouprie
2001-10-11 19:34 ` Alan Cox
2001-10-11 21:02 ` Robbert Kouprie
2001-10-11 17:42 ` Matthew S. Hallacy
2001-10-11 20:08 ` Ion Badulescu
2001-10-11 20:16 ` Dan Hollis
-- strict thread matches above, loose matches on Subject: below --
2001-10-12 8:41 Robbert Kouprie
2001-10-12 13:40 ` Ion Badulescu
2001-10-13 18:16 ` Robbert Kouprie
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='002701c1527a$42bec1d0$020da8c0@nitemare' \
--to=robbert@radium.jvb.tudelft.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgluckca@home.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox