Bug#1120831: [regression] failed command: READ FPDMA QUEUED after boot for INTEL SSDSC2KG480G8, XCV10120 after 9b8b84879d4a ("block: Increase BLK_DEF_MAX_SECTORS_CAP")
On Wednesday, 14 January 2026 at 18:25, Niklas Cassel <cassel@kernel.org> wrote:
>
> It is quite unexpected that 4096 KiB passes.
>
> find-max-sectors.sh performs reads.
>
> The commands that timed out according to dmesg shared were
> also reads:
>
> Dec 10 18:58:49 kernel: ata1.00: failed command: READ FPDMA QUEUED
> Dec 10 18:58:49 kernel: ata1.00: cmd 60/00:18:50:4a:4c/20:00:0c:00:00/40 tag 3 ncq dma 4194304 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
>
> And also of size 4194304 == 4096 KiB.
>
>
> The script has been able to detect different limits for other
> "broken" drives, and was used to get the quirk value for e.g.
> commit 2e9832713631 ("ata: libata-core: Quirk DELLBOSS VD max_sectors"),
> so I wonder why it is not workin here (why 4 MiB reads passes).
>
> Damien, ideas?
>
>
> Kind regards,
> Niklas
Hi, Niklas
Udev rule
ACTION=="add|change", SUBSYSTEM=="block", KERNEL=="sda", ATTR{queue/max_sectors_kb}="4096"
is not working.
Regards,
Wolf
Reply to: