AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Moock <mm@dorfdsl.de>
To: amd-gfx@lists.freedesktop.org
Subject: Re: amdgpu 100% CPU usage causing freeze 1002:15d8
Date: Thu, 16 Jan 2025 17:29:16 +0100	[thread overview]
Message-ID: <20250116172916.0dba9ff6@ryz.dorfdsl.de> (raw)
In-Reply-To: <CADnq5_MbeTRb642qwb0Q7JbL=2UsnK6RnLm6NWTeVLZOEuyn4A@mail.gmail.com>

Am 16.01.2025 um 11:21:11 Uhr schrieb Alex Deucher:

> On Wed, Jan 15, 2025 at 4:02 PM Marco Moock <mm@dorfdsl.de> wrote:
> >
> > Am Wed, 15 Jan 2025 15:27:00 -0500
> > schrieb Alex Deucher <alexdeucher@gmail.com>:
> >  
> > > On Wed, Jan 15, 2025 at 3:22 PM Marco Moock <mm@dorfdsl.de>
> > > wrote:  
> > > >
> > > > Am Wed, 15 Jan 2025 16:08:34 +0100
> > > > schrieb Marco Moock <mm@dorfdsl.de>:
> > > >  
> > > > > I assume it was 6.12.6, but Debian doesn't have the old
> > > > > packages anymore and it has been purged from my system
> > > > > already.  
> > > >
> > > > I've now tried 6.12.6, same situation.
> > > >
> > > > Any further ideas what could cause this?  
> > >
> > > Can you provide more details about what you are seeing?  What
> > > does `ps aux` or `top` show as using all of the CPU time?  
> >
> > I saw
> >    2977 root      20   0       0      0      0 R  99,3   0,0
> > 5:18.68 kworker/u16:39+amdgpu-reset-dev
> >
> > But the system is almost unusable, it takes seconds to print the
> > characters in terminal when connecting from a remote machine. Local,
> > the system doesn't care about keyboard anymore, except Sysrq.
> > Switching to another tty wasn't possible.
> >
> > In some cases, even the sysrq keystroke won't be recognized and I
> > need to use the reset switch on the case.  
> 
> Can you get the dmesg output when this happens?  Might be easier to
> get it over a remote connection like ssh if possible.

Jan 15 20:40:26 ryz kernel: amdgpu 0000:08:00.0: amdgpu: Dumping IP
State

This is the only message that is related to the problem. 
After that are some firewall messages, I doubt that they are useful to
be posted here.

-- 
Gruß
Marco

  reply	other threads:[~2025-01-16 16:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 20:32 amdgpu 100% CPU usage causing freeze 1002:15d8 Marco Moock
2025-01-14 22:25 ` Alex Deucher
2025-01-15 15:08   ` Marco Moock
2025-01-15 20:10     ` Marco Moock
2025-01-15 20:27       ` Alex Deucher
2025-01-15 20:35         ` Marco Moock
2025-01-16 16:21           ` Alex Deucher
2025-01-16 16:29             ` Marco Moock [this message]
2025-01-16 16:32               ` Alex Deucher
2025-01-16 16:37                 ` Marco Moock
2025-01-20 16:35                   ` Alex Deucher
2025-01-20 19:44                     ` Marco Moock
2025-01-24 10:02                     ` Marco Moock
2025-01-24 21:40                       ` Alex Deucher
2025-01-25 18:38                         ` Marco Moock
2025-01-28 15:07                           ` Alex Deucher
2025-01-28 17:06                             ` Alex Deucher
2025-01-28 21:48                               ` Alex Deucher
2025-01-29 18:57                               ` Marco Moock
2025-01-29 19:02                                 ` Marco Moock
2025-01-24 10:02                     ` Marco Moock
2025-01-18 11:24       ` Marco Moock

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=20250116172916.0dba9ff6@ryz.dorfdsl.de \
    --to=mm@dorfdsl.de \
    --cc=amd-gfx@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