Journalctl and identifying problems

Steve · 2017-05-06 14:48:31

For lack of a better word and experience im describing journalctl in the sense it can diagnose problems, how?

I installed kernel https://www.archlinux.org/packages/comm … -hardened/

Woked fine for 5 or so minutes and the system rdid random reboots not commanded by the user, did this three times before i decided there must be a problem with compatibily of this kernel and my machine. I have a feeling this kernel has conflicts with user and root setting in Arch Linux.

Me being a complete newb and not understanding the readout journalctl gives makes it a bit hard to understand. I fully admit that i most likely do not need a hardened kernel, but maybe i do?

So below is the journalctl event i can identify with a problem as far what i think maybe a kernel panic or incomapitibilty.

Suggestions and helpfull comments welcome.

I have installed the latest Arch Linux iso doing it the arch way, i know its not Debian or Bunsenlabs but more to do with systemd perhaps?

journalctl --since=2017-05-04 -b10

May 05 13:25:59 pure systemd-journald[225]: Time spent on flushing to /var is 2.
May 05 13:25:59 pure kernel: Linux version 4.11.0-1-hardened (builduser@strcat) 
May 05 13:25:59 pure kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux-harden
May 05 13:25:59 pure kernel: Disabled fast string operations
May 05 13:25:59 pure kernel: x86/fpu: x87 FPU will use FXSAVE
May 05 13:25:59 pure kernel: e820: BIOS-provided physical RAM map:
May 05 13:25:59 pure kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d7
May 05 13:25:59 pure kernel: BIOS-e820: [mem 0x000000000009d800-0x000000000009ff
May 05 13:25:59 pure kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fff
May 05 13:25:59 pure kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000bbb0ef
May 05 13:25:59 pure kernel: BIOS-e820: [mem 0x00000000bbb0f000-0x00000000bbe57f
May 05 13:25:59 pure kernel: BIOS-e820: [mem 0x00000000bbe58000-0x00000000bbe70f
May 05 13:25:59 pure kernel: BIOS-e820: [mem 0x00000000bbe71000-0x00000000bbe9bf
May 05 13:25:59 pure kernel: BIOS-e820: [mem 0x00000000bbe9c000-0x00000000bbeccf
May 05 13:25:59 pure kernel: BIOS-e820: [mem 0x00000000bbecd000-0x00000000bbf11f
May 05 13:25:59 pure kernel: BIOS-e820: [mem 0x00000000bbf12000-0x00000000bbf12f
May 05 13:25:59 pure kernel: BIOS-e820: [mem 0x00000000bbf13000-0x00000000bbf1ef
May 05 13:25:59 pure kernel: BIOS-e820: [mem 0x00000000bbf1f000-0x00000000bbf9ef
May 05 13:25:59 pure kernel: BIOS-e820: [mem 0x00000000bbf9f000-0x00000000bbffef
May 05 13:25:59 pure kernel: BIOS-e820: [mem 0x00000000bbfff000-0x00000000bbffff
May 05 13:25:59 pure kernel: BIOS-e820: [mem 0x00000000bc000000-0x00000000bfffff
May 05 13:25:59 pure kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffff
lines 1-23

my system specs via inxi, note i have since elected to install the liquorice kernel.

System:    Host: pure Kernel: 4.10.14-zen-lqx x86_64 (64 bit)
           Desktop: Openbox 3.6.1 Distro: Arch Linux
Machine:   Device: laptop System: TOSHIBA product: Satellite A660 v: PSAW3A-07S00R
           Mobo: TOSHIBA model: NWQAA v: 1.00
           UEFI [Legacy]: TOSHIBA v: 2.30 date: 11/24/11
Battery    BAT1: charge: 27.3 Wh 100.0% condition: 27.3/45.0 Wh (61%)
CPU:       Quad core Intel Core i7 Q 740 (-HT-MCP-) speed/max: 933/1734 MHz
Graphics:  Card: NVIDIA GT216M [GeForce GT 330M]
           Display Server: N/A drivers: modesetting (unloaded: vesa)
           Resolution: 80x24
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169
           Card-2: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter
           driver: bcma-pci-bridge
Drives:    HDD Total Size: 1008.0GB (13.4% used)
Info:      Processes: 198 Uptime: 1:45 Memory: 791.8/3885.0MB Init: systemd
           Client: Shell (bash) inxi: 2.3.8

Last edited by Steve (2017-05-06 14:55:48)

Head_on_a_Stick · 2017-05-06 15:02:14

Steve wrote:

So below is the journalctl event i can identify with a problem as far what i think maybe a kernel panic or incomapitibilty.

I don't think so, my system has that same journal content and it all works perfectly

If you are not comfortable posting a link to a pastebin containing the full journal contents for the few seconds (or maybe minutes) leading up to the reboot then it will not be practical to troubleshoot this here and a formal bug report would probably be more appropriate.

Steve · 2017-05-06 15:13:22

Before i continue i am going to d/l and install again and see if i get the same problem Hoas. Any idea on how to leave out IP address from the journalctl output though?

Head_on_a_Stick · 2017-05-06 15:20:41

It will only show addresses on your private subnet, the hardware firewall in your router should protect you against infringements for those IPs.

If you are feeling paranoid, use a pastebin with a short expiry limit.

Steve · 2017-05-06 15:28:45

Im using a tethered smartphone.

Reinstalled the hardened kernel and using it now. Ill post up a pastebin if i get another reboot.

Head_on_a_Stick · 2017-05-06 15:40:01

Steve wrote:

Im using a tethered smartphone.

Ah, I see.

That will still use NAT so I think you're safe.

#1 2017-05-06 14:48:31

Journalctl and identifying problems

#2 2017-05-06 15:02:14

Re: Journalctl and identifying problems

#3 2017-05-06 15:13:22

Re: Journalctl and identifying problems

#4 2017-05-06 15:20:41

Re: Journalctl and identifying problems

#5 2017-05-06 15:28:45

Re: Journalctl and identifying problems

#6 2017-05-06 15:40:01

Re: Journalctl and identifying problems

Board footer