Am 19.12.2014 um 14:48 schrieb Michael Biebl: > 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.
Could you also provide the requested journalctl output. To get persistent logs, follow the instructions in /usr/share/doc/README.Debian and create /var/log/journal. This would you should have access the journal log after a reboot. To get the logs of the previous, the following command should work journalctl -alb -1 It would also help, if you can test with systemd from testing/unstable and the Debian kernel from testing/unstable. -- 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
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
