Re: x86: Expected system state when resumed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
_______________________________________________
linux-pm mailing list
linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/linux-pm

[Index of Archives]     [Linux ACPI]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [CPU Freq]     [Kernel Newbies]     [Fedora Kernel]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux