From: Pavel Machek <pavel@ucw.cz>
To: David Brownell <david-b@pacbell.net>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: WARN_ON(): proc_dir_entry 'rtc' already registered
Date: Mon, 18 Feb 2008 11:54:41 +0100 [thread overview]
Message-ID: <20080218105441.GE7198@elf.ucw.cz> (raw)
In-Reply-To: <200802121029.08007.david-b@pacbell.net>
Hi!
> > I'm getting this during bootup:
> >
> > PM: Adding info for No Bus:event6
> > PM: Adding info for No Bus:uinput
> > PM: Adding info for No Bus:rtc0
> > proc_dir_entry 'rtc' already registered
> > Pid: 1, comm: swapper Not tainted 2.6.25-rc1 #125
> > ... deletia
> > =======================
> > rtc_cmos 00:07: rtc core: registered rtc_cmos as rtc0
> > rtc0: alarms up to one month, y3k
> > PM: Adding info for platform:coretemp.0
> > PM: Adding info for No Bus:hwmon1
> >
> > ... .config attached.
>
> Which shows:
>
> CONFIG_GEN_RTC=y
> CONFIG_GEN_RTC_X=y
>
> Disable that, then those warnings will vanish. (I'm told that
> having proc_register() return a fault code is off the table,
> much like impeachment.)
Ok.
> How to fix ... how about: instead of just warning folk
> off such legacy RTC drivers [1] we just wrap them with
> an "if RTC_LIB != n" so this mistake won't be possible.
Yes, disabling bad configs in Kconfig seems like way to go.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-02-18 10:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 13:26 Pavel Machek
2008-02-12 18:29 ` David Brownell
2008-02-18 10:54 ` Pavel Machek [this message]
2008-02-18 11:08 ` David Brownell
2008-02-19 10:12 ` Pavel Machek
2008-03-08 22:50 ` David Brownell
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=20080218105441.GE7198@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®