Re: [RFC][PATCH] alarmtimers: Handle late rtc module loading

[john stultz <johnstul@us.ibm.com>]

On Fri, 2011-06-17 at 11:33 -0700, John Stultz wrote:
> On Fri, 2011-06-17 at 12:43 +0300, Meelis Roos wrote:
> > > Meelis: Could you give this patch a shot to make sure it resolves
> > > the issues you've seen on x86 and sparc?
> > 
> > Worked on sparc64 (Netra X1) on all 3 boots, on top of 
> > 3.0.0-rc3-00202-geb96c92.
> > 
> > One the PC, I get the following about RTC in dmesg:
> > 
> > [    0.319145] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> > [    3.614132] rtc_cmos 00:03: RTC can wake from S4
> > [    3.614480] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
> > [    3.614582] rtc0: alarms up to one year, y3k, 114 bytes nvram
> 
> I'll double check, but I suspect that "unable to open rtc device"
> message isn't new. The issue is that the rtc_cmos driver is built as a
> module, and the hctosys functionality is running before the module is
> loaded.

Yep. You're likely to see the same message with 2.6.37 or earlier if the
rtc drvier is a module and you have the hwtosys option enabled. Building
the driver statically will resolve this issue.

Clearly this is not ideal, but at least its not a regression.

thanks
-john