Bug#1120831: [regression] failed command: READ FPDMA QUEUED after boot for INTEL SSDSC2KG480G8, XCV10120 after 9b8b84879d4a ("block: Increase BLK_DEF_MAX_SECTORS_CAP")
- 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: Bug#1120831: [regression] failed command: READ FPDMA QUEUED after boot for INTEL SSDSC2KG480G8, XCV10120 after 9b8b84879d4a ("block: Increase BLK_DEF_MAX_SECTORS_CAP")
- From: Niklas Cassel <cassel@kernel.org>
- Date: Wed, 14 Jan 2026 15:17:41 +0100
- Message-id: <[🔎] aWelaQYNJyulLBVc@ryzen>
- Reply-to: Niklas Cassel <cassel@kernel.org>, 1120831@bugs.debian.org
- In-reply-to: <[🔎] 176839089913.2398366.61500945766820256@eldamar.lan>
- References: <[🔎] 176839089913.2398366.61500945766820256@eldamar.lan> <176336488265.3298.17713871127662017371.reportbug@gdeltop.millenium.ro>
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
Reply to: