Bug 48492

Summary:	[ILK SNB regression] system hang while resuming from S3
Product:	DRI	Reporter:	Yi Sun <yi.sun>
Component:	DRM/Intel	Assignee:	Daniel Vetter <daniel>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	medium	CC:	ben, chris, daniel, guang.a.yang, jbarnes
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Yi Sun 2012-04-10 00:05:16 UTC

System Environment:
--------------------------
Platform:  SandyBrage(mobile & desktop), IronLake (E6510 with eDP)

Kernel: (drm-intel-fixes)b4db1e35ac59c144965f517bc575a0d75b60b03f

Bug detailed description:
-------------------------
After suspending to the memory, pressed the power button. The screen didn't turn up, meanwhile we weren't able to connect it with ssh, unless force power off, and restart machine. This issue happen on IronLake mobile platform and SandyBridge both desktop and mobile platform.

We tried the netconsole to catch the dmesg, but failed.

The issue doesn't exist on the -next-queued branch.

Comment 1 Daniel Vetter 2012-04-10 00:11:44 UTC

On Tue, Apr 10, 2012 at 07:05:16AM +0000, bugzilla-daemon@freedesktop.org wrote:
> Bug detailed description:
> -------------------------
> After suspending to the memory, pressed the power button. The screen didn't
> turn up, meanwhile we weren't able to connect it with ssh, unless force power
> off, and restart machine. This issue happen on IronLake mobile platform and
> SandyBridge both desktop and mobile platform.
> 
> We tried the netconsole to catch the dmesg, but failed.
> 
> The issue doesn't exist on the -next-queued branch.

I've had similar issues on my ilk and snb with plain 3.4-rc1. 3.4-rc2
works for me. I've already moved -fixes forward to that, so can you please
retest on latest -fixes?

Comment 2 Guang Yang 2012-04-10 19:24:06 UTC

(In reply to comment #1)
> On Tue, Apr 10, 2012 at 07:05:16AM +0000, bugzilla-daemon@freedesktop.org
> wrote:
> > Bug detailed description:
> > -------------------------
> > After suspending to the memory, pressed the power button. The screen didn't
> > turn up, meanwhile we weren't able to connect it with ssh, unless force power
> > off, and restart machine. This issue happen on IronLake mobile platform and
> > SandyBridge both desktop and mobile platform.
> > 
> > We tried the netconsole to catch the dmesg, but failed.
> > 
> > The issue doesn't exist on the -next-queued branch.
> I've had similar issues on my ilk and snb with plain 3.4-rc1. 3.4-rc2
> works for me. I've already moved -fixes forward to that, so can you please
> retest on latest -fixes?

Hi,daniel,I have try with the latest -fixes branch,
Kernel: (drm-intel-fixes)c4867936474183332db4c19791a65fdad6474fd5
the issue doesn't exist.

Comment 3 Chris Wilson 2012-04-11 03:06:35 UTC

Closing now that -next has merged in the suspend and resume fixes from -fixes and -rc2.

Comment 4 Guang Yang 2012-04-11 23:58:39 UTC

tested by guang yang

Comment 5 Elizabeth 2017-10-06 14:50:28 UTC

Closing old verified.

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.