All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 221959] New: ttm_lru_bulk_move_tail cause CPU stuck
Date: Thu, 03 Sep 2026 09:11:17 +0000	[thread overview]
Message-ID: <bug-221959-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 221959
           Summary: ttm_lru_bulk_move_tail cause CPU stuck
           Product: Drivers
           Version: 2.5
          Hardware: AMD
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: twyoda@gmail.com
        Regression: No

Created attachment 310777
  --> https://bugzilla.kernel.org/attachment.cgi?id=310777&action=edit
ttm_lru_bulk_move_tail failed  dmesg

This issue seems happened only after hibernation resume and randomly hang after
some times of using.
The attachment starts at 2026-09-03 16:37:10, "BUG: unable to handle page fault
for address: 0000000000002008" then following with "soft lock - CPU#? stuck for
??s".
The GUI screen totally freeze, "caps lock" key works, but Ctrl+Alt+F3 doesn't.
The dmesg records until I long press Power Button.
I had already turn of "Transparent Hugepage support".

My hardware:
Asus ROG Strix G17 2022, G713RM
DRAM: 64G
SSD: 1G+4G
CPU: AMD Ryzen 9 6900HX with Radeon Graphics
Discrete GPU: Nvidia Geforce RTX 3060M with 6G VRAM
OS: Gentoo Linux

What else information should I provide to deal with this issue ?

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

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

             reply	other threads:[~2026-09-03  9:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03  9:11 bugzilla-daemon [this message]
2026-09-03  9:11 ` [Bug 221959] ttm_lru_bulk_move_tail cause CPU stuck bugzilla-daemon
2026-09-05  9:24 ` bugzilla-daemon
2026-09-07  8:08 ` 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-221959-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.