[GUTSY] RTC alarm does not retain setting from /proc/acpi/alarm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
linux-source-2.6.22 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: linux-source-2.6.22
Ubuntu version: Kubuntu Gutsy (development) ... last upgraded 9/16/2007
Kernel version: 2.6.22-11-386
Motherboard: ASUS P4P800E-Deluxe
BIOS RTC Alarm Setting: Disabled
First broken: This worked fine with Feisty and kernel 2.6.20-13-386. It broke upon dist-upgrading to Gutsy.
Problem:
I have a file on my system called /home/mythtv/
$ cat /home/mythtv/
2007-09-15 09:53:59
The command below is issued by a script, and it copies the wakeup time to the BIOS.
sudo sh -c 'cat /home/mythtv/
Double-checking this reveals that the time is set correctly BEFORE shutdown:
$ cat /proc/acpi/alarm
2007-09-15 09:26:59
After shutting down the computer, it does not wake at the schedule time. When it is turned back on, the day is set to '00' in /proc/acpi/alarm, as shown below:
$ cat /proc/acpi/alarm
2007-09-00 09:26:59
This is presumably the cause of the alarm failure.
Troubleshooting attempts:
-- None of the suggestions at http://
-- There is an interesting comment on that page under the heading " Kernel 2.6.22+ and /sys/class/
-- A similar bug is discussed here, but my bug occurs after a full power off: http://
A solution is proposed on the kernel.org bugzilla by 'rafael', but I do not have the skills needed to test it, and it sounds hibernation-
>I think the suspend/hibernation code ordering changes after 2.6.20 are to blame
>here.
>
>Reportedly, the problem can be fixed by applying the patch from
>http://
>are not present in 2.6.22.
>
>It would be nice if that could be tested on 2.6.23-rc5 with the patchset from
>http://
>and the patch from http://
>
>Greetings,
>Rafael
-- MahoneyR has the same symptoms as described in this thread: http://
I'd be happy to provide more files and logs if they will help. Just PM "Fisslefink" on the ubuntuforums.
description: | updated |
Hi,
Just curious if this was still an issue in the official 7.10 Gutsy Gibbon release (kernel 2.6.22-14)? If so, the Hardy Heron kernel was recently uploaded for testing. We'd really appreciate it if you could try testing with this newer kernel and verify if this issue still exists. Unfortunately, the Hardy Heron Alpha1 LiveCD was released with the older 2.6.22 kernel. You'll have to manually install the newer Hardy Heron kernel in order to test. This should not be the case for Alpha2 which is set to come out around Dec 20. However, here are the instructions to install if you choose to do so, otherwise just wait for Alpha2 to come out:
1) edit the file /etc/apt/ sources. list and add the following line:
deb http:// archive. ubuntu. com/ubuntu hardy main restricted
2) sudo apt-get update 2.6.24- 1-generic
3) sudo apt-get install linux-image-
4) reboot and select the new kernel from the grub menu
After you've tested, please feel free to revert back - ie boot into the old kernel, sudo apt-get remove linux-image- 2.6.24- 1-generic, and remove the line from /etc/apt/ sources. list . Please update this report with your results. Thanks in advance!