Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755795Ab1FNJYh (ORCPT ); Tue, 14 Jun 2011 05:24:37 -0400 Received: from smtp2.it.da.ut.ee ([193.40.5.67]:58514 "EHLO smtp2.it.da.ut.ee" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755068Ab1FNJYg (ORCPT ); Tue, 14 Jun 2011 05:24:36 -0400 X-Greylist: delayed 1066 seconds by postgrey-1.27 at vger.kernel.org; Tue, 14 Jun 2011 05:24:36 EDT Date: Tue, 14 Jun 2011 12:06:49 +0300 (EEST) From: Meelis Roos To: John Stultz , Thomas Gleixner cc: Linux Kernel list Subject: 3.0-rc3: No RTC device found In-Reply-To: Message-ID: References: User-Agent: Alpine 1.00 (SOC 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 964 Lines: 26 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@linux.ee) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/