Thank you for taking the time to report this bug and helping to make Ubuntu better.
You state "It then has to be restarted the hard way (i.e. by prssing the power button for several seconds)" So does this mean even SysRq commands direct to the kernel don't work to allow a safe reboot, shutdown? (if you don't recall the keys, a quick search on a phone for "magic sysrq" will find https://en.wikipedia.org/wiki/Magic_SysRq_key which is pretty good to find the common REISUB statekeystrokes). (Not being able to use SysRq to direct kernel directly shows the kernel is a very bad state. I read a RO file-system sometimes in your description, so I'd also check the health of your hardware & explore the logs and the messages before your "the file system is read-only" mentioned issue.) You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community- support/709 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938126 Title: System hangs up or make filesystem read-only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
