Bug 109232

Summary: Raven Ridge with ABM enabled turns display off erroneously on mostly black colored windows
Product: DRI Reporter: Samantha McVey <samantham>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium CC: david.francis, harry.wentland, nicholas.kazlauskas, waqasahmadtarar786
Version: XOrg git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
xorg log
none
dmesg log none

Description Samantha McVey 2019-01-06 17:42:53 UTC
Created attachment 142986 [details]
xorg log

With ABM off and brightness at the minimum (0), the screen is on but low brightness. If you set ABM to 4 and then maximize a black terminal window, the screen will for all intents and purposes turn itself off. When going back to a bright screen it will turn on again. By on and off here I don't mean actually off, but the brightness is almost not visible.

I am using a Lenovo A485
Comment 1 Samantha McVey 2019-01-06 17:43:10 UTC
Created attachment 142987 [details]
dmesg log
Comment 2 Samantha McVey 2019-01-06 18:27:23 UTC
I logged the actual and brightness settings with 1 second delay:

actual: 771 brightness: 0  abm level: 0 
actual: 771 brightness: 0  abm level: 0 
actual: 771 brightness: 0  abm level: 0 
actual: 771 brightness: 0  abm level: 0

ABM is turned to 4

/* Screen is on initially, but */
actual: 593 brightness: 0  abm level: 4 
actual: 428 brightness: 0  abm level: 4
/* About here the screen is basically off */
actual: 368 brightness: 0  abm level: 4
actual: 339 brightness: 0  abm level: 4
Comment 3 Martin Peres 2019-11-19 09:09:09 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/656.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.