From: "Don Krause" <dkrause@optivus.com>
To: <linux-kernel@vger.kernel.org>
Subject: RE: Camino 2 (82815/82820) v2.4.x eth/sound related lockups
Date: Tue, 14 Aug 2001 09:07:08 -0700 [thread overview]
Message-ID: <005c01c124db$2bf30870$6cc8c58f@satoy> (raw)
In-Reply-To: <E15WcZ9-0000zr-00@the-village.bc.nu>
I have 2 new systems with eepro 100's on the MB, and each one has that
problem with the eepro100 driver. Switching to the e100 module has solved
all issues with that card.
Both of these machines are Pogo linux rack mount units, and Pogo's default
RH 7.1 install is using the e100 driver also. For grins, I swithed those
boxes to the eepro100, and both lost their network connections within a few
hours if lightly loaded, and they lost it just a few minutes into large
(>100 meg) file transfers. Ftp or NFS, it didn't matter. (The kernel kept
running, the console was usable. Unloading the eepro100 didn't work,
however, the machine needed a power off reboot to get the net back)
After reinstalling RH 7.1 on both machines, and changing the detected
eepro100 driver back to the e100, the machines have not crashed since they
were put into service, some 20 days ago.
FWIW, one Pogo box has an Intel i810 MB, with onboard eepro100 eth, and an
additional pci intel nic, the other is a Tyan Thunder LE S2510, with a pair
of onboard nics.
--
Don Krause ph: 909.799.8327
Systems Administrator page: 909.512.0174
Optivus Technology, Inc e-mail: dkrause@optivus.com
"Splitting Atoms.. Saving Lives" http://www.optivus.com
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Alan Cox
> Sent: Tuesday, August 14, 2001 4:41 AM
> To: Ime Smits
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: Camino 2 (82815/82820) v2.4.x eth/sound related lockups
>
>
> > Funny things in syslog include:
> > kernel: mtrr: base(0xe8000000) is not aligned on a
> > size(0x4b0000) boundary
>
> Thats
> ok
>
> > kernel: eepro100: wait_for_cmd_done timeout!
>
> Those are not so good. I was having similar problems on an
> i810 box with
> onboard eepro100 until I disabled the pm stuff in 2.4.8ac2, but you
> seem to be running that one
>
> Alan
next prev parent reply other threads:[~2001-08-16 14:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-14 11:31 Camino 2 (82815/82820) v2.4.x eth/sound related lockups Ime Smits
2001-08-14 11:40 ` Alan Cox
2001-08-14 12:01 ` Ime Smits
2001-08-15 10:58 ` Andrey Savochkin
2001-08-14 16:07 ` Don Krause [this message]
2001-08-14 13:47 ` benjilr
2001-08-14 15:18 ` Ime Smits
2001-08-15 11:02 ` Andrey Savochkin
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='005c01c124db$2bf30870$6cc8c58f@satoy' \
--to=dkrause@optivus.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