From: Joanna Rutkowska <joanna@invisiblethingslab.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Marek Marczykowski <marmarek@mimuw.edu.pl>
Subject: Re: Resume not working on 2nd gen Core i5
Date: Thu, 23 Feb 2012 18:39:29 +0100 [thread overview]
Message-ID: <4F4679D1.3000806@invisiblethingslab.com> (raw)
In-Reply-To: <20120223173146.GA22922@phenom.dumpdata.com>
[-- Attachment #1.1: Type: text/plain, Size: 1949 bytes --]
On 02/23/12 18:31, Konrad Rzeszutek Wilk wrote:
> On Thu, Feb 23, 2012 at 09:18:27AM -0500, Konrad Rzeszutek Wilk wrote:
>> On Thu, Feb 23, 2012 at 10:13:56AM +0100, Joanna Rutkowska wrote:
>>> Hello,
>>>
>>> I've been trying to resolve the issue of my T420s (Core i5 2540M, Intel
>>> integrated GPU) freezing at resume from S3 sleep... It seems like a
>>> Xen-related problems, as a similar kernel to what we use in Dom0
>>> (2.6.38+xenlinux), when run on baremetal shows no signs of problems at
>>> suspend/resume. Also I cannot find any problems reported on the internet
>>> with people having problems here.
>>>
>>> Unfortunately the only COM port on ExpressCard I have, presents itself
>>> as a USB device, and so I cannot really debug this issue via console.
>>> The /var/log/pm-suspend also doesn't reveal anything useful (after I
>>> reboot, that is).
>>>
>>> Does anybody have a similar problem on 2nd Gen Core i5? Any advises how
>>> to approach debugging it?
>>>
>>> I'm running Xen 4.1.1 with some minor patches, and 2.6.38 with xenlinux
>>> patches, and the i915 for the graphics. (Unfortunately I cannot just
>>> boot the same Dom0 kernel without Xen, as the GRUB complains about
>>> executable being unrecognized -- probably some problem with wrong
>>> compression algo).
>>>
>>> I also tried 3.2.5 pvops kernel for Dom0 (essentially a vanilla kernel)
>>> -- in this case it's even worse, as the system hangs at suspend and
>>> never enters S3 :/
>>
>> Right. You need some patches for that in git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git devel/acpi-s3.v7
>> to make that work.
>
> What I meant to say - please try it out with those patches. It might that you
> are hitting on one of the Intel bugs of the video adapter that I think
> are mostly fixed in the upstream kernel.
So, you're saying those (presumed) bugs a fixed only in the pvops, and
not in xenlinux?
joanna.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-02-23 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 9:13 Resume not working on 2nd gen Core i5 Joanna Rutkowska
2012-02-23 14:18 ` Konrad Rzeszutek Wilk
2012-02-23 17:31 ` Konrad Rzeszutek Wilk
2012-02-23 17:39 ` Joanna Rutkowska [this message]
2012-02-23 18:03 ` Konrad Rzeszutek Wilk
2012-02-24 1:01 ` Marek Marczykowski
2012-02-24 5:54 ` Konrad Rzeszutek Wilk
2012-02-24 16:03 ` Marek Marczykowski
2012-02-24 23:09 ` Konrad Rzeszutek Wilk
2012-02-24 9:55 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F4679D1.3000806@invisiblethingslab.com \
--to=joanna@invisiblethingslab.com \
--cc=konrad.wilk@oracle.com \
--cc=marmarek@mimuw.edu.pl \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).