linux-kernel - Re: [regression] failed command: READ FPDMA QUEUED after boot for INTEL SSDSC2KG480G8, XCV10120 after 9b8b84879d4a ("block: Increase BLK_DEF_MAX_SECTORS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aWelaQYNJyulLBVc@ryzen>
Date: Wed, 14 Jan 2026 15:17:41 +0100
From: Niklas Cassel <cassel@...nel.org>
To: Salvatore Bonaccorso <carnil@...ian.org>
Cc: Damien Le Moal <dlemoal@...nel.org>,
	"Martin K . Petersen" <martin.petersen@...cle.com>,
	Christoph Hellwig <hch@....de>,
	John Garry <john.g.garry@...cle.com>,
	Johannes Thumshirn <johannes.thumshirn@....com>,
	Hannes Reinecke <hare@...e.de>, Jens Axboe <axboe@...nel.dk>,
	linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org,
	1120831@...s.debian.org, snow.wolf.29@...ton.me,
	stable@...r.kernel.org, regressions@...ts.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")

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