| Bug ID | 108892 |
|---|---|
| Summary | kernel BUG at kernel/time/timer.c:1137 in drm_sched_job_finis= h [gpu_sched] |
| Product | DRI |
| Version | DRI git |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | vicluo96@gmail.com |
Created attachment 142656 =
[details]
kernel dmesg
Sometimes my AMD-2500U with amd.dc=3D1 crashes with the above messages in d=
mesg.
What kernel version is this? Please also try with the latest.<=
/pre>
| What | Removed | Added |
|---|---|---|
| Attachment #142656 mime type | text/x-log | text/plain |
(In reply to Christian K=C3=B6nig from comment #1) > What kernel version is this? Please also try wit= h 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 proble= m.
(In reply to Zheng Luo from comment #2) > (In reply to Christian K=C3=B6nig from comment #1) > > What kernel version is this? Please also try with the latest. >=20 > I'm using 4.19.4-arch1-1-ARCH. Should I try 4.20rc4? Hi brother , does the kernel upgrade work=EF=BC=9F
(In reply to sunnanyong from comment #5) > Hi brother , does the kernel upgrade work=EF=BC= =9F I switched between 4.19 and 4.20rc4/5 these days. However with none of the = two kernels I can reproduce this bug.
| What | Removed | Added |
|---|---|---|
| CC | viktor@troja.ch |
Created attachme=
nt 142985 [details]
Journalctl Output re Kernel Bug
Since I upgraded to 4.19 from 4.18 about a 2 weeks, I'm experiencing the sa=
me
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.=20
I now just upgraded to 4.20 and hope the error won't appear there, too.
| What | Removed | Added |
|---|---|---|
| Priority | medium | high |
| Severity | normal | critical |
Created attachment 144130 [details]<=
/span>
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=20
Display: server: Fedora Project X.org 1.20.4 driver: amdgpu,ati
unloaded: fbdev,modesetting,vesa=20
resolution: 3840x2160~60Hz=20
OpenGL: renderer: Radeon 550 Series (POLARIS12 DRM 3.27.0 4.19.3=
8+
LLVM 7.0.1) v: 4.5 Mesa 19.0.3
| What | Removed | Added |
|---|---|---|
| Resolution | --- | MOVED |
| Status | NEW | RESOLVED |
-- 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.