Ubuntu
linux package

AMDGPU causes kernel panic with

Bug #1656649 reported by Alexis Lecocq on 2017-01-15

This bug affects 3 people

Affects

Status

Importance

Assigned to

Milestone

linux (Ubuntu)

Fix Released

Medium

Unassigned

You need to log in to change this bug's status.

Affecting:	linux (Ubuntu)
Filed here by:	Alexis Lecocq
When:	2017-01-15
Confirmed:	2017-03-20
Started work:	2017-05-07
Completed:	2017-05-07

Target

Distribution
Package	(Find…)
Project	(Find…)

Status	Importance
	Medium

Assigned to

	Nobody
	Me

Comment on this change (optional)

Email me about changes to this bug report

(?)

Bug Description

Laptop is Toshiba Satellite S50-B-12R http://www.toshiba.be/fr/discontinued-products/satellite-s50-b-12r/
Graphic card is AMD Radeon R7 M260

Running Ubuntu 16.04, system was unstable when first installed it (a lot of random kernel panic). Problem seemed related to new AMDGPU drivers introduced into new kernels so I tried to disable graphic card by adding radeon.modeset=0 to GRUB_CMDLINE_LINUX_DEFAULT as suggested here http://askubuntu.com/questions/771562/16-04-power-off-discrete-graphics-ati-amd and there http://askubuntu.com/questions/771838/should-i-disable-amd-graphic

After this, system is stable except when sleeping. After wake up, I get a kernel panic within 5min (time is random). System logs show a trouble about AMDGPU *ERROR*.

WORKAROUND: Do not disable switcheroo and add to GRUB_CMDLINE_LINUX_DEFAULT:
radeon.modeset=0 amdgpu.runpm=0 acpi_backlight=intel_backlight

WORKAROUND: Use the Intel integrated graphics card.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-59-generic 4.4.0-59.80
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: axtux 1963 F.... pulseaudio
/dev/snd/controlC1: axtux 1963 F.... pulseaudio
CurrentDesktop: Unity
Date: Sun Jan 15 13:29:26 2017
HibernationDevice: RESUME=UUID=d3a0be1f-38a0-475c-863c-38ca63b47d81
InstallationDate: Installed on 2016-11-01 (74 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: TOSHIBA SATELLITE S50-B
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash radeon.modeset=0 vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-59-generic N/A
linux-backports-modules-4.4.0-59-generic N/A
linux-firmware 1.157.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/26/2014
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.80
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: dmi:bvnINSYDECorp.:bvr1.80:bd08/26/2014:svnTOSHIBA:pnSATELLITES50-B:pvrPSPQ6E-01K002BT:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE S50-B
dmi.product.version: PSPQ6E-01K002BT
dmi.sys.vendor: TOSHIBA

See original description

Tags: Edit Tag help

Alexis Lecocq (axtux) wrote on 2017-01-15:

AlsaInfo.txt Edit (33.0 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (392 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (74.0 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.3 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (507 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (11.2 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (11.6 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (433 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (4.0 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (325 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (3.0 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (6.7 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (23.2 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (126 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (176.5 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (119.8 KiB, text/plain; charset="utf-8")

Brad Figg (brad-figg) wrote on 2017-01-15: Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Alexis Lecocq (axtux) wrote on 2017-01-15:

kernel.log Edit (23.3 KiB, text/plain)

The working workaround for me was to add "radeon.modeset=0 amdgpu.runpm=0 acpi_backlight=intel_backlight" to GRUB_CMDLINE_LINUX_DEFAULT and NOT to switch off switcheroo

In case I disable switcheroo, I have a bug on shutdown. The screen goes to console printing some errors (logs attached) and freezes (caps lock not blinking).

Joseph Salisbury (jsalisbury) wrote on 2017-01-17:

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-rc4

Changed in linux (Ubuntu):
importance:	Undecided → Medium
status:	Confirmed → Incomplete

Alexis Lecocq (axtux) wrote on 2017-02-09:

kernel-fixed-upstream

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed
information type:	Public → Public Security
information type:	Public Security → Public

Alexis Lecocq (axtux) wrote on 2017-02-09:

I am new to bug reports so I don't know how to set tags but I changed status to confirmed with message "kernel-fixed-upstream". I tested with latest mainline kernel v4.10-rc7 mainline build for amd64.

Christopher M. Penalver (penalvch) wrote on 2017-02-13:

Alexis Lecocq, to clarify https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656649/comments/6 did you remove all non-default kernel parameters/WORKAROUNDs/switcharoo and then test the kernel?

tags:	added: bios-outdated-2.00
description:	updated
Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

Paco Raxim (raxim1) wrote on 2017-02-22:

After simply logging out problem happens Edit (932.7 KiB, image/jpeg)

Similar problem happens, Toshiba L50-B-16C

I cannot report a bug in an official way (ubuntu-bug), because i have installed a google chrome from the official "Google" website, and i'm not willing to remove it in no way. - at least pls. fix, that official chrome distro should be accepted on different bug report. Google is a trustable third party.

Error message is saying:
Unable to handle kernel NULL pointer dereference
amdgpu_vm_grab_id+0x122/310 [amdgpu]

I don't dare to make my computer allow to sleep, as some hours later it simply freezes.
It's a relatively new notebook.

Paco Raxim (raxim1) wrote on 2017-02-22:

The logout problem happens only from 16.04.2 or 16.04.1, never happened before, just the wake up issue, which i haven't tested so far.

Paco Raxim (raxim1) on 2017-02-22

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Alexis Lecocq (axtux) wrote on 2017-02-22:

#10

Christopher M. Penalver, of course mainline kernel has been tested and is working fine without any non-default kernel parameters/WORKAROUNDs/switcharoo.

Why did you add tag bios-outdated-2.00 ? Where did you see this information ? Added tag "kernel-fixed-upstream"

Paco Raxim I suggest you to open a new bug report.

tags:

added: kernel-fixed-upstream

Christopher M. Penalver (penalvch) on 2017-03-09

tags:

added: kernel-fixed-upstream-4.10-rc4

Christopher M. Penalver (penalvch) wrote on 2017-03-09:

#11

Alexis Lecocq, the BIOS was found via the link in the Bug Description.

Despite this, to confirm this is resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

Alexis Lecocq (axtux) wrote on 2017-03-20:

#12

I tested daily-live of March 19. I don't get any AMDGPU *ERROR* and suspend is as expected so I think this bug has been fixed.

So what about current 16.04 LTS ? For now I'm using kernel 4.10 but I have to manually update it.

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Christopher M. Penalver (penalvch) wrote on 2017-05-07:

#13

Alexis Lecocq, I am closing this report because as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656649/comments/12 the bug has been fixed in the latest development version of Ubuntu.

In terms of a backport to 16.04, you would want to test the latest enablement stack as outlined in https://wiki.ubuntu.com/Kernel/LTSEnablementStack to see if it's resolved.