dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 211425] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 20secs aborting
Date: Sat, 27 Nov 2021 13:34:11 +0000	[thread overview]
Message-ID: <bug-211425-2300-wn6Udhb1Cj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211425-2300@https.bugzilla.kernel.org/>

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

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

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

--- Comment #23 from Andreas (icedragon.aw@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.

  parent reply	other threads:[~2021-11-27 13:34 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27  8:29 [Bug 211425] New: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 20secs aborting bugzilla-daemon
2021-01-27 10:30 ` [Bug 211425] " bugzilla-daemon
2021-01-27 21:19 ` bugzilla-daemon
2021-01-27 21:20 ` bugzilla-daemon
2021-02-02 16:41 ` bugzilla-daemon
2021-02-05  8:19 ` bugzilla-daemon
2021-02-09 13:49 ` bugzilla-daemon
2021-02-09 16:55 ` bugzilla-daemon
2021-02-09 21:06 ` bugzilla-daemon
2021-02-13 19:48 ` bugzilla-daemon
2021-02-13 19:48 ` bugzilla-daemon
2021-02-15 15:14 ` bugzilla-daemon
2021-02-16 17:59 ` bugzilla-daemon
2021-02-19  8:50 ` bugzilla-daemon
2021-02-27 17:00 ` bugzilla-daemon
2021-03-06 16:43 ` bugzilla-daemon
2021-03-08  8:13 ` bugzilla-daemon
2021-03-09 19:15 ` bugzilla-daemon
2021-03-30 19:28 ` bugzilla-daemon
2021-03-30 20:49 ` bugzilla-daemon
2021-03-31  7:40 ` bugzilla-daemon
2021-04-08  9:27 ` bugzilla-daemon
2021-06-23 17:59 ` bugzilla-daemon
2021-06-26 12:11 ` bugzilla-daemon
2021-07-07  7:13 ` bugzilla-daemon
2021-07-21  7:08 ` bugzilla-daemon
2021-07-22 17:40 ` bugzilla-daemon
2021-07-22 17:43 ` bugzilla-daemon
2021-08-01 10:10 ` bugzilla-daemon
2021-08-17 18:21 ` bugzilla-daemon
2021-08-27 18:21 ` bugzilla-daemon
2021-09-13 16:07 ` bugzilla-daemon
2021-09-22  7:02 ` bugzilla-daemon
2021-09-24 15:53 ` bugzilla-daemon
2021-10-20 14:48 ` bugzilla-daemon
2021-10-31 17:00 ` bugzilla-daemon
2021-11-06 10:53 ` bugzilla-daemon
2021-11-27 13:34 ` bugzilla-daemon [this message]
2021-12-18 10:28 ` bugzilla-daemon
2022-04-11  0:06 ` bugzilla-daemon
2022-12-21 16:35 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-211425-2300-wn6Udhb1Cj@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).