[Bug 84903] [BSW] 3rd S3 fail with error, with i915 loaded

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Dec 1 21:23:34 PST 2014


https://bugs.freedesktop.org/show_bug.cgi?id=84903

wendy.wang at intel.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |ASSIGNED

--- Comment #13 from wendy.wang at intel.com ---
(In reply to Ville Syrjala from comment #11)
> (In reply to wendy.wang from comment #10)
> > Created attachment 110297 [details]
> > V47_s3_dmesg.log
> > 
> > Sorry, attached v47-s3-dmesg log file.
> 
> There's no failure in the log. Just a warning about new_config being out of
> whack
> "[  737.980749] WARN_ON(intel_crtc->new_config && intel_crtc->new_config !=
> &intel_crtc->config)"
> 
> It's harmless, but if you want to get rid of it you can cherry-pick
>  commit 2d3d111a8f34606469e589d3491c9a64f62310b8
>  Author: Ville Syrjälä <ville.syrjala at linux.intel.com>
>  Date:   Fri Nov 21 21:00:36 2014 +0200
> 
>     drm/i915: Don't clobber crtc->new_config when nothing changes
> 
> Is there an actual failure that affects the user?

Hello Ville,

I tested your patch: "commit 2d3d111a8f34606469e589d3491c9a64f62310b8",
With this commit + V47 BIOS+ BSW B1 CPU+ FAB2 board,
I can continually execute S3 command more than 5 cycles, feedback
i915_pm_resume_early message.-----------attach dmesg log:
ww39.2_patch_s3_dmesg.log

While double-check with kernel: tag drm-intel-nightly 2014-11-21, I only can do
S3 2 or 3 times, then IP address unavailable, S3 command fail to execute with
"resource temporary unavailable" message.
attach two dmesg log: WW39.2_v47_s3_3rd_Resume_dmesg1.log, 
WW39.2_v47_s3_2nd_Resume_dmesg2.log

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20141202/9cb96f9a/attachment.html>


More information about the intel-gfx-bugs mailing list