From: Bart Van Assche <bvanassche@acm.org>
To: kernel test robot <oliver.sang@intel.com>,
Ming Lei <ming.lei@redhat.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: Mon, 4 Nov 2019 19:52:59 -0800 [thread overview]
Message-ID: <824c5a0b-a31a-b0a2-b14a-ab6edd294d07@acm.org> (raw)
In-Reply-To: <20191104085021.GF13369@xsang-OptiPlex-9020>
On 2019-11-04 00:50, 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
Hi Ming,
This is the second report by the build robot that this patch causes the
suspend_stress test to fail. I assume that that means that that test
failure is not a coincidence. The previous report (Oct-22) is available
at https://lore.kernel.org/linux-scsi/20191023003027.GD12647@shao2-debian/.
Bart.
WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <bvanassche@acm.org>
To: lkp@lists.01.org
Subject: Re: [scsi] 74eb6c22dc: suspend_stress.fail
Date: Mon, 04 Nov 2019 19:52:59 -0800 [thread overview]
Message-ID: <824c5a0b-a31a-b0a2-b14a-ab6edd294d07@acm.org> (raw)
In-Reply-To: <20191104085021.GF13369@xsang-OptiPlex-9020>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
On 2019-11-04 00:50, 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
Hi Ming,
This is the second report by the build robot that this patch causes the
suspend_stress test to fail. I assume that that means that that test
failure is not a coincidence. The previous report (Oct-22) is available
at https://lore.kernel.org/linux-scsi/20191023003027.GD12647(a)shao2-debian/.
Bart.
next prev parent reply other threads:[~2019-11-05 3:53 UTC|newest]
Thread overview: 22+ 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-10-08 19:33 ` kbuild test robot
2019-10-09 8:29 ` Dan Carpenter
2019-10-09 8:29 ` Dan Carpenter
2019-11-04 8:50 ` [scsi] 74eb6c22dc: suspend_stress.fail kernel test robot
2019-11-04 8:50 ` kernel test robot
2019-11-05 3:52 ` Bart Van Assche [this message]
2019-11-05 3:52 ` Bart Van Assche
2019-11-05 6:11 ` Ming Lei
2019-11-05 6:11 ` Ming Lei
2019-11-13 17:00 ` Bart Van Assche
2019-11-13 17:00 ` Bart Van Assche
2019-11-14 1:25 ` Ming Lei
2019-11-14 1:25 ` Ming Lei
2019-11-16 8:54 ` Ming Lei
2019-11-16 8:54 ` Ming Lei
2019-11-21 6:50 ` Oliver Sang
2019-11-21 6:50 ` Oliver Sang
2019-11-21 7:36 ` Ming Lei
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=824c5a0b-a31a-b0a2-b14a-ab6edd294d07@acm.org \
--to=bvanassche@acm.org \
--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=oliver.sang@intel.com \
--cc=osandov@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.