Bug 101412 - [SKL] Dell XPS 9350 screen sometimes garbled after suspend/resume
Summary: [SKL] Dell XPS 9350 screen sometimes garbled after suspend/resume
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: low normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-13 20:30 UTC by milan.plzik
Modified: 2017-10-17 15:15 UTC (History)
1 user (show)

See Also:
i915 platform: SKL
i915 features: power/suspend-resume


Attachments
xorg output of the affected laptop (419.02 KB, text/plain)
2017-06-13 20:31 UTC, milan.plzik
no flags Details
lspci output on the affected laptop (8.61 KB, text/plain)
2017-06-13 20:31 UTC, milan.plzik
no flags Details
lshw on the affected laptop (15.20 KB, text/plain)
2017-06-13 20:32 UTC, milan.plzik
no flags Details

Description milan.plzik 2017-06-13 20:30:54 UTC
After a suspend/resume cycle, screen of Dell XPS 9350 becomes garbled (last tested with 4.11-rc8, linux mint/ubuntu-based) -- first few lines are correct, the rest being more-or-less static random white lines. This state is preserved across reboots, sometimes affecting POST screen.
A known remedy is to connect USB-C HDMI adapter and enter/leave dual-screen mode, which sometimes tends to make the screen working again.
Comment 1 milan.plzik 2017-06-13 20:31:27 UTC
Created attachment 131932 [details]
xorg output of the affected laptop
Comment 2 milan.plzik 2017-06-13 20:31:50 UTC
Created attachment 131933 [details]
lspci output on the affected laptop
Comment 3 milan.plzik 2017-06-13 20:32:28 UTC
Created attachment 131934 [details]
lshw on the affected laptop
Comment 4 Elizabeth 2017-06-14 19:13:19 UTC
Good afternoon, could you please add the parameter drm.debug=0xe in your grub, then remove the kern.log and boot again to get a clean kern.log for the bug and attach it together with a dmesg log?  
Once you provide more information, please change the tag from "NEEDINFO" o "REOPEN". Thank you.
Comment 5 Elizabeth 2017-08-16 17:01:59 UTC
Dropping priority since it seems hard to replicate.
Hello Milan,
Any update with latest kernel versions and/or drm-tip??
Thank you.
https://www.kernel.org/
https://cgit.freedesktop.org/drm-tip
Comment 6 milan.plzik 2017-08-16 17:07:41 UTC
Apologies, I did not have much time to look into it, as the affected laptop is now few thoudsands kilometres from me. Will try get results with the supplied debug info as soon as possible.
Comment 7 Elizabeth 2017-10-16 23:22:59 UTC
(In reply to milan.plzik from comment #6)
> Apologies, I did not have much time to look into it, as the affected laptop
> is now few thoudsands kilometres from me. Will try get results with the
> supplied debug info as soon as possible.
Sorry for pestering, just asking if there is any news on this case. Thanks.
Comment 8 milan.plzik 2017-10-17 09:01:03 UTC
Hi; no worries, you're asking at the right time. The laptop got its motherboard replaced and from the first feelings it could have had solved the issue. Let's close this and if the issues re-appear, there's always an option to re-open or file a new bug. Thanks a lot for patience (and apologies for lengthy delays).
Comment 9 Elizabeth 2017-10-17 15:15:32 UTC
(In reply to milan.plzik from comment #8)
> Hi; no worries, you're asking at the right time. The laptop got its
> motherboard replaced and from the first feelings it could have had solved
> the issue. Let's close this and if the issues re-appear, there's always an
> option to re-open or file a new bug. Thanks a lot for patience (and
> apologies for lengthy delays).
Thank you very much for the update, reporters feedback is always appreciated to not let this kind of cases in the uncertainty. Closing the bug then, if problem appear again please file a new bug.


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.