Skip to contentSkip to conversation

failed command: READ FPDMA QUEUED after boot for INTEL SSDSC2KG480G8, XCV10120 after 9b8b84879d4a ("block: Increase BLK_DEF_MAX_SECTORS_CAP")

regression Salvatore Bonaccorso 2 participants 4 messages Jan 14 – Jan 16 2 messages not in the archive

Subsystems (3)
Stable branch libata Regressions
lore
Share & tools
lore

Salvatore Bonaccorso

author
#0 lore raw

Control: forwarded -1 https://lore.kernel.org/regressions/[email protected]
Hi

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 full report is at https://bugs.debian.org/1120831

One full boot log (without tainted kernel) is provided in
https://bugs.debian.org/1120831#55 , where:

Dec 10 18:56:03 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
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
Dec 10 18:56:03 kernel: ata1.00: 937703088 sectors, multi 1: LBA48 NCQ (depth 32)
Dec 10 18:56:03 kernel: ata1.00: configured for UDMA/133
Dec 10 18:56:03 kernel: scsi 0:0:0:0: Direct-Access ATA INTEL SSDSC2KG48 0120 PQ: 0 ANSI: 5
Dec 10 18:56:03 kernel: iTCO_vendor_support: vendor-support=0
Dec 10 18:56:03 kernel: ata1.00: Enabling discard_zeroes_data
Dec 10 18:56:03 kernel: sd 0:0:0:0: [sda] 937703088 512-byte logical blocks: (480 GB/447 GiB)
Dec 10 18:56:03 kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks
Dec 10 18:56:03 kernel: sd 0:0:0:0: [sda] Write Protect is off
Dec 10 18:56:03 kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Dec 10 18:56:03 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 10 18:56:03 kernel: sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
Dec 10 18:56:03 kernel: ata1.00: Enabling discard_zeroes_data
[...]
Dec 10 18:58:49 kernel: ata1.00: exception Emask 0x0 SAct 0x81fff8 SErr 0x0 action 0x6 frozen
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)
Dec 10 18:58:49 kernel: ata1.00: status: { DRDY }
Dec 10 18:58:49 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 18:58:49 kernel: ata1.00: cmd 60/00:20:50:6a:4c/20:00:0c:00:00/40 tag 4 ncq dma 4194304 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 18:58:49 kernel: ata1.00: status: { DRDY }
Dec 10 18:58:49 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 18:58:49 kernel: ata1.00: cmd 60/00:28:50:8a:4c/20:00:0c:00:00/40 tag 5 ncq dma 4194304 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 18:58:49 kernel: ata1.00: status: { DRDY }
Dec 10 18:58:49 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 18:58:49 kernel: ata1.00: cmd 60/80:30:88:28:00/00:00:00:00:00/40 tag 6 ncq dma 65536 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 18:58:49 kernel: ata1.00: status: { DRDY }
Dec 10 18:58:49 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 18:58:49 kernel: ata1.00: cmd 60/28:38:00:08:40/00:00:00:00:00/40 tag 7 ncq dma 20480 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 18:58:49 kernel: ata1.00: status: { DRDY }
Dec 10 18:58:49 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 18:58:49 kernel: ata1.00: cmd 60/48:40:38:08:40/00:00:00:00:00/40 tag 8 ncq dma 36864 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 18:58:49 kernel: ata1.00: status: { DRDY }
Dec 10 18:58:49 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 18:58:49 kernel: ata1.00: cmd 60/28:48:00:08:80/00:00:00:00:00/40 tag 9 ncq dma 20480 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 18:58:49 kernel: ata1.00: status: { DRDY }
Dec 10 18:58:49 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 18:58:49 kernel: ata1.00: cmd 60/48:50:38:08:80/00:00:00:00:00/40 tag 10 ncq dma 36864 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 18:58:49 kernel: ata1.00: status: { DRDY }
Dec 10 18:58:49 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 18:58:49 kernel: ata1.00: cmd 60/80:58:00:08:c0/00:00:00:00:00/40 tag 11 ncq dma 65536 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 18:58:49 kernel: ata1.00: status: { DRDY }
Dec 10 18:58:49 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 18:58:49 kernel: ata1.00: cmd 60/10:60:00:08:00/00:00:01:00:00/40 tag 12 ncq dma 8192 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 18:58:49 kernel: ata1.00: status: { DRDY }
Dec 10 18:58:49 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 18:58:49 kernel: ata1.00: cmd 60/60:68:20:08:00/00:00:01:00:00/40 tag 13 ncq dma 49152 in res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 18:58:49 kernel: ata1.00: status: { DRDY }
Dec 10 18:58:49 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 18:58:49 kernel: ata1.00: cmd 60/80:70:00:08:40/00:00:01:00:00/40 tag 14 ncq dma 65536 in res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 18:58:49 kernel: ata1.00: status: { DRDY }
Dec 10 18:58:49 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 18:58:49 kernel: ata1.00: cmd 60/80:78:00:08:80/00:00:01:00:00/40 tag 15 ncq dma 65536 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 18:58:49 kernel: ata1.00: status: { DRDY }
Dec 10 18:58:49 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 18:58:49 kernel: ata1.00: cmd 60/80:80:00:08:c0/00:00:01:00:00/40 tag 16 ncq dma 65536 in res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 18:58:49 kernel: ata1.00: status: { DRDY }
Dec 10 18:58:49 kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Dec 10 18:58:49 kernel: ata1.00: cmd 61/20:b8:68:28:b2/00:00:1e:00:00/40 tag 23 ncq dma 16384 out res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 18:58:49 kernel: ata1.00: status: { DRDY }
Dec 10 18:58:49 kernel: ata1: hard resetting link
Dec 10 18:58:49 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 10 18:58:49 kernel: ata1.00: configured for UDMA/133
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#6 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=35s
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#6 Sense Key : Aborted Command [current]
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#6 Add. Sense: No additional sense information
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#6 CDB: Read(10) 28 00 00 00 28 88 00 00 80 00
Dec 10 18:58:49 kernel: I/O error, dev sda, sector 10376 op 0x0:(READ) flags 0x83700 phys_seg 16 prio class 2
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=35s
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#7 Sense Key : Aborted Command [current]
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#7 Add. Sense: No additional sense information
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#7 CDB: Read(10) 28 00 00 40 08 00 00 00 28 00
Dec 10 18:58:49 kernel: I/O error, dev sda, sector 4196352 op 0x0:(READ) flags 0x83700 phys_seg 5 prio class 2
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=35s
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#8 Sense Key : Aborted Command [current]
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#8 Add. Sense: No additional sense information
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#8 CDB: Read(10) 28 00 00 40 08 38 00 00 48 00
Dec 10 18:58:49 kernel: I/O error, dev sda, sector 4196408 op 0x0:(READ) flags 0x83700 phys_seg 9 prio class 2
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=35s
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#9 Sense Key : Aborted Command [current]
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#9 Add. Sense: No additional sense information
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#9 CDB: Read(10) 28 00 00 80 08 00 00 00 28 00
Dec 10 18:58:49 kernel: I/O error, dev sda, sector 8390656 op 0x0:(READ) flags 0x83700 phys_seg 5 prio class 2
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#10 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=35s
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#10 Sense Key : Aborted Command [current]
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#10 Add. Sense: No additional sense information
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 00 80 08 38 00 00 48 00
Dec 10 18:58:49 kernel: I/O error, dev sda, sector 8390712 op 0x0:(READ) flags 0x83700 phys_seg 9 prio class 2
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#11 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=35s
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#11 Sense Key : Aborted Command [current]
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#11 Add. Sense: No additional sense information
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#11 CDB: Read(10) 28 00 00 c0 08 00 00 00 80 00
Dec 10 18:58:49 kernel: I/O error, dev sda, sector 12584960 op 0x0:(READ) flags 0x83700 phys_seg 16 prio class 2
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#12 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=35s
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#12 Sense Key : Aborted Command [current]
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#12 Add. Sense: No additional sense information
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#12 CDB: Read(10) 28 00 01 00 08 00 00 00 10 00
Dec 10 18:58:49 kernel: I/O error, dev sda, sector 16779264 op 0x0:(READ) flags 0x83700 phys_seg 2 prio class 2
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#13 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=35s
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#13 Sense Key : Aborted Command [current]
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#13 Add. Sense: No additional sense information
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#13 CDB: Read(10) 28 00 01 00 08 20 00 00 60 00
Dec 10 18:58:49 kernel: I/O error, dev sda, sector 16779296 op 0x0:(READ) flags 0x83700 phys_seg 12 prio class 2
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=35s
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#14 Sense Key : Aborted Command [current]
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#14 Add. Sense: No additional sense information
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 01 40 08 00 00 00 80 00
Dec 10 18:58:49 kernel: I/O error, dev sda, sector 20973568 op 0x0:(READ) flags 0x83700 phys_seg 16 prio class 2
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#15 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=35s
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#15 Sense Key : Aborted Command [current]
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#15 Add. Sense: No additional sense information
Dec 10 18:58:49 kernel: sd 0:0:0:0: [sda] tag#15 CDB: Read(10) 28 00 01 80 08 00 00 00 80 00
Dec 10 18:58:49 kernel: I/O error, dev sda, sector 25167872 op 0x0:(READ) flags 0x83700 phys_seg 16 prio class 2
Dec 10 18:58:49 kernel: ata1: EH complete
Dec 10 18:58:49 kernel: ata1.00: Enabling discard_zeroes_data
Dec 10 18:59:21 kernel: ata1.00: exception Emask 0x0 SAct 0x600 SErr 0x0 action 0x6 frozen
Dec 10 18:59:21 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 18:59:21 kernel: ata1.00: cmd 60/00:48:50:6a:4c/20:00:0c:00:00/40 tag 9 ncq dma 4194304 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 18:59:21 kernel: ata1.00: status: { DRDY }
Dec 10 18:59:21 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 18:59:21 kernel: ata1.00: cmd 60/00:50:50:8a:4c/20:00:0c:00:00/40 tag 10 ncq dma 4194304 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 18:59:21 kernel: ata1.00: status: { DRDY }
Dec 10 18:59:21 kernel: ata1: hard resetting link
Dec 10 18:59:21 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 10 18:59:21 kernel: ata1.00: configured for UDMA/133
Dec 10 18:59:21 kernel: ata1: EH complete
Dec 10 18:59:51 kernel: ata1.00: exception Emask 0x0 SAct 0x20 SErr 0x0 action 0x6 frozen
Dec 10 18:59:51 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 18:59:51 kernel: ata1.00: cmd 60/00:28:50:8a:4c/20:00:0c:00:00/40 tag 5 ncq dma 4194304 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 18:59:51 kernel: ata1.00: status: { DRDY }
Dec 10 18:59:51 kernel: ata1: hard resetting link
Dec 10 18:59:52 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 10 18:59:52 kernel: ata1.00: configured for UDMA/133
Dec 10 18:59:52 kernel: ata1: EH complete
Dec 10 18:59:52 kernel: ata1.00: Enabling discard_zeroes_data
Dec 10 19:00:22 kernel: ata1.00: NCQ disabled due to excessive errors
Dec 10 19:00:22 kernel: ata1.00: exception Emask 0x0 SAct 0x20003400 SErr 0x0 action 0x6 frozen
Dec 10 19:00:22 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 19:00:22 kernel: ata1.00: cmd 60/00:50:50:2a:4c/20:00:0c:00:00/40 tag 10 ncq dma 4194304 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 19:00:22 kernel: ata1.00: status: { DRDY }
Dec 10 19:00:22 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 19:00:22 kernel: ata1.00: cmd 60/00:60:50:6a:4c/20:00:0c:00:00/40 tag 12 ncq dma 4194304 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 19:00:22 kernel: ata1.00: status: { DRDY }
Dec 10 19:00:22 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 19:00:22 kernel: ata1.00: cmd 60/00:68:50:8a:4c/20:00:0c:00:00/40 tag 13 ncq dma 4194304 in res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 19:00:22 kernel: ata1.00: status: { DRDY }
Dec 10 19:00:22 kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 10 19:00:22 kernel: ata1.00: cmd 60/08:e8:68:08:c0/00:00:01:00:00/40 tag 29 ncq dma 4096 in res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 10 19:00:22 kernel: ata1.00: status: { DRDY }
Dec 10 19:00:22 kernel: ata1: hard resetting link
Dec 10 19:00:22 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 10 19:00:22 kernel: ata1.00: configured for UDMA/133
Dec 10 19:00:22 kernel: ata1: EH complete
Dec 10 19:00:22 kernel: ata1.00: Enabling discard_zeroes_data

The user bisected the issue down to the mentioned 9b8b84879d4a ("block: Increase BLK_DEF_MAX_SECTORS_CAP").

#regzbot introduced: 9b8b84879d4adc506b0d3944e20b28d9f3f6994b #regzbot link: https://bugs.debian.org/1120831

What helps as a workaround was to apply a udev rule

ACTION=="add|change", SUBSYSTEM=="block", KERNEL=="sda", ATTR{queue/max_sectors_kb}="1280"

and decreasing again max_sectors_kb to 1280 KiB.

So maybe this device would need a similar quirk and limit the maximum size for these device I/O's to 2560 sectors?

Regards,
Salvatore

maintainer
#1 lore raw

Hello Salvatore,

Quoted 4 lines · Salvatore Bonaccorso

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:

Quoted 2 lines
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

A message that is not in the archive (sent off-list or not yet received): kkJPUUv8aExqrXPkwlzwEJV7Ywy3ogYCeTawLZZJm3wHBYylIhyCUeIKVFg6PWku-5BbspvtELJC6Tok6ens7Ib26hFkuSKKSm8NEwigRYo=@proton.me

maintainer
#3 lore raw

Hello Wolf,

Quoted 25 lines · Wolf

Here is find-max-sectors.sh output:

Drive model:
INTEL SSDSC2KG480G8

Drive firmware:
XCV10120

SATA / AHCI controller:
00:17.0 SATA controller [0106]: Intel Corporation Cannon Lake Mobile PCH SATA AHCI Controller [8086:a353] (rev 10)

Drive values before running the test:
/sys/block/sda/queue/max_hw_sectors_kb:32767
/sys/block/sda/queue/max_sectors_kb:1280
/sys/block/sda/queue/read_ahead_kb:128

Running test with max_sectors 128 KiB
Test: PASS

Running test with max_sectors 1024 KiB
Test: PASS

Running test with max_sectors 2048 KiB
Test: PASS

Quoted 8 lines

Running test with max_sectors 3072 KiB
Test: PASS

Running test with max_sectors 4095 KiB
Test: PASS

Running test with max_sectors 4096 KiB
Test: PASS

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

A message that is not in the archive (sent off-list or not yet received): iy-aryUnhtm6ORlJyPqOF0OrRSv1jAmyv_rOu1PswCnpCfQoNL8DKbBg26v5qsmW1zSU1MfDdWnvFJ5Y3mzYqXCq121b-I5pWll_AkEj1Sc=@proton.me

maintainer
#5 lore raw

Hello Wolf,

Quoted 7 lines · Wolf

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