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.
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?
(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.
Closing now that -next has merged in the suspend and resume fixes from -fixes and -rc2.
tested by guang yang
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.