Bug 133832 - e1000 lock ups on Dell Precision 650
Summary: e1000 lock ups on Dell Precision 650
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 3
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks: FC3Target FC4Target
TreeView+ depends on / blocked
 
Reported: 2004-09-27 19:58 UTC by Thomas J. Baker
Modified: 2015-01-04 22:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-07-15 18:03:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Thomas J. Baker 2004-09-27 19:58:22 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040926
Firefox/0.10

Description of problem:
Just updated my main desktop to FC3T2 for real world testing and am
seeing this repeatedly:

Sep 27 15:39:49 wintermute kernel: NETDEV WATCHDOG: eth0: transmit
timed out
Sep 27 15:39:50 wintermute kernel: e1000: eth0: e1000_watchdog: NIC
Link is Up 100 Mbps Full Duplex


[root@wintermute etc]# ethtool -i eth0
driver: e1000
version: 5.3.19-k2-NAPI
firmware-version: N/A
bus-info: 0000:03:0e.0
[root@wintermute etc]#


Version-Release number of selected component (if applicable):
kernel-smp-2.6.8-1.541

How reproducible:
Sometimes

Steps to Reproduce:
1. Install FC3T2
2. Use network
3.
    

Additional info:

Comment 1 Dave Jones 2005-07-15 17:45:11 UTC
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'.

Thank you.

Comment 2 Thomas J. Baker 2005-07-15 18:03:30 UTC
The person who now has this system has upgraded to FC4 and doesn't seem to have
the problem so I'm calling it good.


Note You need to log in before you can comment on or make changes to this bug.