Created attachment 131787 [details] dmesg ==Bug detailed description== -------------------------------------------------- DP with single sources transmission configuration present some irregular events. When the platform send to S3 and unplug DP and plug again DP the platform wake up by itself ------------------------------------------------- ==Steps to reproduce== -------------------------------------------------- Connect platform to DP using required dongle Turn device ON Login to you user account Send to S3 (echo mem > /sys/power/state) Unplug the DP cable Wait 10 seconds Plug the DP cable Resume back from S3 state Verify that the displays doesn't have any corruption -------------------------------------------------- ==Actual results== -------------------------------------------------- Platform wake up with the plug event ------------------------------------------------- ==Expected results== -------------------------------------------------- Platform doesn't wake up with the plug event --------------------------------------------------- ==Software configuration== -------------------------------------------------- kernel version : 4.12.0-rc3- architecture : x86_64 os version : Ubuntu 17.04 xserver : X.Org X Server 1.19.99.1 -------------------------------------------------- ==kernel configuration== -------------------------------------------------- commit: 187376e ==Attachments== -------------------------------------------------- dmesg
Could you please add the HW information?
Hi, adding required information: ====================================== Hardware ====================================== platform : BDW motherboard id : NUC5i7RYB form factor : Desktop cpu family : Core i7 cpu family id : 6 cpu information : Intel(R) Core(TM) i7-5557U CPU @ 3.10GHz gpu card : Intel Corporation Iris Graphics 6100 (rev 09) (prog-if 00 [VGA controller]) memory ram : 15.58 GB max memory ram : 16 GB display resolution : 1600x900 cpu thread : 4 cpu core : 2 cpu model : 61 cpu stepping : 4 socket : Socket BGA1168 signature : Type 0, Family 6, Model 61, Stepping 4 hard drive : 111GiB (120GB) current cd clock frequency : 337500 kHz maximum cd clock frequency : 540000 kHz displays connected : DP-2
First of all. Sorry about spam. This is mass update for our bugs. Sorry if you feel this annoying but with this trying to understand if bug still valid or not. If bug investigation still in progress, please ignore this and I apologize! If you think this is not anymore valid, please comment to the bug that can be closed. If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Created attachment 138601 [details] dmesg-s3-unplug I can't reproduce this issue on BDW anymore. Closing.
====================================== Software ====================================== kernel version : 4.16.0 hostname : gfx-desktop architecture : x86_64 os version : Ubuntu 17.10 os codename : artful kernel driver : i915 bios revision : 5.6 bios release date : 01/16/2017 hardware acceleration : disabled swap partition : enabled on (/dev/sda2) ====================================== Hardware ====================================== platform : Broadwell motherboard id : NUC5i5MYBE form factor : Desktop cpu family : Core i5 cpu family id : 6 cpu information : Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz gpu card : Intel Corporation HD Graphics 5500 (rev 09) (prog-if 00 [VGA controller]) memory ram : 11.6 GB max memory ram : 16 GB display resolution : 5440x1080 cpu thread : 4 cpu core : 2 cpu model : 61 cpu stepping : 4 socket : Socket BGA1168 signature : Type 0, Family 6, Model 61, Stepping 4 hard drive : 111GiB (120GB) current cd clock frequency : 337500 kHz maximum cd clock frequency : 540000 kHz ====================================== kernel parameters ====================================== quiet splash drm.debug=0xe log_bug_len=16M I'm using latest stable on kernel.org
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.