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

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

Hello,

On 14/01/12 17:33, Jonathan Nieder wrote:

Eric Lavarde wrote:


I'm surely not experienced in these topics, but I thought that there
should be no difference for the BIOS / ACPI between a pure shutdown
and a suspend to disk.


Nah, they are different.  Suspend to disk happens with ACPI
cooperation.

[...]

Let me know if I can test / do anything further to solve the issue,


It's possible your machine only supports wake from S4 and not S5, in
which case the best bet would be to get your (out-of-tree?) driver
to suspend to disk sanely.  By the way, has there been any effort to
get that out-of-tree driver merged upstream?  Please file a bug
describing the missing functionality it provides, and I can try
working on that.

All that said, I see no reason _in principle_ that a machine that can
wake from S4 should not be able to wake from S5.  It might be possible
to debug this as an ACPI or RTC issue.  Please test 3.2-rc7 from
experimental without any out-of-tree drivers, and provide:

  i.  full "dmesg" output from booting, setting the wakeup timer,
      hibernating with "echo disk>/sys/power/state", and waking up

  ii. information about what happens if you instead boot, set the wakeup
      time, shutdown with "shutdown -h now", and wake up
Done (see attached files from an xterm -l logfile + the script used) - in the 2nd case it doesn't wake up, so that's easy... 



Also, when you set the wakeup timer, is it visible from the CMOS menus?
If it is, that might help in comparing what happens in cases (i)
and (ii).
With "CMOS menus" you mean the BIOS? If yes, then it doesn't appear, I only see what I enter in the BIOS. Perhaps interesting: if I do a 'cat /proc/driver/rtc' after a reboot (i.e. before having entered myself a time), I see what I entered manually in the BIOS under alrm_time and 
alrm_date:

rtc_time        : 07:39:05
rtc_date        : 2012-01-17
alrm_time       : 18:15:00
alrm_date       : 2012-01-17
alarm_IRQ       : yes
alrm_pending    : no
update IRQ enabled      : no
periodic IRQ enabled    : no
periodic IRQ frequency  : 1024
max user IRQ frequency  : 64
24hr            : yes
periodic_IRQ    : no
update_IRQ      : no
HPET_emulated   : yes
BCD             : yes
DST_enable      : no
periodic_freq   : 1024
batt_status     : okay
If I read the rtc after resume from suspend, I see the time I had entered from the command line before the suspend: 

rtc_time        : 07:53:29
rtc_date        : 2012-01-17
alrm_time       : 07:52:21
alrm_date       : 2012-01-17
alarm_IRQ       : yes
alrm_pending    : no
update IRQ enabled      : no
periodic IRQ enabled    : no
periodic IRQ frequency  : 1024
max user IRQ frequency  : 64
24hr            : yes
periodic_IRQ    : no
update_IRQ      : no
HPET_emulated   : yes
BCD             : yes
DST_enable      : no
periodic_freq   : 1024
batt_status     : okay
Could it be that the BIOS overwrites my command line entry at shutdown time, but not at suspend time? I have the impression that the BIOS has 2 places with wake-up time: A for the configuration itself (what has been entered in the BIOS by the user, me, and is visible in the BIOS GUI) and B to actually get the PC to wake-up, and it copies A to B at shutdown time... 

What do you think? Am I f* up?



Thanks,
Jonathan


I thank you, Eric

Attachment: Xterm.log.emil.2012.01.17.08.13.05.DISKSUSPEND.gz
Description: GNU Zip compressed data

Attachment: Xterm.log.emil.2012.01.17.08.24.24.HALT.gz
Description: GNU Zip compressed data

Attachment: acpi_test.sh.gz
Description: GNU Zip compressed data

Reply to: