https://bugzilla.kernel.org/show_bug.cgi?id=21952
Len Brown <l...@kernel.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |ASSIGNED
Component|intel_idle |Power-Sleep-Wake
Product|Power Management |ACPI
Summary|resume hangs unless |resume hangs unless
|intel_idle.max_cstate=3 or |intel_idle.max_cstate=3 or
|maxcpus=1 - Samsung N145, |maxcpus=1 - Samsung N145,
|N148, N150, N210 |N148, N150, N210, Lenovo
| |S10-3
--- Comment #58 from Len Brown <l...@kernel.org> 2012-08-24 03:34:11 ---
Regarding the Lenovo S10-3...
originally its resume problem was fixed by this patch in 2.6.36:
commit 4731fdcf6f7bdab3e369a3f844d4ea4d4017284d
Author: Len Brown <len.br...@intel.com>
Date: Fri Sep 24 21:02:27 2010 -0400
intel_idle: PCI quirk to prevent Lenovo Ideapad s10-3 boot hang
You can tell if that quirk is running b/c it spews a dmesg line:
[ 0.624375] pci 0000:00:1f.0: [Firmware Bug]: TigerPoint LPC.BM_STS cleared
The way that original issue was debugged was finding the difference
between the working acpi_idle and the failing intel_idle.
But today the failure is different.
I have access to a Lenovo S10-3
I just dropped FC17 on it, which is 3.5.2, and resume hangs
with a black screen. The quirk above is in place.
intel_idle.max_cstate=3 allows resume to work.
But some cmdline params that fail are surprising:
intel_idle.max_cstate=1
maxcpus=1
intel_idle.max_cstate=0
intel_idle.max_cstate=0 processor.max_cstate=1
intel_idle.max_cstate=0 processor.max_cstate=2 (gives MWAIT 0x10)
cpuidle.off=1 crashes on boot
nohpet
idle=poll
here is a clue, after leaving the system "failed" for about 5 minutes
it actually resumed, and dmesg says this:
[ 118.624575] PM: Syncing filesystems ... done.
[ 118.627338] PM: Preparing system for mem sleep
[ 118.779349] Freezing user space processes ... (elapsed 0.01 seconds) done.
[ 118.791287] Freezing remaining freezable tasks ... (elapsed 0.01 seconds)
done.
[ 118.802295] PM: Entering mem sleep
[ 118.802338] Suspending console(s) (use no_console_suspend to debug)
[ 118.803318] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[ 118.803577] sd 1:0:0:0: [sda] Stopping disk
[ 119.169169] ACPI handle has no context!
[ 119.365118] PM: suspend of devices complete after 562.255 msecs
[ 119.365590] PM: late suspend of devices complete after 0.459 msecs
[ 119.377247] pcieport 0000:00:1c.0: wake-up capability enabled by ACPI
[ 119.388261] ehci_hcd 0000:00:1d.7: wake-up capability enabled by ACPI
[ 119.399244] uhci_hcd 0000:00:1d.3: wake-up capability enabled by ACPI
[ 120.757907] uhci_hcd 0000:00:1d.1: wake-up capability enabled by ACPI
[ 120.758006] uhci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI
[ 120.758137] PM: noirq suspend of devices complete after 1392.536 msecs
[ 120.758174] ACPI: Preparing to enter system sleep state S3
[ 120.784273] PM: Saving platform NVS memory
[ 120.784330] Disabling non-boot CPUs ...
[ 120.786548] CPU 1 is now offline
[ 120.787428] Extended CMOS year: 2000
[ 120.787428] ACPI: Low-level resume complete
[ 120.787428] PM: Restoring platform NVS memory
[ 120.787428] CPU0: Thermal monitoring handled by SMI
[ 120.787428] Extended CMOS year: 2000
[ 120.787428] microcode: CPU0 updated to revision 0x107, date = 2009-08-25
[ 120.792528] Enabling non-boot CPUs ...
[ 120.792749] Booting Node 0 Processor 1 APIC 0x1
[ 120.807014] microcode: CPU1 updated to revision 0x107, date = 2009-08-25
[ 120.812158] CPU1 is up
[ 120.812539] ACPI: Waking up from system sleep state S3
[ 424.700077] ACPI Exception: AE_TIME, Returned by Handler for
[EmbeddedControl] (20120320/evregion-501)
[ 424.700185] ACPI Error: Method parse/execution failed
[\_SB_.PCI0.LPCB.EC0_.DSSV] (Node ffff88003d1d0488), AE_TIME
(20120320/psparse-536)
[ 424.700228] ACPI Error: Method parse/execution failed [\_WAK] (Node
ffff88003d1cbaf0), AE_TIME (20120320/psparse-536)
[ 424.700402] ACPI Exception: AE_TIME, While executing method \_WAK
(20120320/hwesleep-82)
[ 424.721458] uhci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI
[ 424.728327] uhci_hcd 0000:00:1d.1: wake-up capability disabled by ACPI
[ 424.732428] uhci_hcd 0000:00:1d.3: wake-up capability disabled by ACPI
[ 424.732540] ehci_hcd 0000:00:1d.7: wake-up capability disabled by ACPI
[ 424.733523] PM: noirq resume of devices complete after 21.159 msecs
[ 424.733927] PM: early resume of devices complete after 0.323 msecs
So it appears that we had some kind of time-out in the EC while evaluating _WAK
This is not intel_idle specific, and it looks like ACPI,
so moving bug categories.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
