From: Niklas Cassel <cassel@kernel.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: Damien Le Moal <dlemoal@kernel.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>,
John Garry <john.g.garry@oracle.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Hannes Reinecke <hare@suse.de>, Jens Axboe <axboe@kernel.dk>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
1120831@bugs.debian.org, snow.wolf.29@proton.me,
stable@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [regression] failed command: READ FPDMA QUEUED after boot for INTEL SSDSC2KG480G8, XCV10120 after 9b8b84879d4a ("block: Increase BLK_DEF_MAX_SECTORS_CAP")
Date: Wed, 14 Jan 2026 15:17:41 +0100 [thread overview]
Message-ID: <aWelaQYNJyulLBVc@ryzen> (raw)
In-Reply-To: <176839089913.2398366.61500945766820256@eldamar.lan>
Hello Salvatore,
On Wed, Jan 14, 2026 at 12:47:45PM +0100, Salvatore Bonaccorso wrote:
> A user reported a regression affecting his devices after 9b8b84879d4a
> ("block: Increase BLK_DEF_MAX_SECTORS_CAP") which maybe needs a
> similar quirk like 2e9832713631 ("ata: libata-core: Quirk DELLBOSS VD
> max_sectors").
The drive:
> Dec 10 18:56:03 kernel: ata1.00: Model 'INTEL SSDSC2KG480G8', rev 'XCV10120', applying quirks: zeroaftertrim
> Dec 10 18:56:03 kernel: ata1.00: ATA-10: INTEL SSDSC2KG480G8, XCV10120, max UDMA/133
The SATA controller:
00:17.0 SATA controller [0106]: Intel Corporation Cannon Lake Mobile PCH SATA AHCI Controller [8086:a353] (rev 10) (prog-if 01 [AHCI 1.0])
DeviceName: Onboard - SATA
Subsystem: Dell Device [1028:0924]
Perhaps the user could run:
https://github.com/floatious/max-sectors-quirk/blob/master/find-max-sectors.sh
So we could find which max sectors value we should quirk the device with,
since while the drive obviously chokes on a command of size 4 MiB / 8192
sectors, it might be able to handle something larger than 1280 KiB / 2560
sectors.
Kind regard,
Niklas
prev parent reply other threads:[~2026-01-14 14:17 UTC|newest]
Thread overview: 2+ 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 [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=aWelaQYNJyulLBVc@ryzen \
--to=cassel@kernel.org \
--cc=1120831@bugs.debian.org \
--cc=axboe@kernel.dk \
--cc=carnil@debian.org \
--cc=dlemoal@kernel.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=johannes.thumshirn@wdc.com \
--cc=john.g.garry@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=regressions@lists.linux.dev \
--cc=snow.wolf.29@proton.me \
--cc=stable@vger.kernel.org \
/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