Bug 212003 - Regression: Screen ignores ACPI intel_backlight sysfs values greater than 1
Summary: Regression: Screen ignores ACPI intel_backlight sysfs values greater than 1
Status: CLOSED MOVED
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Video (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: Zhang Rui
URL: https://gitlab.freedesktop.org/drm/in...
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-28 23:43 UTC by Brandon Arnold
Modified: 2021-03-08 07:32 UTC (History)
2 users (show)

See Also:
Kernel Version: Linux 5.11.2-arch1-1 x86_64
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
dmesg (101.55 KB, text/plain)
2021-02-28 23:43 UTC, Brandon Arnold
Details
systemd boot config with linux kernel parameters (232 bytes, text/plain)
2021-02-28 23:45 UTC, Brandon Arnold
Details
Xorg.conf when in optimus modesetting i915 mode (715 bytes, text/plain)
2021-02-28 23:46 UTC, Brandon Arnold
Details
Xorg.conf when in nvidia mode (342 bytes, text/plain)
2021-02-28 23:47 UTC, Brandon Arnold
Details
lspci -k (6.19 KB, text/plain)
2021-03-01 00:04 UTC, Brandon Arnold
Details

Description Brandon Arnold 2021-02-28 23:43:34 UTC
Created attachment 295535 [details]
dmesg

In a recent update, the values of /sys/class/backlight/intel_backlight/brightness no longer correspond with my screen brightness.

Steps to reproduce:

Change the value of /sys/class/backlight/intel_backlight/brightness to an integer from 0-255 (where 255 is the max_brightness).

Expected results:

At value 0, the screen is off, and at values 1-255, the screen gradually goes from dim to full brightness.

Actual results:

At value 0, the screen is off, and at values 1-255, the screen is the same brightness.

My system: 

My system requires the i915.enable_dpcd_backlight=1 kernel parameter for this feature to work. But I performed a normal Arch system upgrade to 5.11.2-arch1-1 on 2/21/2021, which has caused the behavior above. My linux version before the upgrade was 5.10.16.arch1-1. 

I tried many values of the other kernel parameters acpi_backlight but they did not resolve anything. My hardware is Dell XPS 17 9700 with an NVIDIA Optimus graphics hardware. The optimus setup uses i915 for the intel modesetting and nvidia for the main nvidia setting.
Comment 1 Brandon Arnold 2021-02-28 23:45:26 UTC
Created attachment 295537 [details]
systemd boot config with linux kernel parameters
Comment 2 Brandon Arnold 2021-02-28 23:46:38 UTC
Created attachment 295539 [details]
Xorg.conf when in optimus modesetting i915 mode
Comment 3 Brandon Arnold 2021-02-28 23:47:02 UTC
Created attachment 295541 [details]
Xorg.conf when in nvidia mode
Comment 4 Brandon Arnold 2021-03-01 00:01:39 UTC
Update: I put version 5.10.16.arch1-1 as the kernel that was working, but I cannot guarantee this is true. It may have broken sooner than this, but it was certainly in the month of February, during which I upgraded several times starting from 5.10.11.
Comment 5 Brandon Arnold 2021-03-01 00:04:13 UTC
Created attachment 295543 [details]
lspci -k
Comment 6 Zhang Rui 2021-03-04 03:31:43 UTC
can you check both vanilla 5.10 and 5.11 kernel and see if this is an upstream regression?
Comment 7 Zhang Rui 2021-03-04 03:38:02 UTC
If this is an upstream regression, it is probably a graphics problem.
It would be great if you can use git bisect to find out the offending commit.
Comment 8 Brandon Arnold 2021-03-04 06:46:07 UTC
Thanks Zhang, I will check this weekend.
Comment 9 Brandon Arnold 2021-03-05 03:46:02 UTC
Confirmed after downgrading only the kernel package that the problem does not exist in 5.10.16. I will git bisect it this weekend.
Comment 10 Brandon Arnold 2021-03-08 02:15:35 UTC
Hi Zhang. You were right. It came from the intel-drm project. I singled out the offending commit to be 98e497e203a5, "[1/2] drm/i915/dpcd_bl: uncheck PWM_PIN_CAP when detect eDP backlight capabilities".

I have found a similar bug report and will tag my information there. I have updated the URL for this bug to be that bug report.

I also noticed that the kernel is well into the 5.12 branch and the affected codefile has gone through a lot of refactoring, so I'm going to rebuild that branch and see if they have already fixed it.
Comment 11 Brandon Arnold 2021-03-08 02:35:01 UTC
Not fixed in 5.12 yet. Anywho feel free to close this bug as a dupe.
Comment 12 Zhang Rui 2021-03-08 07:32:29 UTC
Thanks for update.
Bug closed.

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