Bug 243767 - NetworkManager believes tg3 interface is up even though cable is unplugged
NetworkManager believes tg3 interface is up even though cable is unplugged
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
7
i386 Linux
low Severity low
: ---
: ---
Assigned To: Dan Williams
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-06-11 15:17 EDT by Benny Amorsen
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-11-02 06:59:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Cut from /var/log/messages (9.94 KB, text/plain)
2007-06-11 15:17 EDT, Benny Amorsen
no flags Details

  None (edit)
Description Benny Amorsen 2007-06-11 15:17:08 EDT
Description of problem:

When I boot my laptop, an HP nx8220 --
http://smolt.fedoraproject.org/show?UUID=bca3bdcf-1263-4846-bcb6-a38c8ff7a5c7
-- NetworkManager detects that the eth0 interface has link, even though it
actually doesn't (no cable plugged in). Therefore it fails to switch to the
wireless network.

Version-Release number of selected component (if applicable):
NetworkManager-0.6.5-3.fc7


How reproducible:

Every boot
Comment 1 Benny Amorsen 2007-06-11 15:17:08 EDT
Created attachment 156749 [details]
Cut from /var/log/messages
Comment 2 Dan Williams 2007-10-31 20:59:38 EDT
Can you test with the latest kernel?  Also, when the cable is _un_plugged, can
you give the output of:

cat /sys/class/net/eth0/carrier

and 

cat /sys/class/net/eth1/carrier
Comment 3 Benny Amorsen 2007-11-01 17:49:01 EDT
The problem does not exist in kernel-2.6.23.1-41.fc8. The problem has been gone
for a while even in F7-kernels, but I am not sure exactly which kernel fixed it.
Comment 4 Dan Williams 2007-11-02 06:59:45 EDT
ok, thanks

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