Arch Linux

Tharbad

Member

Registered: 2016-02-27

Posts: 333

kernel: ata10: COMRESET failed

Hi everyone,

I see the following errors in journalctl:

Mar 02 18:31:04 <PC Name> kernel: ata10: COMRESET failed (errno=-16)
Mar 02 18:31:04 <PC Name> kernel: ata11: COMRESET failed (errno=-16)
Mar 02 18:31:04 <PC Name> kernel: ata8: COMRESET failed (errno=-16)
Mar 02 18:31:04 <PC Name> kernel: ata13: COMRESET failed (errno=-16)
Mar 02 18:31:04 <PC Name> kernel: ata7: COMRESET failed (errno=-16)
Mar 02 18:31:04 <PC Name> kernel: ata9: COMRESET failed (errno=-16)
Mar 02 18:31:04 <PC Name> kernel: ata12: COMRESET failed (errno=-16)
Mar 02 18:31:04 <PC Name> kernel: ata14: COMRESET failed (errno=-16)
Mar 02 18:31:04 <PC Name> kernel: ata3: COMRESET failed (errno=-16)

They show up after resuming from suspend. I recently upgraded my GPU but it's not related, they were there even before.
PC works fine, and by grep'ing the boot log, I think those represent some of my disks. All of them are OK.

Any ideas why they show up?

Edit: As long as I don't get system crash it should be OK:
https://askubuntu.com/questions/174137/ … ith-my-ssd

As to why it happens after a suspend, I'll keep investigating.
Might be related to this bug:
https://bugs.launchpad.net/ubuntu/+sour … bug/297058

Might be a physical connection problem:
https://askubuntu.com/questions/988909/ … d-errno-16
Will check.

Might be the solution:
https://forums.opensuse.org/showthread. … -connected
TL;DR: Kernel watchdog is impatient and some drives take their time after suspend. Could've been in the logs forever before I noticed it.

Thanks

Last edited by Tharbad (2020-03-04 22:20:29)