Bug 107580

Summary:	[amdgpu] Firefox can force driver into a crash (AMD Radeon HD 8600M HANIAN)
Product:	DRI	Reporter:	Kami <kami911>
Component:	DRM/AMDgpu	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED MOVED	QA Contact:
Severity:	normal
Priority:	medium
Version:	XOrg git
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Kami 2018-08-15 12:12:53 UTC

Hi,
I got an AMD GOPU in a hybrid graphic laptop:
01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430]

I am using DRI_PRIME=1 to use AMD GPU during Firefox.
glxinfo of both videocards:
https://pastebin.com/8zER7byy
I updated the kernel since the last matter. I used a 4.17 kernel on a Linux Mint 19 64 bit base on Ubuntu 18.04. 
Time by time Firefox is stopping to work, because become unclickable.
I saw this in kernel logs:
https://pastebin.com/dkH24AVZ


Xorg.log:
cat /var/log/Xorg.0.log
[   213.984] 
X.Org X Server 1.19.6
Release Date: 2017-12-20
[   213.984] X Protocol Version 11, Revision 0
[   213.984] Build Operating System: Linux 4.4.0-119-generic x86_64 Ubuntu
[   213.984] Current Operating System: Linux godzilla 4.18.0-041800-generic #201808122131 SMP Sun Aug 12 21:33:20 UTC 2018 x86_64
[   213.984] Kernel command line: BOOT_IMAGE=/vmlinuz-4.18.0-041800-generic root=/dev/mapper/main-root ro rootflags=subvol=@ elevator=deadline zswap.enabled=1 pti=1 ibrs=1 ibpb=1 radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 amdgpu.dc=1 quiet splash vt.handoff=1
[   213.984] Build Date: 13 April 2018  08:07:36PM
[   213.984] xorg-server 2:1.19.6-1ubuntu4 (For technical support please see http://www.ubuntu.com/support) 
[   213.984] Current version of pixman: 0.34.0

When this happens the AMD become unreachable, for instance I am not able to run glxinfo on AMD card.

00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06)
	Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05bd]
	Kernel driver in use: i915
	Kernel modules: i915
00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06)
	Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [1028:05bd]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller [8086:8c20] (rev 04)
	Subsystem: Dell 8 Series/C220 Series Chipset High Definition Audio Controller [1028:05bd]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430] [1002:6660]
	Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] [1028:05bd]
	Kernel driver in use: amdgpu
	Kernel modules: radeon, amdgpu

Versions:

ii  libdrm-amdgpu1:amd64                        2.4.91-2                                                
ii  libdrm-amdgpu1:i386                         2.4.91-2                                                
ii  xserver-xorg-video-amdgpu                   18.0.1-1

Comment 1 Andrey Grodzovsky 2018-08-15 19:06:09 UTC

Can you provide a full dmesg log ?

From the log you did provide it seems the device was during suspend operation. Is it so ?

Does it happen only when you work with DRI_PRIME feature ? Can you run with AMD only (excluding Intel) and see if this still happens ?

Comment 2 Martin Peres 2019-11-19 08:47:01 UTC

-- 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/478.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.