From: Rong Chen <rong.a.chen@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
tipbuild@zytor.com, lkp@01.org
Subject: Re: [x86/hotplug] e1056a25da: WARNING:at_arch/x86/kernel/apic/apic.c:#setup_local_APIC
Date: Tue, 25 Jun 2019 09:46:01 +0800 [thread overview]
Message-ID: <58ea508f-dc2e-8537-fe96-49cca0a7c799@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1906212108150.5503@nanos.tec.linutronix.de>
On 6/22/19 3:08 AM, Thomas Gleixner wrote:
> On Thu, 20 Jun 2019, kernel test robot wrote:
>
>> FYI, we noticed the following commit (built with gcc-7):
>>
>> commit: e1056a25daa6460c95e92d7d6853d05ad62458f7 ("x86/hotplug: Silence APIC and NMI when CPU is dead")
>> https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git WIP.x86/ipi
>>
>> in testcase: locktorture
>> with following parameters:
>>
>> runtime: 300s
>> test: cpuhotplug
>>
>> test-description: This torture test consists of creating a number of kernel threads which acquire the lock and hold it for specific amount of time, thus simulating different critical region behaviors.
>> test-url: https://www.kernel.org/doc/Documentation/locking/locktorture.txt
>>
>>
>> on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 2G
> I cannot reproduce that issue. What's the underlying hardware machine?
brand: Genuine Intel(R) CPU 000 @ 2.27GHz
model: Westmere-EX
memory: 256G
nr_node: 4
nr_cpu: 80
Best Regards,
Rong Chen
>
> Thanks,
>
> tglx
next prev parent reply other threads:[~2019-06-25 1:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 2:18 kernel test robot
2019-06-21 19:08 ` Thomas Gleixner
2019-06-25 1:46 ` Rong Chen [this message]
2019-06-25 6:24 ` Thomas Gleixner
2019-06-25 8:40 ` [LKP] " Rong Chen
2019-06-25 11:32 ` Thomas Gleixner
2019-06-26 1:19 ` Rong Chen
2019-06-27 14:26 ` Thomas Gleixner
2019-06-28 8:51 ` Rong Chen
2019-06-28 6:32 ` Feng Tang
2019-06-28 9:19 ` Thomas Gleixner
2019-06-29 7:15 ` Thomas Gleixner
2019-06-30 11:35 ` Thomas Gleixner
2019-06-30 13:03 ` Feng Tang
2019-06-30 18:21 ` Thomas Gleixner
2019-07-01 7:13 ` Thomas Gleixner
2019-07-01 8:36 ` Feng Tang
2019-07-01 9:26 ` Thomas Gleixner
2019-07-01 9:44 ` Rong Chen
2019-07-01 22:41 ` [BUG] kvm: APIC emulation problem - was Re: [LKP] [x86/hotplug] Thomas Gleixner
2019-07-02 5:29 ` Wanpeng Li
2019-07-02 6:40 ` Thomas Gleixner
2019-07-02 9:44 ` Wanpeng Li
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=58ea508f-dc2e-8537-fe96-49cca0a7c799@intel.com \
--to=rong.a.chen@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=tipbuild@zytor.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
Powered by JetHome