Am 19.12.2014 um 08:32 schrieb Jos van Wolput: > On 12/19/2014 06:28 AM, Michael Biebl wrote: >> Please enable persistent logging (see >> /usr/share/doc/systemd/README.Debian) and/or use something like SSH, >> which should allow you to access the system and then boot the system with >> systemd.log_level=debug on the kernel command line. >> >> If you can access the system via SSH, the output of journalctl -alb >> would be helpful. Is systemd still functional at this point, i.e. can >> you run systemctl status for example? >> > > As you asked I booted with systemd.log_level=debug on the kernel command > line. > Please see the attached daemon.log and kern.log. > I swiched to tty1 (at 13:30) and started apt-get --reinstall install > cups-daemon, > soon screen output, keys and mouse stopped working. > At 13.35 I started a hard reset. > > While I only have one computer I can't do SSH as suggested. > Hopefully you can find a clue to solve this issue!
I couldn't find anything in the log which would indicate a crash or malfunction of systemd. It seems to be running correctly up until the time you force-reset the system. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
