xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Marek Marczykowski <marmarek@invisiblethingslab.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Joanna Rutkowska <joanna@invisiblethingslab.com>
Subject: Re: Resume not working on 2nd gen Core i5
Date: Fri, 24 Feb 2012 17:03:28 +0100	[thread overview]
Message-ID: <4F47B4D0.2030806@invisiblethingslab.com> (raw)
In-Reply-To: <20120224055418.GA11780@phenom.dumpdata.com>


[-- Attachment #1.1: Type: text/plain, Size: 1802 bytes --]

On 24.02.2012 06:54, Konrad Rzeszutek Wilk wrote:
>>>>>>> Does anybody have a similar problem on 2nd Gen Core i5? Any advises how
>>>>>>> to approach debugging it?
>>>>>>>
> .. snip..
>> (the same hardware)
>> On 2.6.38.3 xenlinux kernel after resume there is screen content from before
>> suspend, power led light constantly (as it should), but system is
>> irresponsible (no capslock led, no reaction to sysrq, network etc).
>> On 3.x with your patches system goes into S3, but on resume is even worse - no
>> screen content at all (and no backlight) and also irresponsible, power led
>> still blinking. As 3.x tried:
>>  - your devel/acpi-s3.v7 branch directly
>>  - 3.2.7 merged with devel/acpi-s3.v7
>>  - 3.3-rc4 with devel/acpi-s3.v7
> 
> OK. That is weird - it worked for me last time. One thing at at time then -
> try doing this from text-mode, so no graphic mode involved. For that you might
> need to disable your i915 driver altogether. Then just run 'pm-suspend' and
> see where it stops.
> 
> The next part is... Wait a minute, this reminds me of something I encountered
> with a SandyBrige i2100 - the suspend would work, but resume would get stuck.
> 
> The issue was with the hypervisor and if I had the acpi-cpufreq drivers loaded
> it resumed just fine. If I didn't - so hypervisor had no idea about C states or
> P states, it would be stuck in the default_idle and never come back.
> 
> So you might want for fun try also using the stable/processor-passthru.v5 and
> build it with CONFIG_XEN_PROCESSOR_PASSTHRU=y.

Looks much better. At least for few suspend/resume it works. Thanks!
And: when is it planned to upstream above patches (acpi-s3 and
processor-passthru)?

-- 
Best Regards / Pozdrawiam,
Marek Marczykowski
Invisible Things Lab


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 554 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2012-02-24 16:03 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
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 [this message]
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=4F47B4D0.2030806@invisiblethingslab.com \
    --to=marmarek@invisiblethingslab.com \
    --cc=joanna@invisiblethingslab.com \
    --cc=konrad.wilk@oracle.com \
    --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).