From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 221827] Backlight regression with 7.1.6
Date: Tue, 04 Aug 2026 08:48:07 +0000 [thread overview]
Message-ID: <bug-221827-2300-y7ENeI0DRn@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221827-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221827
The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mario.limonciello@amd.com,
| |regressions@leemhuis.info
--- Comment #1 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) ---
(In reply to Raymond Jay Golo from comment #0)
> Upon upgrading to 7.1.6, backlight at 100% is set to dimmest level.
@Mario, this is apparently caused by the following change of yours that was
backported to 7.1.y: f1b5d8f9cc54ae ("drm/amd/display: Fix backlight
max_brightness to match exported range") [v7.2-rc4, v7.1.6 (1191285ecb4233),
v6.18.42]
@Raymond: This might be a general problem or something specific to the
backport. Testing 7.2-rc6 or later is thus advised. You might also want to
attach dmesg files separately from a working and a broken kernel, as they most
likely will be helpful for debugging.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-08-04 8:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 13:12 [Bug 221827] New: Backlight regression with 7.1.6 bugzilla-daemon
2026-08-03 13:13 ` [Bug 221827] " bugzilla-daemon
2026-08-04 8:48 ` bugzilla-daemon [this message]
2026-08-04 11:23 ` bugzilla-daemon
2026-08-04 12:22 ` bugzilla-daemon
2026-08-04 12:22 ` bugzilla-daemon
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=bug-221827-2300-y7ENeI0DRn@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=dri-devel@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 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.