> > and here's the one that failed and then ended up coming back on a keypress: > > > > ... > > [ 54.628375] PM: Saving platform NVS memory > > [ 54.628387] Disabling non-boot CPUs ... > > [ 63.554966] ACPI Exception: AE_BAD_PARAMETER, Returned by Handler > > for [EmbeddedControl] (20110112/evregion-474) > > [ 63.554992] ACPI Error: Method parse/execution failed > > [\_SB_.PCI0.SBRG.EC0_.RCTP] (Node f5c2dea0), AE_BAD_PARAMETER > > (20110112/psparse-536) > > [ 63.555022] ACPI Error: Method parse/execution failed > > [\_TZ_.RTMP] (Node f5c32fa8), AE_BAD_PARAMETER (20110112/psparse-536) > > [ 63.555047] ACPI Error: Method parse/execution failed > > [\_TZ_.TZ00._TMP] (Node f5c34018), AE_BAD_PARAMETER > > (20110112/psparse-536) > > [ 63.555079] Thermal: failed to read out thermal zone 0 > > [ 63.556361] CPU 1 is now offline > > [ 63.556944] PM: Restoring platform NVS memory > > [ 63.556944] Enabling non-boot CPUs ... > > [ 63.556944] Booting Node 0 Processor 1 APIC 0x1 > > [ 63.556279] Initializing CPU#1 > > ... > > > > which really doesn't tell me much, except that clearly something in > > ACPI-land is unhappy, and it looks thermal-related (that last error > > message comes from thermal_zone_device_update()). > > The thermal code failed to get the current > temperature (via AML "_TMP" method) because > the embedded controller (or our interface to it) malfunctioned. Hmm, on looking closer with Rafael, we discovered that this isn't the EC malfunctioning, these messages result from us disabling the EC via acpi_ec_block_transactions(). Apparently you've got a thermal zone with polling enabled every 30 seconds. These are quite rare, I've only seen them on asus boxes. This timeout happened during suspend when EC was disabled and thus the message. We should have frozen that work-queue... I don't know if fixing that symptom will fix the suspend problem, but it can't hurt. -Len Brown, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
