From: Oliver Sang <oliver.sang@intel.com>
To: Ming Lei <ming.lei@redhat.com>, "Zhang, Rui" <rui.zhang@intel.com>
Cc: linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Jens Axboe <axboe@kernel.dk>,
"Ewan D . Milne" <emilne@redhat.com>,
Omar Sandoval <osandov@fb.com>, Christoph Hellwig <hch@lst.de>,
Kashyap Desai <kashyap.desai@broadcom.com>,
Hannes Reinecke <hare@suse.de>,
Laurence Oberman <loberman@redhat.com>,
Bart Van Assche <bart.vanassche@wdc.com>,
lkp@lists.01.org
Subject: Re: [scsi] 74eb6c22dc: suspend_stress.fail
Date: Thu, 21 Nov 2019 14:50:00 +0800 [thread overview]
Message-ID: <20191121065000.GA9619@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20191116085443.GA24667@ming.t460p>
On Sat, Nov 16, 2019 at 04:54:43PM +0800, Ming Lei wrote:
> Hello Oliver,
>
> On Mon, Nov 04, 2019 at 04:50:21PM +0800, kernel test robot wrote:
> > FYI, we noticed the following commit (built with gcc-7):
> >
> > commit: 74eb6c22dc70e395b333c9ca579855cd88db8845 ("[RFC PATCH V3 2/2] scsi: core: don't limit per-LUN queue depth for SSD")
> > url: https://github.com/0day-ci/linux/commits/Ming-Lei/scsi-core-avoid-host-wide-host_busy-counter-for-scsi_mq/20191009-015827
> > base: https://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git for-next
> >
> > in testcase: suspend_stress
> > with following parameters:
> >
> > mode: freeze
> > iterations: 10
> >
> >
> >
> > on test machine: 4 threads Skylake with 8G 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 <oliver.sang@intel.com>
> >
> > test started
> >
> > (then just like hang)
> > (below is what looks like if test can pass
> > SUSPEND RESUME TEST STARTED
> > Suspend to freeze 1/10:
> > ...
> > Done
> > Sleep for 10 seconds
> > Suspend to freeze 2/10:
> > ...
> > Suspend to freeze 10/10:
> > ...
> > Sleep for 10 seconds
> > SUSPEND RESUME TEST SUCCESS)
>
> From the dmesg via 'zcat kmsg.xz', looks there isn't any failure found.
> 'Suspend to freeze' has run successfully 10 times, and finally the
> message of 'SUSPEND RESUME TEST SUCCESS' does show in the log.
>
> Could you double check if it is a valid report?
Hi Ming, sorry for confusion. this case didn't always fail in our tests, and unfortunately,
due to some code problem, the kmsg.xz attached in the original mail is from PASS test.
(In failed tests, we cannot generate the kmsg so far actually)
However, in our tests, the regression is clear, for parent commit, the test all passed,
for this commit, the tests are easy to fail.
69fdd747ae1fa088 74eb6c22dc70e395b333c9ca57
---------------- --------------------------
:18 50% 9:18 suspend_stress.fail
@Rui also helped double confirm the regression by another power test - analyze_suspend, which
also shows this clear regression. Rui maybe could supply more information. Thanks!
>
> Thanks,
> Ming
>
next prev parent reply other threads:[~2019-11-21 6:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 10:09 [PATCH V3 0/2] scsi: avoid atomic operations in IO path Ming Lei
2019-10-08 10:09 ` [PATCH V3 1/2] scsi: core: avoid host-wide host_busy counter for scsi_mq Ming Lei
2019-10-08 10:09 ` [RFC PATCH V3 2/2] scsi: core: don't limit per-LUN queue depth for SSD Ming Lei
2019-11-04 8:50 ` [scsi] 74eb6c22dc: suspend_stress.fail kernel test robot
2019-11-05 3:52 ` Bart Van Assche
2019-11-05 6:11 ` Ming Lei
2019-11-13 17:00 ` Bart Van Assche
2019-11-14 1:25 ` Ming Lei
2019-11-16 8:54 ` Ming Lei
2019-11-21 6:50 ` Oliver Sang [this message]
2019-11-21 7:36 ` Ming Lei
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=20191121065000.GA9619@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=axboe@kernel.dk \
--cc=bart.vanassche@wdc.com \
--cc=emilne@redhat.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kashyap.desai@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=loberman@redhat.com \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=osandov@fb.com \
--cc=rui.zhang@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