Zbigniew Jędrzejewski-Szmek composed on 2015-04-15 18:11 (UTC): > On Wed, Apr 15, 2015 at 13:31:38 -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. My fingers and keyboards are old. I just hold CAD down until reboot proceeds, or not. All that have repeat and delay configurable in BIOS are set to 20 cps & 250 delay. KDE I always set to same. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
