Fresh i3 Install crashes randomly

I recently installed the community edition of i3, I was using the xfce prior to that with no problems. Now however, my system randomly freezes. I have been unable to diagnose the problem, one thing that I did however was use this script GitHub - erpalma/throttled: Workaround for Intel throttling issues in Linux. as I am using a lenovo X1 Carbon 6 laptop.

    inxi -Fza
    System:    Kernel: 5.8.18-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0
               parameters: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64 root=UUID=ea024c99-a84e-4340-a0c6-9f0aac65f36d rw quiet
               resume=UUID=7a56d5a5-0ba2-4732-bfda-0d6e5eaa0340 udev.log_priority=3
               Desktop: i3 4.18.3 info: polybar dm: LightDM 1.30.0 Distro: Manjaro Linux
    Machine:   Type: Laptop System: LENOVO product: 20KHCTO1WW v: ThinkPad X1 Carbon 6th serial: <filter> Chassis: type: 10
               serial: <filter>
               Mobo: LENOVO model: 20KHCTO1WW serial: <filter> UEFI: LENOVO v: N23ET75W (1.50 ) date: 10/13/2020
    Battery:   ID-1: BAT0 charge: 41.9 Wh condition: 42.1/57.0 Wh (74%) volts: 12.9/11.6 model: LGC 01AV494 type: Li-poly
               serial: <filter> status: Unknown cycles: 222
               Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master 3 serial: <filter>
               charge: 100% (should be ignored) rechargeable: yes status: Discharging
    CPU:       Info: Quad Core model: Intel Core i7-8650U bits: 64 type: MT MCP arch: Kaby Lake family: 6 model-id: 8E (142)
               stepping: A (10) microcode: E0 L2 cache: 8192 KiB
               flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 33615
               Speed: 700 MHz min/max: 400/4200 MHz Core speeds (MHz): 1: 700 2: 700 3: 700 4: 700 5: 700 6: 700 7: 700 8: 700
               Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
               Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
               Type: mds mitigation: Clear CPU buffers; SMT vulnerable
               Type: meltdown mitigation: PTI
               Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
               Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
               Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
               Type: srbds mitigation: Microcode
               Type: tsx_async_abort mitigation: Clear CPU buffers; SMT vulnerable
    Graphics:  Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5917
               Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus ID: 1-8:5 chip ID: 04f2:b61e serial: <filter>
               Display: x11 server: X.Org 1.20.9 compositor: picom v: git-dac85 driver: intel unloaded: modesetting
               alternate: fbdev,vesa display ID: :0 screens: 1
               Screen-1: 0 s-res: 4480x1440 s-dpi: 96 s-size: 1185x381mm (46.7x15.0") s-diag: 1245mm (49")
               Monitor-1: eDP1 res: 1920x1080 hz: 60 dpi: 157 size: 310x170mm (12.2x6.7") diag: 354mm (13.9")
               Monitor-2: HDMI1 res: 2560x1440 hz: 60 dpi: 108 size: 600x340mm (23.6x13.4") diag: 690mm (27.2")
               OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.2.1 direct render: Yes
    Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel alternate: snd_soc_skl
               bus ID: 00:1f.3 chip ID: 8086:9d71
               Sound Server: ALSA v: k5.8.18-1-MANJARO
    Network:   Device-1: Intel Ethernet I219-LM vendor: Lenovo driver: e1000e v: 3.2.6-k port: efa0 bus ID: 00:1f.6
               chip ID: 8086:15d7
               IF: enp0s31f6 state: down mac: <filter>
               Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel port: efa0 bus ID: 02:00.0 chip ID: 8086:24fd
               IF: wlp2s0 state: up mac: <filter>
    Drives:    Local Storage: total: 534.74 GiB used: 77.91 GiB (14.6%)
               SMART Message: Required tool smartctl not installed. Check --recommends
               ID-1: /dev/nvme0n1 vendor: Lenovo model: LENSE30512GMSP34MEAT3TA size: 476.94 GiB block size: physical: 512 B
               logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 2.5.0412 scheme: GPT
               ID-2: /dev/sda type: USB vendor: Kingston model: DataTraveler 3.0 size: 28.90 GiB block size: physical: 512 B
               logical: 512 B serial: <filter> rev: PMAP scheme: MBR
               ID-3: /dev/sdb type: USB vendor: Kingston model: DataTraveler 3.0 size: 28.90 GiB block size: physical: 512 B
               logical: 512 B serial: <filter> rev: PMAP scheme: MBR
    Partition: ID-1: / raw size: 459.71 GiB size: 451.49 GiB (98.21%) used: 77.89 GiB (17.3%) fs: ext4 dev: /dev/nvme0n1p2
    Swap:      Kernel: swappiness: 60 (default) cache pressure: 100 (default)
               ID-1: swap-1 type: partition size: 16.93 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p3
    Sensors:   System Temperatures: cpu: 54.0 C mobo: N/A
               Fan Speeds (RPM): cpu: 0
    Info:      Processes: 216 Uptime: 8m Memory: 15.39 GiB used: 1.57 GiB (10.2%) Init: systemd v: 246 Compilers: gcc: 10.2.0
               Packages: pacman: 1295 lib: 410 Shell: Bash v: 5.0.18 running in: alacritty inxi: 3.1.08

Below is the output of journalctl -b-1

    lines 1-78
    -- Logs begin at Fri 2020-11-06 12:09:38 EET, end at Tue 2020-11-17 13:21:14 EET. --
    Nov 17 09:25:08 kritical kernel: Linux version 5.8.18-1-MANJARO (builder@b81df68610d1) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.35.1) #1 SMP PREEMPT Sun Nov 1 14:10:04 UTC 2020
    Nov 17 09:25:08 kritical kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64 root=UUID=ea024c99-a84e-4340-a0c6-9f0aac65f36d rw quiet resume=UUID=7a56d5a5-0ba2-4732-bfda-0d6e5eaa0340 udev.log_priority=3
    Nov 17 09:25:08 kritical kernel: KERNEL supported cpus:
    Nov 17 09:25:08 kritical kernel:   Intel GenuineIntel
    Nov 17 09:25:08 kritical kernel:   AMD AuthenticAMD
    Nov 17 09:25:08 kritical kernel:   Hygon HygonGenuine
    Nov 17 09:25:08 kritical kernel:   Centaur CentaurHauls
    Nov 17 09:25:08 kritical kernel:   zhaoxin   Shanghai
    Nov 17 09:25:08 kritical kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
    Nov 17 09:25:08 kritical kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
    Nov 17 09:25:08 kritical kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
    Nov 17 09:25:08 kritical kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
    Nov 17 09:25:08 kritical kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
    Nov 17 09:25:08 kritical kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
    Nov 17 09:25:08 kritical kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
    Nov 17 09:25:08 kritical kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
    Nov 17 09:25:08 kritical kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
    Nov 17 09:25:08 kritical kernel: BIOS-provided physical RAM map:
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009cfff] usable
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x000000000009d000-0x00000000000fffff] reserved
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003fffffff] usable
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000403fffff] reserved
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x0000000040400000-0x000000004545ffff] usable
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x0000000045460000-0x0000000045460fff] ACPI NVS
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x0000000045461000-0x0000000045461fff] reserved
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x0000000045462000-0x000000004edc5fff] usable
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x000000004edc6000-0x000000004ee94fff] type 20
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x000000004ee95000-0x000000004ff1bfff] reserved
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x000000004ff1c000-0x000000004ff99fff] ACPI NVS
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x000000004ff9a000-0x000000004fffefff] ACPI data
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x000000004ffff000-0x000000004fffffff] usable
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x0000000050000000-0x0000000057ffffff] reserved
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x0000000058600000-0x000000005c7fffff] reserved
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x00000000fe010000-0x00000000fe010fff] reserved
    Nov 17 09:25:08 kritical kernel: BIOS-e820: [mem 0x0000000100000000-0x00000004a17fffff] usable
    Nov 17 09:25:08 kritical kernel: NX (Execute Disable) protection: active
    Nov 17 09:25:08 kritical kernel: efi: EFI v2.50 by Lenovo
    Nov 17 09:25:08 kritical kernel: efi: TPMFinalLog=0x4ff92000 SMBIOS=0x4f05a000 SMBIOS 3.0=0x4f057000 ACPI=0x4fffe000 ACPI 2.0=0x4fffe014 ESRT=0x4eee4000 MEMATTR=0x495f7018
    Nov 17 09:25:08 kritical kernel: SMBIOS 3.0.0 present.
    Nov 17 09:25:08 kritical kernel: DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET75W (1.50 ) 10/13/2020
    Nov 17 09:25:08 kritical kernel: tsc: Detected 2100.000 MHz processor
    Nov 17 09:25:08 kritical kernel: tsc: Detected 2099.944 MHz TSC
    Nov 17 09:25:08 kritical kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    Nov 17 09:25:08 kritical kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    Nov 17 09:25:08 kritical kernel: last_pfn = 0x4a1800 max_arch_pfn = 0x400000000
    Nov 17 09:25:08 kritical kernel: MTRR default type: write-back
    Nov 17 09:25:08 kritical kernel: MTRR fixed ranges enabled:
    Nov 17 09:25:08 kritical kernel:   00000-9FFFF write-back
    Nov 17 09:25:08 kritical kernel:   A0000-BFFFF uncachable
    Nov 17 09:25:08 kritical kernel:   C0000-FFFFF write-protect
    Nov 17 09:25:08 kritical kernel: MTRR variable ranges enabled:
    Nov 17 09:25:08 kritical kernel:   0 base 0080000000 mask 7F80000000 uncachable
    Nov 17 09:25:08 kritical kernel:   1 base 0060000000 mask 7FE0000000 uncachable
    Nov 17 09:25:08 kritical kernel:   2 base 005C000000 mask 7FFC000000 uncachable
    Nov 17 09:25:08 kritical kernel:   3 base 005A000000 mask 7FFE000000 uncachable
    Nov 17 09:25:08 kritical kernel:   4 base 2000000000 mask 7000000000 uncachable
    Nov 17 09:25:08 kritical kernel:   5 disabled
    Nov 17 09:25:08 kritical kernel:   6 disabled
    Nov 17 09:25:08 kritical kernel:   7 disabled
    Nov 17 09:25:08 kritical kernel:   8 disabled
    Nov 17 09:25:08 kritical kernel:   9 disabled
    Nov 17 09:25:08 kritical kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
    Nov 17 09:25:08 kritical kernel: last_pfn = 0x50000 max_arch_pfn = 0x400000000
    Nov 17 09:25:08 kritical kernel: esrt: Reserving ESRT space from 0x000000004eee4000 to 0x000000004eee4088.
    Nov 17 09:25:08 kritical kernel: check: Scanning 1 areas for low memory corruption
    Nov 17 09:25:08 kritical kernel: Using GB pages for direct mapping
    Nov 17 09:25:08 kritical kernel: Secure boot could not be determined
    Nov 17 09:25:08 kritical kernel: RAMDISK: [mem 0x3674b000-0x3739cfff]
    Nov 17 09:25:08 kritical kernel: ACPI: Early table checksum verification disabled
    Nov 17 09:25:08 kritical kernel: ACPI: RSDP 0x000000004FFFE014 000024 (v02 LENOVO)
    Nov 17 09:25:08 kritical kernel: ACPI: XSDT 0x000000004FFB2188 000124 (v01 LENOVO TP-N23   00001500 PTEC 00000002)
    Nov 17 09:25:08 kritical kernel: ACPI: FACP 0x000000004FFEB000 0000F4 (v05 LENOVO TP-N23   00001500 PTEC 00000002)
    Nov 17 09:25:08 kritical kernel: ACPI: DSDT 0x000000004FFC0000 026DC4 (v02 LENOVO SKL      00000000 INTL 20160527)
    Nov 17 09:25:08 kritical kernel: ACPI: FACS 0x000000004FF3E000 000040

Any ideas as to what might be going on? Should I maybe be using an older kernel?

Please cleanup the post a bit by setting the inxi and journal output between ```
so it reads a bit easier.

Did you also use that script when you had the xfce version installed?
And did you follow the pointer to the Ubuntu howto in the link you provided?
Seems to me there should be some settings changed

btw did you try without the script? How does it run then?

Apologies about the formatting. Fixed it now.
No I didn’t have that script running while I was using xfce. I should try without the script. I will do that.

However, I think the problem might be related to spotify potentially. This is the output of
journalctl | grep “error” | tail -n 10

Nov 17 00:57:22 kritical dbus-daemon[403]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.27" (uid=1000 pid=1349 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.12" (uid=0 pid=1143 comm="/usr/lib/bluetooth/bluetoothd ")
Nov 17 03:28:13 kritical kernel: spotify[3560]: segfault at 31 ip 00007fc0cd391992 sp 00007ffcacd739e0 error 4 in libcef.so[7fc0cacfa000+6dbb000]
Nov 17 09:25:08 kritical kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwl-debug-yoyo.bin failed with error -2
Nov 17 09:25:13 kritical systemd[1212]: Not generating service for XDG autostart app-fluxgui-autostart.service, error parsing Exec= line: Invalid argument
Nov 17 10:45:26 kritical dbus-daemon[402]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.28" (uid=1000 pid=1323 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.12" (uid=0 pid=1149 comm="/usr/lib/bluetooth/bluetoothd ")
Nov 17 13:18:55 kritical kernel: spotify[2721]: segfault at 31 ip 00007fb81aaf3992 sp 00007fffb301f0e0 error 4 in libcef.so[7fb81845c000+6dbb000]
Nov 17 13:19:20 kritical kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwl-debug-yoyo.bin failed with error -2
Nov 17 13:19:25 kritical systemd[1237]: Not generating service for XDG autostart app-fluxgui-autostart.service, error parsing Exec= line: Invalid argument
Nov 17 13:40:01 kritical dbus-daemon[374]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.28" (uid=1000 pid=1341 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.12" (uid=0 pid=1140 comm="/usr/lib/bluetooth/bluetoothd ")
Nov 17 14:09:11 kritical dbus-daemon[374]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.28" (uid=1000 pid=1341 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.12" (uid=0 pid=1140 comm="/usr/lib/bluetooth/bluetoothd ")

So it seems that spotify is triggering this crash, correct? Thanks for the help :slight_smile:

Should not be because that is an segmentation fault and related to Spotify when you start it.
If you have set it to autostart remove it, check if problem persists. But since your saying roundom freezes it cannot be the issue.

Also why did you install the script in I3 when in XCFE you did not? Did you had specific problems that could be related to throttling issues?

Yes I’ve got spotify to exec in my i3 config. I will try removing that.

To answer your question, yes my CPU was throttling recently. But I suspect that might’ve been due to a polybar script that was showing what was playing in spotify. Once I disabled those scripts, my CPU usage went back to normal. So I don’t think that there was a throttling issue to begin with, it was the polybar script.

I will remove spotify from the i3 config and let you know how things go. Is there anything else you recommend I should try?

Well first I would check without that script, since is you had no issues when you run XFCE there should be no issues when running i3 (custom scripts aside).

Alright, thanks a lot! I will try removing the script.
Just to be sure the logs I’ve posted aren’t pointing to a specific problem correct?

Not regarding the issue you described here no