Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

davehardy20 · 2013-03-18 11:18:28

Since I updated to the kernel 3.8.3-2 x86_64 this morning the ethernet (eth0) has not worked even though it shows up in list with ip link and the driver is loaded.

I can manually setting the ip address and route using ifconfig/route add, but there is no connection.
I normally use wicd, but the adaptor (eth0) doesn't appear in the list of adaptors. Strangely wicd allows me to connect to a wireless connection with no issue.
As a last resort I tried netcfg and it reported 'no connection'

I am using a Lenovo x230 laptop

00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)

Reverting back to kernel 3.7.10-1 fixes the issue

Thanks

Dave

Trilby · 2013-03-18 11:26:09

What do you mean there is no connection when you put it up manually - what are the errors/symptoms? You sould use ip in place of ifconfig, then run dhcpcd or dhclient on eth0:
1) `ip link set eth0 up`
2) `dhcpcd eth0`

Last edited by Trilby (2013-03-18 11:26:32)

davehardy20 · 2013-03-18 12:21:55

After some further troubleshooting I found that dhcpcd was not enabled

systemctl enable dhcpcd

now gives;

dhcpcd.service - dhcpcd on all interfaces
   Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; enabled)
   Active: active (running) since Mon 2013-03-18 12:08:00 GMT; 1min 19s ago
   Process: 1073 ExecStart=/sbin/dhcpcd -q -b (code=exited, status=0/SUCCESS)
Main PID: 1740 (dhcpcd)
   CGroup: name=systemd:/system/dhcpcd.service
   └─1740 /sbin/dhcpcd -q -b

But ip link set eth0 up does not put the interface 'up'

3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT qlen 1000
link/ether 3c:97:0e:29:0a:12 brd ff:ff:ff:ff:ff:ff

so dhcpcd gives

dhcpcd[2241]: sending commands to master dhcpcd process

but no ip address is leased.

mediaserf · 2013-03-18 13:17:25

Same issue, Thinkpad W520. Tried disabling ipv6 but no luck.

Update: Some tips in this Gentoo post: http://forums.gentoo.org/viewtopic-t-94 … art-0.html

Upstream Bug report (may not be quite the same): https://bugzilla.kernel.org/show_bug.cgi?id=52021

Last edited by mediaserf (2013-03-18 13:20:13)

mediaserf · 2013-03-18 13:21:41

This brings up the interface on my Thinkpad W520: echo on > /sys/bus/pci/devices/0000\:00\:19.0/power/control

progandy · 2013-03-18 13:54:44

mediaserf wrote:

This brings up the interface on my Thinkpad W520: echo on > /sys/bus/pci/devices/0000\:00\:19.0/power/control

You could also try to find the device using the symlink instead of searching for the bus address: /sys/class/net/eth0/device/power/control

twouters · 2013-03-18 15:14:33

I've had the same issue earlier.
I deleted /etc/udev/rules.d/80-net-name-slot.rules and after a reboot my network seems to work fine.
But beware, your network interfaces won't have the same name as before. See http://www.freedesktop.org/wiki/Softwar … rfaceNames

ulke · 2013-03-19 09:16:25

Same problem here, Dell Latitude E6420, also after the upgrade to kernel 3.8.3-2. "echo on > /sys/class/net/eth0/device/power/control" fixed it (thanks mediaserf and progandy).

megawebmaster · 2013-03-19 09:47:00

I've got the same problem but with wireless connection - driver is loaded (automatically!), workaround does not work. Broadcom-wl driver does not work either. Card is BCM4322. Anyone having similar issues?

twouters · 2013-03-19 10:02:58

twouters wrote:

I've had the same issue earlier.
I deleted /etc/udev/rules.d/80-net-name-slot.rules and after a reboot my network seems to work fine.
But beware, your network interfaces won't have the same name as before. See http://www.freedesktop.org/wiki/Softwar … rfaceNames

Looks like this didn't help at all. Same issue today.
As suggested, the following does work for me.

echo on > /sys/class/net/$interface/device/power/control

sero · 2013-03-19 10:25:21

echo on > /sys/class/net/eth0/device/power/control

works for me
HP Compaq 6720s

andmars · 2013-03-19 13:29:38

Maybe a bit off topic but I'm wondering why you guys are refering to eth0 since the systemd version 197 brought persistent device names. Or have you disabled that?

https://wiki.archlinux.org/index.php/Ne … vice_names

in my case;

ls /sys/class/net

gives me: enp3s0 and I use dhcpcd with;

systemctl enable dhcpcd@enp3s0(mydevice).service

twouters · 2013-03-19 13:33:17

andmars wrote:

Maybe a bit off topic but I'm wondering why you guys are refering to eth0 since the systemd version 197 brought persistent device names. Or have you disabled that?
https://wiki.archlinux.org/index.php/Ne … vice_names
in my case;
ls /sys/class/net
gives me: enp3s0 and I use dhcpcd with;
systemctl enable dhcpcd@enp3s0(mydevice).service

Yea, the wiki states: "Users upgrading from an earlier systemd version will have a blank rules file created automatically."
I don't think many users have removed that file.

sero · 2013-03-19 13:33:37

In my case

ls /sys/class/net

gives:

eth0  lo  wlan0

andmars · 2013-03-19 14:26:28

sero wrote:

In my case
ls /sys/class/net
gives:
eth0  lo  wlan0

do you have this file on your system?

/etc/udev/rules.d/80-net-name-slot.rules

then remove this file and stop and disable the systemd dhcpdc eth0 service.
with this script you can find out the name of your device;

#!/usr/bin/bash

for i in /sys/class/net/*; do
    echo "==$i"
    udevadm test-builtin net_id "$i";
    echo
done 2>/dev/null

the output looks similar to this;

==/sys/class/net/enp3s0
ID_NET_NAME_MAC=enxf46d049c8367
ID_OUI_FROM_DATABASE=ASUSTek COMPUTER INC.
ID_NET_NAME_PATH=enp3s0

==/sys/class/net/lo

now you can restart the systemd service with the correct name (in my case enp3s0)

ulke · 2013-03-19 14:29:50

andmars, thank you for pointing this out, but this is seems pretty irrelevant to the topic, no? The renaming of interfaces has nothing to do with the kernel bug preventing the interface from going up (no matter what's their name).

andmars · 2013-03-19 14:46:25

ulke wrote:

andmars, thank you for pointing this out, but this is seems pretty irrelevant to the topic, no? The renaming of interfaces has nothing to do with the kernel bug preventing the interface from going up (no matter what's their name).

Fair enough. But I'm on kernel 3.8.3-2, too with dhcpcd@enp3s0.service enabled and my internet connection is up. If systemd 197 wants it that way then maybe you guys should change to the new method first before complaining about eth0 issues. Agreed?

ball · 2013-03-19 15:58:17

@andmars: Thank you very much for your helpful instructions!

I have now these "automatic" device names and my ethernet connection works when enabling & starting dhcpcd@enp0s25.service.

But my previous configuration of net-auto-wired stopped to work. I altered my profile accordingly to the new device name:

CONNECTION='ethernet'
DESCRIPTION='A basic dhcp ethernet connection using iproute'
INTERFACE='enp0s25'
IP='dhcp'

Any ideas why this fails?

ulke · 2013-03-19 16:30:32

@andmars: Apologies are in order. To my surprise, removing /etc/udev/rules.d/80-net-name-slot.rules, enabling dhcpcd.service and rebooting did the trick. The strange thing is I installed systemd 197 back in January, and the problems only started after the update to kernel 3.8.3-2 yesterday.

twouters · 2013-03-19 16:36:58

ulke wrote:

@andmars: Apologies are in order. To my surprise, removing /etc/udev/rules.d/80-net-name-slot.rules, enabling dhcpcd.service and rebooting did the trick. The strange thing is I installed systemd 197 back in January, and the problems only started after the update to kernel 3.8.3-2 yesterday.

I made the same change yesterday, though today I've noticed that the interface was down and had to enable the interface manually.

ball · 2013-03-20 08:05:29

This is strange: After a reboot my newly renamed device does not get any ip address. The trick with echo on > /sys/class/net/enp0s25/device/power/control works though.

twouters · 2013-03-20 08:20:39

seriously, am I invisible or what.

Last edited by twouters (2013-03-21 10:23:54)

ulke · 2013-03-20 08:39:20

Yep, I rejoiced to early. The interface was up after a reboot, but after a suspend-resume cycle, it's down again and had to be woken up manually by the "echo on…" thing.

dext · 2013-03-20 08:45:04

The same on my Thinkpad T61. On Linux LTS works fine.

I don't know, if it's relevant, but I have some dmesg output on Linux 3.8.3-2

[   28.638901] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X
[   28.740140] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X
[   28.740266] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   33.821317] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X
[   33.958571] e1000e 0000:00:19.0 eth0: MAC Wakeup cause - Link Status Change
[   40.777156] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X
[   40.880141] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X
[   40.880315] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

davehardy20 · 2013-03-21 10:21:42

I have followed the various instructions from above

removed the udev rule
enable the dhcpcd service etc
and following a reboot I still have to bring up the interface with echo on > /sys/class/net/enp0s25/device/power/control
before it will respond.

I tried this setup with the 3.7.10 kernel and it worked fine without the echo on > /sys/class/net/enp0s25/device/power/control command

Must be a bug with kernel 3.8.3-2 kernel.

Arch Linux

#1 2013-03-18 11:18:28

Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#2 2013-03-18 11:26:09

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#3 2013-03-18 12:21:55

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#4 2013-03-18 13:17:25

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#5 2013-03-18 13:21:41

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#6 2013-03-18 13:54:44

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#7 2013-03-18 15:14:33

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#8 2013-03-19 09:16:25

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#9 2013-03-19 09:47:00

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#10 2013-03-19 10:02:58

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#11 2013-03-19 10:25:21

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#12 2013-03-19 13:29:38

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#13 2013-03-19 13:33:17

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#14 2013-03-19 13:33:37

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#15 2013-03-19 14:26:28

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#16 2013-03-19 14:29:50

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#17 2013-03-19 14:46:25

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#18 2013-03-19 15:58:17

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#19 2013-03-19 16:30:32

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#20 2013-03-19 16:36:58

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#21 2013-03-20 08:05:29

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#22 2013-03-20 08:20:39

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#23 2013-03-20 08:39:20

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#24 2013-03-20 08:45:04

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

#25 2013-03-21 10:21:42

Re: Ethernet (eth0) broken after upgrade to kernel 3.8.3-2

Board footer