Red Hat Bugzilla – Bug 150220
intel e100 driver drops out regularly
Last modified: 2007-11-30 17:11:01 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6)
Gecko/20050224 Firefox/1.0.1 Fedora/1.0.1-1.3.1
Description of problem:
Regularly the e100 driver stops functioning. The NETDEV WATCHDOG has
to come in and reset the driver/card.
It seems to behave correct under Windows 2k. Also does it seems to
behave correct when connected to a 100Mbit/Full-duplex line. I'm
usally on 10Mbit/Half-duplex.
I've had this problem before years ago (+-3 year), but then the
problem was solved by using the e100 driver instead of the eepro100.
At this moment the eepro100 doesn't work at all and constantly gives
wait_for_cmd_done timeout errors.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot the machine
2. Do some network related activity
3. Wait a while, sometimes it takes longer than other times before it
4. The card stops functioning and a few seconds later it's resetten by
the kernel and it works again.
Actual Results: A temporary loss of connection
Expected Results: No loss of connection
Toshiba satellite pro 4600
intel etherexpress 100
Created attachment 111636 [details]
Kernel log of a e100 drop out
I believe that I am experiancing a similar bug. When attempting to play a mythtv
recording from a remote machine the e100 driver will crash. The differenct
appears to be that the network does not work after the network watchdog brings
it back up.
The machine is a Toshiba satellite 2805-s402 and the network card is a intel
Created attachment 114277 [details]
kernel log of an e100 driver crash
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
The problem had somewhat faded to a less-frequent case lately. With this new
kernel it seems to have dissapeared.
If it comes back, then I will let you know.
I'm in the planning of installing FC4, so I'll update this record appropriately
Seems I was just a few hours to early. It just droppped out again. Leaving only
the following message:
kernel: e100: eth0: e100_watchdog: link up, 10Mbps, half-duplex
I'm sorry for any inconvinience from my last post.
Maybe bad device? Or trable at "sleep mode". I have same device, but have not
problems with it.
Could you post the output from `lsmod` and a complete `dmesg -s`?
Created attachment 120562 [details]
Output of lsmod and dmesg command
Per request I've updated to version fieldto FC4, since I'm running FC4 now and
the problem has remained.
I think you may have a similar issue as bug 172067. Everyone affected by this
seems to be using toshiba satellite notebooks.
Could you try the `echo 3 >/proc/acpi/sleep` and wake to reproduce the bug?
I don't necessarily advise people to try the rmmod trick from 172067. I've
corrupted my filesystem before by rmmodding network drivers and modprobing new
Tried the echo trick, but ethernet works fine before and after that. I'll try
some mouse movement when the card malfunctions. All I got was a nice kernel
stacktrace for an illegal context in slab.c.
Mass update to all FC4 bugs:
An update has been released (2.6.14-1.1637_FC4) which rebases to a new upstream
kernel (18.104.22.168). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.
Please retest with this update, and update this bug if necessary.
Closed due to lack of response. Please reopen when the requested information