Directly after boot there is no network

[Steven]

When doing a cold boot from a full power off, or a soft reboot, after gnome loads, I have no Internet connections. This happens without fail after every cold boot and intermittently after a soft reboot.

It has occurred since ubuntu desktop 14.04 all the way up to 16.04. I only use kernels that is provided by unbuntu and only when the system tells me there is an update to them. I have no custom drivers installed, all drivers are from the kernel minus the nivida drivers, but it does this even when i dont use the proprietary drivers from nvidia.

The fix for the problem is to soft reboot multiple times until it corrects itself. I have done many search's and tried several options, none have corrected the problem.

Im currently using ubuntu desktop 16.04 (gnome)

below is a copy of dmesg from one of the network failed boots. Let me know if there is anything else I can provide to assist.

http://pastebin.com/84mqSUuW

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-22-generic 4.4.0-22.40
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: sysx 1813 F.... pulseaudio
 /dev/snd/controlC0: sysx 1813 F.... pulseaudio
CurrentDesktop: GNOME
Date: Thu May 19 00:09:47 2016
HibernationDevice: RESUME=UUID=73058683-1e8a-4e97-9b1b-e34e7f4a5511
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=ede95eeb-fd81-4883-bfe1-6d2cb0567e66 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic N/A
 linux-firmware 1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/24/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 990FXA-UD5
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd06/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety

[Steven (gunn-steven)]

I do not recall encountering the problem with kernel 3.13 on Ubuntu 14.04, I want to say that it was happening after 3.16, but that was some time ago so I may be mistaken there.

I will install 4.6 tonight and report back with my findings.

Also, I forgot to mention that my bios is up-to-date with current stable firmware, as are all other hardware that I have that can be updated.

[Steven (gunn-steven)]

As requested, I used kernel 4.6 generic and problem still happens.

[Roberto (roberto-arro)]

I have the same problem.
I added "systemctl restart NetworkManager.service¨ to "/etc/rc.local" to solv it temporarily

[Steven (gunn-steven)]

I tried Roberto's temp fix, this did not resolve my problem. also tried it with networking instead of networkmanager. No dice.

I did however save the entire apport output to a file during the last time it did this to me, it may help more then the output that was sent with the initial bug report as I sent that when the network was working. (didn't know I could save the output.)

please see the attached file (bug).

[penalvch (penalvch)]

Steven, could you please test the latest mainline kernel (4.7-rc1) and advise to the results?

[Steven (gunn-steven)]

Christopher,

I attempted to install 4.7, install failed related to:

https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1573508

Attempted boot regardless, as expected failed and exit to ASH during boot.

I will remove 4.7 and change to open video card drivers and attempt again.

[Steven (gunn-steven)]

Christopher,

After removing 4.7, and Nvidia drivers, then reinstalling 4.7. the result is similar. While I did not get an error during install, the boot failed with an exit the ASH. From what I gathered, The only thing displayed was something about AMD-VI with a bunch of hex codes on many lines. Stated that it was done waiting on root and asked if it was looking for the correct device, then listed the main SSD's UID.

[penalvch (penalvch)]

Steven, as an alternative, would the next most recent kernel (4.6.1) provide a testable environment?

[Steven (gunn-steven)]

Christopher,

Removing Nvidia and AMD microcode got me bootable on mainline. I tried, 4.6.1, 4.6rc7, 4.7rc1, 4.7rc2. Each hand different errors and crashes for unrelated things, however each did not resolve network issues. DMESG was roughly the same as previous, minus the addition of not having AMD microcode errors.

I attempted to get apport report, however since they were all mainline kernels, apport refused to generate the report for me.

[penalvch (penalvch)]

Steven, the next step is to fully commit bisect from kernel 3.13 to 4.4 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

After the offending commit (not kernel version) has been identified, then please mark this report Status Confirmed.

Thank you for your understanding.

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

[Steven (gunn-steven)]

Chris,

Sorry it has taken me sometime to get to this.

I started working towards finding a kernel that does not have my problem. I must have been mistaken on what version I thought did not do this. as every mainline or Ubuntu kernel from 3 up to 4.7 I have this issue with. Some are worse then others. I cant get you a commit as i cannot find a kernel it does not happen in.

On that note. Ubuntu has pushed 4.4.0-24 and 28. 28 occurs every boot, as 24 is only every few. 22 seems to be the most stable as it only happens one out of every 15 boots.

Ideas?

[penalvch (penalvch)]

Steven, could you please attach (not pastebin) untarred/uncompressed an example dmesg when this issue occurs?

[Steven (gunn-steven)]

Chris,

Attached as requested. It is from May. But kernel and drivers are same.