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

Bug#562008: ACPI wakeup doesn't work on ASUS P8H67-M EVO



Hi,

On 12/12/11 03:29, Jonathan Nieder wrote:
Hey Eric,

Eric Lavarde wrote:

root@hdvdr:~# dmesg | grep -i rtc
[    1.229556] rtc_cmos 00:04: RTC can wake from S4
[    1.229653] rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
[    1.229679] rtc0: alarms up to one month, y3k, 114 bytes nvram
[...]
Broadcast message from root@hdvdr (pts/0) (Sat Nov 26 12:17:17 2011):

The system is going down for system halt NOW!

How did you shut down the machine?  Does suspend-to-disk ("echo
I tried poweroff and halt, same (negative) result.

disk>/sys/power/state") work fine in general?
No idea in general, but I made some tests.

First, it kind of worked: after restarting the computer, I got error messages in dmesg like the following:
[  569.260555] PM: Image restored successfully.
[  569.260556] Restarting tasks ... done.
[  569.260643] PM: Basic memory bitmaps freed
[  569.260646] video LNXVIDEO:00: Restoring backlight state
[  569.336385] zd1211rw 1-1.4:1.0: firmware version 4725
[ 569.376318] zd1211rw 1-1.4:1.0: zd1211b chip 0ace:1215 v4810 high 00-02-72 AL2230_RF pa0 g--NS
[  569.394922] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  570.265915] I2C timeout
[  570.265921] IRS 00000001
[  571.264229] I2C timeout
[  571.264234] IRS 00000001
[  572.262546] I2C timeout
[  572.262552] IRS 00000001
[  573.260870] I2C timeout
[  573.260875] IRS 00000001
[  574.259168] I2C timeout
[  574.259174] IRS 00000001
[  574.646076] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  575.257486] I2C timeout
[  575.257491] IRS 00000001
[  576.255805] I2C timeout
[  576.255810] IRS 00000001
[  577.254120] I2C timeout
[  577.254125] IRS 00000001
[  578.252435] I2C timeout
[  578.252440] IRS 00000001
[  578.252442] stv0367: i2c_write error
[  579.250752] I2C timeout
[  579.250757] IRS 00000001
[  579.250758] tda18212: i2c_write error
[  580.249069] I2C timeout
[  580.249073] IRS 00000001
[  580.249075] stv0367: i2c_write error
[  581.247437] I2C timeout
[  581.247442] IRS 00000001
[... hundreds of line of this type ...]
[  676.092300] tda18212: i2c_write error
[  677.089780] I2C timeout
[  677.090203] IRS 00000001
[  677.090607] stv0367: i2c_write error
[  677.090737] c_release
[  677.091408] DDBridge 0000:03:00.0: PCI INT A disabled

And VDR was frozen for perhaps one minute, then it restarted itself, and then everything was fine. Only WLAN was still not working, unplug/plug the USB stick did make it work again.

Then I modified my test script to set the wake-up time and disk > state but then my computer froze (see attached picture). After reboot, I tried again, shutting off nodm (for vdr-sxfe) and vdr before calling my test script. And the computer woke up!

So I tried echo standby > /sys/power/state but then computer didn't wake up.

A last test with disk > state did work again (ok, WLAN had to be helped again).

Sounds promising, thanks for this. I thought nevertheless that disk suspend doesn't have a special power state but is just a special way to shutoff and reboot. Am I wrong? Could the "shutoff" method of disk suspend be copied to normal shutdown?

Thanks already, I feel better :-)
 Eric

Attachment: hang_after_disk_power_state.jpg
Description: JPEG image


Reply to: