[code]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 sysl

Name
Email
Subject
Comment *
File	Select/drop/paste files here
* = required field	[▶ Show post options & limits] Confused? See the FAQ.

Flag
Oekaki	Show oekaki applet (replaces files and can be used instead)
Options	Do not bump (you can also write sage in the email field) Spoiler images (this replaces the thumbnails of your images with question marks)
Password	(For file and post deletion.)
Allowed file types:jpg, jpeg, gif, png, webm, mp4, pdf Max filesize is 16 MB. Max image dimensions are 15000 x 15000. You may upload 3 per post.

File (hide): 466a0dcde89e8da⋯.jpg (31.83 KB, 480x454, 240:227, 1417382266679.jpg) (h) (u)

▶Anonymous 03/07/18 (Wed) 11:32:48 No.879093>>879702 >>881010 [Watch Thread][Show All Posts]

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

>mfw this shit pops up in all my terminals at once at 6am

▶Anonymous 03/07/18 (Wed) 11:57:16 No.879098

>>733048

▶Anonymous 03/08/18 (Thu) 18:17:52 No.879677>>879698

>professional free software audited by billions of programmers

>le ebin easter eggs eksdee

▶Anonymous 03/08/18 (Thu) 19:17:46 No.879698>>879703 >>879733

>>879677

>any large amount of people audit systemd

>systemd reads the audits

>systemd doesn't ignore the pull requests or issues

>systemd doesn't outright censor their issues

▶Anonymous 03/08/18 (Thu) 19:29:07 No.879702>>879733

>>879093 (OP)

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

▶Anonymous 03/08/18 (Thu) 19:32:27 No.879703>>879733

>>879698

NOTABUG, WONTFIX

▶Anonymous 03/08/18 (Thu) 19:36:40 No.879705>>879709

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.

▶Anonymous 03/08/18 (Thu) 19:43:46 No.879709>>879731

>>879705

>why the fuck even have a system log?

Here's why

>Server starts fucking up/fucked up

>"Anon why is our server fucking up/did it fuck up?"

>Read syslog

>"oh hey that's why!"

>...

>profit

▶Anonymous 03/08/18 (Thu) 20:15:41 No.879727

spooky

▶Anonymous 03/08/18 (Thu) 20:23:42 No.879731>>879744

>>879709

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

▶Anonymous 03/08/18 (Thu) 20:28:50 No.879733>>880004

>>879698

>>879702

>>879703

Those messages are from the kernel. That's why it says "kernel:". systemd is just forwarding them.

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

▶Anonymous 03/08/18 (Thu) 21:06:34 No.879744>>879747

>>879731

>i'm thinking about desktop use

here's why

>Desktop starts fucking up/fucked up

>"Why is my desktop fucking up/did it fuck up?"

>Read syslog

>"oh hey that's why!"

>...

>profit

▶Anonymous 03/08/18 (Thu) 21:12:10 No.879747>>879749 >>879750 >>879799

>>879744

>Desktop starts fucking up/fucked up

>Read syslog

>...

>"oh hey that's why!"

said no-one ever

▶Anonymous 03/08/18 (Thu) 21:14:27 No.879749

>>879747

oh thats right, i forgot that /tech/ jusp reformats, reinstalls, and reconfigures any time a problem arises.

▶Anonymous 03/08/18 (Thu) 21:18:10 No.879750>>879805

>>879747

I use it a lot, for hardware problems. If some driver is acting up it'll usually start spewing into the syslog, which at the very least tells you which driver/piece of hardware is malfunctioning. If some USB device is having issues you can watch it to see which stages it does and doesn't go through when you log in.

This is bog standard stuff. It's not weird or obscure.

▶Anonymous 03/08/18 (Thu) 22:15:16 No.879780

See, if you weren't using systemd you wouldn't have this problem since the system wouldn't even get that far.

▶Anonymous 03/08/18 (Thu) 23:12:15 No.879799>>879805

>>879747

I use the system logs when trying to debug USB devices for seeing errors when plugging it in.

▶Anonymous 03/08/18 (Thu) 23:28:53 No.879805>>879995

>>879750

>>879799

why wouldn't you just enable it when you notice problems so you can catch errors, instead of leaving it enabled 24/7 while it mindlessly write's garbage and other possibly sensitive data to your disk that your never going to read?

▶Anonymous 03/09/18 (Fri) 07:04:29 No.879995

>>879805

Because then I can't catch errors that happened before I enabled it, and the disk is where I keep my other sensitive data anyway.

▶Anonymous 03/09/18 (Fri) 07:30:55 No.880004

>>879733

but le systemd hate!

systemd bad rite?

▶Anonymous 03/11/18 (Sun) 01:50:26 No.881010

>>879093 (OP)

I know this, and get it sometimes. If you use tlp or laptop-mode-tools and also fuck with your power savings settings with powertop, you will get these errors when your computer goes to sleep.

Doesn't have anything to do with systemd (for once) and you shouldn't enable the NMI watchdog timer anyway unless you're debugging the kernel or a module. It's completely harmless BTW.

/tech/ - Technology★

General

WebM

Theme

User JS

Do not paste code here unless you absolutely trust the source or have read it yourself!

Favorites

Customize Formatting

Filters