x86: Expected system state when resumed

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

 



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.

Thanks,
~Deepak (an ARM person swimming in x86 land)

-- 
In the end, they will not say, "those were dark times,"  they will ask
"why were their poets silent?" - Bertold Brecht

_______________________________________________
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