[Bug 66301] New: [HSW mobile] resume from s4 sporadically causes call trace and machine is reachable
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Jun 28 00:26:42 PDT 2013
https://bugs.freedesktop.org/show_bug.cgi?id=66301
Priority: medium
Bug ID: 66301
Assignee: intel-gfx-bugs at lists.freedesktop.org
Summary: [HSW mobile] resume from s4 sporadically causes call
trace and machine is reachable
QA Contact: intel-gfx-bugs at lists.freedesktop.org
Severity: major
Classification: Unclassified
OS: All
Reporter: yangweix.shui at intel.com
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/Intel
Product: DRI
Created attachment 81617
--> https://bugs.freedesktop.org/attachment.cgi?id=81617&action=edit
dmesg: S4 cause call trace sporadically
Environment:
-------------------------
Acer Haswell Notebook Aspire V3 772G 17.3 ;
Host bridge ID=0x0c04 (rev 06);
VGA ID=0x0416 (rev06);
CPU: i7-4702MQ 2.2GHz;
BIOS:v1.04 MEM: 4G ;
Kernel: (drm-intel-next-queued)9199918a1e148c18e3519cb7b2d90a127d7ea87b
Author: Daniel Vetter <daniel.vetter at ffwll.ch>
Date: Thu Jun 27 17:52:15 2013 +0200
drm/i915: fix hpd interrupt register locking
Description:
-------------------------
Running S4 on HSW mobile acer product will cause call trace sporadically, It
will reproduced about loop running S4 3 times. The machine is reachable. Remove
i915, S4 works well. I also test another MSI HSW mobile product, S4 is good.
I list the MSI machine info below:
--------
MSI Haswell Notebook MSI MS-16GC Notebook 15.6;
Host bridge ID=0x0c04 (rev 06);
VGA ID=0x0416 (rev06);
CPU: i7-4700MQ 2.4GHz
BIOS: E16GCIMS.509 (04/24/2013) EC: 16GCEMS1 ver5.00 (04/12/2013);
ME: 9.0.2.1345;
reproduce step:
-------------------------
1. boot up machine
2. loop running S4 about 3 times.
3. call trace will come up on screen.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20130628/652c2ce9/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list