linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rong Chen <rong.a.chen@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: tipbuild@zytor.com, "H. Peter Anvin" <hpa@zytor.com>,
	lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [LKP] [x86/hotplug] e1056a25da: WARNING:at_arch/x86/kernel/apic/apic.c:#setup_local_APIC
Date: Tue, 25 Jun 2019 16:40:50 +0800	[thread overview]
Message-ID: <f5c36f89-61bf-a82e-3d3b-79720b2da2ef@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1906250821220.32342@nanos.tec.linutronix.de>

[-- Attachment #1: Type: text/plain, Size: 784 bytes --]

On 6/25/19 2:24 PM, Thomas Gleixner wrote:
> Rong,
>
> On Tue, 25 Jun 2019, Rong Chen wrote:
>> On 6/22/19 3:08 AM, Thomas Gleixner wrote:
>>>> 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
> Ok. I'll try to find something similar. Can please you rerun that test on
> that particular configuration with the updated branch?
>
>     git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/ipi
>
Hi tglx,

I have tested commit e0b179bc1a ("x86/apic/x2apic: Add conditional IPI 
shorthands support"), the problem is still exist.

Best Regards,
Rong Chen


[-- Attachment #2: dmesg.xz --]
[-- Type: application/x-xz, Size: 15208 bytes --]

  reply	other threads:[~2019-06-25  8:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-20  2:18 [x86/hotplug] e1056a25da: WARNING:at_arch/x86/kernel/apic/apic.c:#setup_local_APIC kernel test robot
2019-06-21 19:08 ` Thomas Gleixner
2019-06-25  1:46   ` Rong Chen
2019-06-25  6:24     ` Thomas Gleixner
2019-06-25  8:40       ` Rong Chen [this message]
2019-06-25 11:32         ` [LKP] " 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=f5c36f89-61bf-a82e-3d3b-79720b2da2ef@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;
as well as URLs for NNTP newsgroup(s).