All of
 help / color / mirror / Atom feed
From: "Linux regression tracking #adding (Thorsten Leemhuis)" <>
To: Matt Fagnani <>,
	"" <>
Cc: Vasant Hegde <>,
	Alex Deucher <>,
	Linux kernel regressions list <>
Subject: Re: amdgpu failed to resume with AMD IOMMU enabled and 6.2.2-301 and 6.3.0-0.rc0.20230227gitf3a2439f20d9.9.fc39 and later resulting in a black screen
Date: Mon, 13 Mar 2023 11:30:09 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]

On 11.03.23 19:57, Matt Fagnani wrote:
> I booted a Fedora 38 KDE Plasma installation with the 6.2.2-301 kernel
> on an hp laptop with an AMD A10-9620P CPU, an integrated Radeon R5 GPU,
> and an AMD IOMMU enabled. I selected Sleep in either the Application
> Launcher menu in Plasma 5.27.2 on Wayland or sddm on Wayland. The system
> went to sleep. I moved the mouse to wake the system. The screen remained
> black, but the LEDs on the side of the laptop flickered indicating drive
> activity and the fan resumed making noise. I pressed sysrq+alt+s,u,b to
> do an emergency sync, remount read-only, and reboot. The system
> rebooted. The journal indicated the amdgpu failed to resume due to
> errors including amdgpu: amdgpu_device_ip_resume failed (-6). which
> started after the kernel failed to resume the AMD IOMMU.
> [...]
Thanks for the report. To be sure the issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
tracking bot (note, the version number is not entirely correct, but
things are a bit tricky here, but that version doesn't matter much
anyway in this case):

#regzbot ^introduced v6.1..v6.3-rc
#regzbot title amdgpu/iommu/: failed to resume
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (the parent of this mail). See page linked in footer for

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
Everything you wanna know about Linux kernel regression tracking:
That page also explains what to do if mails like this annoy you.

      parent reply	other threads:[~2023-03-13 10:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11 18:57 amdgpu failed to resume with AMD IOMMU enabled and 6.2.2-301 and 6.3.0-0.rc0.20230227gitf3a2439f20d9.9.fc39 and later resulting in a black screen Matt Fagnani
2023-03-13  4:21 ` Vasant Hegde
2023-03-13 23:02   ` Felix Kuehling
2023-03-15  6:40     ` Matt Fagnani
2023-03-15 16:14       ` Felix Kuehling
2023-03-15 17:07         ` Matt Fagnani
2023-03-13 10:30 ` Linux regression tracking #adding (Thorsten Leemhuis) [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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.