On 6/16/26 11:12, Uwe Kleine-König wrote:
Control: forwarded -1https://lore.kernel.org/amd-gfx/ajEQr3IXQ8byLFvC@monoceros
Hello,
a Debian user reported an issue while using the amdgpu user. The full
details are available athttps://bugs.debian.org/1139599. The relvant (I
hope) parts are also in this mail, but you can find more logs there if
you want to take a look.
On Wed, Jun 10, 2026 at 09:01:09AM +0200, Olaf Flebbe wrote:
* What led up to the situation?
Heavy use of LM-Studio with local GPU accellerated models.
HW: AMD Ryzen™ 7 7840U w/ Radeon™ 780M Graphics × 16 (Framework 13
Laptop)
* What exactly did you do (or not do) that was effective (or
ineffective)?
Normal use (use gnome-calc for instance) while LM-Studio was active.
* What was the outcome of this action?
Moved the mouse: Computer totally locked, hat to power off.
* What outcome did you expect instead?
Mouse movement :)
Happend two times with Kernel reports both mentioning "ttm something" and
"amdgpu_bo_move"
@Olaf: If you still have both issues in your logs, providing both might
help to identify the issue. Also it would be great to know, how reliably
you can reproduce the issue, in case we have to resort to bisecting or
testing a fix. Is this a regression, i.e. did the same workflow work
fine before, with an older kernel version? If so, which one?
I found 5 of these Oopses starting in June 9 with kernel 7.0.10-1.
Found out that some of these oopses happened while waking up for
hibernation or running LLM's.
(some hangs when waking up did not leave traces in the logs)
It happens almost every 2 days.
Hibernation worked great before (factoring out the issues with the
parport module race when booting).
Best
Olaf
