From: Niklas Cassel <cassel@kernel.org>
To: Wolf <snow.wolf.29@proton.me>
Cc: 1120831@bugs.debian.org, linux-ide@vger.kernel.org, dlemoal@kernel.org
Subject: Re: [regression] failed command: READ FPDMA QUEUED after boot for INTEL SSDSC2KG480G8, XCV10120 after 9b8b84879d4a ("block: Increase BLK_DEF_MAX_SECTORS_CAP")
Date: Fri, 16 Jan 2026 14:59:30 +0100 [thread overview]
Message-ID: <aWpEQqCHuDx8i5VT@ryzen> (raw)
In-Reply-To: <iy-aryUnhtm6ORlJyPqOF0OrRSv1jAmyv_rOu1PswCnpCfQoNL8DKbBg26v5qsmW1zSU1MfDdWnvFJ5Y3mzYqXCq121b-I5pWll_AkEj1Sc=@proton.me>
Hello Wolf,
On Thu, Jan 15, 2026 at 05:29:28AM +0000, Wolf wrote:
> Hi, Niklas
>
> Udev rule
>
> ACTION=="add|change", SUBSYSTEM=="block", KERNEL=="sda", ATTR{queue/max_sectors_kb}="4096"
>
> is not working.
Ok, since you seem to be able to reproduce it so easily,
then perhaps try with different values here, e.g.
1280 2048 3072 4095
and tell us the largest one that is working, and we could
add a quirk for the device with the highest value that is
working for you.
Kind regards,
Niklas
prev parent reply other threads:[~2026-01-16 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 11:47 [regression] failed command: READ FPDMA QUEUED after boot for INTEL SSDSC2KG480G8, XCV10120 after 9b8b84879d4a ("block: Increase BLK_DEF_MAX_SECTORS_CAP") Salvatore Bonaccorso
2026-01-14 14:17 ` Niklas Cassel
[not found] ` <kkJPUUv8aExqrXPkwlzwEJV7Ywy3ogYCeTawLZZJm3wHBYylIhyCUeIKVFg6PWku-5BbspvtELJC6Tok6ens7Ib26hFkuSKKSm8NEwigRYo=@proton.me>
2026-01-14 16:25 ` Niklas Cassel
[not found] ` <iy-aryUnhtm6ORlJyPqOF0OrRSv1jAmyv_rOu1PswCnpCfQoNL8DKbBg26v5qsmW1zSU1MfDdWnvFJ5Y3mzYqXCq121b-I5pWll_AkEj1Sc=@proton.me>
2026-01-16 13:59 ` Niklas Cassel [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=aWpEQqCHuDx8i5VT@ryzen \
--to=cassel@kernel.org \
--cc=1120831@bugs.debian.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=snow.wolf.29@proton.me \
/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