From: Olivier Sessink <olivier@lx.student.wau.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: Problem with SMC Etherpower II + kernel newer 2.4.2
Date: Tue, 03 Jul 2001 16:57:50 +0200 [thread overview]
Message-ID: <20010703165750.A1521@fender.fakenet> (raw)
In-Reply-To: <01070311300700.00765@phoenix>; from florian@galois.de on Tue, Jul 03, 2001 at 11:31:42AM +0200
In-Reply-To: <3B40611D.F1485C1B@N-Club.de> <01070311300700.00765@phoenix>
On 0, Florian Schmitt <florian@galois.de> wrote:
>
> > Does anybody else got these errors or knows about a solution for this ??
>
> Same problem here, it won't run at all on newer kernels. But it isn't even
> 100% stable in 2.2.x here - on very high network traffic the card stops
> working. In this case, it helps to pull the network plug for a short time,
> then everything goes back to normal. I reduced speed to 10MB, and now it is
> stable at least in 2.2.x.
I use (kernel 2.4.4 and 2.4.5) a cron script that pings, and will run
ifdown eth0; ifup eth0
when the ping fails, this seems to be good enough to get it up and running
again, sometimes I need to reload the module, but it's indeed very annoying.
if ! ping -c 1 -n -q 192.168.100.2 ; then
ifdown eth0
ifup eth0
if ! ping -c 1 -n -q 192.168.100.2 ; then
ifdown eth0
rmmod epic100
insmod epic100
ifup eth0
fi
fi
regards,
Olivier
prev parent reply other threads:[~2001-07-03 14:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 11:55 Juergen Wolf
2001-07-02 14:18 ` John Jasen
2001-07-04 9:15 ` Juergen Wolf
2001-07-04 12:57 ` Francois Romieu
2001-07-06 7:48 ` Juergen Wolf
2001-07-06 11:44 ` Francois Romieu
2001-07-06 12:27 ` Juergen Wolf
2001-07-06 12:34 ` Jeff Garzik
2001-07-06 12:51 ` Juergen Wolf
2001-07-06 12:59 ` [PATCH] " Jeff Garzik
2001-07-06 15:04 ` Francois Romieu
2001-07-03 9:31 ` Florian Schmitt
2001-07-04 9:19 ` Francois Romieu
2001-07-04 15:30 ` Florian Schmitt
2001-07-03 14:57 ` Olivier Sessink [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=20010703165750.A1521@fender.fakenet \
--to=olivier@lx.student.wau.nl \
--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
all inboxes | Powered by JetHome®