Upgraded or Live USB 16.10 hangs at boot up blank purple screen

[renm]

My HP dm3z-2000 laptop works out of box for everything with Ubuntu 16.04, but fails to boot up after upgraded to 16.10. The upgrading went smooth itself.

Laptop still can boot up with the latest 4.4 kernel of 16.04 which I did a regular update/upgrade before 16.10 release upgrade.

Then I tried to boot with 16.10 Live USB and got same result.

It also can boot up with kernel 4.8 if "acpi=off" parameter in place, but it takes long time to boot up. Everything seems fine after logged in and Unity 8 session works too.

I couldn't get any log files since the system won't boot up, Ctrl+Alt+F1 does nothing. I can only see some messages in text boot mode, so I took a screen shot with my phone and attached here.

Let me know how to get more details.
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: renm 2918 F.... pulseaudio
 /dev/snd/controlC1: renm 2918 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=UUID=7e8ca036-f81d-43e2-820a-1deadcffc2dc
InstallationDate: Installed on 2016-10-08 (13 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Hewlett-Packard HP Pavilion dm3t Notebook PC
Package: linux (not installed)
ProcFB:
 0 radeondrmfb
 1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=19005996-db50-4249-9c73-17cf874dc678 ro acpi=off
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-22-generic N/A
 linux-backports-modules-4.8.0-22-generic N/A
 linux-firmware 1.161
Tags: yakkety
Uname: Linux 4.8.0-22-generic x86_64
UpgradeStatus: Upgraded to yakkety on 2016-10-15 (6 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/13/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.15
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1482
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 76.34
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.15:bd10/13/2010:svnHewlett-Packard:pnHPPaviliondm3tNotebookPC:pvr0486200000241F00110320000:rvnHewlett-Packard:rn1482:rvr76.34:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion dm3t Notebook PC
dmi.product.version: 0486200000241F00110320000
dmi.sys.vendor: Hewlett-Packard

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1635447/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[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 1635447

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.

[Joseph Salisbury (jsalisbury)]

So does a prior kernel versions for 16.04 that worked fine now also exhibit this bug? But only after upgrading to 16.10?

[renm (renmsa)]

apport information

[renm (renmsa)]

apport information

[renm (renmsa)]

apport information

[renm (renmsa)]

apport information

[renm (renmsa)]

apport information

[renm (renmsa)]

apport information

[renm (renmsa)]

apport information

[renm (renmsa)]

apport information

[renm (renmsa)]

apport information

[renm (renmsa)]

apport information

[renm (renmsa)]

apport information

[renm (renmsa)]

apport information

[renm (renmsa)]

apport information

[renm (renmsa)]

apport information

[renm (renmsa)]

apport information

[renm (renmsa)]

Note: apport data was collected under 16.10/kernel 4.8 with acpi=off boot option.

[renm (renmsa)]

Also attach the demsg info after boot up from the kernel 4.4.0-43 with 16.10 for comparison.

[kjellahl (kjell-ahlstedt)]

This looks very much like what's happening to me.
I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot,
Windows 10 and Ubuntu 16.10.

Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45.
When I try to start with any of the 4.8.0 kernels delivered with regular
Ubuntu updates, they all hang after printing

  Läser in Linux 4.8.0-30-generic ...
  Läser in initial ramdisk ...

Sorry for the partly Swedish text. I guess that the lines would start with
"Loading" instead of "Läser in" on an English version.

The behaviour is the same with all 4.8.0 versions, 4.8.0-26, -27, -28 and -30,
and with -generic, -generic (upstart) and -generic (recovery mode).

After a while the fan runs at full speed, as if the processor is working hard,
but nothing happens.

[kjellahl (kjell-ahlstedt)]

The newest kernel, 4.8.0-32, behaves just like the other 4.8.0 versions.
Ubuntu never starts up.

After I've tried in vain to start with Linux 4.8.0-xx, and then starts
with 4.4.0-45, the following errors are printed:

[ 2.511733] usb 4-3: string descriptor 0 read error: -22
[ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller
/dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks
[ 21.335117] usb 4-3: string descriptor 0 read error: -22

When a successful start has not been immediately preceded by a failed start,
only the line beginning "/dev/sda7" is printed.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 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.10-rc3

[renm (renmsa)]

@Joseph, I've installed v4.10-rc3 via Ukuu and my laptop boots up successfully.

~$ uname -a
Linux chengdu 4.10.0-041000rc3-generic #201701081831 SMP Sun Jan 8 23:33:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Everything seems work normal, even though I noticed some message about b43, but the WIFI works fine too.

~$ dmesg | grep b43
[ 21.933153] Support for cores revisions 0x17 and 0x18 disabled by module param allhwsupport=0. Try b43.allhwsupport=1
[ 21.933350] b43: probe of bcma0:1 failed with error -524

Thank you for your help.

[kjellahl (kjell-ahlstedt)]

Kernel v4.10-rc3 does not boot up for me. Now I've also tested with
acpi=off. Neither v4.10-rc3 nor v4.8.0-34 boots up with acpi=off.
Perhaps my case does not fit in this bug report. It's probably not the
same problem as renm's, although the symptoms are similar.

[Joseph Salisbury (jsalisbury)]

@kjellahl, you may want to open a new bug report.

@renm, thanks for testing. We can perform a "Reverse" bisect to identify the commit that fixes this bug. We first need to identify the last kernel that had the bug and the first kernel version that did not.

Can you test the following kernels:

4.9 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/
4.10-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc1/

[renm (renmsa)]

@Joseph, both versions can boot up properly.

And more, I just found out the latest v4.8.0-34 already can boot up successfully without acpi=off while previous v4.8.0-30 does not.

So looks like that my issue has been fixed in 4.8.0-34.