Bug 816719
| Summary: | driver 'ne2k-pci' does not support carrier detection | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andy Pengelly <apengelly> | ||||
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 17 | CC: | danw, dcbw, jklimes | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-08-01 20:05:37 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Andy Pengelly
2012-04-26 19:16:26 UTC
Created attachment 580559 [details]
Ensure carrier is always on for devices incapable of carrier detection
danw/jklimes: does this look OK? Comment on attachment 580559 [details] Ensure carrier is always on for devices incapable of carrier detection looks sane >+ if (caps & NM_DEVICE_CAP_CARRIER_DETECT) >+ carrier = get_carrier_sync (NM_DEVICE_WIRED (dev)); >+ else { >+ /* Carrier is always on for devices incapable of carrier detect */ >+ carrier = TRUE; >+ } >+ > set_carrier (NM_DEVICE_WIRED (dev), carrier, carrier ? FALSE : TRUE); it looks like there's no way for priv->carrier to ever end up FALSE on a non-CAP_CARRIER_DETECT device now, so you could just move the set_carrier call inside the if body, and remove the else clause Fixed upstream as a091c7aa0f15ca2eb7a0c3d3e99405aa98855965 NetworkManager-0.9.4.0-8.git20120502.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/NetworkManager-0.9.4.0-8.git20120502.fc17 Package NetworkManager-0.9.4.0-8.git20120502.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing NetworkManager-0.9.4.0-8.git20120502.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-7066/NetworkManager-0.9.4.0-8.git20120502.fc17 then log in and leave karma (feedback). This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This problem is still present in F17, NetworkManager-0.9.6.4-3.fc17.i686 The log now reads: Mar 10 00:19:24 trinity NetworkManager[597]: <info> Networking is enabled by state file Mar 10 00:19:24 trinity NetworkManager[597]: <warn> failed to allocate link cache: (-10) Operation not supported Mar 10 00:19:24 trinity NetworkManager[597]: <info> (p5p1): driver 'ne2k-pci' does not support carrier detection. Mar 10 00:19:24 trinity NetworkManager[597]: <info> (p5p1): new Ethernet device (driver: 'ne2k-pci' ifindex: 2) Mar 10 00:19:24 trinity NetworkManager[597]: <info> (p5p1): exported as /org/freedesktop/NetworkManager/Devices/0 Mar 10 00:19:24 trinity NetworkManager[597]: <info> (p5p1): now managed Mar 10 00:19:24 trinity NetworkManager[597]: <info> (p5p1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Mar 10 00:19:24 trinity NetworkManager[597]: <info> (p5p1): bringing up device. Mar 10 00:19:24 trinity NetworkManager[597]: <info> (p5p1): preparing device. Mar 10 00:19:24 trinity NetworkManager[597]: <info> (p5p1): deactivating device (reason 'managed') [2] Mar 10 00:19:24 trinity NetworkManager[597]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring... Mar 10 00:19:24 trinity NetworkManager[597]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring... Mar 10 00:19:24 trinity NetworkManager[597]: <info> (p5p1): device state change: unavailable -> disconnected (reason 'none') [20 30 0] Mar 10 00:19:24 trinity dbus[676]: [system] Successfully activated service 'org.freedesktop.ModemManager' Mar 10 00:19:24 trinity NetworkManager[597]: <info> modem-manager is now available The interface can be brought up with: sudo ifup p5p1 This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |