linux-kernel - Re: [rtc-linux] Re: 2.6.21-rc2 : Oops in rtc

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]

Message-Id: <200703061423.42118.david-b@pacbell.net>
Date:	Tue, 6 Mar 2007 14:23:40 -0800
From:	David Brownell <david-b@...bell.net>
To:	Alessandro Zummo <alessandro.zummo@...ertech.it>
Cc:	rtc-linux@...glegroups.com, rol@...917.net,
	"'Adrian Bunk'" <bunk@...sta.de>, linux-kernel@...r.kernel.org,
	a.zummo@...ertech.it
Subject: Re: [rtc-linux] Re: 2.6.21-rc2 : Oops in rtc_cmos...

On Tuesday 06 March 2007 12:50 pm, Alessandro Zummo wrote:
> On Tue, 6 Mar 2007 11:32:28 -0800
> David Brownell <david-b@...bell.net> wrote:
> 
> > > on then... My dmesg says, related to rtc :
> > > 
> > > ...
> > > rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
> > 
> > I think the RTC core shouldn't emit this message; I'll send
> > a patch.  It's just confusing on error paths; and on success
> > paths it's less informative than a message from the driver
> > itself could be.
> 
>  I would like a way to have a common "welcome" message among
>  all the drivers. Please take this into account if you want
>  to send a patch ;)

Well, I already sent such a patch.  :)

I don't much object to such a message, although it's not
necessary ... and "not necessary" is all but synonymous
with being syslog spam.


> > > What does this all mean ? I thought an RTC Cmos was always there on a
> > > standard PC motherboard... (that's why I had activated the option in the
> > > first time).
> > 
> > You enabled CONFIG_RTC (under char drivers, "Enhanced Real Time Clock Support")
> > so that driver has claimed the CMOS RTC instead of "rtc-cmos.c".  Disable it.
> > Then you'll be able to use this driver with no little surprises.
> 
>  maybe we should consider this in the Kconfig.

Kconfig for both drivers, ideally:  select one, the other becomes unavailable.
Someone could generate such a patch...

- Dave
-
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/