delta,tn48m-dn: ata1: hard resetting link #308
Description
One device Delta TN48M-DN showed the error below:
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd081]
[ 0.000000] Linux version 5.15.11-g3d377b49270b (ubuntu@onlbuilder10) (aarch64-linux-gnu-gcc (Debian 8.3.0-2) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1 SMP PREEMPT Sat Sep 16 13:49:42 UTC 2023
[ 0.000000] Machine model: delta,tn48m-dn
[ 0.000000] earlycon: uart8250 at MMIO32 0x00000000f0512000 (options '')
[ 0.000000] printk: bootconsole [uart8250] enabled
[ 0.000000] efi: UEFI not found.
[ 0.000000] [Firmware Bug]: Kernel image misaligned at boot, please fix your bootloader!
[ 0.000000] NUMA: No NUMA configuration found
[ 0.000000] NUMA: Faking a node at [mem 0x0000000000000000-0x000000023fffffff]
[ 0.000000] NUMA: NODE_DATA [mem 0x23efd8200-0x23efd9fff]
[…]
[2333810.863007] ata1: hard resetting link
[2333820.910106] ata1: hard resetting link
[2333830.966084] ata1: hard resetting link
[2333841.500748] ata1: link is slow to respond, please be patient (ready=0)
[2333866.013929] ata1: limiting SATA link speed to 3.0 Gbps
[2333866.019288] ata1: hard resetting link
[2333871.246302] ata1.00: disabled
[2333871.249519] ata1: EH complete
[2333871.252788] sd 0:0:0:0: [sda] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=97s
[2333871.262766] sd 0:0:0:0: [sda] tag#16 CDB: opcode=0x2a 2a 00 02 6c c3 c8 00 00 08 00
[2333871.281420] EXT4-fs warning (device sda4): ext4_end_bio:346: I/O error 10 writing to inode 1184028 starting block 5085306)
[2333871.299152] sd 0:0:0:0: [sda] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
[2333871.309040] sd 0:0:0:0: [sda] tag#17 CDB: opcode=0x2a 2a 00 02 6c ab 00 00 00 08 00
[2333871.327692] EXT4-fs warning (device sda4): ext4_end_bio:346: I/O error 10 writing to inode 1184015 starting block 5084513)
[2333871.345395] sd 0:0:0:0: [sda] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=122s
[2333871.355453] sd 0:0:0:0: [sda] tag#18 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
Rebooting did not help, but power cycling the device.
Is that likely a hardware issue or a driver problem?