From: Borislav Petkov <bp@alien8.de>
To: John Stultz <john.stultz@linaro.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Thomas Gleixner <tglx@linutronix.de>, Len Brown <lenb@kernel.org>
Subject: Re: ACPI Error: Could not enable RealTimeClock event (20140214/evxfevnt-212)
Date: Wed, 28 May 2014 13:23:44 +0200 [thread overview]
Message-ID: <20140528112344.GC17196@pd.tnic> (raw)
In-Reply-To: <CALAqxLWSLq8vgkcs3-Cu-coMB9L=eL-gmBPfsZ+ZuxF0LuY5LA@mail.gmail.com>
On Tue, May 27, 2014 at 11:56:29AM -0700, John Stultz wrote:
> On Mon, May 26, 2014 at 9:04 AM, Borislav Petkov <bp@alien8.de> wrote:
> > Hi guys,
> >
> > so I get this with rc7+tip but not with rc6+tip:
> >
> > ACPI Error: Could not enable RealTimeClock event (20140214/evxfevnt-212)
> > ACPI Warning: Could not enable fixed event - RealTimeClock (4) (20140214/evxface-628)
>
> Does it happen on -rc7 w/o tip?
>
> Looking at the -rc6 to -rc7 commit list, I don't see anything that
> pops out at me. There's no changes to drivers/rtc nor drivers/acpi.
>
> The only change that might be relevant from arch/x86/ is:
> a4b4f11b2783ec678cccb4ce7e4ce9665aa04a24 (perf/x86/intel: Fix
> Silvermont's event constraints). Any other hardware details, etc?
Yeah, I just did a fresh merge of Linus' master + tip/master and the
error message is gone. It could've been a glitch so I'll watch out for
it if it reappears.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
prev parent reply other threads:[~2014-05-28 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 16:04 ACPI Error: Could not enable RealTimeClock event (20140214/evxfevnt-212) Borislav Petkov
2014-05-27 18:56 ` John Stultz
2014-05-28 11:23 ` Borislav Petkov [this message]
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=20140528112344.GC17196@pd.tnic \
--to=bp@alien8.de \
--cc=john.stultz@linaro.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
/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