[AMD]Power-off/reboot stalls = no tty on Kernel 4.9.0.x

Bug #1648524 reported by Mikemecanic
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
High
Unassigned
Zesty
Fix Released
High
Unassigned

Bug Description

I’m able to build and run custom Kernel if and only if I don’t shutdown or reboot. Otherwise, the process ends in a dead screen CRTL+ALT+xyz has no effect. Works fine up to Kernel 4.8.12. Apport is not showing anything.
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.10
InstallationDate: Installed on 2016-12-04 (4 days ago)
InstallationMedia: Ubuntu-Kylin 16.10 "Yakkety Yak" - Alpha amd64 (20161010)
Package: linux (not installed)
Tags: yakkety
Uname: Linux 4.8.12-040812-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: yy 1973 F.... pulseaudio
 /dev/snd/controlC0: yy 1973 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=UUID=59eb0b0f-016e-4fe4-85c5-6ec5d5e83bab
InstallationDate: Installed on 2016-12-04 (4 days ago)
InstallationMedia: Ubuntu-Kylin 16.10 "Yakkety Yak" - Alpha amd64 (20161010)
MachineType: HP 24-b019
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-9-generic root=/dev/mapper/ubuntu--kylin--vg-root ro locale=zh_CN quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.9.0-9.10-generic 4.9.0-rc8
RelatedPackageVersions:
 linux-restricted-modules-4.9.0-9-generic N/A
 linux-backports-modules-4.9.0-9-generic N/A
 linux-firmware 1.161.1
Tags: yakkety
Uname: Linux 4.9.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/25/2016
dmi.bios.vendor: AMI
dmi.bios.version: F.02
dmi.board.asset.tag: 8CC6351M4W
dmi.board.name: 81B8
dmi.board.vendor: HP
dmi.board.version: 0100
dmi.chassis.asset.tag: 8CC6351M4W
dmi.chassis.type: 13
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
dmi.product.name: 24-b019
dmi.sys.vendor: HP
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.10
InstallationDate: Installed on 2016-12-04 (4 days ago)
InstallationMedia: Ubuntu-Kylin 16.10 "Yakkety Yak" - Alpha amd64 (20161010)
Package: linux (not installed)
Tags: yakkety
Uname: Linux 4.9.0-040900rc8-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: yy 1917 F.... pulseaudio
 /dev/snd/controlC0: yy 1917 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=UUID=59eb0b0f-016e-4fe4-85c5-6ec5d5e83bab
InstallationDate: Installed on 2016-12-04 (4 days ago)
InstallationMedia: Ubuntu-Kylin 16.10 "Yakkety Yak" - Alpha amd64 (20161010)
MachineType: HP 24-b019
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-10-generic root=/dev/mapper/ubuntu--kylin--vg-root ro locale=zh_CN quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.9.0-10.11-generic 4.9.0-rc8
RelatedPackageVersions:
 linux-restricted-modules-4.9.0-10-generic N/A
 linux-backports-modules-4.9.0-10-generic N/A
 linux-firmware 1.161.1
Tags: yakkety
Uname: Linux 4.9.0-10-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/25/2016
dmi.bios.vendor: AMI
dmi.bios.version: F.02
dmi.board.asset.tag: 8CC6351M4W
dmi.board.name: 81B8
dmi.board.vendor: HP
dmi.board.version: 0100
dmi.chassis.asset.tag: 8CC6351M4W
dmi.chassis.type: 13
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
dmi.product.name: 24-b019
dmi.sys.vendor: HP
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: yy 1940 F.... pulseaudio
 /dev/snd/controlC0: yy 1940 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=UUID=59eb0b0f-016e-4fe4-85c5-6ec5d5e83bab
InstallationDate: Installed on 2016-12-04 (4 days ago)
InstallationMedia: Ubuntu-Kylin 16.10 "Yakkety Yak" - Alpha amd64 (20161010)
MachineType: HP 24-b019
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-10-generic root=/dev/mapper/ubuntu--kylin--vg-root ro locale=zh_CN quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.9.0-10.11-generic 4.9.0-rc8
RelatedPackageVersions:
 linux-restricted-modules-4.9.0-10-generic N/A
 linux-backports-modules-4.9.0-10-generic N/A
 linux-firmware 1.161.1
Tags: yakkety
Uname: Linux 4.9.0-10-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/25/2016
dmi.bios.vendor: AMI
dmi.bios.version: F.02
dmi.board.asset.tag: 8CC6351M4W
dmi.board.name: 81B8
dmi.board.vendor: HP
dmi.board.version: 0100
dmi.chassis.asset.tag: 8CC6351M4W
dmi.chassis.type: 13
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
dmi.product.name: 24-b019
dmi.sys.vendor: HP
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.10
InstallationDate: Installed on 2016-12-04 (4 days ago)
InstallationMedia: Ubuntu-Kylin 16.10 "Yakkety Yak" - Alpha amd64 (20161010)
Package: linux (not installed)
Tags: yakkety
Uname: Linux 4.9.0-040900rc4-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.10
InstallationDate: Installed on 2016-12-04 (5 days ago)
InstallationMedia: Ubuntu-Kylin 16.10 "Yakkety Yak" - Alpha amd64 (20161010)
Package: linux (not installed)
Tags: yakkety
Uname: Linux 4.9.0-040900rc1-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.10
InstallationDate: Installed on 2016-12-04 (5 days ago)
InstallationMedia: Ubuntu-Kylin 16.10 "Yakkety Yak" - Alpha amd64 (20161010)
Package: linux (not installed)
Tags: yakkety
Uname: Linux 4.8.12-040812-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.10
InstallationDate: Installed on 2016-12-04 (7 days ago)
InstallationMedia: Ubuntu-Kylin 16.10 "Yakkety Yak" - Alpha amd64 (20161010)
Package: linux (not installed)
Tags: yakkety
Uname: Linux 4.9.0-040900-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

Revision history for this message
Mikemecanic (ppas) wrote :
summary: - Power-off/reboot stalls = no tty on Kernel 4.9.0.x
+ [AMD]Power-off/reboot stalls = no tty on Kernel 4.9.0.x
Colin Watson (cjwatson)
affects: launchpad → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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

apport-collect 1648524

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Mikemecanic (ppas) wrote : JournalErrors.txt

apport information

tags: added: apport-collected yakkety
description: updated
Revision history for this message
Mikemecanic (ppas) wrote : ProcEnviron.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote :

I just removed 4.9.10-12.

Revision history for this message
Mikemecanic (ppas) wrote : AlsaInfo.txt

apport information

description: updated
Revision history for this message
Mikemecanic (ppas) wrote : CRDA.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : IwConfig.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : JournalErrors.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : Lspci.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : Lsusb.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : ProcEnviron.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : ProcModules.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : PulseList.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : RfKill.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : UdevDb.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : WifiSyslog.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote :

The first one is with 4.8.12 and the last one is with Canonical Kernel Team unstable ppa.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

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

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key needs-bisect
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Mikemecanic (ppas) wrote : JournalErrors.txt

apport information

description: updated
Revision history for this message
Mikemecanic (ppas) wrote : ProcEnviron.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote :

Because 4.9.0.9 was already there it did not reboot properly. Plus, after a cold shutdown it didn’t boot properly=dead screen. Still, as usual I’m able to run custom kernel with the same result.

Here I did << apport-collect 1648524 >> before trying to shutdown. The first one is after trying to shutdown or reboot or when I have to do a cold shutdown.

description: updated
Revision history for this message
Mikemecanic (ppas) wrote :

Because 4.9.0.9 was already there it did not reboot properly. Plus, after a cold shutdown it didn’t boot properly=dead screen. Still, as usual I’m able to run custom kernel with the same result.

kernel-bug-exists-upstream

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Mikemecanic (ppas) wrote :

It is pretty hard to deal with a computer that cannot reboot or shutdown:

Commit Log for Thu Dec 8 16:53:41 2016

Completely removed the following packages:
linux-headers-4.9.0-040900rc8
linux-headers-4.9.0-9
linux-image-4.9.0-040900rc8-generic
linux-image-4.9.0-9-generic
linux-libc-dev

Removed the following packages:
linux-headers-4.9.0-040900rc8-generic
linux-headers-4.9.0-9-generic
linux-image-extra-4.9.0-9-generic
Commit Log for Thu Dec 8 16:55:06 2016

Completely removed the following packages:
libxdelta2
linux-image-4.8.0-29-generic
linux-image-extra-4.8.0-29-generic
linux-image-extra-4.9.0-9-generic

dpkg --list | grep linux-image
ii linux-image-4.8.12-040812-generic 4.8.12-040812.201612020431 amd64 Linux kernel image for version 4.8.12 on 64 bit x86 SMP

Revision history for this message
Mikemecanic (ppas) wrote : AlsaInfo.txt

apport information

description: updated
Revision history for this message
Mikemecanic (ppas) wrote : CRDA.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : IwConfig.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : JournalErrors.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : Lspci.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : Lsusb.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : ProcEnviron.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : ProcModules.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : PulseList.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : RfKill.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : UdevDb.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : WifiSyslog.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote :

Same result

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

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?

v4.8 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8/
v4.9-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc1/
v4.9-rc4 http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc4

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

Changed in linux (Ubuntu Zesty):
importance: Medium → High
tags: added: performing-bisect
tags: added: zesty
Revision history for this message
Mikemecanic (ppas) wrote : AlsaInfo.txt

apport information

description: updated
Revision history for this message
Mikemecanic (ppas) wrote : CRDA.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : IwConfig.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : JournalErrors.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : Lspci.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : Lsusb.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : ProcEnviron.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : ProcModules.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : PulseList.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : RfKill.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : UdevDb.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : WifiSyslog.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : JournalErrors.txt

apport information

description: updated
Revision history for this message
Mikemecanic (ppas) wrote : ProcEnviron.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : JournalErrors.txt

apport information

description: updated
Revision history for this message
Mikemecanic (ppas) wrote : ProcEnviron.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote : JournalErrors.txt

apport information

description: updated
Revision history for this message
Mikemecanic (ppas) wrote : ProcEnviron.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote :

This last one works. rc1 = rc8. Will now try the only one that was working: rc-5

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

So 4.9-rc4 works and 4.9-rc5 does not?

Revision history for this message
Mikemecanic (ppas) wrote :

RC-5 gives the same result.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

If -rc4 is good and -rc5 is bad, I can bisect between the two of them. Does -rc4 work properly?

Revision history for this message
Mikemecanic (ppas) wrote :

No, again rc-4 is freezing into the Kylin boot image and is the only noticeable difference. CTRL+ALT+xyz are not working. Must shutdown manually.

Revision history for this message
Mikemecanic (ppas) wrote : JournalErrors.txt

apport information

description: updated
Revision history for this message
Mikemecanic (ppas) wrote : ProcEnviron.txt

apport information

Revision history for this message
Mikemecanic (ppas) wrote :

Happy ending! The computer runs normally now. Thanks to all for help!
For testing purposes, if you don't mind, will now try a last thing with this October 10th build: upgrading to ZZ, LVM encrypted on custom Kernel. Almost done.

Special thanks (among many others) to Dave Airlie for its contribution and for making AMD 10 series back to work.

Changed in linux (Ubuntu Zesty):
status: Confirmed → Fix Released
Revision history for this message
Mikemecanic (ppas) wrote :

I'm back to ZZ and things are back to normal. Kernel 4.9 should go back in Proposed.
lsb_release -a && uname -r
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Zesty Zapus (development branch)
Release: 17.04
Codename: zesty
4.9.0-040900-generic

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.