Bug 556188 - rtc: wakealarm behaviour change in recent kernels
Summary: rtc: wakealarm behaviour change in recent kernels
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-17 02:08 UTC by Kieran Clancy
Modified: 2012-06-05 17:48 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-04 15:02:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Kieran Clancy 2010-01-17 02:08:56 UTC
Description of problem:
I use the rtc wakealarm every day to make my PC start at the right time, but recently this stopped working properly after either a kernel update (or perhaps it was when I upgraded to F12).

This is the process I use to set the wakealarm. This is how I've done it for the past couple of years, so I expect it to work:
date -d '8am tomorrow' +%s > /sys/class/rtc/rtc0/wakealarm

Recently though my timezone offset has been interfering somehow.
# cat /proc/driver/rtc 
rtc_time	: 12:19:04
rtc_date	: 2010-01-17
alrm_time	: 21:30:00
alrm_date	: 2010-01-17
...

Notice how it has set the alarm 10 and a half hours too early (my timezone offset is +1030).

Now, I could adjust for this in my script, but it seems like a bug that the kernel has suddenly changed its behaviour.

To reproduce this you will need to have a non-zero timezone offset.

Version-Release number of selected component (if applicable):
2.6.31.9-174.fc12.i686.PAE

Comment 1 Bug Zapper 2010-11-04 00:46:27 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Kieran Clancy 2010-11-04 01:59:25 UTC
This bug is still present in 2.6.33.6-147.2.4.fc13.x86_64.

Comment 3 Bug Zapper 2010-12-04 00:17:32 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Kieran Clancy 2010-12-04 01:25:40 UTC
Why was this closed? I clearly said it was still a bug in F13. Silly bug zapper.

Comment 5 Bug Zapper 2011-06-02 16:51:07 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Kieran Clancy 2011-06-03 16:11:56 UTC
Still present in F15. Any news? Can someone confirm that this behaviour is correct or not?

Comment 7 Kieran Clancy 2012-06-05 17:48:31 UTC
Can I get an explanation of the WONTFIX?


Note You need to log in before you can comment on or make changes to this bug.