Bug 58799

Summary: [HSW B0 desktop] S4 fail to resume
Product: DRI Reporter: shui yangwei <yangweix.shui>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: major    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
situation1 dmesg
none
situation1 /var/log/messages
none
situation2 /var/log/messages none

Description shui yangwei 2012-12-27 09:39:00 UTC 
Created attachment 72172 [details]
situation1 dmesg

Environment:
--------------------------
Kernel: (drm-intel-next-queued)c0c36b941b6f0be6ac74f340040cbb29d6a0b06c
Some additional commit info:
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Wed Dec 19 16:08:43 2012 +0000

    drm/i915: Return the real error code from intel_set_mode()


Bug detailed description:
--------------------------
--------------------------------------------------------------------------------
Observation with Haddock creek Board (AIO):

While resuming DUT from S4,DUT hangs in POST code 00d3,after one reboot DUT
resumes from the S4 state
********************************************************************************

Observation with Flathead creek Board (Desktop):

situation1:
---------------------------
While resuming DUT from S4,DUT hangs in POST code 00d5,after one power "OFF" &
power "ON" DUT resumes from the S4 state


situation2:
---------------------------
While resuming DUT from S4,DUT hangs in POST code 00d5,after one power "OFF" &
power "ON" DUT hangs in POST code 0004.
--------------------------------------------------------------------------------
Comment 1 shui yangwei 2012-12-27 09:40:37 UTC 
Created attachment 72173 [details]
situation1 /var/log/messages
Comment 2 shui yangwei 2012-12-27 09:43:02 UTC 
Created attachment 72174 [details]
situation2 /var/log/messages
Comment 3 Yi Sun 2013-02-05 06:59:17 UTC 
Now we haven't such hardware. But on another machine, the issue doesn't exist. The lspci is as following:
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:0412] (rev 06)

Can we close it?
Comment 4 Daniel Vetter 2013-02-05 11:59:44 UTC 
Yeah, I guess we can shrug this off as early silicon (or maybe bios) issues.

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.