public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Deepak Saxena <dsaxena@plexity.net>
Cc: linux-pm@lists.osdl.org
Subject: Re: x86: Expected system state when resumed
Date: Tue, 21 Jul 2009 22:48:17 +0200	[thread overview]
Message-ID: <200907212248.18050.rjw@sisk.pl> (raw)
In-Reply-To: <20090721164542.GA30390@plexity.net>

On Tuesday 21 July 2009, Deepak Saxena wrote:
> 
> I am working on getting suspend/resume working on an x86 system
> (OLPC XO-1.5) where we are implementing ACPI based suspend/resume
> using Open Firmware and what I am seeing right now is that on 
> resume, we're not receiving interrupts so the system locks
> up in the suspend path when msleep() is called from the EHCI
> HCD resume code. lapic_resume() is being called so the APIC
> is being restored.  I'm looking for information on what else
> Linux's expectation from the firmware when control is handed back 
> before I start dumping every system register pre and post resume.

If that's 2.6.30 or later and your timer interrupt is MSI, for example, please
check if the timer interrupt is marked as IRQF_TIMER.  If it's not,
suspend_device_irqs() will mark it as disabled and it won't work during
early resume.

Best,
Rafael

  reply	other threads:[~2009-07-21 20:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 16:45 x86: Expected system state when resumed Deepak Saxena
2009-07-21 20:48 ` Rafael J. Wysocki [this message]
2009-07-22  2:09   ` Wu Zhangjin
2009-07-22 14:17   ` Deepak Saxena
2009-07-22 14:30     ` [linux-pm] " Rafael J. Wysocki
2009-07-29 15:08 ` Pavel Machek

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=200907212248.18050.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=dsaxena@plexity.net \
    --cc=linux-pm@lists.osdl.org \
    /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