Bug 2333789 - Loss of screen brightness control after suspend/hibernate resume
Summary: Loss of screen brightness control after suspend/hibernate resume
Keywords:
Status: CLOSED DUPLICATE of bug 2333543
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 41
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://discussion.fedoraproject.org/...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-12-22 22:27 UTC by fedora
Modified: 2025-01-06 09:37 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-01-06 09:37:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
journalctl (101.14 KB, text/plain)
2024-12-22 22:30 UTC, fedora
no flags Details
journalctl kernel log containing a sleep/resume cycle (117.35 KB, text/plain)
2025-01-03 17:26 UTC, 9Lukas5
no flags Details

Description fedora 2024-12-22 22:27:17 UTC
1. Please describe the problem:

Huawei Matebook 13 AMD with Radeon Vega 8.

After resuming from either suspend or hibernate, screen brightness control is non-effective and the system runs at full brightness. Values are changing at /sys/class/backlight/*/brightness and /sys/class/backlight/*/actual_brightness, but the screen continues at full brightness


2. What is the Version-Release number of the kernel:

kernel-6.12.5-200.fc41.x86_64


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

Yes, the fault is only present starting with kernel-6.12.5-200.fc41.x86_64


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Boot with kernel-6.12.5-200.fc41.x86_64, suspend or hibernate, resume.


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

Yes.


6. Are you running any modules that not shipped with directly Fedora's kernel?:

No


7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.


Reproducible: Always

Comment 1 fedora 2024-12-22 22:30:49 UTC
Created attachment 2063566 [details]
journalctl

Comment 2 fedora 2024-12-30 08:27:19 UTC
The fault still exists in vmlinuz-6.12.6-200.fc41.x86_64

Comment 3 fedora 2024-12-30 08:27:58 UTC
The fault still exists in vmlinuz-6.12.7-200.fc41.x86_64

Comment 4 Vlad 2024-12-30 12:00:32 UTC
I have similar issue with Fedora Silverblue with 6.12.6 kernel. When I unplug charger and suspend laptop and then resume - screen brightness begin to fade in at first, then jump to 0 and fade to 100 again multiple times, faster and faster and then screen just turns off and I need to do hard restart. I don't know if it can damage the screen - seems like it. When charger is plugged in - there is no such problem.

Laptop: Honor Magic Book 15
APU: Ryzen 5500U

Comment 5 9Lukas5 2025-01-03 17:25:49 UTC
I'm also affected from this with 6.12.6-200.fc41 and 6.12.7-200.fc41.
Latest version unaffected for me is 6.12.4-200.fc41

I'm using a Lenovo Ideapad Flex5 with an AMD Ryzen 4700U

Comment 6 9Lukas5 2025-01-03 17:26:53 UTC
Created attachment 2064599 [details]
journalctl kernel log containing a sleep/resume cycle

Comment 7 Hans de Goede 2025-01-06 09:35:11 UTC
Thank you for reporting this and sorry about the regression.

This should be fixed by:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=queue/6.12&id=6f300b3e29b20f23dffb0e046853e560a8e3da00

which will be in the upcoming 6.12.9 stable kernel release. Once 6.12.9 is released it should show up in the Fedora updates-testing repo soon after its release.

Comment 8 Hans de Goede 2025-01-06 09:37:37 UTC

*** This bug has been marked as a duplicate of bug 2333543 ***


Note You need to log in before you can comment on or make changes to this bug.