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-next>] [day] [month] [year] [list]
Date:	Tue, 14 Jun 2011 12:06:49 +0300 (EEST)
From:	Meelis Roos <mroos@...ee>
To:	John Stultz <john.stultz@...aro.org>,
	Thomas Gleixner <tglx@...utronix.de>
cc:	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: 3.0-rc3: No RTC device found

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 (mroos@...ux.ee)
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ