Bug 750319 - Ethernet driver missing in 3.2 kernel
Summary: Ethernet driver missing in 3.2 kernel
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-31 17:32 UTC by Tom
Modified: 2011-11-03 13:00 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-03 13:00:10 UTC
Type: ---


Attachments (Terms of Use)
lsmod output for 3.1 and 3.2 kernels (6.52 KB, text/plain)
2011-11-01 12:28 UTC, Tom
no flags Details
dmesg output for both kernels (146.05 KB, text/plain)
2011-11-02 06:48 UTC, Tom
no flags Details
dmesg for 3.2.0-0.rc0.git4.1 (74.48 KB, text/plain)
2011-11-03 08:02 UTC, Tom
no flags Details

Description Tom 2011-10-31 17:32:07 UTC
Description of problem:
Upgraded from kernel 3.1 to 3.2, and ethernet driver is missing.

Version-Release number of selected component (if applicable):
Ethernet driver in 3.1.0-0.rc10.git0.1.fc17.x86_64 works, and driver in  3.2.0-0.rc0.git2.0.fc17 is missing.


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:
Ethernet driver in Acer 5552G laptop doesn't work and doesn't show in ifconfig.
Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe

Expected results:
Ethernet works and shows in ifconfig

Additional info:

Comment 1 Josh Boyer 2011-10-31 18:45:15 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.

Comment 2 Tom 2011-11-01 12:28:16 UTC
Created attachment 531119 [details]
lsmod output for 3.1 and 3.2 kernels

Comment 3 Tom 2011-11-01 12:29:24 UTC
Unsure which module, since same modules loaded for both.

Comment 4 Josh Boyer 2011-11-01 14:08:59 UTC
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?

Comment 5 Tom 2011-11-02 06:48:34 UTC
Created attachment 531262 [details]
dmesg output for both kernels

Comment 6 Josh Boyer 2011-11-02 11:58:05 UTC
(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?

Comment 7 Tom 2011-11-03 04:31:43 UTC
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

Comment 8 Tom 2011-11-03 08:00:15 UTC
Ethernet works for me again in today's update to 3.2.0-0.rc0.git4.1.fc17.x86_64

Comment 9 Tom 2011-11-03 08:02:17 UTC
Created attachment 531505 [details]
dmesg for 3.2.0-0.rc0.git4.1

Comment 10 Josh Boyer 2011-11-03 13:00:10 UTC
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.


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