Bug 66951 - [Calpella Baytrail]Resume from S4 causes system reboot sporadically
Summary: [Calpella Baytrail]Resume from S4 causes system reboot sporadically
Status: CLOSED NOTOURBUG
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other All
: medium critical
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-16 07:50 UTC by cancan,feng
Modified: 2017-10-06 14:45 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
boot dmesg (84.15 KB, text/plain)
2013-07-17 05:50 UTC, cancan,feng
no flags Details

Description cancan,feng 2013-07-16 07:50:04 UTC
System Environment:
--------------------------------------------
Description :
Kernel: (drm-intel-next-queued)50b44a449ff1a19712ebc36ffccf9ac0a68033bf
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Wed Jun 5 13:34:33 2013 +0200

    drm/i915: clear DPLL reg when disabling i9xx dplls

Bug detail Description:
--------------------------------------------
System can suspend to disk successfully, but will reboot while resuming from S4 sporadically. This happens about 1 in 5 times. 

Reproduce step:
--------------------------------------------
1. booting up machine
2. echo disk > /sys/power/state --> system reboot
Comment 1 Daniel Vetter 2013-07-16 09:33:51 UTC
Wikipedia failed me, so what's a "Calpella" plaform? Also please attach dmesg with drm.debug=0xe for this machine (with all the boot messages).
Comment 2 Chris Wilson 2013-07-16 09:38:38 UTC
Capella is the 5-series chipset, used by Arrandale (Ironlake GPU).
Comment 3 Daniel Vetter 2013-07-16 12:02:25 UTC
Ok, now I'm back in the game ;-)

First things first: Is this a regression, or do older kernels (e.g. 3.9 or so) also sometimes randomly crash in resume?
Comment 4 cancan,feng 2013-07-17 01:30:10 UTC
(In reply to comment #1)
> Wikipedia failed me, so what's a "Calpella" plaform? Also please attach

Calpella and Piketon are both Ironlake platform, Calpella is a mobile platform and Piketon is a desktop platform. This S4 issue can reproduce on Calpella easily, about 1 in 3~5 times. I also did S4 syscles on Piketon about 30 times, but Piketon did it ok. That's why I marked the title "Calpella". ;-)

> dmesg with drm.debug=0xe for this machine (with all the boot messages).

I did try many times to get the boot messages but falied. Generally, we get messages through three ways: "dmesg", netconsole and serial port. These are my difficulties here:
1. Because the machine will reboot while this issue happens, so I can't get messages directly from "dmesg".
2. It's a S4 issue, and netconsole can't work. Because netconsole can't receive output info after machine resume from S4.
3. This mobile platform has no serial port, so we can't get messages from serial port..

So I don't know how to get the boot messages while this issue happens,;-( 
Do you have any advice?
Comment 5 cancan,feng 2013-07-17 03:41:24 UTC
(In reply to comment #3)
> Ok, now I'm back in the game ;-)
> 
> First things first: Is this a regression, or do older kernels (e.g. 3.9 or
> so) also sometimes randomly crash in resume?

I tried 3.9, 3.8 and 3.6 kernel but can't find a good commit.. It's very wired..
Here I describe the issue details: 
After suspend to S4 successfully, I press power button, then system begin to resume. In grub stage, I select one kernel, and now the machine will reboot again..
Comment 6 Daniel Vetter 2013-07-17 04:56:48 UTC
Oh, I just wanted to have dmesg from a normal boot so that we know a bit about the details of the machine. After S4 it seems to die too early to grab anything ...
Comment 7 cancan,feng 2013-07-17 05:50:18 UTC
Created attachment 82522 [details]
boot dmesg
Comment 8 Jani Nikula 2013-08-08 14:19:50 UTC
(In reply to comment #5)
> (In reply to comment #3)
> > Ok, now I'm back in the game ;-)
> > 
> > First things first: Is this a regression, or do older kernels (e.g. 3.9 or
> > so) also sometimes randomly crash in resume?
> 
> I tried 3.9, 3.8 and 3.6 kernel but can't find a good commit.. It's very
> wired..
> Here I describe the issue details: 
> After suspend to S4 successfully, I press power button, then system begin to
> resume. In grub stage, I select one kernel, and now the machine will reboot
> again..

Is this reproducible without i915 loaded?
Comment 9 shui yangwei 2013-08-09 07:18:17 UTC
(In reply to comment #8)
> (In reply to comment #5)
> > (In reply to comment #3)
> > > Ok, now I'm back in the game ;-)
> > > 
> > > First things first: Is this a regression, or do older kernels (e.g. 3.9 or
> > > so) also sometimes randomly crash in resume?
> > 
> > I tried 3.9, 3.8 and 3.6 kernel but can't find a good commit.. It's very
> > wired..
> > Here I describe the issue details: 
> > After suspend to S4 successfully, I press power button, then system begin to
> > resume. In grub stage, I select one kernel, and now the machine will reboot
> > again..
> 
> Is this reproducible without i915 loaded?

Yes, this issue also exist without i915 loaded. The machine will probably reboot when resume from S4, I tried the reliability test of S4 two times, the first time failed at 5th round , the second time failed at 2nd round.
Comment 10 Jani Nikula 2013-08-09 07:46:06 UTC
(In reply to comment #9)
> > Is this reproducible without i915 loaded?
> 
> Yes, this issue also exist without i915 loaded. The machine will probably
> reboot when resume from S4, I tried the reliability test of S4 two times,
> the first time failed at 5th round , the second time failed at 2nd round.

Reproducible without our driver -> NOTOURBUG. Please report this, uhm, wherever is the appropriate place... bugzilla.kernel.org or lkml.
Comment 11 shui yangwei 2013-09-11 10:38:09 UTC
I find this issue also exists on Baytrail machine.
Comment 12 Guang Yang 2013-09-11 14:29:19 UTC
Tracked this issue as not gfx driver's bug at https://bugzilla.kernel.org/show_bug.cgi?id=60804
Comment 13 Elizabeth 2017-10-06 14:45:05 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.