From: Danilo Machado <danilomachado2002@hotmail.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Cc: "alexander.deucher@amd.com" <alexander.deucher@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux@leemhuis.info" <linux@leemhuis.info>
Subject: Re: [BUG REPORT] AMD Radeon R9 380 (Tonga) - HDMI no signal after suspend / regression tracking update
Date: Mon, 7 Sep 2026 15:21:04 +0000 [thread overview]
Message-ID: <CPUPR80MB65833B1554155D4CCF024CF2A3B22@CPUPR80MB6583.lamprd80.prod.outlook.com> (raw)
#regzbot back in-progress
#regzbot monitor https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142389
#regzbot monitor https://gitlab.freedesktop.org/drm/amd/-/work_items/5123
Hi Thorsten, Alex, and Linux Kernel Maintainers,
I am writing to update the status of this regression after checking the Regzbot tracking dashboard:
https://linux-regtracking.leemhuis.info/regzbot/regression/lore/CAOnW2VTGBP=MMWM=W41uPDLrzTVHM1sw8P1myvftnNk0vEMMFw@mail.gmail.com/
The dashboard currently lists this issue as "fizzled out / resolved: inconclusive", but I want to clarify that this bug is ACTIVE, UNRESOLVED, and actively tracked. The lack of recent email activity on LKML was due to ongoing technical data collection on Launchpad and GitLab while awaiting upstream feedback.
Current Status & Verification:
1. Launchpad Report (#2142389):
- Status: Confirmed (assigned to maintainer Timo Aaltonen).
- Heat/Users: 220 Bug Heat points with 44+ explicitly confirmed affected users across various AMD architectures (Tonga R9 380, Polaris RX 400/500, and recent Vega APUs).
- Link: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142389
2. Freedesktop GitLab Issue (#5123):
- Status: Open.
- Link: https://gitlab.freedesktop.org/drm/amd/-/work_items/5123
3. Technical Summary:
- I have executed 3 full git bisect routines on hardware testbenches, isolating the regression behavior between kernel transitions.
- Recent user reports confirm the same black screen / no EDID handshake failure upon resume and DPMS display wake-up across multiple Linux distributions (Ubuntu, Fedora, Void Linux) and kernel versions (up to kernel 7.0).
Please re-open and maintain active tracking for this regression on Regzbot. I remain available to test candidate patches, kernel builds, or debug flags on physical hardware.
Best regards,
Danilo Machado
next reply other threads:[~2026-09-07 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 15:21 Danilo Machado [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-07 15:01 Danilo Machado
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=CPUPR80MB65833B1554155D4CCF024CF2A3B22@CPUPR80MB6583.lamprd80.prod.outlook.com \
--to=danilomachado2002@hotmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
/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
all inboxes | Powered by JetHome®