On 29/03/2019 01:33, Ming Lei wrote:
[...]
>> + blk_queue_segment_boundary(ctrl->ctrl.admin_q, PAGE_SIZE - 1);
>
> The above isn't needed for linus tree, however it is required for 5.0 and
> older
> releases.
Yes but it was worth a try after days of failing to find the issue.
> But nvme-
On 28/03/2019 18:52, Jens Axboe wrote:
> On 3/28/19 11:48 AM, Christoph Hellwig wrote:
>> On Thu, Mar 28, 2019 at 05:31:29PM +0100, Johannes Thumshirn wrote:
>>> In all cases I could reproduce it I had nsegs == 2 and
>>> rq->nr_phys_segments == 1 (rq->bio->bi_phys_segments == 1).
>>
>> And all case
On Fri, Mar 29, 2019 at 12:32 AM Johannes Thumshirn wrote:
>
> On 25/03/2019 02:04, kernel test robot wrote:
> [...]
> > nvme/005 (reset local loopback target)
> > runtime ...
> > nvme/005 (reset local loopback target) [failed]
> > runtime ... 0.596s
> > someth
On 3/28/19 11:48 AM, Christoph Hellwig wrote:
> On Thu, Mar 28, 2019 at 05:31:29PM +0100, Johannes Thumshirn wrote:
>> In all cases I could reproduce it I had nsegs == 2 and
>> rq->nr_phys_segments == 1 (rq->bio->bi_phys_segments == 1).
>
> And all cases are pass through as well?
>
> Can you chec
On Thu, Mar 28, 2019 at 05:31:29PM +0100, Johannes Thumshirn wrote:
> In all cases I could reproduce it I had nsegs == 2 and
> rq->nr_phys_segments == 1 (rq->bio->bi_phys_segments == 1).
And all cases are pass through as well?
Can you check if this still shows up with the series from Ming which
s
On 25/03/2019 02:04, kernel test robot wrote:
[...]
> nvme/005 (reset local loopback target)
> runtime ...
> nvme/005 (reset local loopback target) [failed]
> runtime ... 0.596s
> something found in dmesg:
> [ 24.160182] run blktests
