[Asus P8Z77-V DELUXE] Kernel upgrade to 3.16.0-28 causes boot hang on my system

[Soren Mogensen]

Under Ubuntu 14.10, I installed the latest kernel 3.16.0-28 and after reboot my system won't boot - result is blank screen. No console from ctrl+alt+fX.

Re-installed from 14.10 install media, choosing do-not-install-updates, and found that strangely this still resulted in 3.16.0-28 being installed - and thus same boot hang.

System boots fine with earlier kernel version (3.16.0-23).

I tried the 'ubuntu-bug linux' console command to report a bug with the kernel - however, this gathers information about the running (working) kernel 3.16.0-23 rather than the broken 3.16.0-28.

Will attach screenshot of output of text error during boot.
---
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: soren 2355 F.... pulseaudio
 /dev/snd/controlC1: soren 2355 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=0e328329-6f3c-4967-a46e-9f695c6dd970
InstallationDate: Installed on 2014-12-12 (0 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
IwConfig:
 eth0 no wireless extensions.

 eth1 no wireless extensions.

 lo no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=3347210c-8dee-4b0b-a67c-fb900809ae6f ro quiet splash
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-23-generic N/A
 linux-backports-modules-3.16.0-23-generic N/A
 linux-firmware 1.138
RfKill:

Tags: utopic
Uname: Linux 3.16.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 02/24/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V DELUXE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd02/24/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Soren Mogensen (soren-mogensen)]

Attached output from 'sudo lspci -vnvn > lspci-vnvn.log'

[Soren Mogensen (soren-mogensen)]

Changed to specific kernel version package.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1401943

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Soren Mogensen (soren-mogensen)]

apport information

[Soren Mogensen (soren-mogensen)]

apport information

[Soren Mogensen (soren-mogensen)]

apport information

[Soren Mogensen (soren-mogensen)]

apport information

[Soren Mogensen (soren-mogensen)]

apport information

[Soren Mogensen (soren-mogensen)]

apport information

[Soren Mogensen (soren-mogensen)]

apport information

[Soren Mogensen (soren-mogensen)]

apport information

[Soren Mogensen (soren-mogensen)]

apport information

[Soren Mogensen (soren-mogensen)]

apport information

[Soren Mogensen (soren-mogensen)]

apport information

[Soren Mogensen (soren-mogensen)]

apport information

[Soren Mogensen (soren-mogensen)]

apport information

[Soren Mogensen (soren-mogensen)]

apport information

[Soren Mogensen (soren-mogensen)]

Just to confirm - apport collected information refers to 3.16.0-23 - there is no issue with this kernel version. The problem is specific to 3.16.0-28. But since that version fails during boot it is not possible to collect the apport information for the broken version.

[penalvch (penalvch)]

Soren Mogensen, thank you for reporting this and helping make Ubuntu better. As per http://www.asus.com/Motherboards/P8Z77V_DELUXE/HelpDesk_Download/ an update to your BIOS is available (2104). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, then please mark this report Status Confirmed.

Thank you for your understanding.

[Soren Mogensen (soren-mogensen)]

Hi Christopher, thanks for getting back to me.

I have updated the BIOS - the output from 'sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date' is:
2104
08/13/2013

Apart from making it hard to get into the grub menu, the BIOS upgrade didn't seem to change much - I still end up with a kernel panic for kernel 3.16.0-28. HOWEVER, found that if I boot into 3.16.0-28 recovery mode, and then resume normal boot, then this kernel panic does not occur (however, graphics resolution is severely reduced).

Attached is a new screenshot of the text output during boot when hung (this time after BIOS upgrade).

[penalvch (penalvch)]

Soren Mogensen, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested exactly shown as:
kernel-fixed-upstream-3.18

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Soren Mogensen (soren-mogensen)]

I tested with the most recent 3.16 upstream kernel (3.16.7 from 201410301735), and my system boots correctly with this kernel.
Thank you for your help!

[penalvch (penalvch)]

Soren Mogensen, the next step is to fully reverse commit bisect from kernel 3.16 to 3.16.7 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ? Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

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

[Soren Mogensen (soren-mogensen)]

Christopher, I have now gone through and tested the upstream kernels 3.16.7, 3.16.4, 3.16.2, 3.16.1, and 3.16.0 - and they all work fine. I.e. I cannot find a bad kernel in the upstream archive. It seems to only be 3.16.0-28 that is failing on my system.

Let me know if you need me to test anything else - but with only good kernels in the upstream archive, I am not sure how to proceed.

[penalvch (penalvch)]

Soren Mogensen, it appears that the issue you are facing is either due to a specific combination of commits, and/or out-of-tree commits. Hence, this would be a downstream issue for the Ubuntu Kernel Team to review. I'll mark it Triaged for now.

[Tommy_CZ (t-kijas)]

Hi, same situation with kernel 3.13.0-43 in Ubuntu 14.04.1, black screen, cannot switch to tty - version before upgrade works OK.
3.16.0-28 - the bug is still here.
The new version of kernel 3.13.0-43 is being installed automatically during installation of Ubuntu 14.04 and makes the Ubuntu unusable.

[penalvch (penalvch)]

Tommy_CZ, thank you for your comment. So your problem and hardware 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
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
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

[Joseph Salisbury (jsalisbury)]

Can you see if this bug also happens with the 3.16..7-ckt1 kernel:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.7-ckt1-utopic/

That is the upstream kernel 3.16.0-28 is based on.

[Soren Mogensen (soren-mogensen)]

Joseph, I have now tested with both 3.16.7-ckt1 and 3.16.7-ckt2:

3.16.7-ckt1 exhibits the same issue as 3.16.0-28 - i.e. hang at boot.

3.16.7-ckt2 does not have the issue - i.e. it appears to have been fixed after 3.16.7-ckt1.

[Soren Mogensen (soren-mogensen)]

Not sure if it adds anything - but tested this mornings update to 3.16.0-28 (3.16.0-28.38) - and the issue has not been fixed, so am back to running 3.16.7-ckt2 on my system.

[William (wnyessen)]

Same on my Ubuntu 14.10 system right after upgrade to kernel version 3.16.0-28. The earlier version (3.16.0-25) boots just fine. Will be reverting back to the early version for now.

[Joseph Salisbury (jsalisbury)]

Utopic will pick up the fix when it gets the 3.16.7-ckt2 updates. Those updates have now been applied to the -proposed repository. Would it be possible for you to test this latest kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.

Thank you in advance!

[Soren Mogensen (soren-mogensen)]

I can confirm that this is indeed fixed in 3.16.0-29!

$ uname -r
3.16.0-29-generic

Thanks!

[Rolf Leggewie (r0lf)]

utopic has seen the end of its life and is no longer receiving any updates. Marking the utopic task for this ticket as "Won't Fix".