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: Mon, 20 Jan 2025 20:44:28 +0100	[thread overview]
Message-ID: <20250120204428.2bc7b3e6@ryz.dorfdsl.de> (raw)
In-Reply-To: <CADnq5_O_WcZJ7yoDKEJpktSqffbP8RENhChmkD8Es7NHRYhCAg@mail.gmail.com>

Am 20.01.2025 um 11:35:07 Uhr schrieb Alex Deucher:

> On Thu, Jan 16, 2025 at 11:57 AM Marco Moock <mm@dorfdsl.de> wrote:
> >
> > Am 16.01.2025 um 11:32:42 Uhr schrieb Alex Deucher:
> >
> > > I'd like to see the driver messages leading up to that.
> >
> > I've now attached the entire dmesg without the firewall stuff.
> 
> Does the attached test patch help?

Is there a simple way to compile just the module and install it in a
"safe" way?
I haven't compiled kernels yet and don't know how far that could
destroy my installed system.

If that is too risky, I will set up another on a second disk.

-- 
Gruß
Marco

  reply	other threads:[~2025-01-20 19:46 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
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 [this message]
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=20250120204428.2bc7b3e6@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