[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140528112344.GC17196@pd.tnic>
Date: Wed, 28 May 2014 13:23:44 +0200
From: Borislav Petkov <bp@...en8.de>
To: John Stultz <john.stultz@...aro.org>
Cc: lkml <linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Thomas Gleixner <tglx@...utronix.de>,
Len Brown <lenb@...nel.org>
Subject: Re: ACPI Error: Could not enable RealTimeClock event
(20140214/evxfevnt-212)
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@...en8.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.
--
--
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