[Gigabyte GA-MA78GPM-DS2H] ACPI wakeup fails if HPET enabled in BIOS

[Diego]

if I type this (as root):
echo `date '+%s' -d '+ 5 minutes'` > /sys/class/rtc/rtc0/wakealarm

or:
rtcwake -d rtc0 -u -m no -t `date '+%s' -d '+ 5 minutes'`

and then I shutdown the computer, it used to wake up after 5 minutes until I upgraded from linux-image-3.8.0-23-generic to a newer package. I've always had HPET enabled in BIOS.

Maybe it's related to this patch found in the changelog
zdiff /usr/share/doc/linux-image-3.8.0-23-generic/changelog.Debian.gz /usr/share/doc/linux-image-3.8.0-24-generic/changelog.Debian.gz | grep hpet
> * drivers/rtc/rtc-cmos.c: don't disable hpet emulation on suspend

WORKAROUND: If I disable HPET in BIOS, my computer successfully wakes up in kernels > 3.8.0-23

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-26-generic 3.8.0-26.38
ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
Uname: Linux 3.8.0-26-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: usuario 2971 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Thu Jul 4 17:32:03 2013
HibernationDevice:
 #RESUME=UUID=e38f6a8b-948e-434c-a8e1-eb1e207dad4f
 RESUME=UUID=3ddd6504-083d-4af2-bcaa-5af1dbbf1f77
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-MA78GPM-DS2H
MarkForUpload: True
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-26-generic root=UUID=22b58a09-ddc9-4068-8d9c-d225ad781780 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-26-generic N/A
 linux-backports-modules-3.8.0-26-generic N/A
 linux-firmware 1.106
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2013-05-02 (63 days ago)
WpaSupplicantLog:

dmi.bios.date: 12/25/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F6h
dmi.board.name: GA-MA78GPM-DS2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6h:bd12/25/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA78GPM-DS2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA78GPM-DS2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA78GPM-DS2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-saucy/

[Diego (gran-diego)]

Same behavior with kernel 3.10. If HPET is enabled, it wakes up fine. If disabled, then nothing happens

[Diego (gran-diego)]

Sorry, my mistake. If HPET is DISABLED, it wakes up fine. If ENABLED, nothing happens.

[glennric (glennric)]

I have this problem now that I have upgraded to Ubuntu 13.10 with kernel version 3.11.0-13-generic.

If I add "hpet=disabled" to the GRUB_CMDLINE_LINUX_DEFAULT variable in /etc/default/grub (and run sudo update-grub), then the computer wakes on alarm. Otherwise it does not.

I have had this problem on and off through various distributions of Ubuntu. I did not have this problem with Ubuntu 13.04. I think I did with Ubuntu 12.10 though.

[penalvch (penalvch)]

Diego, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please just make a comment to this?

Also, could you please test the latest upstream kernel available (v3.13-rc3 as rc4 doesn't have all the necessary files) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Diego (gran-diego)]

Hi, Christopher

I've just tested kernel 3.13-rc3, bug still present.

 I repeated the same test in other computers I own (intel based), with mixed results: one with a Gigabyte GA-G31MF-S2 motherboard (intel G31 chipset, socket 775) is affected by this bug. Another one with an ASUS socket 775 motherboard goes fine.

Thanks in advance

[penalvch (penalvch)]

Diego, thank you for performing the requested test. Regarding your other hardware tests, I would let this report focus on the hardware you initially reported against. If you wanted fixes for the others computers you had, please feel free to report a separate report, one for each computer, via a terminal:
ubuntu-bug linux

Despite this, the next step would be to fully commit bisect from 3.8.0-23-generic to 3.8.0-26-generic in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Diego (gran-diego)]

Bisect done.

Bisect log follows.

# bad: [e2689a0f2068cfd300fd7f4d444d72571cfe5d48] UBUNTU: Ubuntu-3.8.0-26.38
# good: [680faeb696565a564b9b7a678fa042de4f5fbee9] UBUNTU: Ubuntu-3.8.0-23.34
git bisect start 'Ubuntu-3.8.0-26.38' 'Ubuntu-3.8.0-23.34'
# bad: [67dca26a087c23aabf8f4f92de630d3285551c87] benet: Wait f/w POST until timeout
git bisect bad 67dca26a087c23aabf8f4f92de630d3285551c87
# bad: [65b3745f82d86d6ba3efc19054e3cc2bde452b45] ixgbe: fix EICR write in ixgbe_msix_other
git bisect bad 65b3745f82d86d6ba3efc19054e3cc2bde452b45
# good: [5f17a84fb89bccf83ad1d07ae3caa12b9322cecc] tracing: Reset ftrace_graph_filter_enabled if count is zero
git bisect good 5f17a84fb89bccf83ad1d07ae3caa12b9322cecc
# good: [e5dc414e4d888330436fcd4bea3f6348276dbba9] swap: redirty page if page write fails on swap file
git bisect good e5dc414e4d888330436fcd4bea3f6348276dbba9
# bad: [ef40ce18151e6a78cc7c084558ea8044566c54b7] inotify: invalid mask should return a error number but not set it
git bisect bad ef40ce18151e6a78cc7c084558ea8044566c54b7
# bad: [07053b6237d7a1983d80fb0d3839e9889244dc33] ACPI / thermal: do not always return THERMAL_TREND_RAISING for active trip points
git bisect bad 07053b6237d7a1983d80fb0d3839e9889244dc33
# bad: [6d22382d7148a132fb7b4c461cb2940df4f0c77e] drivers/rtc/rtc-cmos.c: don't disable hpet emulation on suspend
git bisect bad 6d22382d7148a132fb7b4c461cb2940df4f0c77e
# good: [2ef4473b0027df0e7558557feb83da2c3e1826d0] mm: swap: mark swap pages writeback before queueing for direct IO
git bisect good 2ef4473b0027df0e7558557feb83da2c3e1826d0
# first bad commit: [6d22382d7148a132fb7b4c461cb2940df4f0c77e] drivers/rtc/rtc-cmos.c: don't disable hpet emulation on suspend

Last git bisect throwed this:

6d22382d7148a132fb7b4c461cb2940df4f0c77e is the first bad commit
commit 6d22382d7148a132fb7b4c461cb2940df4f0c77e
Author: Derek Basehore <email address hidden>
Date: Mon Apr 29 16:20:23 2013 -0700

    drivers/rtc/rtc-cmos.c: don't disable hpet emulation on suspend

    BugLink: http://bugs.launchpad.net/bugs/1178361

    commit e005715efaf674660ae59af83b13822567e3a758 upstream.

    There's a bug where rtc alarms are ignored after the rtc cmos suspends
    but before the system finishes suspend. Since hpet emulation is
    disabled and it still handles the interrupts, a wake event is never
    registered which is done from the rtc layer.

    This patch reverts commit d1b2efa83fbf ("rtc: disable hpet emulation on
    suspend") which disabled hpet emulation. To fix the problem mentioned
    in that commit, hpet_rtc_timer_init() is called directly on resume.

    Signed-off-by: Derek Basehore <email address hidden>
    Cc: Maxim Levitsky <email address hidden>
    Cc: "H. Peter Anvin" <email address hidden>
    Cc: Thomas Gleixner <email address hidden>
    Cc: Ingo Molnar <email address hidden>
    Cc: "Rafael J. Wysocki" <email address hidden>
    Signed-off-by: Andrew Morton <email address hidden>
    Signed-off-by: Linus Torvalds <email address hidden>
    Signed-off-by: Greg Kroah-Hartman <email address hidden>
    Signed-off-by: Steve Conklin <email address hidden>

:040000 040000 3e84b9874d08e64109a8e7155b0b0734f...

[penalvch (penalvch)]

Diego, thank you for bisecting this issue. Could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc5-trusty/ and advise to the results?

[Diego (gran-diego)]

Hi, Christopher.

I've just tested v3.13-rc5 as requested. Unfortunately, the bug is still present.

Thanks.

[penalvch (penalvch)]

Diego, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream (would check in with the linux-kernel mailing list CC Clemens Ladisch <email address hidden> and "Venkatesh Pallipadi (Venki)" <email address hidden>)?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked.

Thank you for your understanding.

[penalvch (penalvch)]

Diego, could you please provide a direct URL to the mailing list post, where you followed the kernel.org format noted in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1197871/comments/13 ?

[Diego (gran-diego)]

Sent to rtc-linux mailling list

https://groups.google.com/forum/#!topic/rtc-linux/qJF_XjYG8mQ

Also sent to kernel mailing list, still not present in lkml.org. Will update as soon as it pops up.

[Diego (gran-diego)]

https://lkml.org/lkml/2014/1/2/352

[Diego (gran-diego)]

https://bugzilla.kernel.org/show_bug.cgi?id=68331