Bug 93230 - eDP brightness flicker when you control it(also HDMI plugged), and return from S3 fails
Summary: eDP brightness flicker when you control it(also HDMI plugged), and return fro...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: All All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-03 15:47 UTC by Marco Del Mastro
Modified: 2016-06-20 06:53 UTC (History)
2 users (show)

See Also:
i915 platform: BYT
i915 features: display/eDP, display/HDMI


Attachments
dmesg file (1001.15 KB, text/plain)
2015-12-03 15:47 UTC, Marco Del Mastro
no flags Details
xrandr file (13.84 KB, text/plain)
2015-12-03 15:47 UTC, Marco Del Mastro
no flags Details
intel_reg_dumper file (17.27 KB, text/plain)
2015-12-03 15:48 UTC, Marco Del Mastro
no flags Details
dmesg with drm.debug=14 (641.19 KB, text/plain)
2015-12-04 14:06 UTC, Marco Del Mastro
no flags Details
dmesg with drm.debug=14 (1001.56 KB, text/plain)
2015-12-17 15:51 UTC, Marco Del Mastro
no flags Details

Description Marco Del Mastro 2015-12-03 15:47:02 UTC
Created attachment 120305 [details]
dmesg file

I have a board based on Intel Atom E38xx (Bay Trail), if I plug HDMI/DP and an eDP, when I control the brightness value, I see some flicker on eDP.
Other problem is about S3 state(standby), when I return from standby, the eDP is off and my board freezes.

If I plug only the eDP, I don't see any bug, the brightness control works fine and the S3 state works fine.

System information :
- system architecture : i686
- kernel version : 4.4.0-rc2+
- linux ubuntu 15.10
- display connection : HDMI/DP and eDP

Attached:
- dmesg.txt
- xrandr.txt
- intel_reg_dumper.txt
Comment 1 Marco Del Mastro 2015-12-03 15:47:39 UTC
Created attachment 120306 [details]
xrandr file
Comment 2 Marco Del Mastro 2015-12-03 15:48:06 UTC
Created attachment 120307 [details]
intel_reg_dumper file
Comment 3 Jani Nikula 2015-12-04 13:21:24 UTC
Do you have some local, non-upstream modifications in the kernel?

Please add drm.debug=14 module parameter, and attach dmesg all the way from boot to the problem. The early boot is missing and the logs are filled with atomic debugging.
Comment 4 Marco Del Mastro 2015-12-04 14:05:38 UTC
I don't have any local, non-upstream modifications in the kernel

Attached the dmesg file with drm.debug=14 parameter.
Comment 5 Marco Del Mastro 2015-12-04 14:06:10 UTC
Created attachment 120348 [details]
dmesg with drm.debug=14
Comment 6 Adolfo 2015-12-16 15:20:50 UTC
Hello Marco

I think there is a mistake in the latest attachment, if you check the kernel command line it still shows drm.debug=0x1e instead of drm.debug=0x14.
Comment 7 Marco Del Mastro 2015-12-17 15:51:30 UTC
Created attachment 120566 [details]
dmesg with drm.debug=14

the correct dmesg with drm.debug=14
Comment 8 Jani Nikula 2016-06-17 15:57:22 UTC
There are some issues in the logs that we think we've fixed. Closing. Please reopen if the problem persists with latest kernels.


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.