Bug 26869 - Random crash of AMDGPU driver
Summary: Random crash of AMDGPU driver
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-28 09:26 CEST by Albert Rayanov
Modified: 2020-09-01 22:19 CEST (History)
3 users (show)

See Also:
Source RPM: x11-driver-video-amdgpu-19.1.0-4.mga8.src.rpm
CVE:
Status comment:


Attachments

Description Albert Rayanov 2020-06-28 09:26:44 CEST
Description of problem:
Crash of AMDGPU driver with soft freeze
journalctl fragment: http://paste.org.ru/?4vw6tb

Version-Release number of selected component (if applicable):
kernel-desktop-5.7.5-1.mga8-1-1.mga8
kernel-firmware-20190603-2.mga8
lib64drm_amdgpu1-2.4.102-1.mga8
x11-driver-video-amdgpu-19.1.0-4.mga8

How reproducible:
Random

Steps to Reproduce:
Use PC, make dd-backups between NVMe and HDD
Comment 1 Albert Rayanov 2020-06-28 09:34:40 CEST
UPD:
cat /proc/cpuinfo = http://paste.org.ru/?p25af7
(model name: AMD Ryzen 5 3500X 6-Core Processor)
lspci = http://paste.org.ru/?fjjvv4
(VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5))
Comment 2 Lewis Smith 2020-06-30 22:11:55 CEST
Thank you for the report, and apologies for the slow reply.
In future, can you please attach bulky information to the bug "Add an attachment" at the head, which allows a comment also. (If the attached file is very large, it is useful to compress it first; we suggest 'xz'). Use of intermediate sites can lose the info. For the graphics data, please post here just the section "VGA compatible controller" from:
 $ lspci -v

> Steps to Reproduce:
> Use PC, make dd-backups between NVMe and HDD
Is this a way of saying "Use the computer a long time"?
What do you mean by "soft freeze"?

CC: (none) => lewyssmith
Source RPM: x11-driver-video-amdgpu => x11-driver-video-amdgpu-19.1.0-4.mga8.src.rpm

Comment 3 Dave Hodgins 2020-06-30 23:49:48 CEST
Better to include the output of
lspcidrake -v|grep Card

That will include the pci vender and device ids.

CC: (none) => davidwhodgins

Comment 4 Lewis Smith 2020-07-01 22:04:03 CEST
@DH Not sure of the relevance of "the pci vender and device ids". Never mind.

Keywords: (none) => NEEDINFO

Comment 5 Dave Hodgins 2020-07-02 00:31:15 CEST
(In reply to Lewis Smith from comment #4)
> @DH Not sure of the relevance of "the pci vender and device ids". Never mind.

There of use to help id when a change is needed for pcitables, which controls
which kernel modules are loaded for newly added hardware.
Comment 6 Albert Rayanov 2020-07-02 04:37:27 CEST
(In reply to Lewis Smith from comment #2)
For the graphics data, please post
> here just the section "VGA compatible controller" from:
>  $ lspci -v
For the record: lspci -v | grep VGA = «09:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5) (prog-if 00 [VGA controller])»

> Is this a way of saying "Use the computer a long time"?
Nope, I have installed Cauldron one day before crash occured

> What do you mean by "soft freeze"?
Video driver failure awhile system is accessible via SSH.

(In reply to Dave Hodgins from comment #3)
> Better to include the output of
> lspcidrake -v|grep Card
lspcidrake -v | grep Card = «Card:ATI Volcanic Islands and later (amdgpu/fglrx): Advanced Micro Devices, Inc. [AMD/ATI]|Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [DISPLAY_VGA] (vendor:1002 device:7340 subv:1462 subd:3822) (rev: c5)»
Comment 7 Albert Rayanov 2020-07-02 04:39:38 CEST
UPD: No crashes occured since 28th June.
Comment 8 Lewis Smith 2020-07-02 09:00:57 CEST
Thank you for the clarification.
My request in comment 2 was also to see what drivers are being used, which would be what to investigate.

Re your comment above, let us leave it in suspense for a time.

Ever confirmed: 1 => 0
Status: NEW => UNCONFIRMED

Comment 9 Aurelien Oudelet 2020-08-22 21:09:53 CEST
Hi,

@Albert, do you still be affected by this bug?

Closing this on 2020-09-01 if no answer.

CC: (none) => ouaurelien

Aurelien Oudelet 2020-08-27 11:53:20 CEST

Severity: critical => major

Comment 10 Aurelien Oudelet 2020-09-01 22:19:51 CEST
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: UNCONFIRMED => RESOLVED
Resolution: (none) => OLD
Keywords: NEEDINFO => (none)


Note You need to log in before you can comment on or make changes to this bug.