* ACPI Error: Could not enable RealTimeClock event (20140214/evxfevnt-212)
@ 2014-05-26 16:04 Borislav Petkov
2014-05-27 18:56 ` John Stultz
0 siblings, 1 reply; 3+ messages in thread
From: Borislav Petkov @ 2014-05-26 16:04 UTC (permalink / raw)
To: lkml; +Cc: Rafael J. Wysocki, John Stultz, Thomas Gleixner
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)
rtc_cmos gets initialized fine with both though:
rc6+tip:
========
rtc_cmos 00:06: RTC can wake from S4
rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
rtc_cmos 00:06: alarms up to one year, y3k, 242 bytes nvram, hpet irqs
rtc_cmos 00:06: setting system clock to 2014-05-26 17:21:31 UTC (1401124891)
rc7+tip:
========
rtc_cmos 00:06: RTC can wake from S4
rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
rtc_cmos 00:06: alarms up to one year, y3k, 242 bytes nvram, hpet irqs
rtc_cmos 00:06: setting system clock to 2014-05-26 17:50:18 UTC (1401126618)
Any ideas?
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: ACPI Error: Could not enable RealTimeClock event (20140214/evxfevnt-212)
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
0 siblings, 1 reply; 3+ messages in thread
From: John Stultz @ 2014-05-27 18:56 UTC (permalink / raw)
To: Borislav Petkov; +Cc: lkml, Rafael J. Wysocki, Thomas Gleixner, Len Brown
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?
thanks
-john
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: ACPI Error: Could not enable RealTimeClock event (20140214/evxfevnt-212)
2014-05-27 18:56 ` John Stultz
@ 2014-05-28 11:23 ` Borislav Petkov
0 siblings, 0 replies; 3+ messages in thread
From: Borislav Petkov @ 2014-05-28 11:23 UTC (permalink / raw)
To: John Stultz; +Cc: lkml, Rafael J. Wysocki, Thomas Gleixner, Len Brown
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.
--
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-05-28 11:23 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox