| Summary: | Ethernet driver missing in 3.2 kernel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tom <thomasbelvin> | ||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | rawhide | CC: | dcbw, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2011-11-03 13:00:10 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
Tom
2011-10-31 17:32:07 UTC
Which specific module is this? Can you run lsmod on the working kernel and tell me which is missing in 3.2? There was some change in how the ethernet drivers are organized, so perhaps that switch left it disabled. Created attachment 531119 [details]
lsmod output for 3.1 and 3.2 kernels
Unsure which module, since same modules loaded for both. Well, the driver doesn't appear to actually be missing then. Looks like the tg3 driver would be for ethernet. Perhaps it's not binding to the device for some reason. Can you attach the boot logs from both the 3.1 and 3.2 kernels as well? Created attachment 531262 [details]
dmesg output for both kernels
(In reply to comment #5) > Created attachment 531262 [details] > dmesg output for both kernels Hm. So the driver binds to the device just fine, it's just that NM doesn't seem to do anything with it. Not sure why that would be the case. What does 'sudo ethtool eth0' show? Can you manually bring eth0 up if you disable NM? e.g. sudo service NetworkManager stop sudo ifconfig eth0 up Dan, do you have any tips for what to do next? Nothing for eth0, but for p4p1:
[root@computer]# ethtool p4p1
Settings for p4p1:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Speed: Unknown!
Duplex: Unknown! (255)
Port: MII
PHYAD: 1
Transceiver: external
Auto-negotiation: on
Supports Wake-on: g
Wake-on: g
Current message level: 0x000000ff (255)
drv probe link timer ifdown ifup rx_err tx_err
Link detected: no
I can't manually bring network back up with:
sudo service NetworkManager stop
sudo ifconfig p4p1 up
Ethernet works for me again in today's update to 3.2.0-0.rc0.git4.1.fc17.x86_64 Created attachment 531505 [details]
dmesg for 3.2.0-0.rc0.git4.1
OK, thanks for letting us know. We have another report of ethernet coming back for someone with that kernel as well, so it seems some general issue was fixed upstream. Closing this out. If you see it again with future kernels, please reopen. |