From: Peter Zijlstra <peterz@infradead.org>
To: Chen Yu <yu.chen.surf@gmail.com>
Cc: kernel test robot <rong.a.chen@intel.com>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, Zhang Rui <rui.zhang@intel.com>
Subject: Re: [smp] b2a02fc43a: suspend-stress.fail
Date: Thu, 11 Jun 2020 18:10:22 +0200 [thread overview]
Message-ID: <20200611161022.GL2531@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CADjb_WSLpKrkt-Oq_3krGBp8ZLjVZ4caUAd0d0s1_6s1tOHdHQ@mail.gmail.com>
On Thu, Jun 11, 2020 at 04:24:53PM +0800, Chen Yu wrote:
> Hi Peter,
> On Wed, Jun 10, 2020 at 5:52 PM Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > On Wed, Jun 10, 2020 at 04:35:02PM +0800, kernel test robot wrote:
> > > Greeting,
> > >
> > > FYI, we noticed the following commit (built with gcc-9):
> > >
> > > commit: b2a02fc43a1f40ef4eb2fb2b06357382608d4d84 ("smp: Optimize send_call_function_single_ipi()")
> > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> > >
> > > in testcase: suspend-stress
> > > with following parameters:
> > >
> > > mode: freeze
> > > iterations: 10
> > >
> > >
> > >
> > > on test machine: 2 threads Broxton with 4G memory
> > >
> > > caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
> > >
> > >
> > > If you fix the issue, kindly add following tag
> > > Reported-by: kernel test robot <rong.a.chen@intel.com>
> > >
> > >
> > > the result of this commit:
> > >
> > > test started
> >
> > No dmesg output? No splat?
> This issue was only found on one of the test machines from lkp team.
> I've borrowed that machine and will try to narrow down and give feedback later.
Thanks! One thing to maybe try is hotplug tests. Suspend does hotplugs,
and it might be easier to debug hotplug than it is to debug suspend.
prev parent reply other threads:[~2020-06-11 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 8:35 [smp] b2a02fc43a: suspend-stress.fail kernel test robot
2020-06-10 9:50 ` Peter Zijlstra
2020-06-11 8:24 ` Chen Yu
2020-06-11 16:10 ` Peter Zijlstra [this message]
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=20200611161022.GL2531@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=mingo@kernel.org \
--cc=rong.a.chen@intel.com \
--cc=rui.zhang@intel.com \
--cc=yu.chen.surf@gmail.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