Fedora 33 - ata3: lost interrupt (Status 0x50)

Ask Fedora
,
1

The message below occurs very often!
When it happens, the system freezes (100% CPU) !!!

What is going wrong?

> Σεπ 12 20:08:29 fedorahost kernel: ata3: lost interrupt (Status 0x50)
> Σεπ 12 20:08:30 fedorahost kernel: ata3.00: exception Emask 0x10 SAct 0x0 SErr 0x4050002 action 0xe frozen
> Σεπ 12 20:08:30 fedorahost kernel: ata3: SError: { RecovComm PHYRdyChg CommWake DevExch }
> Σεπ 12 20:08:30 fedorahost kernel: ata3.00: failed command: FLUSH CACHE EXT
> Σεπ 12 20:08:30 fedorahost kernel: ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
>                                                res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x14 (ATA bus error)
> Σεπ 12 20:08:30 fedorahost kernel: ata3.00: status: { DRDY }
> Σεπ 12 20:08:30 fedorahost kernel: ata3: hard resetting link
> Σεπ 12 20:08:30 fedorahost kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> Σεπ 12 20:08:30 fedorahost kernel: ata3.00: configured for UDMA/133
> Σεπ 12 20:08:30 fedorahost kernel: ata3.00: retrying FLUSH 0xea Emask 0x14
> Σεπ 12 20:08:30 fedorahost kernel: ata3: EH complete
1 Like
2

You do not say which drive that may relate to nor the machine make/model, but an ata error like that seems to mean either a bad connection at a cable end, a bad cable, or the electronics on the drive or the sata controller failing.

The quick test would be to disconnect then reconnect the cable to the drive, both power and data. If this is a desktop then that part is really easy. A laptop not quite so but still pretty simple unless you have to open up the whole case to access the drive. A laptop will also usually have a ribbon cable hidden inside the case that could work loose.