This was my earlier report that I tought was sparc64 specific:
> Dmesg finds both OF RTC and PC RTC but later complains
> "No RTC device found, ALARM timers will not wake from suspend"
But today I noticed this while testing 3.0-rc3 on a PC:
[ 0.313944] No RTC device found, ALARM timers will not wake from suspend
[ 0.314275] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Later it detects PC RTC:
[ 3.610210] rtc_cmos 00:03: RTC can wake from S4
[ 3.611554] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[ 3.611669] rtc0: alarms up to one year, y3k, 114 bytes nvram
Bisecting it on sparc64 got me nowhere. Have not tried bisecting it on
PC yet.
--
Meelis Roos ([email protected])
On Tue, 2011-06-14 at 12:06 +0300, Meelis Roos wrote:
> This was my earlier report that I tought was sparc64 specific:
>
> > Dmesg finds both OF RTC and PC RTC but later complains
> > "No RTC device found, ALARM timers will not wake from suspend"
>
> But today I noticed this while testing 3.0-rc3 on a PC:
>
> [ 0.313944] No RTC device found, ALARM timers will not wake from suspend
> [ 0.314275] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
>
> Later it detects PC RTC:
>
> [ 3.610210] rtc_cmos 00:03: RTC can wake from S4
> [ 3.611554] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
> [ 3.611669] rtc0: alarms up to one year, y3k, 114 bytes nvram
>
> Bisecting it on sparc64 got me nowhere. Have not tried bisecting it on
> PC yet.
Hmm. I'm guessing this is due to the RTC cmos module loading later then
expected. Don't bother bisecting, I'll see what I can do about it.
Thanks for the testing and feedback!
-john
On wtorek, 14 czerwca 2011 o 11:06:49 Meelis Roos wrote:
> This was my earlier report that I tought was sparc64 specific:
> > Dmesg finds both OF RTC and PC RTC but later complains
> > "No RTC device found, ALARM timers will not wake from suspend"
>
> But today I noticed this while testing 3.0-rc3 on a PC:
>
> [ 0.313944] No RTC device found, ALARM timers will not wake from suspend
> [ 0.314275] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
>
> Later it detects PC RTC:
>
> [ 3.610210] rtc_cmos 00:03: RTC can wake from S4
> [ 3.611554] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
> [ 3.611669] rtc0: alarms up to one year, y3k, 114 bytes nvram
>
> Bisecting it on sparc64 got me nowhere. Have not tried bisecting it on
> PC yet.
I created a Bugzilla entry at
https://bugzilla.kernel.org/show_bug.cgi?id=38092
for your bug report, please add your address to the CC list in there, thanks!
--
Maciej Rutecki
http://www.maciek.unixy.pl