From: John Stultz <john.stultz@linaro.org>
To: Meelis Roos <mroos@ut.ee>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 3.0-rc3: No RTC device found
Date: Tue, 14 Jun 2011 10:54:39 -0700 [thread overview]
Message-ID: <1308074079.7261.1.camel@work-vm> (raw)
In-Reply-To: <alpine.SOC.1.00.1106141203350.11764@math.ut.ee>
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
next prev parent reply other threads:[~2011-06-14 18:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 12:02 RTC problem on Netra X1? Meelis Roos
2011-06-08 21:56 ` David Miller
2011-06-09 9:54 ` Meelis Roos
2011-06-11 16:51 ` Meelis Roos
2011-06-13 17:28 ` Meelis Roos
2011-06-13 20:52 ` John Stultz
2011-06-14 4:55 ` Meelis Roos
2011-06-14 9:06 ` 3.0-rc3: No RTC device found Meelis Roos
2011-06-14 17:54 ` John Stultz [this message]
2011-06-23 17:32 ` Maciej Rutecki
2011-06-14 16:14 ` RTC problem on Netra X1? John Stultz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1308074079.7261.1.camel@work-vm \
--to=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@ut.ee \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.