https://bugzilla.suse.com/show_bug.cgi?id=1231800 https://bugzilla.suse.com/show_bug.cgi?id=1231800#c34 Anthony Iliopoulos <ailiopoulos@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(slawek@lach.art.p | |l) | Status|NEW |IN_PROGRESS --- Comment #34 from Anthony Iliopoulos <ailiopoulos@suse.com> --- (In reply to Sławomir Lach from comment #33)

Backup done.

So, if I understood, I should debug case of remounting fs to read only mode? But how to debug this case? Should I wrote 'echo c > /proc/sysrq-trigger' into terminal? How to detect case, when it occur? Should I listen some udiskctl dbus signal?

So according to your comment #32 everything works as expected when the amd_sfh module is blacklisted. Presumably this is causing memory corruptions (comment #17). The amd_sfh fix [1] landed on v6.11.4 and the commit message mentions: "resolve memory errors, page faults, btrfs going read-only, and btrfs disk corruption." Thus my recommendation would be to update to v6.11.5, remove amd_sfh from the blacklist, and see how it goes. [1] commit c56f9ecb7fb6 ("HID: amd_sfh: Switch to device-managed dmam_alloc_coherent()") -- You are receiving this mail because: You are on the CC list for the bug.