From: Dou Liyang <douly.fnst@cn.fujitsu.com>
To: Ye Xiaolong <xiaolong.ye@intel.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: <x86@kernel.org>, <linux-kernel@vger.kernel.org>,
<xen-devel@lists.xenproject.org>, <mingo@kernel.org>,
<hpa@zytor.com>, <ebiederm@xmission.com>, <bhe@redhat.com>,
<boris.ostrovsky@oracle.com>, <peterz@infradead.org>,
<izumi.taku@jp.fujitsu.com>, <lkp@01.org>
Subject: Re: [x86/time] 03fa63cc96: ACPI_Error:Table[DMAR]is_not_invalidated_during_early_boot_stage(#/tbxface -#)
Date: Fri, 7 Jul 2017 10:39:10 +0800 [thread overview]
Message-ID: <1802eca6-9956-8287-40ea-55654bc0cba8@cn.fujitsu.com> (raw)
In-Reply-To: <20170707015445.GG5222@yexl-desktop>
Hi xiaolong,
Really thanks for your testing.
At 07/07/2017 09:54 AM, Ye Xiaolong wrote:
> On 07/06, Thomas Gleixner wrote:
>> 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?
>
> Sorry for the confusion, here commit 43436935b7 boot failed due to OOM which
> happened at the late stage of kernel boot while the ACPI error showed at the
> early boot stage for commit 03fa63cc96 and it didn't appear in 43436935b7's
> dmesg.
>
let's make the problem clearly firstly:
1) Commit 43436935b7 ("x86/xen: Bypass intr mode setup in enlighten_pv
system") made kernel boot failed, which caused by OOM.
2) Commit 03fa63cc96 ("x86/time: Initialize interrupt mode behind timer
init") can make the kernel boot success again, but with an ACPI error
happened.
And both *1* and *2* used the same configuration showed in the
attachment.
Does anything I missed?
Thanks,
dou.
> Thanks,
> Xiaolong
>
>>
>> Thanks,
>>
>> tglx
>>
>
>
>
next prev parent reply other threads:[~2017-07-07 2:39 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 4:07 [PATCH v5 00/12] Unify the interrupt delivery mode and do its setup in advance Dou Liyang
2017-06-30 4:07 ` [PATCH v5 01/12] x86/apic: Construct a selector for the interrupt delivery mode Dou Liyang
2017-07-02 17:37 ` Thomas Gleixner
2017-07-03 1:44 ` Dou Liyang
2017-06-30 4:07 ` [PATCH v5 02/12] x86/apic: Prepare for unifying the interrupt delivery modes setup Dou Liyang
2017-07-02 17:47 ` Thomas Gleixner
2017-07-03 1:58 ` Dou Liyang
2017-07-03 6:41 ` Thomas Gleixner
2017-07-03 6:47 ` Dou Liyang
2017-06-30 4:07 ` [PATCH v5 03/12] x86/apic: Split local APIC timer setup from the APIC setup Dou Liyang
2017-06-30 4:07 ` [PATCH v5 04/12] x86/apic: Move logical APIC ID away from apic_bsp_setup() Dou Liyang
2017-07-02 17:54 ` Thomas Gleixner
2017-07-03 2:02 ` Dou Liyang
2017-06-30 4:07 ` [PATCH v5 05/12] x86/apic: Unify interrupt mode setup for SMP-capable system Dou Liyang
2017-07-02 18:07 ` Thomas Gleixner
2017-07-03 2:34 ` Dou Liyang
2017-06-30 4:07 ` [PATCH v5 06/12] x86/apic: Mark the apic_intr_mode extern for sanity check cleanup Dou Liyang
2017-06-30 4:07 ` [PATCH v5 07/12] x86/apic: Unify interrupt mode setup for UP system Dou Liyang
2017-07-02 18:19 ` Thomas Gleixner
2017-07-03 2:34 ` Dou Liyang
2017-06-30 4:07 ` [PATCH v5 08/12] x86/ioapic: Refactor the delay logic in timer_irq_works() Dou Liyang
2017-07-02 19:15 ` Thomas Gleixner
2017-07-03 3:23 ` Dou Liyang
2017-06-30 4:07 ` [PATCH v5 09/12] x86/init: add intr_mode_init to x86_init_ops Dou Liyang
2017-07-02 19:16 ` Thomas Gleixner
2017-07-03 3:28 ` Dou Liyang
2017-06-30 4:07 ` [PATCH v5 10/12] x86/xen: Bypass intr mode setup in enlighten_pv system Dou Liyang
2017-07-02 19:18 ` Thomas Gleixner
2017-07-03 3:53 ` Dou Liyang
2017-07-03 6:56 ` Thomas Gleixner
2017-07-03 7:17 ` Dou Liyang
2017-06-30 4:07 ` [PATCH v5 11/12] x86/time: Initialize interrupt mode behind timer init Dou Liyang
2017-07-06 14:54 ` [x86/time] 03fa63cc96: ACPI_Error:Table[DMAR]is_not_invalidated_during_early_boot_stage(#/tbxface-#) kernel test robot
2017-07-06 21:03 ` [x86/time] 03fa63cc96: ACPI_Error:Table[DMAR]is_not_invalidated_during_early_boot_stage(#/tbxface -#) Thomas Gleixner
2017-07-07 1:54 ` Ye Xiaolong
2017-07-07 2:39 ` Dou Liyang [this message]
2017-07-07 3:04 ` Ye Xiaolong
2017-07-07 4:46 ` Dou Liyang
2017-06-30 4:07 ` [PATCH v5 12/12] x86/apic: Remove the init_bsp_APIC() Dou Liyang
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=1802eca6-9956-8287-40ea-55654bc0cba8@cn.fujitsu.com \
--to=douly.fnst@cn.fujitsu.com \
--cc=bhe@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xiaolong.ye@intel.com \
/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®