On Thu, 16.04.15 07:55, Andrei Borzenkov ([email protected]) 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. > > > > How long? systemd will enable watchdog on shutdown/reboot which fires > off in 10 minutes by default I think.
Apparently the machie in question is an old Athlon, which means the machine is so old that it is highly unlikely it already had a hw watchdog on-chipset. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
