Hi Damien, one of the affected users here.
Damien Le Moal wrote: > In the bug report, I did not see a dmesg output for a failed boot. But I > guess it is because the user cannot capture it. Correct. > Could you have a look at this bug report for Fedora: > > https://bugzilla.kernel.org/show_bug.cgi?id=215519 > > This Debian case does sound similar. The problem is fixed with commit: > > fda17afc6166 ("ata: libata-core: Fix ata_dev_config_cpr()") > > which is included in kernel 5.16.9. Then it didn't help. > Could the users try that kernel version to see if that fixes the > issue ? Both affected users already tried 5.16.11 and the issue is still there. Nevertheless thanks for your prompt reply and all the details so far! Regards, Axel -- ,''`. | Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
