| Summary: | kernel BUG at kernel/time/timer.c:1137 in drm_sched_job_finish [gpu_sched] | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Zheng Luo <vicluo96> | ||||||||
| Component: | DRM/AMDgpu | Assignee: | Default DRI bug account <dri-devel> | ||||||||
| Status: | RESOLVED MOVED | QA Contact: | |||||||||
| Severity: | critical | ||||||||||
| Priority: | high | CC: | vicluo96, viktor | ||||||||
| Version: | DRI git | ||||||||||
| Hardware: | x86-64 (AMD64) | ||||||||||
| OS: | Linux (All) | ||||||||||
| Whiteboard: | |||||||||||
| i915 platform: | i915 features: | ||||||||||
| Attachments: |
|
||||||||||
What kernel version is this? Please also try with the latest. (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? 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. Is there any new progress in this issue? I had the same problem. (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？ (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. 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.
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
-- 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/620. |
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.
Created attachment 142656 [details] kernel dmesg Sometimes my AMD-2500U with amd.dc=1 crashes with the above messages in dmesg.