From: Florin Andrei <florin@sgi.com>
To: Ben Greear <greearb@candelatech.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"eepro100@scyld.com" <eepro100@scyld.com>
Subject: Re: Problem with Linux 2.4.7 and builtin eepro on Intel's EEA2 motherboard.
Date: 08 Aug 2001 17:42:54 -0700 [thread overview]
Message-ID: <997317775.19780.40.camel@stantz.corp.sgi.com> (raw)
In-Reply-To: <3B704BBE.A3AA1C99@candelatech.com>
In-Reply-To: <3B704BBE.A3AA1C99@candelatech.com>
On 07 Aug 2001 13:12:46 -0700, Ben Greear wrote:
> The driver seems to lock up for a while and then recover...
>
> Aug 7 11:55:19 lanf1 last message repeated 5 times
> Aug 7 11:56:04 lanf1 last message repeated 21 times
> Aug 7 11:56:07 lanf1 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Same hardware, same problem, only worse: for me, it locks up forever!
Had this problem with several 2.4.x versions, then switched to Intel's
driver. I'm using the Intel driver now, with 2.4.7, and i have no
problem.
--
Florin Andrei
next prev parent reply other threads:[~2001-08-09 0:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-07 20:12 Problem with Linux 2.4.7 and builtin eepro on Intel's EEA2 motherboard Ben Greear
2001-08-07 21:53 ` [eepro100] " Donald Becker
2001-08-07 22:21 ` [eepro100] Problem with Linux 2.4.7 and builtin eepro on Intel'sEEA2 motherboard Ben Greear
2001-08-07 22:28 ` Christian Robottom Reis
2001-08-07 23:02 ` Donald Becker
2001-08-08 20:53 ` [eepro100] Problem with Linux 2.4.7 and builtin eepro onIntel'sEEA2 motherboard. (Solved, kinda) Ben Greear
2001-08-07 22:11 ` [eepro100] Problem with Linux 2.4.7 and builtin eepro on Intel's EEA2 motherboard Christian Robottom Reis
2001-08-07 22:25 ` [eepro100] Problem with Linux 2.4.7 and builtin eepro on Intel'sEEA2 motherboard Ben Greear
2001-08-07 22:38 ` Justin Guyett
2001-08-09 0:42 ` Florin Andrei [this message]
2001-08-09 1:58 ` [eepro100] Re: Problem with Linux 2.4.7 and builtin eepro on Intel's EEA2 motherboard Luc Lalonde
2001-08-09 17:46 ` Florin Andrei
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=997317775.19780.40.camel@stantz.corp.sgi.com \
--to=florin@sgi.com \
--cc=eepro100@scyld.com \
--cc=greearb@candelatech.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