From: "Dead2" <dead2@circlestorm.org>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Intel EEPro 100 with kernel drivers
Date: Tue, 30 Oct 2001 09:54:12 +0100 [thread overview]
Message-ID: <008e01c16120$723d6b00$d2c0ecd5@dead2> (raw)
In-Reply-To: <20011029021339.B23985@stud.ntnu.no> <3BDE6699.86FFF44F@softers.net>
>We have almost the same problem, except it totally locks up the
>computer. Light network utilization is ok, but heavy traffic does the
>effect.
>No syslog reports, even keyboards leds won't light up (numlock, etc).
>Rebooting helps for a while. We had to install another network card for
>a workaround. I've tried kernels 2.4.10 and 2.4.12.
>
>The network card is integrated at the motherboard.
>
>dmesg:
>----
>*snip*
>-----
>*snip*
>----
>Oh, eepro100-diag reported 'Sleep mode is enabled', which could do
>something like this -> I disabled it, but no positive effect.
>
>
>Any similar problems?
Sounds like this might be the same problem that we are experiencing
here. The nic does get a high load of traffic immedeately when it has
booted up.
No messages of anything remotely wrong whatsoever, even after
setting the highest debug level in the eepro100 driver.
-=Dead2=-
*my previous message to this list about this issue*
> Tested now with another motherboard with the same results.
> MSI 6321 Pro 1.0
>
> Both these motherboards use VIA dual-cpu chipsets.
> Same results with 2.4.13-Pre6 on both motherboards.
>
> > I have an Asus CUV266-d motherboard, and want to use my Intel NIC's..
> >
> > 2.4.10 & 2.4.12 hangs while "Setting up routing"
> > No error messages appear.
> >
> > 2.4.x(4 maybe?) has both 'e100' drivers and the 'eepro100' drivers.
> > When loading the 'eepro100', it hangs just like with todays kernels.
> > When loading the 'e100', everything works just fine for a short while..
> > 20-40seconds I guess.. Then the computer hangs.
> >
> > When not loading any NIC drivers, everything works just fine.
> >
> > The NIC's i've tried are named "Intel(R) PRO/100+ Dual Port Server
> Adapter"
> > Have also tried a "Intel(R) PRO/100+ Adapter"
> >
> > Any ideas of what to test?
> > I have the latest bios and have tried just about all bios settings.
> > 'noapic' doesn't help.
next prev parent reply other threads:[~2001-10-30 8:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 1:13 Intel EEPro 100 with kernel drivers Thomas Langås
2001-10-29 1:57 ` Jim Hull
2001-10-29 3:43 ` J Sloan
2001-10-31 8:01 ` Thomas Langås
2001-10-31 15:22 ` Andrey Savochkin
2001-10-31 15:52 ` Kirill Ratkin
2001-11-01 7:55 ` Thomas Langås
2001-11-01 9:47 ` Andrey Savochkin
2001-11-01 10:00 ` Thomas Langås
2001-10-31 18:10 ` Juergen Hasch
2001-11-01 8:03 ` Thomas Langås
2001-11-01 8:48 ` Juergen Hasch
2001-11-01 9:06 ` Thomas Langås
2001-11-01 9:43 ` Juergen Hasch
2001-11-01 11:11 ` Andrey Savochkin
2001-11-01 12:00 ` Thomas Langås
2001-11-01 12:15 ` Juergen Hasch
2001-11-01 13:39 ` Henning P. Schmiedehausen
2001-10-29 10:44 ` Alan Cox
2001-10-29 11:40 ` Michael Rozhavsky
2001-10-29 11:49 ` Alan Cox
2001-10-29 11:45 ` Michael Rozhavsky
2001-10-29 13:52 ` Thomas Langås
2001-10-30 8:36 ` Jarmo Järvenpää
2001-10-30 8:54 ` Dead2 [this message]
2001-10-30 9:02 ` Jarmo Järvenpää
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='008e01c16120$723d6b00$d2c0ecd5@dead2' \
--to=dead2@circlestorm.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.