Bug 236956 - e1000 carrier detect doesn't work on X60s
e1000 carrier detect doesn't work on X60s
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
6
All Linux
medium Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
:
Depends On:
Blocks: 427887
  Show dependency treegraph
 
Reported: 2007-04-18 13:26 EDT by Dan Williams
Modified: 2008-02-07 23:25 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-02-07 23:25:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Dan Williams 2007-04-18 13:26:34 EDT
FC6 kernel 2.6.20-1.2944 Xen

8086:109a

"Intel 82573L Gigabit Ethernet controller"

Didn't work with original FC6 kernel either (2.6.18 something).

/sys/class/eth0/carrier _always_ contains 1, even if a cable is unplugged.
Comment 1 Dan Williams 2007-04-18 13:27:29 EDT
Thinkpad X60s I mean.
Comment 2 Bryan O'Sullivan 2007-06-21 01:43:02 EDT
Also doesn't work with kernel-2.6.21-1.3228.fc7.x86_64.

Symptoms are as follows.

If I boot with a live ethernet cable plugged in, everything works.

Boot without one plugged in, and carrier will not subsequently be detected.

A workaround of sorts is to rmmod and modprobe the e1000 driver, but this causes
subsequent attempts to suspend to disk to fail (see bug 245107).
Comment 3 Andy Shevchenko 2007-08-19 02:58:35 EDT
Last shipped 2.6.20 kernel works fine on my x60s.
Also I try with last official FC6 update.

But I havn't try to play with suspend functions.
Comment 4 Jon Stanley 2008-01-07 20:48:05 EST
(This is a mass-update to all current FC6 kernel bugs in NEW state)

Hello,

I'm reviewing this bug list as part of the kernel bug triage project, an attempt
to isolate current bugs in the Fedora kernel.

http://fedoraproject.org/wiki/KernelBugTriage

I am CC'ing myself to this bug, however this version of Fedora is no longer
maintained.

Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.

Thanks for using Fedora!
Comment 5 Jon Stanley 2008-02-07 23:25:37 EST
Per the previous comment in this bug, I am closing it as INSUFFICIENT_DATA,
since no information has been lodged for over 30 days.

Please re-open this bug or file a new one if you can provide the requested data,
and thanks for filing the original report!

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