Bug 108892 - kernel BUG at kernel/time/timer.c:1137 in drm_sched_job_finish [gpu_sched]
Summary: kernel BUG at kernel/time/timer.c:1137 in drm_sched_job_finish [gpu_sched]
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: DRI git
Hardware: x86-64 (AMD64) Linux (All)
: high critical
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-29 06:38 UTC by Zheng Luo
Modified: 2019-05-02 20:59 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
kernel dmesg (10.01 KB, text/plain)
2018-11-29 06:38 UTC, Zheng Luo
no flags Details
Journalctl Output re Kernel Bug (2.45 KB, text/plain)
2019-01-06 15:58 UTC, Vik-T
no flags Details
dmesg (21.90 KB, text/plain)
2019-05-02 20:59 UTC, Sami Farin
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Zheng Luo 2018-11-29 06:38:43 UTC
Created attachment 142656 [details]
kernel dmesg

Sometimes my AMD-2500U with amd.dc=1 crashes with the above messages in dmesg.
Comment 1 Christian König 2018-11-29 07:35:34 UTC
What kernel version is this? Please also try with the latest.
Comment 2 Zheng Luo 2018-11-29 09:31:07 UTC
(In reply to Christian König from comment #1)
> What kernel version is this? Please also try with the latest.

I'm using 4.19.4-arch1-1-ARCH. Should I try 4.20rc4?
Comment 3 Christian König 2018-11-29 16:10:19 UTC
Yes please, or even better Alex amd-staging-drm-next tree.

No idea how that is possible, but it looks like we are trying to schedule a timeout worker which is already scheduled.
Comment 4 sunnanyong 2018-12-06 11:58:59 UTC
Is there any new progress in this issue? I had the same problem.
Comment 5 sunnanyong 2018-12-06 12:04:15 UTC
(In reply to Zheng Luo from comment #2)
> (In reply to Christian König from comment #1)
> > What kernel version is this? Please also try with the latest.
> 
> I'm using 4.19.4-arch1-1-ARCH. Should I try 4.20rc4?

Hi brother , does the kernel upgrade work?
Comment 6 Zheng Luo 2018-12-07 05:04:33 UTC
(In reply to sunnanyong from comment #5)
> Hi brother , does the kernel upgrade work?

I switched between 4.19 and 4.20rc4/5 these days. However with none of the two kernels I can reproduce this bug.
Comment 7 Vik-T 2019-01-06 15:58:34 UTC
Created attachment 142985 [details]
Journalctl Output re Kernel Bug

Since I upgraded to 4.19 from 4.18 about a 2 weeks, I'm experiencing the same issue, unfortunately. Sometimes once a day, sometimes several times per day. I don't always get an entry in syslog so it wasn't clear to me from the start where the problem lies. I have attached the respective log entry for your reference. 

I now just upgraded to 4.20 and hope the error won't appear there, too.
Comment 8 Sami Farin 2019-05-02 20:59:44 UTC
Created attachment 144130 [details]
dmesg

4.19.37 has this bug also.

Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Lexa PRO [Radeon RX 550/550X] driver: amdgpu v: kernel 
           Display: server: Fedora Project X.org 1.20.4 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa 
           resolution: 3840x2160~60Hz 
           OpenGL: renderer: Radeon 550 Series (POLARIS12 DRM 3.27.0 4.19.38+ LLVM 7.0.1) v: 4.5 Mesa 19.0.3


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.