From: Michael Schmitz <schmitzmic@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k <linux-m68k@lists.linux-m68k.org>,
Jens Axboe <axboe@kernel.dk>, Laibin Qiu <qiulaibin@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-block <linux-block@vger.kernel.org>
Subject: Re: Regression in 5.17-rc1 on pata-falcon
Date: Sun, 6 Feb 2022 10:59:07 +1300 [thread overview]
Message-ID: <eb5fc9ae-45a7-44d3-0238-5cdaa1ae3558@gmail.com> (raw)
In-Reply-To: <CAMuHMdVnkvSCHKt5ouZP7HrMBg7nPg7fjiio-KVJ7dehA=FwyQ@mail.gmail.com>
Hi Geert, Jens,
thanks for the hint - applying 10825410b956dc1e on top of 5.17-rc1 does
indeed fix the issue.
nr_tags == 1 on the Falcon may explain why I ran into this. Oddly
enough, I have the same on ARAnyM. Adding a second 'disk' there does
reproduce the issue on ARAnyM though. nr_tags == 1 && nr_disks > 1
appears to be sufficient to reproduce this.
I surmised I couldn't be the only one to run into this, but hadn't seen
any other reports yet.
Cheers,
Michael
Am 05.02.2022 um 21:31 schrieb Geert Uytterhoeven:
> Hi Michael,
>
> On Sat, Feb 5, 2022 at 1:04 AM Michael Schmitz <schmitzmic@gmail.com> wrote:
>> commit 180dccb0dba4f5e84a4a70c1be1d34cbb6528b32 (blk-mq: fix tag_get
>> wait task can't be awakened) does cause a regression on my m68k hardware
>> test rig (m68k Falcon030, IDE disk attached through pata-falcon driver
>> which does use polled IO instead of interrupts, so may be a little on
>> the slow side).
>
>> Bisection between v5.16 and v5.17-rc1 points to
>> 180dccb0dba4f5e84a4a70c1be1d34cbb6528b32 as the culprit, which is
>> corroborated by reverting that commit in v5.17-rc1 and booting as
>> rapidly as before.
>
> Now you know the culprit, it looks like several other people ran into this.
> Does this fix help?
> https://lore.kernel.org/all/1643040870.3bwvk3sis4.none@localhost/
>
> It is commit 10825410b956dc1e ("blk-mq: Fix wrong wakeup
> batch configuration which will cause hang") in v5.17-rc2.
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
next prev parent reply other threads:[~2022-02-05 21:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 17:30 [PATCH] m68k: mm: Remove check for VM_IO to fix deferred I/O Geert Uytterhoeven
2022-01-28 21:26 ` Michael Schmitz
2022-01-28 23:55 ` Finn Thain
2022-01-29 2:08 ` Michael Schmitz
2022-01-30 0:32 ` Michael Schmitz
2022-01-30 6:57 ` Michael Schmitz
2022-02-05 0:04 ` Regression in 5.17-rc1 on pata-falcon (was: Re: [PATCH] m68k: mm: Remove check for VM_IO to fix deferred I/O) Michael Schmitz
2022-02-05 8:31 ` Geert Uytterhoeven
2022-02-05 21:59 ` Michael Schmitz [this message]
2022-01-31 2:21 ` [PATCH] m68k: mm: Remove check for VM_IO to fix deferred I/O Michael Schmitz
2022-02-07 13:06 ` Geert Uytterhoeven
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=eb5fc9ae-45a7-44d3-0238-5cdaa1ae3558@gmail.com \
--to=schmitzmic@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=geert@linux-m68k.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=qiulaibin@huawei.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