[Bug 211425] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 20secs aborting

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Sat Nov 27 13:34:11 UTC 2021


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

Andreas (icedragon.aw at web.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Kernel Version|5.15                        |5.15.5
           Severity|normal                      |blocking

--- Comment #23 from Andreas (icedragon.aw at web.de) ---
I tried a lot different configurations:

A) A different cable DP-to-DP instead DP-to-miniDP (both 4k and 60Hz capable):
makes no difference

B) The issue can still be triggered and it recovers after 2x20 seconds with the
error message above until at least 5.15.2!

C) Beginning from kernel 5.15.3 it can be still triggered, BUT it did not
recover any more until reboot! Also the Error message are changed to:

[147325.153678] BUG: workqueue lockup - pool cpus=7 node=0 flags=0x0 nice=-20
stuck for 32s!
[147325.153694] Showing busy workqueues and worker pools:
[147325.153697] workqueue events: flags=0x0
[147325.153700]   pwq 30: cpus=15 node=0 flags=0x0 nice=0 active=1/256 refcnt=2
[147325.153706]     in-flight: 127037:dbs_work_handler
[147325.153735] workqueue events_highpri: flags=0x10
[147325.153740]   pwq 15: cpus=7 node=0 flags=0x0 nice=-20 active=2/256
refcnt=3
[147325.153745]     in-flight: 477:dm_irq_work_func
[147325.153749]     pending: dm_irq_work_func
[147325.153851] pool 15: cpus=7 node=0 flags=0x0 nice=-20 hung=32s workers=2
idle: 59
[147325.153856] pool 30: cpus=15 node=0 flags=0x0 nice=0 hung=0s workers=2
idle: 110635

D) from 5.15.4 to 5.15.5 it still occurs and hangs until reboot, BUT in
addition I can not find any error message in the kernel log (like above) any
more! Also no error message with activated debug symbols!

Because the occurring can not be controlled, this makes a stable use of kernel
5.15.3 and newer impossible!!!

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.


More information about the dri-devel mailing list