[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1707062258320.3239@nanos>
Date: Thu, 6 Jul 2017 23:03:06 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: kernel test robot <xiaolong.ye@...el.com>
cc: Dou Liyang <douly.fnst@...fujitsu.com>, x86@...nel.org,
linux-kernel@...r.kernel.org, xen-devel@...ts.xenproject.org,
mingo@...nel.org, hpa@...or.com, ebiederm@...ssion.com,
bhe@...hat.com, boris.ostrovsky@...cle.com, peterz@...radead.org,
izumi.taku@...fujitsu.com, lkp@...org
Subject: Re: [x86/time] 03fa63cc96:
ACPI_Error:Table[DMAR]is_not_invalidated_during_early_boot_stage(#/tbxface
-#)
On Thu, 6 Jul 2017, kernel test robot wrote:
> commit: 03fa63cc96ab35592e0a7d522b8edbc1e6b02d22 ("x86/time: Initialize interrupt mode behind timer init")
> +----------------+------------+------------+
> | | 43436935b7 | 03fa63cc96 |
> +----------------+------------+------------+
> | boot_successes | 0 | 4 |
> +----------------+------------+------------+
So 03fa63cc96 makes the box boot again. I'm confused as usual by the
output of this tool.
> kern :info : [ 0.005000] tsc: Fast TSC calibration using PIT
> kern :info : [ 0.006000] tsc: Detected 2195.020 MHz processor
> kern :info : [ 0.007000] Calibrating delay loop (skipped), value calculated using timer frequency.. 4390.04 BogoMIPS (lpj=2195020)
> kern :info : [ 0.008001] pid_max: default: 90112 minimum: 704
> kern :info : [ 0.009037] ACPI: Core revision 20170303
> kern :err : [ 0.010002] ACPI Error: Table [DMAR] is not invalidated during early boot stage (20170303/tbxface-193)
Sure we have a error message here, but compared to what? Compared to
something which does not boot at all?
Thanks,
tglx
Powered by blists - more mailing lists