From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 221320] ring gfx_0.1.0 timeout, signaled seq=5855035, emitted seq=5855037
Date: Sat, 04 Apr 2026 20:39:08 +0000 [thread overview]
Message-ID: <bug-221320-2300-oQnDZQamuN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221320-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221320
--- Comment #2 from Witold Baryluk (witold.baryluk+kernel@gmail.com) ---
The issue also happens with MATE desktop (X11), and no other programms running
(i.e. no Firefox)
LM studio log:
```
$ tail -f 2026-04-04.1.log
slot update_slots: id 3 | task 0 | prompt processing progress, n_tokens =
35328, batch.n_tokens = 512, progress = 0.797292
[2026-04-04 20:36:50][DEBUG] slot update_slots: id 3 | task 0 | n_tokens =
35328, memory_seq_rm [35328, end)
[2026-04-04 20:36:50][DEBUG] slot update_slots: id 3 | task 0 | prompt
processing progress, n_tokens = 35840, batch.n_tokens = 512, progress =
0.808847
[2026-04-04 20:36:54][DEBUG] slot update_slots: id 3 | task 0 | n_tokens =
35840, memory_seq_rm [35840, end)
slot update_slots: id 3 | task 0 | prompt processing progress, n_tokens =
36352, batch.n_tokens = 512, progress = 0.820402
[2026-04-04 20:36:57][DEBUG] slot update_slots: id 3 | task 0 | n_tokens =
36352, memory_seq_rm [36352, end)
slot update_slots: id 3 | task 0 | prompt processing progress, n_tokens =
36864, batch.n_tokens = 512, progress = 0.831957
[2026-04-04 20:37:01][DEBUG] slot update_slots: id 3 | task 0 | n_tokens =
36864, memory_seq_rm [36864, end)
[2026-04-04 20:37:01][DEBUG] slot update_slots: id 3 | task 0 | prompt
processing progress, n_tokens = 37376, batch.n_tokens = 512, progress =
0.843512
[2026-04-04 20:37:08][DEBUG] radv/amdgpu: The CS has been cancelled because the
context is lost. This context is innocent.
```
I did verify it is using system vulkan libraries (vulkan loader, and the radeon
mesa driver too).
The issue is reproducible, by loading same model, and replying the same
conversation to the same point.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-04-04 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 20:09 [Bug 221320] New: ring gfx_0.1.0 timeout, signaled seq=5855035, emitted seq=5855037 bugzilla-daemon
2026-04-04 20:12 ` [Bug 221320] " bugzilla-daemon
2026-04-04 20:12 ` bugzilla-daemon
2026-04-04 20:39 ` bugzilla-daemon [this message]
2026-04-04 23:37 ` bugzilla-daemon
2026-04-05 0:03 ` bugzilla-daemon
2026-04-05 8:37 ` 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-221320-2300-oQnDZQamuN@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox