Network interfaces not working with kernel 3.13.0-24-generic

This change was made by a bot.

Erik - we really need the dmesg from the 3.13 kernel.

I see the following in the dmesg for 3.13, but I don't see this message in teh 3.11 dmesg:

[ 2.654869] systemd-udevd[184]: renamed network interface eth1 to em2

Can you test the latest mainline kernel, just to see if this was already fixed upstream? It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc2-trusty/

I actually already tried that earlier, hence the tag 'kernel-bug-exists-upstream'.

Looks like some interface naming shennanigans. Please attach the output of 'ifconfig -a', /etc/network/interfaces, any files under /etc/udev/rules.d (if any exist), and /etc/udev/rules.d/70-persistent-net.rules (if it exists).

And with the 3.13 kernel

Erik Nasaroff, the next step would be to fully commit bisect from 13.10 to 14.10, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.

Can you test the following kernels and report back? We are looking for the first kernel version that exhibits this bug:

v3.12 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/
If v3.12 final does not exhibit the bug, we should move on to testing some of the v3.13 release candidates.

v3.13-rc3: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc3-trusty/

If v3.13-rc3 does not exhibit the bug then test v3.13-rc6:
v3.13-rc6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc6-trusty/

If v3.13-rc3 does exhibit the bug then test v3.13-rc2:
v3.13-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc2-trusty

You don't have to test every kernel, just up until the kernel that first has this bug.

Thanks in advance!

Sorry, I've been a bit busy.

Christopher, do you mean that I should install 13.10, 14.04 and 14.10?

Joseph, v3.12 final does not work.

As a side note, adding 'GRUB_CMDLINE_LINUX="biosdevname=0"' to /etc/default/grub and running update-grub makes (at least) 3.13.0-24 work.

Can you next give the 3.12-rc1 kernel a test, to see if this bug was introduced by one of the 3.12 release candidates? 3.12-rc1 can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc1-saucy/

3.12-rc1 gets stuck on "Loadin initial ramdisk ..."

Same thing with rc2 and rc3.

The fact that the 3.12 rc candidates wont boot will make it a little difficult to bisect.

Can you see if one of the newer release candidates eventually fixes the "Loading initial ramdisk" issue, then see if it has the original bug?

I just tried all the 3.12 rc kernels and all of them failed to boot.

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

  With the recent release of this Ubuntu release, would like to confirm if this bug is still present. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Still exists in 3.13.0-29.

Erik - perhaps the simplest workaround is to change the name of your network interfaces. For example,

sudo sed -i '/exit 0/d' /etc/rc.local
echo "ip link set dev em1 name eth0" | sudo tee -a /etc/rc.local
echo "ip link set dev em2 name eth1" | sudo tee -a /etc/rc.local
echo "exit 0" | sudo tee -a /etc/rc.local

Can you apply the latest updates and see if this bug still exists?

Still not working with 3.13.0-35.

The problem exists on both 3.13 (Trusty) and 3.16 Unicorn. I tried it on a T60 I tried to installl Ubuntu.

Here's an attachement

Theodotos Andreou, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Erik Nasaroff, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-utopic/ and advise to the results?

I am not sure what you mean by default vs mainline. Should I file the bug using the affected computer or another working one?

I can file a new bug if that's necessary but I am not sure if you are going to get the correct information since I patched it using this hairy hack here:

http://ubuntuforums.org/showthread.php?t=1276211&page=4&p=8021944#post8021944

Should I file the bug anyway?

Theodotos Andreou:
>"Should I file the bug anyway?"

Yes. If you have further questions, please let us not use this bug report further as a support forum. Instead, please contact me directly.

Here's the new bug report:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1378690

Tested with 3.17.0-031700-generic, same situation.

Erik Nasaroff, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc1-utopic/ and advise to the results?

Tested with 3.18-rc1, did not help.

Erik Nasaroff, just to clarify, if you test the latest 3.11 kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.10.15-saucy/ is the problem reproducible?

Hangs on "Loading initial ramdisk ..."

Erik Nasaroff, the issue you are reporting is an upstream one. Could you please report this problem to the appropriate mailing list by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked.

Thank you for your understanding.