Message from syslogd@localhost at Mar 7 06:27:06 ... kernel:Uhhuh. NMI received for unknown reason 0c on CPU 9...

Message from syslogd@localhost at Mar 7 06:27:06 ... kernel:Uhhuh. NMI received for unknown reason 0c on CPU 9.Message from syslogd@localhost at Mar 7 06:27:06 ... kernel:Do you have a strange power saving mode enabled?Message from syslogd@localhost at Mar 7 06:27:06 ... kernel:Dazed and confused, but trying to continue

Attached: 1417382266679.jpg (480x454, 31.83K)

Other urls found in this thread:

git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/x86/kernel/nmi.c?h=v4.16-rc4#n295
twitter.com/SFWRedditImages

...

...

...

It was only a matter of time before systemd became self aware.

NOTABUG, WONTFIX

i was considering a thread on system logging anyway, why the fuck even have a system log? when was the last time anyone got anything useful from your system log. why not just disable it completely and enable it only when there's problems for troubleshooting. i can't think of a single time i've ever needed to read something in the system log in order to troubleshoot an issue.

Here's why

spooky

i'm thinking about desktop use not server use, i could see it on a company server. and things like apache and most other common server software maintain their own log files, they don't use systemd-log