linux-kernel - Re: 3.0-rc3: No RTC device found

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 14 Jun 2011 10:54:39 -0700
From:	John Stultz <john.stultz@...aro.org>
To:	Meelis Roos <mroos@...ee>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: 3.0-rc3: No RTC device found

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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/