From: Feng Tang <feng.tang@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Chen, Rong A" <rong.a.chen@intel.com>,
"tipbuild@zytor.com" <tipbuild@zytor.com>,
Ingo Molnar <mingo@kernel.org>, "lkp@01.org" <lkp@01.org>,
LKML <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Subject: Re: [LKP] [x86/hotplug] e1056a25da: WARNING:at_arch/x86/kernel/apic/apic.c:#setup_local_APIC
Date: Mon, 1 Jul 2019 16:36:54 +0800 [thread overview]
Message-ID: <20190701083654.GB12486@shbuild999.sh.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1907010829590.1802@nanos.tec.linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]
Hi Thomas,
On Mon, Jul 01, 2019 at 09:13:54AM +0200, Thomas Gleixner wrote:
> Feng,
>
> On Sun, 30 Jun 2019, Thomas Gleixner wrote:
> > On Sun, 30 Jun 2019, Feng Tang wrote:
> > > On Sun, Jun 30, 2019 at 01:35:39PM +0200, Thomas Gleixner wrote:
> > > > On Sat, 29 Jun 2019, Thomas Gleixner wrote:
> > > > > On Fri, 28 Jun 2019, Thomas Gleixner wrote:
> > > > > > On Fri, 28 Jun 2019, Feng Tang wrote:
> > > > > > That function just 'works' by chance not by design. I'll stare into it and
> > > > > > fix it up for real.
> > > > > >
> > > > > > Thank you very much for that information. Your debug was spot on!
> > > > >
> > > > > I rewrote that function so it actually handles that case correctly along
> > > > > with some other things which were broken and force pushed the WIP.x86/ipi
> > > > > branch.
> > > > >
> > > > > Can you please run exactly that test again against that new version and
> > > > > verify that this is fixed now?
> > > >
> > > > Just found another issue with that thing. Don't waste your time on it. I'll
> > > > come back to you when I'm done.
> > >
> > > Ok. I noticed that the ipi branch has been merged to tip/master.
> >
> > Yes, but it will be zapped there as well.
>
> In case you still have your debug version (that old tree which triggered
> the warn) around, could you please run that again and add
>
> 'lapic=notscdeadline'
>
> to the kernel command line please?
After adding the boot paramter, the result is the same. The dmesg is attached.
Thanks,
Feng
[-- Attachment #2: dmesg.xz --]
[-- Type: application/x-xz, Size: 15492 bytes --]
next prev parent reply other threads:[~2019-07-01 9:13 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
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 [this message]
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=20190701083654.GB12486@shbuild999.sh.intel.com \
--to=feng.tang@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mingo@kernel.org \
--cc=rong.a.chen@intel.com \
--cc=tglx@linutronix.de \
--cc=tipbuild@zytor.com \
--cc=x86@kernel.org \
/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®