konman

I had a similar issue when I saw "DMA/133" zip by as I watched a Dell booting up. I looked in the logs and saw that it was an occasional thing that corrected itself by the time the boot was complete. I freaked out and cloned the drive but I left the old one in so I could beat up on it a little. I've been a Linux guy since Jessie and I was hoping Buster would take care of an ACPI issue that's been bugging me from the start. But that's another story. I started playing with BIOS settings @ Raid / AHCI / ATA. I knocked the setting down to RAID / ATA and that whispered message turned into yelling. The messages were pretty much the same as the OP's. It got worse on subsequent boots so I toggled the setting back to AHCI and it settled down after a few more reboots. Then original UDMA warning came back and I got the feeling that it was associated with cold booting. I swapped out the SATA cables and that seems to have done the trick. The data cable that I removed looked pretty beat up so you may want give that a try. Reseating them might help. This is a small sample of what came pouring out while it was set for ATA. Sep 10 01:00:09 localhost vmunix: [52183.926487] sd 0:0:0:0: [sda] tag#8 Sense Key : Illegal Request [current] Sep 10 01:00:09 localhost vmunix: [52183.926490] sd 0:0:0:0: [sda] tag#8 Add. Sense: Unaligned write command Sep 10 01:00:09 localhost vmunix: [52183.926493] sd 0:0:0:0: [sda] tag#8 CDB: Read(10) 28 00 00 80 12 18 00 00 08 00 Sep 10 01:00:09 localhost vmunix: [52183.926495] blk_update_request: I/O error, dev sda, sector 8393240 Sep 10 01:00:09 localhost vmunix: [52183.926502] sd 0:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Sep 10 01:00:09 localhost vmunix: [52183.926505] sd 0:0:0:0: [sda] tag#9 Sense Key : Illegal Request [current] Sep 10 01:00:09 localhost vmunix: [52183.926508] sd 0:0:0:0: [sda] tag#9 Add. Sense: Unaligned write command Sep 10 01:00:09 localhost vmunix: [52183.926511] sd 0:0:0:0: [sda] tag#9 CDB: Read(10) 28 00 00 80 12 20 00 00 08 00 Sep 10 01:00:09 localhost vmunix: [52183.926513] blk_update_request: I/O error, dev sda, sector 8393248 Sep 10 01:00:09 localhost vmunix: [52183.926520] sd 0:0:0:0: [sda] tag#10 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Sep 10 01:00:09 localhost vmunix: [52183.926523] sd 0:0:0:0: [sda] tag#10 Sense Key : Illegal Request [current] Sep 10 01:00:09 localhost vmunix: [52183.926526] sd 0:0:0:0: [sda] tag#10 Add. Sense: Unaligned write command Sep 10 01:00:09 localhost vmunix: [52183.926529] sd 0:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 00 80 12 28 00 00 08 00 Sep 10 01:00:09 localhost vmunix: [52183.926531] blk_update_request: I/O error, dev sda, sector 8393256 Sep 10 01:00:09 localhost vmunix: [52183.926589] ata1: EH complete Sep 10 01:00:10 localhost vmunix: [52185.280029] ata1.00: exception Emask 0x50 SAct 0x8000 SErr 0x4090800 action 0xe frozen Sep 10 01:00:10 localhost vmunix: [52185.280035] ata1.00: irq_stat 0x00400040, connection status changed Sep 10 01:00:10 localhost vmunix: [52185.280039] ata1: SError: { HostInt PHYRdyChg 10B8B DevExch } Sep 10 01:00:10 localhost vmunix: [52185.280043] ata1.00: failed command: READ FPDMA QUEUED Sep 10 01:00:10 localhost vmunix: [52185.280050] ata1.00: cmd 60/08:78:70:df:c6/00:00:00:00:00/40 tag 15 ncq dma 4096 in Sep 10 01:00:10 localhost vmunix: [52185.280050] res 40/00:7c:70:df:c6/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Sep 10 01:00:10 localhost vmunix: [52185.280054] ata1.00: status: { DRDY } Sep 10 01:00:10 localhost vmunix: [52185.280058] ata1: hard resetting link Sep 10 01:00:15 localhost vmunix: [52190.840054] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Sep 10 01:00:15 localhost vmunix: [52190.841404] ata1.00: configured for UDMA/133 Sep 10 01:00:15 localhost vmunix: [52190.841420] ata1: EH complete For the record .... I also toggled the MEB-x and Intel Virtualization settings in the BiOS settings. I have 4 similar Dell Optiplexes and they all boot with same ACPI errors. I was hopeful that Buster had addressed that issue and it didn't so I started spit wadding. Totally unrelated, I know. But what I wanted to do was rearrange the IRQ's. With older BIOS there were certain peripherals that I didn't like sharing with each other but I haven't found the key to that hidden door yet. I'll probably s look into Dell's Management portal. (Too many managers.) k