Shutdown crashing when connected to AC adapter

Bug #1730864 reported by Renê Barbosa
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux
Unknown
Medium
linux (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Hello there,

I'm using Ubuntu 17.10 (fully updated) and my system is crashing at shutdown when connected to an AC adapter.

The error is:

Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294280] [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 5secs aborting
Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294336] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing 75A8 (len 272, WS 0, PS 4) @ 0x75F1
Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294384] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing 640C (len 68, WS 0, PS 8) @ 0x6430]

This behavior is only happening when my laptop is charging. When running on battery I got a clean shutdown/reboot.

Already tried to run the latest kernel package (from Mainline) and the problem is exactly the same.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: boot/vmlinuz-4.13.0-16-generic]
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: rene 1249 F.... pulseaudio
 /dev/snd/controlC0: rene 1249 F.... pulseaudio
CurrentDesktop: GNOME
Date: Wed Nov 8 01:00:51 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=0f3b9237-1086-430d-be15-043b9ca00fd2
InstallationDate: Installed on 2017-11-06 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Dell Inc. Inspiron 5447
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=1237aa76-9a2f-4a06-8552-526f124914ff ro quiet splash acpi_backlight=intel_backlight
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic N/A
 linux-firmware 1.169
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/25/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0MHP6R
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A10
dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/25/2016:svnDellInc.:pnInspiron5447:pvrA10:rvnDellInc.:rn0MHP6R:rvrA00:cvnDellInc.:ct8:cvrA10:
dmi.product.family: 00
dmi.product.name: Inspiron 5447
dmi.product.version: A10
dmi.sys.vendor: Dell Inc.

Revision history for this message
Renê Barbosa (renebarbosa) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → 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.14 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.14

Changed in linux (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete
Revision history for this message
Renê Barbosa (renebarbosa) wrote :

Kernel bug exists upstream.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Renê Barbosa (renebarbosa) wrote :

Also tried to disable runpm in amdgpu and switch it off in both kernels (stock and Mainline Build).
For some reason the system is enabling it again (?) and the shutdown/reboot hangs until I force the process using Magic SysRQ.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/amdgpu

Revision history for this message
In , Renê Barbosa (renebarbosa) wrote :

Created attachment 135524
dmesg

Hello there,

I'm using Ubuntu 17.10 (fully updated) and my system is crashing at shutdown. It's freezing until I force a reboot/shutdown using Magic SysRq.

The error is:

Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294280] [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 5secs aborting
Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294336] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing 75A8 (len 272, WS 0, PS 4) @ 0x75F1
Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294384] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing 640C (len 68, WS 0, PS 8) @ 0x6430]

This behavior is only happening when my laptop is charging. When running on battery I got a clean shutdown/reboot.

Already tried to run the latest kernel package from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14 and the problem is exactly the same.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: boot/vmlinuz-4.13.0-16-generic]
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: rene 1249 F.... pulseaudio
 /dev/snd/controlC0: rene 1249 F.... pulseaudio
CurrentDesktop: GNOME
Date: Wed Nov 8 01:00:51 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=0f3b9237-1086-430d-be15-043b9ca00fd2
InstallationDate: Installed on 2017-11-06 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Dell Inc. Inspiron 5447
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=1237aa76-9a2f-4a06-8552-526f124914ff ro quiet splash acpi_backlight=intel_backlight
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic N/A
 linux-firmware 1.169
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/25/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0MHP6R
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A10
dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/25/2016:svnDellInc.:pnInspiron5447:pvrA10:rvnDellInc.:rn0MHP6R:rvrA00:cvnDellInc.:ct8:cvrA10:
dmi.product.family: 00
dmi.product.name: Inspiron 5447
dmi.product.version: A10
dmi.sys.vendor: Dell Inc.

Revision history for this message
In , Renê Barbosa (renebarbosa) wrote :

Created attachment 135525
lspci

Revision history for this message
In , Renê Barbosa (renebarbosa) wrote :

Created attachment 135526
modules

Revision history for this message
Renê Barbosa (renebarbosa) wrote :
Revision history for this message
In , Alexdeucher (alexdeucher) wrote :

(In reply to Rene Barbosa from comment #0)
> Created attachment 135524 [details]
> dmesg

Looks like you attached the wrong file. Please attach your full dmesg output.

Revision history for this message
In , Renê Barbosa (renebarbosa) wrote :

Created attachment 135527
dmesg

Revision history for this message
In , Renê Barbosa (renebarbosa) wrote :

Err. Sorry about that.
I've uploaded the correct file now.

Revision history for this message
In , Renê Barbosa (renebarbosa) wrote :

An interesting information: It's only with open source amdgpu driver. With amdgpu-pro it's not happening but this driver isn't compatible with Ubuntu 17.10.

Changed in linux:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
In , Vadym Krevs (vkrevs) wrote :

I've got a similar issue on a recently purchased Dell Inspiron 5770 with an AMD Radeon 530 graphics card with openSUSE Tumbleweed.

Reboot or attempt to switch to text console causes a hang and /var/log/messages contains the above message + kernel bug with a stack trace. Full details are here:

https://bugzilla.opensuse.org/show_bug.cgi?id=1068793

Revision history for this message
In , Renê Barbosa (renebarbosa) wrote :

<email address hidden>,

Are you using TLP or something similar?

I ran some tests and found that's only happening when using TLP. Tried with Ubuntu 17.10 and Fedora 27, same results.

Regards,
Rene Barbosa

Revision history for this message
In , Vadym Krevs (vkrevs) wrote :

Looks like TLP was installed on my laptop at initial installation time.

rpm -qa | grep -i tlp
tlp-1.0-1.2.noarch
tlp-rdw-1.0-1.2.noarch

The latest openSUSE Tumbleed snapshot switched to 4.14 kernel - I got the same issue with that too on first boot. The bug report in openSUSE's bugzilla contains the /var/log/messages for that first boot with 4.14.

Revision history for this message
In , Vadym Krevs (vkrevs) wrote :

OTOH, TLP services are not enabled according to tlp-stat -s, so does that mean my laptop is not using TLP after all?

tlp-stat -s
--- TLP 1.0 --------------------------------------------

+++ System Info
System = Dell Inc. Inspiron 5770
BIOS = 1.0.5
Release = "openSUSE Tumbleweed"
Kernel = 4.14.0-1-default #1 SMP PREEMPT Mon Nov 13 21:02:46 UTC 2017 (ab9e909) x86_64
/proc/cmdline = BOOT_IMAGE=/boot/vmlinuz-4.14.0-1-default root=UUID=d58e8e85-bfdd-4a74-a694-5149ccd85110 quiet resume=/dev/sda3 splash=silent quiet showopts
Init system = systemd v234
Boot mode = UEFI

+++ TLP Status
State = enabled
Last run = 11:02:47, 14 sec(s) ago
Mode = AC
Power source = AC

Notice: tlp.service is not enabled -- invoke "systemctl enable tlp.service" to correct this!
Notice: tlp-sleep.service is not enabled -- invoke "systemctl enable tlp-sleep.service" to correct this!
Notice: systemd-rfkill.service is not masked -- invoke "systemctl mask systemd-rfkill.service" to correct this!

Revision history for this message
In , Renê Barbosa (renebarbosa) wrote :

These systemd services are not running but according to tlp-stat, it's enabled.
Can you try to uninstall these packages and see if the error persists?

In my laptop, the problem is only happening when I install/enable them. Is it a power management bug?

Regards,
Rene Barbosa

Revision history for this message
In , Vadym Krevs (vkrevs) wrote :

Uninstalling tlp and tlp-rdw packages eliminates the error.

What I don't get is that runtime pm for amggpu driver is supposed to be disabled by default according to TLP docs.

I'll try reinstalling TLP and follow the TLP troubleshooting guide to see exactly what setting is causing this.

Revision history for this message
In , Renê Barbosa (renebarbosa) wrote :

Hey,

Is your system using 'pcieport' module?

I've added it to RUNTIME_PM_DRIVER_BLACKLIST in TLP's configuration and now the problem is fixed!

Not sure why it's happening in Linux 4.13+ and not in 4.4 with AMDGPU-Pro installed.

Revision history for this message
Renê Barbosa (renebarbosa) wrote :

Hello,

For some reason the problem was caused by TLP enabling Runtime PM in devices using 'pcieport' kernel module.

I got the problem fixed configuring TLP to _not_ enable Runtime PM on these devices.

It's only happening in Linux 4.13+.

Revision history for this message
In , Vadym Krevs (vkrevs) wrote :

Hi Rene,

Sorry for the delay in responding. Thanks for your suggestion regarding the pcieport module. Adding it to RUNTIME_PM_DRIVER_BLACKLIST does fix the problem while TLP is installed.

Vadym

Revision history for this message
In , Martin-peres-n (martin-peres-n) wrote :

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/261.

Changed in linux:
status: Confirmed → Unknown
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.