[Bug 201727] New: Hardware Error reported on Ryzen 5 2500U

[b***@bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=201727

Bug ID: 201727
Summary: Hardware Error reported on Ryzen 5 2500U
Product: Drivers
Version: 2.5
Kernel Version: 4.20-rc3
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-***@kernel-bugs.osdl.org
Reporter: ***@gmail.com
Regression: No

Created attachment 279511
--> https://bugzilla.kernel.org/attachment.cgi?id=279511&action=edit
dmesg

How to reproduce: Boot and start any graphical application, for example gdm
Expected: gdm will start
Actual: screen goes black, with the cursor visible in top left corner,
log is full of [Hardware Error]

I have bisected the bug, it seems it is introduced in commit
284dec4317c8e76f45d3ce922f673c80331812f1.

let me know if you think the hardware is actually broken, but i have had no
issues on windows, and no hardware errors on 4.19 kernel.

[b***@bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=201727

--- Comment #1 from Michal Herko (***@gmail.com) ---
Created attachment 279513
--> https://bugzilla.kernel.org/attachment.cgi?id=279513&action=edit
/proc/cpuinfo

[b***@bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=201727

--- Comment #2 from Michal Herko (***@gmail.com) ---
Created attachment 279515
--> https://bugzilla.kernel.org/attachment.cgi?id=279515&action=edit
lspci -vvv

[b***@bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=201727

--- Comment #3 from Michal Herko (***@gmail.com) ---
Created attachment 279517
--> https://bugzilla.kernel.org/attachment.cgi?id=279517&action=edit
.config

[b***@bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=201727

Mike Lothian (***@fireburn.co.uk) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@fireburn.co.uk

--- Comment #4 from Mike Lothian (***@fireburn.co.uk) ---
If you've bisected then it's unlikely to be a hardware issue

If you revert the commit does everything work again?

[b***@bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=201727

Michel Dänzer (***@daenzer.net) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@amd.com

--- Comment #5 from Michel Dänzer (***@daenzer.net) ---
That's

commit 284dec4317c8e76f45d3ce922f673c80331812f1
Author: Christian König <***@amd.com>
Date: Wed Aug 22 16:44:56 2018 +0200

drm/amdgpu: enable GTT PD/PT for raven v3

[b***@bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=201727

--- Comment #6 from Christian König (***@amd.com) ---
Currently GTT is only used for PD/PT as last resort when there is so few stolen
memory assigned to the APU that it won't work at all otherwise.

The faulting address looks suspicious like we miss to handle an error code
correctly somewhere and instead use the value as DMA address.

What is your BIOS setting for the stolen VRAM?

[b***@bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=201727

--- Comment #7 from Michal Herko (***@gmail.com) ---
Everything works after a revert. There was a conflict, i am attaching a diff of
the revert.

[b***@bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=201727

--- Comment #8 from Michal Herko (***@gmail.com) ---
Created attachment 279521
--> https://bugzilla.kernel.org/attachment.cgi?id=279521&action=edit
revert of 284dec

[b***@bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=201727

Post by b***@bugzilla.kernel.org
What is your BIOS setting for the stolen VRAM?

I can't find any such settings in bios. I really do not have any options
regarding video.

[b***@bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=201727

Alex Deucher (***@gmail.com) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #10 from Alex Deucher (***@gmail.com) ---
(In reply to Christian König from comment #6)

Post by b***@bugzilla.kernel.org
What is your BIOS setting for the stolen VRAM?

[ 2.665594] [drm] amdgpu: 256M of VRAM memory ready

[b***@bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=201727

Michal Herko (***@gmail.com) changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |CODE_FIX

--- Comment #11 from Michal Herko (***@gmail.com) ---
The bug is no more present on v4.20-rc5.