From: Florin Andrei <florin@sgi.com>
To: Luc Lalonde <llalonde@giref.ulaval.ca>
Cc: Ben Greear <greearb@candelatech.com>,
LKML <linux-kernel@vger.kernel.org>,
"eepro100@scyld.com" <eepro100@scyld.com>
Subject: Re: [eepro100] Re: Problem with Linux 2.4.7 and builtin eepro on Intel's EEA2 motherboard.
Date: 09 Aug 2001 10:46:17 -0700 [thread overview]
Message-ID: <997379177.31234.5.camel@stantz.corp.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0108082157470.18777-100000@merlin.giref.ulaval.ca>
In-Reply-To: <Pine.LNX.4.33.0108082157470.18777-100000@merlin.giref.ulaval.ca>
On 08 Aug 2001 21:58:39 -0400, Luc Lalonde wrote:
> Hello Fiorin,
>
> What is your uptime on this machine. I've come to the same conclusion and
> I'm up to 13 days with the Intel e100 driver.
With kernel's driver, the interface was frozen in 30 minutes. I had to
ifdown / ifup the interface.
With Intel's driver, it works for days with no problem. But i never had
an uptime bigger than one week on that system.
--
Florin Andrei
prev parent reply other threads:[~2001-08-09 17:48 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 ` Problem with Linux 2.4.7 and builtin eepro on Intel's EEA2 motherboard Florin Andrei
2001-08-09 1:58 ` [eepro100] " Luc Lalonde
2001-08-09 17:46 ` Florin Andrei [this message]
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=997379177.31234.5.camel@stantz.corp.sgi.com \
--to=florin@sgi.com \
--cc=eepro100@scyld.com \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llalonde@giref.ulaval.ca \
/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