On Wed, Apr 15, 2015 at 01:31:38PM -0400, Felix Miata wrote: > This isn't the first time or the only system. This particular one is an old > Athlon booted to F22 just updated last night. In order to try some follow-up > on a bug, I booted with drm.debug=14 log_buf_len=16M on cmdline. Somehow > after exiting IceWM back into KDM, the system quit responding. After some > waiting, I was switched to a tty full of systemd-journal failed to write > readonly filesystem messages. How the system got / into a readonly state I > have no idea, but my complaint is $SUBJECT, the time it takes, or the > complete failure, trying to reboot when there is a problem, often seeing > failed to store sound card state or failing boot *start* jobs. Why has > rebooting to get out of trouble gotten to be so nearly impossible? Did you try to press CAD more than 7 times within 2s? This should result in immedate reboot.
Zbyszek _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
