Jan 01 22:14:19 the-nexus kernel: Linux version 5.15.12-arch1-1 (linux@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Wed, 29 Dec 2021 12:04:56 +0000 Jan 01 22:14:19 the-nexus kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=557a2b29-0d9e-4df9-8d98-fb4a27e5348b rw quiet loglevel=3 nowatchdog nvme_load=YES Jan 01 22:14:19 the-nexus kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Jan 01 22:14:19 the-nexus kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Jan 01 22:14:19 the-nexus kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Jan 01 22:14:19 the-nexus kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' Jan 01 22:14:19 the-nexus kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' Jan 01 22:14:19 the-nexus kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Jan 01 22:14:19 the-nexus kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 Jan 01 22:14:19 the-nexus kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 Jan 01 22:14:19 the-nexus kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. Jan 01 22:14:19 the-nexus kernel: signal: max sigframe size: 2032 Jan 01 22:14:19 the-nexus kernel: BIOS-provided physical RAM map: Jan 01 22:14:19 the-nexus kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable Jan 01 22:14:19 the-nexus kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved Jan 01 22:14:19 the-nexus kernel: BIOS-e820: [mem 0x0000000000100000-0x000000006b729fff] usable Jan 01 22:14:19 the-nexus kernel: BIOS-e820: [mem 0x000000006b72a000-0x000000006b85ffff] type 20 Jan 01 22:14:19 the-nexus kernel: BIOS-e820: [mem 0x000000006b860000-0x000000006fac1fff] reserved Jan 01 22:14:19 the-nexus kernel: BIOS-e820: [mem 0x000000006fac2000-0x000000006fca9fff] ACPI NVS Jan 01 22:14:19 the-nexus kernel: BIOS-e820: [mem 0x000000006fcaa000-0x000000006fd0efff] ACPI data Jan 01 22:14:19 the-nexus kernel: BIOS-e820: [mem 0x000000006fd0f000-0x000000006fd0ffff] usable Jan 01 22:14:19 the-nexus kernel: BIOS-e820: [mem 0x000000006fd10000-0x000000007d7fffff] reserved Jan 01 22:14:19 the-nexus kernel: BIOS-e820: [mem 0x00000000fe010000-0x00000000fe010fff] reserved Jan 01 22:14:19 the-nexus kernel: BIOS-e820: [mem 0x0000000100000000-0x00000004807fffff] usable Jan 01 22:14:19 the-nexus kernel: NX (Execute Disable) protection: active Jan 01 22:14:19 the-nexus kernel: efi: EFI v2.60 by Lenovo Jan 01 22:14:19 the-nexus kernel: efi: TPMFinalLog=0x6fca2000 SMBIOS=0x6de55000 SMBIOS 3.0=0x6de48000 ACPI=0x6fd0e000 ACPI 2.0=0x6fd0e014 MEMATTR=0x68977018 ESRT=0x6c240000 Jan 01 22:14:19 the-nexus kernel: SMBIOS 3.1.1 present. Jan 01 22:14:19 the-nexus kernel: DMI: LENOVO 20QDS3B400/20QDS3B400, BIOS N2HET64W (1.47 ) 07/19/2021 Jan 01 22:14:19 the-nexus kernel: tsc: Detected 1800.000 MHz processor Jan 01 22:14:19 the-nexus kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved Jan 01 22:14:19 the-nexus kernel: e820: remove [mem 0x000a0000-0x000fffff] usable Jan 01 22:14:19 the-nexus kernel: last_pfn = 0x480800 max_arch_pfn = 0x400000000 Jan 01 22:14:19 the-nexus kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT Jan 01 22:14:19 the-nexus kernel: last_pfn = 0x6fd10 max_arch_pfn = 0x400000000 Jan 01 22:14:19 the-nexus kernel: esrt: Reserving ESRT space from 0x000000006c240000 to 0x000000006c2400d8. Jan 01 22:14:19 the-nexus kernel: Using GB pages for direct mapping Jan 01 22:14:19 the-nexus kernel: Secure boot disabled Jan 01 22:14:19 the-nexus kernel: RAMDISK: [mem 0x36577000-0x372b2fff] Jan 01 22:14:19 the-nexus kernel: ACPI: Early table checksum verification disabled Jan 01 22:14:19 the-nexus kernel: ACPI: RSDP 0x000000006FD0E014 000024 (v02 LENOVO) Jan 01 22:14:19 the-nexus kernel: ACPI: XSDT 0x000000006FD0C188 000114 (v01 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: FACP 0x000000006DC62000 000114 (v06 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: DSDT 0x000000006DC34000 0292EF (v02 LENOVO CFL 20170001 INTL 20160422) Jan 01 22:14:19 the-nexus kernel: ACPI: FACS 0x000000006FB07000 000040 Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0x000000006DCB8000 001B26 (v02 LENOVO CpuSsdt 00003000 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0x000000006DCB7000 00056D (v02 LENOVO CtdpB 00001000 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0x000000006DC7E000 004220 (v02 LENOVO DptfTabl 00001000 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0x000000006DC67000 00330A (v02 LENOVO SaSsdt 00003000 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0x000000006DC66000 000612 (v02 LENOVO Tpm2Tabl 00001000 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: TPM2 0x000000006DC65000 000034 (v04 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: UEFI 0x000000006FB24000 000042 (v01 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0x000000006DC63000 000530 (v02 LENOVO PerfTune 00001000 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: HPET 0x000000006DC61000 000038 (v01 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: APIC 0x000000006DC60000 00012C (v03 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: MCFG 0x000000006DC5F000 00003C (v01 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: ECDT 0x000000006DC5E000 000053 (v01 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0x000000006DC32000 001D1B (v02 LENOVO WHL_Tbt_ 00001000 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0x000000006DC31000 000024 (v02 LENOVO PID1Ssdt 00000010 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0x000000006DC2F000 0014C0 (v02 LENOVO ProjSsdt 00000010 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: BOOT 0x000000006DC2E000 000028 (v01 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0x000000006DC2B000 000EF6 (v02 LENOVO UsbCTabl 00001000 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: LPIT 0x000000006DC2A000 000094 (v01 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: WSMT 0x000000006DC29000 000028 (v01 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0x000000006DC27000 001983 (v02 LENOVO TbtTypeC 00000000 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: DBGP 0x000000006DC26000 000034 (v01 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: DBG2 0x000000006DC25000 000054 (v00 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: MSDM 0x000000006DC24000 000055 (v03 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: BATB 0x000000006DA47000 00004A (v02 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: NHLT 0x000000006C23E000 00184A (v00 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: DMAR 0x000000006DC2D000 0000A8 (v01 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: FPDT 0x000000006C23D000 000044 (v01 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: BGRT 0x000000006C23C000 000038 (v01 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: UEFI 0x000000006FB01000 00013E (v01 LENOVO TP-N2H 00001470 PTEC 00000002) Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving FACP table memory at [mem 0x6dc62000-0x6dc62113] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving DSDT table memory at [mem 0x6dc34000-0x6dc5d2ee] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving FACS table memory at [mem 0x6fb07000-0x6fb0703f] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving SSDT table memory at [mem 0x6dcb8000-0x6dcb9b25] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving SSDT table memory at [mem 0x6dcb7000-0x6dcb756c] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving SSDT table memory at [mem 0x6dc7e000-0x6dc8221f] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving SSDT table memory at [mem 0x6dc67000-0x6dc6a309] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving SSDT table memory at [mem 0x6dc66000-0x6dc66611] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving TPM2 table memory at [mem 0x6dc65000-0x6dc65033] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving UEFI table memory at [mem 0x6fb24000-0x6fb24041] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving SSDT table memory at [mem 0x6dc63000-0x6dc6352f] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving HPET table memory at [mem 0x6dc61000-0x6dc61037] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving APIC table memory at [mem 0x6dc60000-0x6dc6012b] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving MCFG table memory at [mem 0x6dc5f000-0x6dc5f03b] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving ECDT table memory at [mem 0x6dc5e000-0x6dc5e052] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving SSDT table memory at [mem 0x6dc32000-0x6dc33d1a] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving SSDT table memory at [mem 0x6dc31000-0x6dc31023] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving SSDT table memory at [mem 0x6dc2f000-0x6dc304bf] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving BOOT table memory at [mem 0x6dc2e000-0x6dc2e027] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving SSDT table memory at [mem 0x6dc2b000-0x6dc2bef5] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving LPIT table memory at [mem 0x6dc2a000-0x6dc2a093] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving WSMT table memory at [mem 0x6dc29000-0x6dc29027] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving SSDT table memory at [mem 0x6dc27000-0x6dc28982] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving DBGP table memory at [mem 0x6dc26000-0x6dc26033] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving DBG2 table memory at [mem 0x6dc25000-0x6dc25053] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving MSDM table memory at [mem 0x6dc24000-0x6dc24054] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving BATB table memory at [mem 0x6da47000-0x6da47049] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving NHLT table memory at [mem 0x6c23e000-0x6c23f849] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving DMAR table memory at [mem 0x6dc2d000-0x6dc2d0a7] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving FPDT table memory at [mem 0x6c23d000-0x6c23d043] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving BGRT table memory at [mem 0x6c23c000-0x6c23c037] Jan 01 22:14:19 the-nexus kernel: ACPI: Reserving UEFI table memory at [mem 0x6fb01000-0x6fb0113d] Jan 01 22:14:19 the-nexus kernel: No NUMA configuration found Jan 01 22:14:19 the-nexus kernel: Faking a node at [mem 0x0000000000000000-0x00000004807fffff] Jan 01 22:14:19 the-nexus kernel: NODE_DATA(0) allocated [mem 0x4807fc000-0x4807fffff] Jan 01 22:14:19 the-nexus kernel: Zone ranges: Jan 01 22:14:19 the-nexus kernel: DMA [mem 0x0000000000001000-0x0000000000ffffff] Jan 01 22:14:19 the-nexus kernel: DMA32 [mem 0x0000000001000000-0x00000000ffffffff] Jan 01 22:14:19 the-nexus kernel: Normal [mem 0x0000000100000000-0x00000004807fffff] Jan 01 22:14:19 the-nexus kernel: Device empty Jan 01 22:14:19 the-nexus kernel: Movable zone start for each node Jan 01 22:14:19 the-nexus kernel: Early memory node ranges Jan 01 22:14:19 the-nexus kernel: node 0: [mem 0x0000000000001000-0x000000000009efff] Jan 01 22:14:19 the-nexus kernel: node 0: [mem 0x0000000000100000-0x000000006b729fff] Jan 01 22:14:19 the-nexus kernel: node 0: [mem 0x000000006fd0f000-0x000000006fd0ffff] Jan 01 22:14:19 the-nexus kernel: node 0: [mem 0x0000000100000000-0x00000004807fffff] Jan 01 22:14:19 the-nexus kernel: Initmem setup node 0 [mem 0x0000000000001000-0x00000004807fffff] Jan 01 22:14:19 the-nexus kernel: On node 0, zone DMA: 1 pages in unavailable ranges Jan 01 22:14:19 the-nexus kernel: On node 0, zone DMA: 97 pages in unavailable ranges Jan 01 22:14:19 the-nexus kernel: On node 0, zone DMA32: 17893 pages in unavailable ranges Jan 01 22:14:19 the-nexus kernel: On node 0, zone Normal: 752 pages in unavailable ranges Jan 01 22:14:19 the-nexus kernel: On node 0, zone Normal: 30720 pages in unavailable ranges Jan 01 22:14:19 the-nexus kernel: Reserving Intel graphics memory at [mem 0x79800000-0x7d7fffff] Jan 01 22:14:19 the-nexus kernel: ACPI: PM-Timer IO Port: 0x1808 Jan 01 22:14:19 the-nexus kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) Jan 01 22:14:19 the-nexus kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) Jan 01 22:14:19 the-nexus kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) Jan 01 22:14:19 the-nexus kernel: ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) Jan 01 22:14:19 the-nexus kernel: ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) Jan 01 22:14:19 the-nexus kernel: ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) Jan 01 22:14:19 the-nexus kernel: ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) Jan 01 22:14:19 the-nexus kernel: ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1]) Jan 01 22:14:19 the-nexus kernel: ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1]) Jan 01 22:14:19 the-nexus kernel: ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1]) Jan 01 22:14:19 the-nexus kernel: ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1]) Jan 01 22:14:19 the-nexus kernel: ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1]) Jan 01 22:14:19 the-nexus kernel: ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1]) Jan 01 22:14:19 the-nexus kernel: ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1]) Jan 01 22:14:19 the-nexus kernel: ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1]) Jan 01 22:14:19 the-nexus kernel: ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1]) Jan 01 22:14:19 the-nexus kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119 Jan 01 22:14:19 the-nexus kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) Jan 01 22:14:19 the-nexus kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Jan 01 22:14:19 the-nexus kernel: ACPI: Using ACPI (MADT) for SMP configuration information Jan 01 22:14:19 the-nexus kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000 Jan 01 22:14:19 the-nexus kernel: e820: update [mem 0x66e78000-0x66f08fff] usable ==> reserved Jan 01 22:14:19 the-nexus kernel: TSC deadline timer available Jan 01 22:14:19 the-nexus kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs Jan 01 22:14:19 the-nexus kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff] Jan 01 22:14:19 the-nexus kernel: PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x000fffff] Jan 01 22:14:19 the-nexus kernel: PM: hibernation: Registered nosave memory: [mem 0x66e78000-0x66f08fff] Jan 01 22:14:19 the-nexus kernel: PM: hibernation: Registered nosave memory: [mem 0x6b72a000-0x6b85ffff] Jan 01 22:14:19 the-nexus kernel: PM: hibernation: Registered nosave memory: [mem 0x6b860000-0x6fac1fff] Jan 01 22:14:19 the-nexus kernel: PM: hibernation: Registered nosave memory: [mem 0x6fac2000-0x6fca9fff] Jan 01 22:14:19 the-nexus kernel: PM: hibernation: Registered nosave memory: [mem 0x6fcaa000-0x6fd0efff] Jan 01 22:14:19 the-nexus kernel: PM: hibernation: Registered nosave memory: [mem 0x6fd10000-0x7d7fffff] Jan 01 22:14:19 the-nexus kernel: PM: hibernation: Registered nosave memory: [mem 0x7d800000-0xfe00ffff] Jan 01 22:14:19 the-nexus kernel: PM: hibernation: Registered nosave memory: [mem 0xfe010000-0xfe010fff] Jan 01 22:14:19 the-nexus kernel: PM: hibernation: Registered nosave memory: [mem 0xfe011000-0xffffffff] Jan 01 22:14:19 the-nexus kernel: [mem 0x7d800000-0xfe00ffff] available for PCI devices Jan 01 22:14:19 the-nexus kernel: Booting paravirtualized kernel on bare hardware Jan 01 22:14:19 the-nexus kernel: clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370452778343963 ns Jan 01 22:14:19 the-nexus kernel: setup_percpu: NR_CPUS:320 nr_cpumask_bits:320 nr_cpu_ids:8 nr_node_ids:1 Jan 01 22:14:19 the-nexus kernel: percpu: Embedded 61 pages/cpu s212992 r8192 d28672 u262144 Jan 01 22:14:19 the-nexus kernel: pcpu-alloc: s212992 r8192 d28672 u262144 alloc=1*2097152 Jan 01 22:14:19 the-nexus kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7 Jan 01 22:14:19 the-nexus kernel: Built 1 zonelists, mobility grouping on. Total pages: 4047662 Jan 01 22:14:19 the-nexus kernel: Policy zone: Normal Jan 01 22:14:19 the-nexus kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=557a2b29-0d9e-4df9-8d98-fb4a27e5348b rw quiet loglevel=3 nowatchdog nvme_load=YES Jan 01 22:14:19 the-nexus kernel: Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-linux nvme_load=YES", will be passed to user space. Jan 01 22:14:19 the-nexus kernel: Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) Jan 01 22:14:19 the-nexus kernel: Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) Jan 01 22:14:19 the-nexus kernel: mem auto-init: stack:byref_all(zero), heap alloc:on, heap free:off Jan 01 22:14:19 the-nexus kernel: Memory: 15968912K/16448292K available (14344K kernel code, 2071K rwdata, 10792K rodata, 1864K init, 3836K bss, 479120K reserved, 0K cma-reserved) Jan 01 22:14:19 the-nexus kernel: random: get_random_u64 called from __kmem_cache_create+0x2a/0x540 with crng_init=0 Jan 01 22:14:19 the-nexus kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1 Jan 01 22:14:19 the-nexus kernel: ftrace: allocating 44301 entries in 174 pages Jan 01 22:14:19 the-nexus kernel: ftrace: allocated 174 pages with 5 groups Jan 01 22:14:19 the-nexus kernel: rcu: Preemptible hierarchical RCU implementation. Jan 01 22:14:19 the-nexus kernel: rcu: RCU dyntick-idle grace-period acceleration is enabled. Jan 01 22:14:19 the-nexus kernel: rcu: RCU restricting CPUs from NR_CPUS=320 to nr_cpu_ids=8. Jan 01 22:14:19 the-nexus kernel: rcu: RCU priority boosting: priority 1 delay 500 ms. Jan 01 22:14:19 the-nexus kernel: Trampoline variant of Tasks RCU enabled. Jan 01 22:14:19 the-nexus kernel: Rude variant of Tasks RCU enabled. Jan 01 22:14:19 the-nexus kernel: Tracing variant of Tasks RCU enabled. Jan 01 22:14:19 the-nexus kernel: rcu: RCU calculated value of scheduler-enlistment delay is 30 jiffies. Jan 01 22:14:19 the-nexus kernel: rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8 Jan 01 22:14:19 the-nexus kernel: NR_IRQS: 20736, nr_irqs: 2048, preallocated irqs: 16 Jan 01 22:14:19 the-nexus kernel: kfence: initialized - using 2097152 bytes for 255 objects at 0x(____ptrval____)-0x(____ptrval____) Jan 01 22:14:19 the-nexus kernel: Console: colour dummy device 80x25 Jan 01 22:14:19 the-nexus kernel: printk: console [tty0] enabled Jan 01 22:14:19 the-nexus kernel: ACPI: Core revision 20210730 Jan 01 22:14:19 the-nexus kernel: hpet: HPET dysfunctional in PC10. Force disabled. Jan 01 22:14:19 the-nexus kernel: APIC: Switch to symmetric I/O mode setup Jan 01 22:14:19 the-nexus kernel: DMAR: Host address width 39 Jan 01 22:14:19 the-nexus kernel: DMAR: DRHD base: 0x000000fed90000 flags: 0x0 Jan 01 22:14:19 the-nexus kernel: DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 19e2ff0505e Jan 01 22:14:19 the-nexus kernel: DMAR: DRHD base: 0x000000fed91000 flags: 0x1 Jan 01 22:14:19 the-nexus kernel: DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da Jan 01 22:14:19 the-nexus kernel: DMAR: RMRR base: 0x0000006fa7e000 end: 0x0000006fa9dfff Jan 01 22:14:19 the-nexus kernel: DMAR: RMRR base: 0x00000079000000 end: 0x0000007d7fffff Jan 01 22:14:19 the-nexus kernel: DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1 Jan 01 22:14:19 the-nexus kernel: DMAR-IR: HPET id 0 under DRHD base 0xfed91000 Jan 01 22:14:19 the-nexus kernel: DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping. Jan 01 22:14:19 the-nexus kernel: DMAR-IR: Enabled IRQ remapping in x2apic mode Jan 01 22:14:19 the-nexus kernel: x2apic enabled Jan 01 22:14:19 the-nexus kernel: Switched APIC routing to cluster x2apic. Jan 01 22:14:19 the-nexus kernel: clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x19f2297dd97, max_idle_ns: 440795236593 ns Jan 01 22:14:19 the-nexus kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 3601.00 BogoMIPS (lpj=6000000) Jan 01 22:14:19 the-nexus kernel: pid_max: default: 32768 minimum: 301 Jan 01 22:14:19 the-nexus kernel: LSM: Security Framework initializing Jan 01 22:14:19 the-nexus kernel: landlock: Up and running. Jan 01 22:14:19 the-nexus kernel: Yama: becoming mindful. Jan 01 22:14:19 the-nexus kernel: LSM support for eBPF active Jan 01 22:14:19 the-nexus kernel: Mount-cache hash table entries: 32768 (order: 6, 262144 bytes, linear) Jan 01 22:14:19 the-nexus kernel: Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes, linear) Jan 01 22:14:19 the-nexus kernel: CPU0: Thermal monitoring enabled (TM1) Jan 01 22:14:19 the-nexus kernel: process: using mwait in idle threads Jan 01 22:14:19 the-nexus kernel: Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8 Jan 01 22:14:19 the-nexus kernel: Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4 Jan 01 22:14:19 the-nexus kernel: Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization Jan 01 22:14:19 the-nexus kernel: Spectre V2 : Mitigation: Enhanced IBRS Jan 01 22:14:19 the-nexus kernel: Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch Jan 01 22:14:19 the-nexus kernel: Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier Jan 01 22:14:19 the-nexus kernel: Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp Jan 01 22:14:19 the-nexus kernel: SRBDS: Mitigation: TSX disabled Jan 01 22:14:19 the-nexus kernel: Freeing SMP alternatives memory: 36K Jan 01 22:14:19 the-nexus kernel: smpboot: Estimated ratio of average max frequency by base frequency (times 1024): 2104 Jan 01 22:14:19 the-nexus kernel: smpboot: CPU0: Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz (family: 0x6, model: 0x8e, stepping: 0xc) Jan 01 22:14:19 the-nexus kernel: Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver. Jan 01 22:14:19 the-nexus kernel: ... version: 4 Jan 01 22:14:19 the-nexus kernel: ... bit width: 48 Jan 01 22:14:19 the-nexus kernel: ... generic registers: 4 Jan 01 22:14:19 the-nexus kernel: ... value mask: 0000ffffffffffff Jan 01 22:14:19 the-nexus kernel: ... max period: 00007fffffffffff Jan 01 22:14:19 the-nexus kernel: ... fixed-purpose events: 3 Jan 01 22:14:19 the-nexus kernel: ... event mask: 000000070000000f Jan 01 22:14:19 the-nexus kernel: rcu: Hierarchical SRCU implementation. Jan 01 22:14:19 the-nexus kernel: smp: Bringing up secondary CPUs ... Jan 01 22:14:19 the-nexus kernel: x86: Booting SMP configuration: Jan 01 22:14:19 the-nexus kernel: .... node #0, CPUs: #1 #2 #3 #4 #5 #6 #7 Jan 01 22:14:19 the-nexus kernel: smp: Brought up 1 node, 8 CPUs Jan 01 22:14:19 the-nexus kernel: smpboot: Max logical packages: 1 Jan 01 22:14:19 the-nexus kernel: smpboot: Total of 8 processors activated (28811.00 BogoMIPS) Jan 01 22:14:19 the-nexus kernel: devtmpfs: initialized Jan 01 22:14:19 the-nexus kernel: x86/mm: Memory block size: 128MB Jan 01 22:14:19 the-nexus kernel: ACPI: PM: Registering ACPI NVS region [mem 0x6fac2000-0x6fca9fff] (1998848 bytes) Jan 01 22:14:19 the-nexus kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370867519511994 ns Jan 01 22:14:19 the-nexus kernel: futex hash table entries: 2048 (order: 5, 131072 bytes, linear) Jan 01 22:14:19 the-nexus kernel: pinctrl core: initialized pinctrl subsystem Jan 01 22:14:19 the-nexus kernel: PM: RTC time: 03:14:17, date: 2022-01-02 Jan 01 22:14:19 the-nexus kernel: NET: Registered PF_NETLINK/PF_ROUTE protocol family Jan 01 22:14:19 the-nexus kernel: DMA: preallocated 2048 KiB GFP_KERNEL pool for atomic allocations Jan 01 22:14:19 the-nexus kernel: DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations Jan 01 22:14:19 the-nexus kernel: DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations Jan 01 22:14:19 the-nexus kernel: audit: initializing netlink subsys (disabled) Jan 01 22:14:19 the-nexus kernel: audit: type=2000 audit(1641093257.026:1): state=initialized audit_enabled=0 res=1 Jan 01 22:14:19 the-nexus kernel: thermal_sys: Registered thermal governor 'fair_share' Jan 01 22:14:19 the-nexus kernel: thermal_sys: Registered thermal governor 'bang_bang' Jan 01 22:14:19 the-nexus kernel: thermal_sys: Registered thermal governor 'step_wise' Jan 01 22:14:19 the-nexus kernel: thermal_sys: Registered thermal governor 'user_space' Jan 01 22:14:19 the-nexus kernel: thermal_sys: Registered thermal governor 'power_allocator' Jan 01 22:14:19 the-nexus kernel: cpuidle: using governor ladder Jan 01 22:14:19 the-nexus kernel: cpuidle: using governor menu Jan 01 22:14:19 the-nexus kernel: Simple Boot Flag at 0x47 set to 0x1 Jan 01 22:14:19 the-nexus kernel: HugeTLB: can free 4094 vmemmap pages for hugepages-1048576kB Jan 01 22:14:19 the-nexus kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Jan 01 22:14:19 the-nexus kernel: ACPI: bus type PCI registered Jan 01 22:14:19 the-nexus kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 Jan 01 22:14:19 the-nexus kernel: PCI: MMCONFIG for domain 0000 [bus 00-7f] at [mem 0xf0000000-0xf7ffffff] (base 0xf0000000) Jan 01 22:14:19 the-nexus kernel: PCI: not using MMCONFIG Jan 01 22:14:19 the-nexus kernel: PCI: Using configuration type 1 for base access Jan 01 22:14:19 the-nexus kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance' Jan 01 22:14:19 the-nexus kernel: Kprobes globally optimized Jan 01 22:14:19 the-nexus kernel: HugeTLB: can free 6 vmemmap pages for hugepages-2048kB Jan 01 22:14:19 the-nexus kernel: HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages Jan 01 22:14:19 the-nexus kernel: HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages Jan 01 22:14:19 the-nexus kernel: ACPI: Added _OSI(Module Device) Jan 01 22:14:19 the-nexus kernel: ACPI: Added _OSI(Processor Device) Jan 01 22:14:19 the-nexus kernel: ACPI: Added _OSI(3.0 _SCP Extensions) Jan 01 22:14:19 the-nexus kernel: ACPI: Added _OSI(Processor Aggregator Device) Jan 01 22:14:19 the-nexus kernel: ACPI: Added _OSI(Linux-Dell-Video) Jan 01 22:14:19 the-nexus kernel: ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) Jan 01 22:14:19 the-nexus kernel: ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics) Jan 01 22:14:19 the-nexus kernel: ACPI: 12 ACPI AML tables successfully acquired and loaded Jan 01 22:14:19 the-nexus kernel: ACPI: EC: EC started Jan 01 22:14:19 the-nexus kernel: ACPI: EC: interrupt blocked Jan 01 22:14:19 the-nexus kernel: ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62 Jan 01 22:14:19 the-nexus kernel: ACPI: EC: Boot ECDT EC used to handle transactions Jan 01 22:14:19 the-nexus kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored Jan 01 22:14:19 the-nexus kernel: ACPI: Dynamic OEM Table Load: Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0xFFFF9F970021C700 0000F4 (v02 PmRef Cpu0Psd 00003000 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: \_SB_.PR00: _OSC native thermal LVT Acked Jan 01 22:14:19 the-nexus kernel: ACPI: Dynamic OEM Table Load: Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0xFFFF9F9701123C00 000400 (v02 PmRef Cpu0Cst 00003001 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: Dynamic OEM Table Load: Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0xFFFF9F9701137000 0004FD (v02 PmRef Cpu0Ist 00003000 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: Dynamic OEM Table Load: Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0xFFFF9F970023E800 000149 (v02 PmRef Cpu0Hwp 00003000 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: Dynamic OEM Table Load: Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0xFFFF9F9701131800 000724 (v02 PmRef HwpLvt 00003000 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: Dynamic OEM Table Load: Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0xFFFF9F9701130000 0005FC (v02 PmRef ApIst 00003000 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: Dynamic OEM Table Load: Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0xFFFF9F9701120400 000317 (v02 PmRef ApHwp 00003000 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: Dynamic OEM Table Load: Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0xFFFF9F9700123000 000AB0 (v02 PmRef ApPsd 00003000 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: Dynamic OEM Table Load: Jan 01 22:14:19 the-nexus kernel: ACPI: SSDT 0xFFFF9F9701124000 00030A (v02 PmRef ApCst 00003000 INTL 20160527) Jan 01 22:14:19 the-nexus kernel: ACPI: Interpreter enabled Jan 01 22:14:19 the-nexus kernel: ACPI: PM: (supports S0 S3 S4 S5) Jan 01 22:14:19 the-nexus kernel: ACPI: Using IOAPIC for interrupt routing Jan 01 22:14:19 the-nexus kernel: PCI: MMCONFIG for domain 0000 [bus 00-7f] at [mem 0xf0000000-0xf7ffffff] (base 0xf0000000) Jan 01 22:14:19 the-nexus kernel: PCI: MMCONFIG at [mem 0xf0000000-0xf7ffffff] reserved in ACPI motherboard resources Jan 01 22:14:19 the-nexus kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug Jan 01 22:14:19 the-nexus kernel: ACPI: Enabled 8 GPEs in block 00 to 7F Jan 01 22:14:19 the-nexus kernel: ACPI: PM: Power Resource [PUBS] Jan 01 22:14:19 the-nexus kernel: ACPI: PM: Power Resource [BTPR] Jan 01 22:14:19 the-nexus kernel: ACPI: PM: Power Resource [USBC] Jan 01 22:14:19 the-nexus kernel: ACPI: PM: Power Resource [PXP] Jan 01 22:14:19 the-nexus kernel: ACPI: PM: Power Resource [PXP] Jan 01 22:14:19 the-nexus kernel: ACPI: PM: Power Resource [V0PR] Jan 01 22:14:19 the-nexus kernel: ACPI: PM: Power Resource [V1PR] Jan 01 22:14:19 the-nexus kernel: ACPI: PM: Power Resource [V2PR] Jan 01 22:14:19 the-nexus kernel: ACPI: PM: Power Resource [WRST] Jan 01 22:14:19 the-nexus kernel: ACPI: PM: Power Resource [PIN] Jan 01 22:14:19 the-nexus kernel: ACPI: PM: Power Resource [PINP] Jan 01 22:14:19 the-nexus kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e]) Jan 01 22:14:19 the-nexus kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI EDR HPX-Type3] Jan 01 22:14:19 the-nexus kernel: acpi PNP0A08:00: _OSC: platform does not support [AER] Jan 01 22:14:19 the-nexus kernel: acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug SHPCHotplug PME PCIeCapability LTR DPC] Jan 01 22:14:19 the-nexus kernel: acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration Jan 01 22:14:19 the-nexus kernel: PCI host bridge to bus 0000:00 Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:00: root bus resource [mem 0x7d800000-0xefffffff window] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:00: root bus resource [mem 0xfc800000-0xfe7fffff window] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:00: root bus resource [bus 00-7e] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:00.0: [8086:3e34] type 00 class 0x060000 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:02.0: [8086:3ea0] type 00 class 0x030000 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:02.0: reg 0x10: [mem 0xe9000000-0xe9ffffff 64bit] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:02.0: reg 0x18: [mem 0xc0000000-0xcfffffff 64bit pref] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:02.0: reg 0x20: [io 0x2000-0x203f] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:02.0: BAR 2: assigned to efifb Jan 01 22:14:19 the-nexus kernel: pci 0000:00:04.0: [8086:1903] type 00 class 0x118000 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:04.0: reg 0x10: [mem 0xea230000-0xea237fff 64bit] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:08.0: [8086:1911] type 00 class 0x088000 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:08.0: reg 0x10: [mem 0xea242000-0xea242fff 64bit] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:12.0: [8086:9df9] type 00 class 0x118000 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:12.0: reg 0x10: [mem 0xea243000-0xea243fff 64bit] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:14.0: [8086:9ded] type 00 class 0x0c0330 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:14.0: reg 0x10: [mem 0xea220000-0xea22ffff 64bit] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold Jan 01 22:14:19 the-nexus kernel: pci 0000:00:14.2: [8086:9def] type 00 class 0x050000 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:14.2: reg 0x10: [mem 0xea240000-0xea241fff 64bit] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:14.2: reg 0x18: [mem 0xea244000-0xea244fff 64bit] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:14.3: [8086:9df0] type 00 class 0x028000 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:14.3: reg 0x10: [mem 0xea238000-0xea23bfff 64bit] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:14.3: PME# supported from D0 D3hot D3cold Jan 01 22:14:19 the-nexus kernel: pci 0000:00:15.0: [8086:9de8] type 00 class 0x0c8000 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:15.0: reg 0x10: [mem 0xea245000-0xea245fff 64bit] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:15.1: [8086:9de9] type 00 class 0x0c8000 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:15.1: reg 0x10: [mem 0xea246000-0xea246fff 64bit] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:16.0: [8086:9de0] type 00 class 0x078000 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:16.0: reg 0x10: [mem 0xea247000-0xea247fff 64bit] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:16.0: PME# supported from D3hot Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.0: [8086:9db0] type 01 class 0x060400 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.0: PTM enabled (root), 4ns granularity Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.4: [8086:9db4] type 01 class 0x060400 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.4: PME# supported from D0 D3hot D3cold Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.4: PTM enabled (root), 4ns granularity Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1f.0: [8086:9d84] type 00 class 0x060100 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1f.3: [8086:9dc8] type 00 class 0x040380 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xea23c000-0xea23ffff 64bit] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1f.3: reg 0x20: [mem 0xea000000-0xea0fffff 64bit] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1f.3: PME# supported from D3hot D3cold Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1f.4: [8086:9da3] type 00 class 0x0c0500 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1f.4: reg 0x10: [mem 0xea248000-0xea2480ff 64bit] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1f.4: reg 0x20: [io 0xefa0-0xefbf] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1f.5: [8086:9da4] type 00 class 0x0c8000 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1f.5: reg 0x10: [mem 0xfe010000-0xfe010fff] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1f.6: [8086:15be] type 00 class 0x020000 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1f.6: reg 0x10: [mem 0xea200000-0xea21ffff] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1f.6: PME# supported from D0 D3hot D3cold Jan 01 22:14:19 the-nexus kernel: pci 0000:03:00.0: [10ec:5765] type 00 class 0x010802 Jan 01 22:14:19 the-nexus kernel: pci 0000:03:00.0: reg 0x10: [mem 0xea100000-0xea103fff 64bit] Jan 01 22:14:19 the-nexus kernel: pci 0000:03:00.0: reg 0x24: [mem 0xea104000-0xea105fff] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.0: PCI bridge to [bus 03] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.0: bridge window [mem 0xea100000-0xea1fffff] Jan 01 22:14:19 the-nexus kernel: pci 0000:05:00.0: [8086:15d3] type 01 class 0x060400 Jan 01 22:14:19 the-nexus kernel: pci 0000:05:00.0: enabling Extended Tags Jan 01 22:14:19 the-nexus kernel: pci 0000:05:00.0: supports D1 D2 Jan 01 22:14:19 the-nexus kernel: pci 0000:05:00.0: PME# supported from D0 D1 D2 D3hot D3cold Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.4: PCI bridge to [bus 05-52] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.4: bridge window [mem 0xd0000000-0xe81fffff] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.4: bridge window [mem 0x80000000-0xbfffffff 64bit pref] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:00.0: [8086:15d3] type 01 class 0x060400 Jan 01 22:14:19 the-nexus kernel: pci 0000:06:00.0: enabling Extended Tags Jan 01 22:14:19 the-nexus kernel: pci 0000:06:00.0: supports D1 D2 Jan 01 22:14:19 the-nexus kernel: pci 0000:06:00.0: PME# supported from D0 D1 D2 D3hot D3cold Jan 01 22:14:19 the-nexus kernel: pci 0000:06:01.0: [8086:15d3] type 01 class 0x060400 Jan 01 22:14:19 the-nexus kernel: pci 0000:06:01.0: enabling Extended Tags Jan 01 22:14:19 the-nexus kernel: pci 0000:06:01.0: supports D1 D2 Jan 01 22:14:19 the-nexus kernel: pci 0000:06:01.0: PME# supported from D0 D1 D2 D3hot D3cold Jan 01 22:14:19 the-nexus kernel: pci 0000:06:02.0: [8086:15d3] type 01 class 0x060400 Jan 01 22:14:19 the-nexus kernel: pci 0000:06:02.0: enabling Extended Tags Jan 01 22:14:19 the-nexus kernel: pci 0000:06:02.0: supports D1 D2 Jan 01 22:14:19 the-nexus kernel: pci 0000:06:02.0: PME# supported from D0 D1 D2 D3hot D3cold Jan 01 22:14:19 the-nexus kernel: pci 0000:06:04.0: [8086:15d3] type 01 class 0x060400 Jan 01 22:14:19 the-nexus kernel: pci 0000:06:04.0: enabling Extended Tags Jan 01 22:14:19 the-nexus kernel: pci 0000:06:04.0: supports D1 D2 Jan 01 22:14:19 the-nexus kernel: pci 0000:06:04.0: PME# supported from D0 D1 D2 D3hot D3cold Jan 01 22:14:19 the-nexus kernel: pci 0000:05:00.0: PCI bridge to [bus 06-52] Jan 01 22:14:19 the-nexus kernel: pci 0000:05:00.0: bridge window [mem 0xd0000000-0xe81fffff] Jan 01 22:14:19 the-nexus kernel: pci 0000:05:00.0: bridge window [mem 0x80000000-0xbfffffff 64bit pref] Jan 01 22:14:19 the-nexus kernel: pci 0000:07:00.0: [8086:15d2] type 00 class 0x088000 Jan 01 22:14:19 the-nexus kernel: pci 0000:07:00.0: reg 0x10: [mem 0xe8100000-0xe813ffff] Jan 01 22:14:19 the-nexus kernel: pci 0000:07:00.0: reg 0x14: [mem 0xe8140000-0xe8140fff] Jan 01 22:14:19 the-nexus kernel: pci 0000:07:00.0: enabling Extended Tags Jan 01 22:14:19 the-nexus kernel: pci 0000:07:00.0: supports D1 D2 Jan 01 22:14:19 the-nexus kernel: pci 0000:07:00.0: PME# supported from D0 D1 D2 D3hot D3cold Jan 01 22:14:19 the-nexus kernel: pci 0000:06:00.0: PCI bridge to [bus 07] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:00.0: bridge window [mem 0xe8100000-0xe81fffff] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:01.0: PCI bridge to [bus 08-2c] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:01.0: bridge window [mem 0xd0000000-0xdbffffff] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:01.0: bridge window [mem 0x80000000-0x9fffffff 64bit pref] Jan 01 22:14:19 the-nexus kernel: pci 0000:2d:00.0: [8086:15d4] type 00 class 0x0c0330 Jan 01 22:14:19 the-nexus kernel: pci 0000:2d:00.0: reg 0x10: [mem 0xdc000000-0xdc00ffff] Jan 01 22:14:19 the-nexus kernel: pci 0000:2d:00.0: enabling Extended Tags Jan 01 22:14:19 the-nexus kernel: pci 0000:2d:00.0: supports D1 D2 Jan 01 22:14:19 the-nexus kernel: pci 0000:2d:00.0: PME# supported from D0 D1 D2 D3hot D3cold Jan 01 22:14:19 the-nexus kernel: pci 0000:2d:00.0: 8.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x4 link at 0000:06:02.0 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link) Jan 01 22:14:19 the-nexus kernel: pci 0000:06:02.0: PCI bridge to [bus 2d] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:02.0: bridge window [mem 0xdc000000-0xdc0fffff] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:04.0: PCI bridge to [bus 2e-52] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:04.0: bridge window [mem 0xdc100000-0xe80fffff] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:04.0: bridge window [mem 0xa0000000-0xbfffffff 64bit pref] Jan 01 22:14:19 the-nexus kernel: ACPI: EC: interrupt unblocked Jan 01 22:14:19 the-nexus kernel: ACPI: EC: event unblocked Jan 01 22:14:19 the-nexus kernel: ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62 Jan 01 22:14:19 the-nexus kernel: ACPI: EC: GPE=0x16 Jan 01 22:14:19 the-nexus kernel: ACPI: \_SB_.PCI0.LPCB.EC__: Boot ECDT EC initialization complete Jan 01 22:14:19 the-nexus kernel: ACPI: \_SB_.PCI0.LPCB.EC__: EC: Used to handle transactions and events Jan 01 22:14:19 the-nexus kernel: iommu: Default domain type: Translated Jan 01 22:14:19 the-nexus kernel: iommu: DMA domain TLB invalidation policy: lazy mode Jan 01 22:14:19 the-nexus kernel: pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=mem,locks=none Jan 01 22:14:19 the-nexus kernel: pci 0000:00:02.0: vgaarb: bridge control possible Jan 01 22:14:19 the-nexus kernel: pci 0000:00:02.0: vgaarb: setting as boot device Jan 01 22:14:19 the-nexus kernel: vgaarb: loaded Jan 01 22:14:19 the-nexus kernel: SCSI subsystem initialized Jan 01 22:14:19 the-nexus kernel: libata version 3.00 loaded. Jan 01 22:14:19 the-nexus kernel: ACPI: bus type USB registered Jan 01 22:14:19 the-nexus kernel: usbcore: registered new interface driver usbfs Jan 01 22:14:19 the-nexus kernel: usbcore: registered new interface driver hub Jan 01 22:14:19 the-nexus kernel: usbcore: registered new device driver usb Jan 01 22:14:19 the-nexus kernel: pps_core: LinuxPPS API ver. 1 registered Jan 01 22:14:19 the-nexus kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti Jan 01 22:14:19 the-nexus kernel: PTP clock support registered Jan 01 22:14:19 the-nexus kernel: EDAC MC: Ver: 3.0.0 Jan 01 22:14:19 the-nexus kernel: Registered efivars operations Jan 01 22:14:19 the-nexus kernel: NetLabel: Initializing Jan 01 22:14:19 the-nexus kernel: NetLabel: domain hash size = 128 Jan 01 22:14:19 the-nexus kernel: NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO Jan 01 22:14:19 the-nexus kernel: NetLabel: unlabeled traffic allowed by default Jan 01 22:14:19 the-nexus kernel: PCI: Using ACPI for IRQ routing Jan 01 22:14:19 the-nexus kernel: PCI: pci_cache_line_size set to 64 bytes Jan 01 22:14:19 the-nexus kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff] Jan 01 22:14:19 the-nexus kernel: e820: reserve RAM buffer [mem 0x66e78000-0x67ffffff] Jan 01 22:14:19 the-nexus kernel: e820: reserve RAM buffer [mem 0x6b72a000-0x6bffffff] Jan 01 22:14:19 the-nexus kernel: e820: reserve RAM buffer [mem 0x6fd10000-0x6fffffff] Jan 01 22:14:19 the-nexus kernel: e820: reserve RAM buffer [mem 0x480800000-0x483ffffff] Jan 01 22:14:19 the-nexus kernel: clocksource: Switched to clocksource tsc-early Jan 01 22:14:19 the-nexus kernel: VFS: Disk quotas dquot_6.6.0 Jan 01 22:14:19 the-nexus kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Jan 01 22:14:19 the-nexus kernel: pnp: PnP ACPI init Jan 01 22:14:19 the-nexus kernel: system 00:00: [mem 0x40000000-0x403fffff] could not be reserved Jan 01 22:14:19 the-nexus kernel: system 00:01: [io 0x1800-0x18fe] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:01: [mem 0xfd000000-0xfd69ffff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:01: [mem 0xfd6b0000-0xfd6cffff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:01: [mem 0xfd6f0000-0xfdffffff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:01: [mem 0xfe000000-0xfe01ffff] could not be reserved Jan 01 22:14:19 the-nexus kernel: system 00:01: [mem 0xfe200000-0xfe7fffff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:01: [mem 0xff000000-0xffffffff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:02: [io 0xff00-0xfffe] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:03: [io 0x0680-0x069f] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:03: [io 0x164e-0x164f] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:04: [io 0x1854-0x1857] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:07: [io 0x1800-0x189f] could not be reserved Jan 01 22:14:19 the-nexus kernel: system 00:07: [io 0x0800-0x087f] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:07: [io 0x0880-0x08ff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:07: [io 0x0900-0x097f] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:07: [io 0x0980-0x09ff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:07: [io 0x0a00-0x0a7f] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:07: [io 0x0a80-0x0aff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:07: [io 0x0b00-0x0b7f] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:07: [io 0x0b80-0x0bff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:07: [io 0x15e0-0x15ef] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:07: [io 0x1600-0x167f] could not be reserved Jan 01 22:14:19 the-nexus kernel: system 00:07: [io 0x1640-0x165f] could not be reserved Jan 01 22:14:19 the-nexus kernel: system 00:07: [mem 0xf0000000-0xf7ffffff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:07: [mem 0xfed10000-0xfed13fff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:07: [mem 0xfed18000-0xfed18fff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:07: [mem 0xfed19000-0xfed19fff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:07: [mem 0xfeb00000-0xfebfffff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:07: [mem 0xfed20000-0xfed3ffff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:07: [mem 0xfed90000-0xfed93fff] could not be reserved Jan 01 22:14:19 the-nexus kernel: system 00:09: [mem 0xfed10000-0xfed17fff] could not be reserved Jan 01 22:14:19 the-nexus kernel: system 00:09: [mem 0xfed18000-0xfed18fff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:09: [mem 0xfed19000-0xfed19fff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:09: [mem 0xf0000000-0xf7ffffff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:09: [mem 0xfed20000-0xfed3ffff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:09: [mem 0xfed90000-0xfed93fff] could not be reserved Jan 01 22:14:19 the-nexus kernel: system 00:09: [mem 0xfed45000-0xfed8ffff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:09: [mem 0xfee00000-0xfeefffff] has been reserved Jan 01 22:14:19 the-nexus kernel: system 00:0a: [mem 0x00000000-0x0009ffff] could not be reserved Jan 01 22:14:19 the-nexus kernel: system 00:0a: [mem 0x000c0000-0x000c3fff] could not be reserved Jan 01 22:14:19 the-nexus kernel: system 00:0a: [mem 0x000c8000-0x000cbfff] could not be reserved Jan 01 22:14:19 the-nexus kernel: system 00:0a: [mem 0x000d0000-0x000d3fff] could not be reserved Jan 01 22:14:19 the-nexus kernel: system 00:0a: [mem 0x000d8000-0x000dbfff] could not be reserved Jan 01 22:14:19 the-nexus kernel: system 00:0a: [mem 0x000e0000-0x000e3fff] could not be reserved Jan 01 22:14:19 the-nexus kernel: system 00:0a: [mem 0x000e8000-0x000ebfff] could not be reserved Jan 01 22:14:19 the-nexus kernel: system 00:0a: [mem 0x000f0000-0x000fffff] could not be reserved Jan 01 22:14:19 the-nexus kernel: system 00:0a: [mem 0x00100000-0x7d7fffff] could not be reserved Jan 01 22:14:19 the-nexus kernel: system 00:0a: [mem 0xfec00000-0xfed3ffff] could not be reserved Jan 01 22:14:19 the-nexus kernel: system 00:0a: [mem 0xfed4c000-0xffffffff] could not be reserved Jan 01 22:14:19 the-nexus kernel: pnp: PnP ACPI: found 11 devices Jan 01 22:14:19 the-nexus kernel: clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns Jan 01 22:14:19 the-nexus kernel: NET: Registered PF_INET protocol family Jan 01 22:14:19 the-nexus kernel: IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear) Jan 01 22:14:19 the-nexus kernel: tcp_listen_portaddr_hash hash table entries: 8192 (order: 5, 131072 bytes, linear) Jan 01 22:14:19 the-nexus kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes, linear) Jan 01 22:14:19 the-nexus kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear) Jan 01 22:14:19 the-nexus kernel: TCP: Hash tables configured (established 131072 bind 65536) Jan 01 22:14:19 the-nexus kernel: MPTCP token hash table entries: 16384 (order: 6, 393216 bytes, linear) Jan 01 22:14:19 the-nexus kernel: UDP hash table entries: 8192 (order: 6, 262144 bytes, linear) Jan 01 22:14:19 the-nexus kernel: UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes, linear) Jan 01 22:14:19 the-nexus kernel: NET: Registered PF_UNIX/PF_LOCAL protocol family Jan 01 22:14:19 the-nexus kernel: NET: Registered PF_XDP protocol family Jan 01 22:14:19 the-nexus kernel: pci 0000:06:01.0: bridge window [io 0x1000-0x0fff] to [bus 08-2c] add_size 1000 Jan 01 22:14:19 the-nexus kernel: pci 0000:06:04.0: bridge window [io 0x1000-0x0fff] to [bus 2e-52] add_size 1000 Jan 01 22:14:19 the-nexus kernel: pci 0000:05:00.0: bridge window [io 0x1000-0x0fff] to [bus 06-52] add_size 2000 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.4: bridge window [io 0x1000-0x0fff] to [bus 05-52] add_size 3000 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.4: BAR 13: assigned [io 0x3000-0x5fff] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.0: PCI bridge to [bus 03] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.0: bridge window [mem 0xea100000-0xea1fffff] Jan 01 22:14:19 the-nexus kernel: pci 0000:05:00.0: BAR 13: assigned [io 0x3000-0x4fff] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:01.0: BAR 13: assigned [io 0x3000-0x3fff] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:04.0: BAR 13: assigned [io 0x4000-0x4fff] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:00.0: PCI bridge to [bus 07] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:00.0: bridge window [mem 0xe8100000-0xe81fffff] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:01.0: PCI bridge to [bus 08-2c] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:01.0: bridge window [io 0x3000-0x3fff] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:01.0: bridge window [mem 0xd0000000-0xdbffffff] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:01.0: bridge window [mem 0x80000000-0x9fffffff 64bit pref] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:02.0: PCI bridge to [bus 2d] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:02.0: bridge window [mem 0xdc000000-0xdc0fffff] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:04.0: PCI bridge to [bus 2e-52] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:04.0: bridge window [io 0x4000-0x4fff] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:04.0: bridge window [mem 0xdc100000-0xe80fffff] Jan 01 22:14:19 the-nexus kernel: pci 0000:06:04.0: bridge window [mem 0xa0000000-0xbfffffff 64bit pref] Jan 01 22:14:19 the-nexus kernel: pci 0000:05:00.0: PCI bridge to [bus 06-52] Jan 01 22:14:19 the-nexus kernel: pci 0000:05:00.0: bridge window [io 0x3000-0x4fff] Jan 01 22:14:19 the-nexus kernel: pci 0000:05:00.0: bridge window [mem 0xd0000000-0xe81fffff] Jan 01 22:14:19 the-nexus kernel: pci 0000:05:00.0: bridge window [mem 0x80000000-0xbfffffff 64bit pref] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.4: PCI bridge to [bus 05-52] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.4: bridge window [io 0x3000-0x5fff] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.4: bridge window [mem 0xd0000000-0xe81fffff] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.4: bridge window [mem 0x80000000-0xbfffffff 64bit pref] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:00: resource 7 [mem 0x7d800000-0xefffffff window] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:00: resource 8 [mem 0xfc800000-0xfe7fffff window] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:03: resource 1 [mem 0xea100000-0xea1fffff] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:05: resource 0 [io 0x3000-0x5fff] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:05: resource 1 [mem 0xd0000000-0xe81fffff] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:05: resource 2 [mem 0x80000000-0xbfffffff 64bit pref] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:06: resource 0 [io 0x3000-0x4fff] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:06: resource 1 [mem 0xd0000000-0xe81fffff] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:06: resource 2 [mem 0x80000000-0xbfffffff 64bit pref] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:07: resource 1 [mem 0xe8100000-0xe81fffff] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:08: resource 0 [io 0x3000-0x3fff] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:08: resource 1 [mem 0xd0000000-0xdbffffff] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:08: resource 2 [mem 0x80000000-0x9fffffff 64bit pref] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:2d: resource 1 [mem 0xdc000000-0xdc0fffff] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:2e: resource 0 [io 0x4000-0x4fff] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:2e: resource 1 [mem 0xdc100000-0xe80fffff] Jan 01 22:14:19 the-nexus kernel: pci_bus 0000:2e: resource 2 [mem 0xa0000000-0xbfffffff 64bit pref] Jan 01 22:14:19 the-nexus kernel: pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff] Jan 01 22:14:19 the-nexus kernel: PCI: CLS 128 bytes, default 64 Jan 01 22:14:19 the-nexus kernel: DMAR: Intel-IOMMU force enabled due to platform opt in Jan 01 22:14:19 the-nexus kernel: DMAR: No ATSR found Jan 01 22:14:19 the-nexus kernel: DMAR: No SATC found Jan 01 22:14:19 the-nexus kernel: DMAR: IOMMU feature fl1gp_support inconsistent Jan 01 22:14:19 the-nexus kernel: DMAR: IOMMU feature pgsel_inv inconsistent Jan 01 22:14:19 the-nexus kernel: DMAR: IOMMU feature nwfs inconsistent Jan 01 22:14:19 the-nexus kernel: DMAR: IOMMU feature pasid inconsistent Jan 01 22:14:19 the-nexus kernel: DMAR: IOMMU feature eafs inconsistent Jan 01 22:14:19 the-nexus kernel: DMAR: IOMMU feature prs inconsistent Jan 01 22:14:19 the-nexus kernel: DMAR: IOMMU feature nest inconsistent Jan 01 22:14:19 the-nexus kernel: DMAR: IOMMU feature mts inconsistent Jan 01 22:14:19 the-nexus kernel: DMAR: IOMMU feature sc_support inconsistent Jan 01 22:14:19 the-nexus kernel: DMAR: IOMMU feature dev_iotlb_support inconsistent Jan 01 22:14:19 the-nexus kernel: DMAR: dmar0: Using Queued invalidation Jan 01 22:14:19 the-nexus kernel: DMAR: dmar1: Using Queued invalidation Jan 01 22:14:19 the-nexus kernel: Trying to unpack rootfs image as initramfs... Jan 01 22:14:19 the-nexus kernel: pci 0000:00:00.0: Adding to iommu group 0 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:02.0: Adding to iommu group 1 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:04.0: Adding to iommu group 2 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:08.0: Adding to iommu group 3 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:12.0: Adding to iommu group 4 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:14.0: Adding to iommu group 5 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:14.2: Adding to iommu group 5 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:14.3: Adding to iommu group 6 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:15.0: Adding to iommu group 7 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:15.1: Adding to iommu group 7 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:16.0: Adding to iommu group 8 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.0: Adding to iommu group 9 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1d.4: Adding to iommu group 10 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1f.0: Adding to iommu group 11 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1f.3: Adding to iommu group 11 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1f.4: Adding to iommu group 11 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1f.5: Adding to iommu group 11 Jan 01 22:14:19 the-nexus kernel: pci 0000:00:1f.6: Adding to iommu group 11 Jan 01 22:14:19 the-nexus kernel: pci 0000:03:00.0: Adding to iommu group 12 Jan 01 22:14:19 the-nexus kernel: pci 0000:05:00.0: Adding to iommu group 13 Jan 01 22:14:19 the-nexus kernel: pci 0000:06:00.0: Adding to iommu group 14 Jan 01 22:14:19 the-nexus kernel: pci 0000:06:01.0: Adding to iommu group 15 Jan 01 22:14:19 the-nexus kernel: pci 0000:06:02.0: Adding to iommu group 16 Jan 01 22:14:19 the-nexus kernel: pci 0000:06:04.0: Adding to iommu group 17 Jan 01 22:14:19 the-nexus kernel: pci 0000:07:00.0: Adding to iommu group 14 Jan 01 22:14:19 the-nexus kernel: pci 0000:2d:00.0: Adding to iommu group 16 Jan 01 22:14:19 the-nexus kernel: DMAR: Intel(R) Virtualization Technology for Directed I/O Jan 01 22:14:19 the-nexus kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Jan 01 22:14:19 the-nexus kernel: software IO TLB: mapped [mem 0x00000000628f5000-0x00000000668f5000] (64MB) Jan 01 22:14:19 the-nexus kernel: platform rtc_cmos: registered platform RTC device (no PNP device found) Jan 01 22:14:19 the-nexus kernel: sgx: EPC section 0x70200000-0x75f7ffff Jan 01 22:14:19 the-nexus kernel: Initialise system trusted keyrings Jan 01 22:14:19 the-nexus kernel: Key type blacklist registered Jan 01 22:14:19 the-nexus kernel: workingset: timestamp_bits=41 max_order=22 bucket_order=0 Jan 01 22:14:19 the-nexus kernel: zbud: loaded Jan 01 22:14:19 the-nexus kernel: Key type asymmetric registered Jan 01 22:14:19 the-nexus kernel: Asymmetric key parser 'x509' registered Jan 01 22:14:19 the-nexus kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 242) Jan 01 22:14:19 the-nexus kernel: io scheduler mq-deadline registered Jan 01 22:14:19 the-nexus kernel: io scheduler kyber registered Jan 01 22:14:19 the-nexus kernel: io scheduler bfq registered Jan 01 22:14:19 the-nexus kernel: pcieport 0000:00:1d.0: PME: Signaling with IRQ 122 Jan 01 22:14:19 the-nexus kernel: pcieport 0000:00:1d.4: PME: Signaling with IRQ 123 Jan 01 22:14:19 the-nexus kernel: pcieport 0000:00:1d.4: pciehp: Slot #12 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ IbPresDis- LLActRep+ Jan 01 22:14:19 the-nexus kernel: pcieport 0000:06:01.0: pciehp: Slot #1 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ IbPresDis- LLActRep+ Jan 01 22:14:19 the-nexus kernel: pcieport 0000:06:04.0: pciehp: Slot #4 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ IbPresDis- LLActRep+ Jan 01 22:14:19 the-nexus kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Jan 01 22:14:19 the-nexus kernel: ACPI: AC: AC Adapter [AC] (on-line) Jan 01 22:14:19 the-nexus kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 Jan 01 22:14:19 the-nexus kernel: ACPI: button: Sleep Button [SLPB] Jan 01 22:14:19 the-nexus kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 Jan 01 22:14:19 the-nexus kernel: ACPI: button: Lid Switch [LID] Jan 01 22:14:19 the-nexus kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 Jan 01 22:14:19 the-nexus kernel: ACPI: button: Power Button [PWRF] Jan 01 22:14:19 the-nexus kernel: smpboot: Estimated ratio of average max frequency by base frequency (times 1024): 2104 Jan 01 22:14:19 the-nexus kernel: thermal LNXTHERM:00: registered as thermal_zone0 Jan 01 22:14:19 the-nexus kernel: ACPI: thermal: Thermal Zone [THM0] (48 C) Jan 01 22:14:19 the-nexus kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled Jan 01 22:14:19 the-nexus kernel: hpet_acpi_add: no address or irqs in _CRS Jan 01 22:14:19 the-nexus kernel: Non-volatile memory driver v1.3 Jan 01 22:14:19 the-nexus kernel: Linux agpgart interface v0.103 Jan 01 22:14:19 the-nexus kernel: AMD-Vi: AMD IOMMUv2 functionality not available on this system - This is not a bug. Jan 01 22:14:19 the-nexus kernel: nvme nvme0: pci function 0000:03:00.0 Jan 01 22:14:19 the-nexus kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Jan 01 22:14:19 the-nexus kernel: ehci-pci: EHCI PCI platform driver Jan 01 22:14:19 the-nexus kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver Jan 01 22:14:19 the-nexus kernel: ohci-pci: OHCI PCI platform driver Jan 01 22:14:19 the-nexus kernel: uhci_hcd: USB Universal Host Controller Interface driver Jan 01 22:14:19 the-nexus kernel: usbcore: registered new interface driver usbserial_generic Jan 01 22:14:19 the-nexus kernel: usbserial: USB Serial support registered for generic Jan 01 22:14:19 the-nexus kernel: rtc_cmos rtc_cmos: RTC can wake from S4 Jan 01 22:14:19 the-nexus kernel: rtc_cmos rtc_cmos: registered as rtc0 Jan 01 22:14:19 the-nexus kernel: rtc_cmos rtc_cmos: setting system clock to 2022-01-02T03:14:17 UTC (1641093257) Jan 01 22:14:19 the-nexus kernel: rtc_cmos rtc_cmos: alarms up to one month, y3k, 114 bytes nvram Jan 01 22:14:19 the-nexus kernel: intel_pstate: Intel P-state driver initializing Jan 01 22:14:19 the-nexus kernel: intel_pstate: HWP enabled Jan 01 22:14:19 the-nexus kernel: ledtrig-cpu: registered to indicate activity on CPUs Jan 01 22:14:19 the-nexus kernel: efifb: probing for efifb Jan 01 22:14:19 the-nexus kernel: efifb: framebuffer at 0xc0000000, using 8128k, total 8128k Jan 01 22:14:19 the-nexus kernel: efifb: mode is 1920x1080x32, linelength=7680, pages=1 Jan 01 22:14:19 the-nexus kernel: efifb: scrolling: redraw Jan 01 22:14:19 the-nexus kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 Jan 01 22:14:19 the-nexus kernel: fbcon: Deferring console take-over Jan 01 22:14:19 the-nexus kernel: fb0: EFI VGA frame buffer device Jan 01 22:14:19 the-nexus kernel: hid: raw HID events driver (C) Jiri Kosina Jan 01 22:14:19 the-nexus kernel: intel_pmc_core INT33A1:00: initialized Jan 01 22:14:19 the-nexus kernel: drop_monitor: Initializing network drop monitor service Jan 01 22:14:19 the-nexus kernel: Initializing XFRM netlink socket Jan 01 22:14:19 the-nexus kernel: NET: Registered PF_INET6 protocol family Jan 01 22:14:19 the-nexus kernel: ACPI: battery: Slot [BAT0] (battery present) Jan 01 22:14:19 the-nexus kernel: Freeing initrd memory: 13552K Jan 01 22:14:19 the-nexus kernel: Segment Routing with IPv6 Jan 01 22:14:19 the-nexus kernel: RPL Segment Routing with IPv6 Jan 01 22:14:19 the-nexus kernel: In-situ OAM (IOAM) with IPv6 Jan 01 22:14:19 the-nexus kernel: NET: Registered PF_PACKET protocol family Jan 01 22:14:19 the-nexus kernel: microcode: sig=0x806ec, pf=0x80, revision=0xea Jan 01 22:14:19 the-nexus kernel: microcode: Microcode Update Driver: v2.2. Jan 01 22:14:19 the-nexus kernel: IPI shorthand broadcast: enabled Jan 01 22:14:19 the-nexus kernel: sched_clock: Marking stable (770595298, 9174892)->(799880679, -20110489) Jan 01 22:14:19 the-nexus kernel: registered taskstats version 1 Jan 01 22:14:19 the-nexus kernel: Loading compiled-in X.509 certificates Jan 01 22:14:19 the-nexus kernel: Loaded X.509 cert 'Build time autogenerated kernel key: d2094633047b7eebd2131812d6ef772775a49f35' Jan 01 22:14:19 the-nexus kernel: zswap: loaded using pool lz4/z3fold Jan 01 22:14:19 the-nexus kernel: Key type ._fscrypt registered Jan 01 22:14:19 the-nexus kernel: Key type .fscrypt registered Jan 01 22:14:19 the-nexus kernel: Key type fscrypt-provisioning registered Jan 01 22:14:19 the-nexus kernel: PM: Magic number: 6:600:208 Jan 01 22:14:19 the-nexus kernel: vc vcsa: hash matches Jan 01 22:14:19 the-nexus kernel: pci 0000:00:08.0: hash matches Jan 01 22:14:19 the-nexus kernel: RAS: Correctable Errors collector initialized. Jan 01 22:14:19 the-nexus kernel: nvme nvme0: failed to set APST feature (2) Jan 01 22:14:19 the-nexus kernel: nvme nvme0: allocated 64 MiB host memory buffer. Jan 01 22:14:19 the-nexus kernel: nvme nvme0: 8/0/0 default/read/poll queues Jan 01 22:14:19 the-nexus kernel: nvme0n1: p1 p2 Jan 01 22:14:19 the-nexus kernel: Freeing unused decrypted memory: 2036K Jan 01 22:14:19 the-nexus kernel: Freeing unused kernel image (initmem) memory: 1864K Jan 01 22:14:19 the-nexus kernel: Write protecting the kernel read-only data: 28672k Jan 01 22:14:19 the-nexus kernel: Freeing unused kernel image (text/rodata gap) memory: 2036K Jan 01 22:14:19 the-nexus kernel: Freeing unused kernel image (rodata/data gap) memory: 1496K Jan 01 22:14:19 the-nexus kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found. Jan 01 22:14:19 the-nexus kernel: rodata_test: all tests were successful Jan 01 22:14:19 the-nexus kernel: Run /init as init process Jan 01 22:14:19 the-nexus kernel: with arguments: Jan 01 22:14:19 the-nexus kernel: /init Jan 01 22:14:19 the-nexus kernel: with environment: Jan 01 22:14:19 the-nexus kernel: HOME=/ Jan 01 22:14:19 the-nexus kernel: TERM=linux Jan 01 22:14:19 the-nexus kernel: BOOT_IMAGE=/boot/vmlinuz-linux Jan 01 22:14:19 the-nexus kernel: nvme_load=YES Jan 01 22:14:19 the-nexus kernel: fbcon: Taking over console Jan 01 22:14:19 the-nexus kernel: Console: switching to colour frame buffer device 240x67 Jan 01 22:14:19 the-nexus kernel: i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12 Jan 01 22:14:19 the-nexus kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 Jan 01 22:14:19 the-nexus kernel: serio: i8042 AUX port at 0x60,0x64 irq 12 Jan 01 22:14:19 the-nexus kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller Jan 01 22:14:19 the-nexus kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1 Jan 01 22:14:19 the-nexus kernel: xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x110 quirks 0x0000000000009810 Jan 01 22:14:19 the-nexus kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15 Jan 01 22:14:19 the-nexus kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Jan 01 22:14:19 the-nexus kernel: usb usb1: Product: xHCI Host Controller Jan 01 22:14:19 the-nexus kernel: usb usb1: Manufacturer: Linux 5.15.12-arch1-1 xhci-hcd Jan 01 22:14:19 the-nexus kernel: usb usb1: SerialNumber: 0000:00:14.0 Jan 01 22:14:19 the-nexus kernel: hub 1-0:1.0: USB hub found Jan 01 22:14:19 the-nexus kernel: hub 1-0:1.0: 12 ports detected Jan 01 22:14:19 the-nexus kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller Jan 01 22:14:19 the-nexus kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2 Jan 01 22:14:19 the-nexus kernel: xhci_hcd 0000:00:14.0: Host supports USB 3.1 Enhanced SuperSpeed Jan 01 22:14:19 the-nexus kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.15 Jan 01 22:14:19 the-nexus kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Jan 01 22:14:19 the-nexus kernel: usb usb2: Product: xHCI Host Controller Jan 01 22:14:19 the-nexus kernel: usb usb2: Manufacturer: Linux 5.15.12-arch1-1 xhci-hcd Jan 01 22:14:19 the-nexus kernel: usb usb2: SerialNumber: 0000:00:14.0 Jan 01 22:14:19 the-nexus kernel: hub 2-0:1.0: USB hub found Jan 01 22:14:19 the-nexus kernel: hub 2-0:1.0: 6 ports detected Jan 01 22:14:19 the-nexus kernel: usb: port power management may be unreliable Jan 01 22:14:19 the-nexus kernel: xhci_hcd 0000:2d:00.0: xHCI Host Controller Jan 01 22:14:19 the-nexus kernel: xhci_hcd 0000:2d:00.0: new USB bus registered, assigned bus number 3 Jan 01 22:14:19 the-nexus kernel: xhci_hcd 0000:2d:00.0: hcc params 0x200077c1 hci version 0x110 quirks 0x0000000200009810 Jan 01 22:14:19 the-nexus kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15 Jan 01 22:14:19 the-nexus kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Jan 01 22:14:19 the-nexus kernel: usb usb3: Product: xHCI Host Controller Jan 01 22:14:19 the-nexus kernel: usb usb3: Manufacturer: Linux 5.15.12-arch1-1 xhci-hcd Jan 01 22:14:19 the-nexus kernel: usb usb3: SerialNumber: 0000:2d:00.0 Jan 01 22:14:19 the-nexus kernel: hub 3-0:1.0: USB hub found Jan 01 22:14:19 the-nexus kernel: hub 3-0:1.0: 2 ports detected Jan 01 22:14:19 the-nexus kernel: xhci_hcd 0000:2d:00.0: xHCI Host Controller Jan 01 22:14:19 the-nexus kernel: xhci_hcd 0000:2d:00.0: new USB bus registered, assigned bus number 4 Jan 01 22:14:19 the-nexus kernel: xhci_hcd 0000:2d:00.0: Host supports USB 3.1 Enhanced SuperSpeed Jan 01 22:14:19 the-nexus kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.15 Jan 01 22:14:19 the-nexus kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Jan 01 22:14:19 the-nexus kernel: usb usb4: Product: xHCI Host Controller Jan 01 22:14:19 the-nexus kernel: usb usb4: Manufacturer: Linux 5.15.12-arch1-1 xhci-hcd Jan 01 22:14:19 the-nexus kernel: usb usb4: SerialNumber: 0000:2d:00.0 Jan 01 22:14:19 the-nexus kernel: hub 4-0:1.0: USB hub found Jan 01 22:14:19 the-nexus kernel: hub 4-0:1.0: 2 ports detected Jan 01 22:14:19 the-nexus kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 Jan 01 22:14:19 the-nexus kernel: random: fast init done Jan 01 22:14:19 the-nexus kernel: usb 1-8: new high-speed USB device number 2 using xhci_hcd Jan 01 22:14:19 the-nexus kernel: usb 1-8: New USB device found, idVendor=04f2, idProduct=b67d, bcdDevice= 4.06 Jan 01 22:14:19 the-nexus kernel: usb 1-8: New USB device strings: Mfr=2, Product=1, SerialNumber=0 Jan 01 22:14:19 the-nexus kernel: usb 1-8: Product: Integrated Camera Jan 01 22:14:19 the-nexus kernel: usb 1-8: Manufacturer: Sonix Technology Co., Ltd. Jan 01 22:14:19 the-nexus kernel: usb 1-9: new full-speed USB device number 3 using xhci_hcd Jan 01 22:14:19 the-nexus kernel: tsc: Refined TSC clocksource calibration: 1799.998 MHz Jan 01 22:14:19 the-nexus kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x19f227af07c, max_idle_ns: 440795246167 ns Jan 01 22:14:19 the-nexus kernel: clocksource: Switched to clocksource tsc Jan 01 22:14:19 the-nexus kernel: usb 1-9: New USB device found, idVendor=06cb, idProduct=00bd, bcdDevice= 0.00 Jan 01 22:14:19 the-nexus kernel: usb 1-9: New USB device strings: Mfr=0, Product=0, SerialNumber=1 Jan 01 22:14:19 the-nexus kernel: usb 1-9: SerialNumber: 5a4d0cd87336 Jan 01 22:14:19 the-nexus kernel: EXT4-fs (nvme0n1p2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none. Jan 01 22:14:19 the-nexus kernel: usb 1-10: new full-speed USB device number 4 using xhci_hcd Jan 01 22:14:19 the-nexus systemd[1]: systemd 250-4-arch running in system mode (+PAM +AUDIT -SELINUX -APPARMOR -IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK +XKBCOMMON +UTMP -SYSVINIT default-hierarchy=unified) Jan 01 22:14:19 the-nexus kernel: usb 1-10: New USB device found, idVendor=8087, idProduct=0aaa, bcdDevice= 0.02 Jan 01 22:14:19 the-nexus kernel: usb 1-10: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Jan 01 22:14:19 the-nexus systemd[1]: Detected architecture x86-64. Jan 01 22:14:19 the-nexus systemd[1]: Hostname set to . Jan 01 22:14:19 the-nexus kernel: random: lvmconfig: uninitialized urandom read (4 bytes read) Jan 01 22:14:19 the-nexus systemd[1]: Queued start job for default target Graphical Interface. Jan 01 22:14:19 the-nexus systemd[1]: Created slice Slice /system/getty. Jan 01 22:14:19 the-nexus systemd[1]: Created slice Slice /system/modprobe. Jan 01 22:14:19 the-nexus systemd[1]: Created slice Slice /system/systemd-fsck. Jan 01 22:14:19 the-nexus systemd[1]: Created slice User and Session Slice. Jan 01 22:14:19 the-nexus systemd[1]: Started Dispatch Password Requests to Console Directory Watch. Jan 01 22:14:19 the-nexus systemd[1]: Started Forward Password Requests to Wall Directory Watch. Jan 01 22:14:19 the-nexus systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. Jan 01 22:14:19 the-nexus systemd[1]: Reached target Local Encrypted Volumes. Jan 01 22:14:19 the-nexus systemd[1]: Reached target Login Prompts. Jan 01 22:14:19 the-nexus systemd[1]: Reached target Local Integrity Protected Volumes. Jan 01 22:14:19 the-nexus systemd[1]: Reached target Path Units. Jan 01 22:14:19 the-nexus systemd[1]: Reached target Remote File Systems. Jan 01 22:14:19 the-nexus systemd[1]: Reached target Slice Units. Jan 01 22:14:19 the-nexus systemd[1]: Reached target Swaps. Jan 01 22:14:19 the-nexus systemd[1]: Reached target Local Verity Protected Volumes. Jan 01 22:14:19 the-nexus systemd[1]: Listening on Device-mapper event daemon FIFOs. Jan 01 22:14:19 the-nexus systemd[1]: Listening on LVM2 poll daemon socket. Jan 01 22:14:19 the-nexus systemd[1]: Listening on Process Core Dump Socket. Jan 01 22:14:19 the-nexus systemd[1]: Listening on Journal Audit Socket. Jan 01 22:14:19 the-nexus systemd[1]: Listening on Journal Socket (/dev/log). Jan 01 22:14:19 the-nexus systemd[1]: Listening on Journal Socket. Jan 01 22:14:19 the-nexus systemd[1]: Listening on udev Control Socket. Jan 01 22:14:19 the-nexus systemd[1]: Listening on udev Kernel Socket. Jan 01 22:14:19 the-nexus systemd[1]: Mounting Huge Pages File System... Jan 01 22:14:19 the-nexus systemd[1]: Mounting POSIX Message Queue File System... Jan 01 22:14:19 the-nexus systemd[1]: Mounting Kernel Debug File System... Jan 01 22:14:19 the-nexus systemd[1]: Mounting Kernel Trace File System... Jan 01 22:14:19 the-nexus systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway. Jan 01 22:14:19 the-nexus systemd[1]: Mounting Temporary Directory /tmp... Jan 01 22:14:19 the-nexus systemd[1]: Starting Create List of Static Device Nodes... Jan 01 22:14:19 the-nexus systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling... Jan 01 22:14:19 the-nexus systemd[1]: Starting Load Kernel Module configfs... Jan 01 22:14:19 the-nexus systemd[1]: Starting Load Kernel Module drm... Jan 01 22:14:19 the-nexus systemd[1]: Starting Load Kernel Module fuse... Jan 01 22:14:19 the-nexus systemd[1]: File System Check on Root Device was skipped because of a failed condition check (ConditionPathIsReadWrite=!/). Jan 01 22:14:19 the-nexus kernel: random: lvm: uninitialized urandom read (4 bytes read) Jan 01 22:14:19 the-nexus systemd[1]: Starting Journal Service... Jan 01 22:14:19 the-nexus systemd[1]: Starting Load Kernel Modules... Jan 01 22:14:19 the-nexus systemd[1]: Starting Remount Root and Kernel File Systems... Jan 01 22:14:19 the-nexus systemd[1]: Repartition Root Disk was skipped because all trigger condition checks failed. Jan 01 22:14:19 the-nexus systemd[1]: Starting Coldplug All udev Devices... Jan 01 22:14:19 the-nexus systemd[1]: Mounted Huge Pages File System. Jan 01 22:14:19 the-nexus systemd[1]: Mounted POSIX Message Queue File System. Jan 01 22:14:19 the-nexus systemd[1]: Mounted Kernel Debug File System. Jan 01 22:14:19 the-nexus systemd[1]: Mounted Kernel Trace File System. Jan 01 22:14:19 the-nexus systemd[1]: Mounted Temporary Directory /tmp. Jan 01 22:14:19 the-nexus systemd[1]: Finished Create List of Static Device Nodes. Jan 01 22:14:19 the-nexus systemd[1]: modprobe@configfs.service: Deactivated successfully. Jan 01 22:14:19 the-nexus systemd[1]: Finished Load Kernel Module configfs. Jan 01 22:14:19 the-nexus systemd[1]: modprobe@drm.service: Deactivated successfully. Jan 01 22:14:19 the-nexus systemd[1]: Finished Load Kernel Module drm. Jan 01 22:14:19 the-nexus systemd[1]: Mounting Kernel Configuration File System... Jan 01 22:14:19 the-nexus kernel: EXT4-fs (nvme0n1p2): re-mounted. Opts: (null). Quota mode: none. Jan 01 22:14:19 the-nexus systemd[1]: Finished Remount Root and Kernel File Systems. Jan 01 22:14:19 the-nexus systemd[1]: Mounted Kernel Configuration File System. Jan 01 22:14:19 the-nexus systemd[1]: First Boot Wizard was skipped because of a failed condition check (ConditionFirstBoot=yes). Jan 01 22:14:19 the-nexus systemd[1]: Rebuild Hardware Database was skipped because of a failed condition check (ConditionNeedsUpdate=/etc). Jan 01 22:14:19 the-nexus kernel: fuse: init (API version 7.34) Jan 01 22:14:19 the-nexus systemd[1]: Starting Load/Save Random Seed... Jan 01 22:14:19 the-nexus systemd[1]: Create System Users was skipped because of a failed condition check (ConditionNeedsUpdate=/etc). Jan 01 22:14:19 the-nexus systemd[1]: Starting Create Static Device Nodes in /dev... Jan 01 22:14:19 the-nexus systemd[1]: modprobe@fuse.service: Deactivated successfully. Jan 01 22:14:19 the-nexus systemd[1]: Finished Load Kernel Module fuse. Jan 01 22:14:19 the-nexus kernel: audit: type=1130 audit(1641093259.000:2): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@fuse comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:19 the-nexus kernel: audit: type=1131 audit(1641093259.000:3): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@fuse comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:19 the-nexus systemd[1]: Mounting FUSE Control File System... Jan 01 22:14:19 the-nexus systemd[1]: Mounted FUSE Control File System. Jan 01 22:14:19 the-nexus kernel: IPMI message handler: version 39.2 Jan 01 22:14:19 the-nexus kernel: ipmi device interface Jan 01 22:14:19 the-nexus systemd[1]: Finished Create Static Device Nodes in /dev. Jan 01 22:14:19 the-nexus kernel: audit: type=1130 audit(1641093259.017:4): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:19 the-nexus kernel: ipmi_si: IPMI System Interface driver Jan 01 22:14:19 the-nexus kernel: ipmi_si: Unable to find any System Interface(s) Jan 01 22:14:19 the-nexus kernel: audit: type=1334 audit(1641093259.020:5): prog-id=14 op=LOAD Jan 01 22:14:19 the-nexus kernel: audit: type=1334 audit(1641093259.020:6): prog-id=15 op=LOAD Jan 01 22:14:19 the-nexus kernel: audit: type=1334 audit(1641093259.020:7): prog-id=16 op=LOAD Jan 01 22:14:19 the-nexus systemd[1]: Starting Rule-based Manager for Device Events and Files... Jan 01 22:14:19 the-nexus systemd[1]: Finished Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. Jan 01 22:14:19 the-nexus kernel: audit: type=1130 audit(1641093259.023:8): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:19 the-nexus systemd[1]: Reached target Preparation for Local File Systems. Jan 01 22:14:19 the-nexus systemd[1]: Virtual Machine and Container Storage (Compatibility) was skipped because of a failed condition check (ConditionPathExists=/var/lib/machines.raw). Jan 01 22:14:19 the-nexus systemd[1]: Mounting Mount unit for bare, revision 5... Jan 01 22:14:19 the-nexus systemd[1]: Mounting Mount unit for core18, revision 2253... Jan 01 22:14:19 the-nexus systemd[1]: Mounting Mount unit for discord, revision 130... Jan 01 22:14:19 the-nexus systemd-journald[277]: Journal started Jan 01 22:14:19 the-nexus systemd-journald[277]: Runtime Journal (/run/log/journal/e97781e181ab43d29f2117e6a7be514f) is 8.0M, max 784.1M, 776.1M free. Jan 01 22:14:19 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@fuse comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:19 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@fuse comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:19 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:19 the-nexus audit: BPF prog-id=14 op=LOAD Jan 01 22:14:19 the-nexus audit: BPF prog-id=15 op=LOAD Jan 01 22:14:19 the-nexus audit: BPF prog-id=16 op=LOAD Jan 01 22:14:19 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:19 the-nexus systemd-modules-load[278]: Inserted module 'crypto_user' Jan 01 22:14:19 the-nexus systemd-random-seed[283]: Kernel entropy pool is not initialized yet, waiting until it is. Jan 01 22:14:19 the-nexus systemd-modules-load[278]: Failed to insert module 'ipmi_si': No such device Jan 01 22:14:19 the-nexus kernel: loop: module loaded Jan 01 22:14:19 the-nexus kernel: loop2: detected capacity change from 0 to 113640 Jan 01 22:14:19 the-nexus kernel: loop1: detected capacity change from 0 to 8 Jan 01 22:14:19 the-nexus kernel: loop0: detected capacity change from 0 to 169760 Jan 01 22:14:19 the-nexus systemd-modules-load[278]: Inserted module 'pkcs8_key_parser' Jan 01 22:14:19 the-nexus kernel: Asymmetric key parser 'pkcs8' registered Jan 01 22:14:19 the-nexus kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher Jan 01 22:14:19 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973008 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:14:19 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16387213: lblock 0: comm systemd: error -5 reading directory block Jan 01 22:14:19 the-nexus systemd[1]: var-lib-snapd-snap-discord-131.mount: Failed to check directory /var/lib/snapd/snap/discord/131: Input/output error Jan 01 22:14:19 the-nexus systemd[1]: Mounting Mount unit for discord, revision 131... Jan 01 22:14:19 the-nexus systemd[1]: Mounting Mount unit for gnome-3-28-1804, revision 161... Jan 01 22:14:19 the-nexus systemd[1]: Mounting Mount unit for gtk-common-themes, revision 1519... Jan 01 22:14:19 the-nexus kernel: loop3: detected capacity change from 0 to 169760 Jan 01 22:14:19 the-nexus systemd[1]: Mounting Mount unit for snapd, revision 14295... Jan 01 22:14:19 the-nexus kernel: loop4: detected capacity change from 0 to 337424 Jan 01 22:14:19 the-nexus kernel: loop5: detected capacity change from 0 to 133552 Jan 01 22:14:19 the-nexus systemd[1]: Mounting Mount unit for spotify, revision 56... Jan 01 22:14:19 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:19 the-nexus kernel: loop6: detected capacity change from 0 to 88616 Jan 01 22:14:19 the-nexus kernel: loop7: detected capacity change from 0 to 342664 Jan 01 22:14:19 the-nexus systemd[1]: Started Journal Service. Jan 01 22:14:19 the-nexus kernel: audit: type=1130 audit(1641093259.680:9): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:19 the-nexus systemd[1]: Finished Load Kernel Modules. Jan 01 22:14:19 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:19 the-nexus systemd[1]: Finished Coldplug All udev Devices. Jan 01 22:14:19 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udev-trigger comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:19 the-nexus kernel: audit: type=1130 audit(1641093259.683:10): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:19 the-nexus systemd[1]: Mounted Mount unit for bare, revision 5. Jan 01 22:14:19 the-nexus systemd[1]: Mounted Mount unit for core18, revision 2253. Jan 01 22:14:19 the-nexus systemd[1]: Mounted Mount unit for discord, revision 130. Jan 01 22:14:19 the-nexus systemd[1]: Mounted Mount unit for discord, revision 131. Jan 01 22:14:19 the-nexus systemd[1]: Mounted Mount unit for gnome-3-28-1804, revision 161. Jan 01 22:14:19 the-nexus systemd[1]: Mounted Mount unit for gtk-common-themes, revision 1519. Jan 01 22:14:19 the-nexus systemd[1]: Mounted Mount unit for snapd, revision 14295. Jan 01 22:14:19 the-nexus systemd[1]: Mounted Mount unit for spotify, revision 56. Jan 01 22:14:19 the-nexus systemd[1]: Starting Flush Journal to Persistent Storage... Jan 01 22:14:19 the-nexus systemd[1]: Starting Apply Kernel Variables... Jan 01 22:14:19 the-nexus systemd-journald[277]: Time spent on flushing to /var/log/journal/e97781e181ab43d29f2117e6a7be514f is 18.555ms for 944 entries. Jan 01 22:14:19 the-nexus systemd-journald[277]: System Journal (/var/log/journal/e97781e181ab43d29f2117e6a7be514f) is 412.7M, max 4.0G, 3.5G free. Jan 01 22:14:19 the-nexus systemd-journald[277]: Received client request to flush runtime journal. Jan 01 22:14:19 the-nexus systemd-journald[277]: File /var/log/journal/e97781e181ab43d29f2117e6a7be514f/system.journal corrupted or uncleanly shut down, renaming and replacing. Jan 01 22:14:19 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:19 the-nexus systemd[1]: Finished Apply Kernel Variables. Jan 01 22:14:19 the-nexus systemd[1]: Finished Flush Journal to Persistent Storage. Jan 01 22:14:19 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-flush comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:19 the-nexus systemd[1]: Started Rule-based Manager for Device Events and Files. Jan 01 22:14:19 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:19 the-nexus kernel: intel_pch_thermal 0000:00:12.0: enabling device (0000 -> 0002) Jan 01 22:14:19 the-nexus kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Jan 01 22:14:19 the-nexus kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Jan 01 22:14:19 the-nexus kernel: acpi PNP0C14:04: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Jan 01 22:14:19 the-nexus kernel: acpi PNP0C14:05: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Jan 01 22:14:19 the-nexus kernel: proc_thermal 0000:00:04.0: enabling device (0000 -> 0002) Jan 01 22:14:19 the-nexus kernel: intel_rapl_common: Found RAPL domain package Jan 01 22:14:19 the-nexus kernel: intel_rapl_common: Found RAPL domain dram Jan 01 22:14:19 the-nexus mtp-probe[343]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9" Jan 01 22:14:19 the-nexus mtp-probe[344]: checking bus 1, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-8" Jan 01 22:14:19 the-nexus mtp-probe[344]: bus: 1, device: 2 was not an MTP device Jan 01 22:14:19 the-nexus mtp-probe[343]: bus: 1, device: 3 was not an MTP device Jan 01 22:14:20 the-nexus kernel: mc: Linux media interface: v0.10 Jan 01 22:14:20 the-nexus kernel: thinkpad_acpi: ThinkPad ACPI Extras v0.26 Jan 01 22:14:20 the-nexus kernel: thinkpad_acpi: http://ibm-acpi.sf.net/ Jan 01 22:14:20 the-nexus kernel: thinkpad_acpi: ThinkPad BIOS N2HET64W (1.47 ), EC N2HHT42W Jan 01 22:14:20 the-nexus kernel: thinkpad_acpi: Lenovo ThinkPad X1 Carbon 7th, model 20QDS3B400 Jan 01 22:14:20 the-nexus kernel: thinkpad_acpi: radio switch found; radios are enabled Jan 01 22:14:20 the-nexus kernel: thinkpad_acpi: Tablet mode switch found (type: GMMS), currently in laptop mode Jan 01 22:14:20 the-nexus kernel: thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver Jan 01 22:14:20 the-nexus kernel: thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... Jan 01 22:14:20 the-nexus kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked Jan 01 22:14:20 the-nexus kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database Jan 01 22:14:20 the-nexus kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Jan 01 22:14:20 the-nexus kernel: thinkpad_acpi: battery 1 registered (start 0, stop 100) Jan 01 22:14:20 the-nexus kernel: ACPI: battery: new extension: ThinkPad Battery Extension Jan 01 22:14:20 the-nexus kernel: input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input5 Jan 01 22:14:20 the-nexus kernel: Bluetooth: Core ver 2.22 Jan 01 22:14:20 the-nexus kernel: NET: Registered PF_BLUETOOTH protocol family Jan 01 22:14:20 the-nexus kernel: Bluetooth: HCI device and connection manager initialized Jan 01 22:14:20 the-nexus kernel: Bluetooth: HCI socket layer initialized Jan 01 22:14:20 the-nexus kernel: Bluetooth: L2CAP socket layer initialized Jan 01 22:14:20 the-nexus kernel: Bluetooth: SCO socket layer initialized Jan 01 22:14:20 the-nexus kernel: videodev: Linux video capture interface: v2.00 Jan 01 22:14:20 the-nexus kernel: intel-lpss 0000:00:15.0: enabling device (0000 -> 0002) Jan 01 22:14:20 the-nexus kernel: i915 0000:00:02.0: enabling device (0006 -> 0007) Jan 01 22:14:20 the-nexus kernel: idma64 idma64.0: Found Intel integrated DMA 64-bit Jan 01 22:14:20 the-nexus kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access Jan 01 22:14:20 the-nexus kernel: checking generic (c0000000 7f0000) vs hw (e9000000 1000000) Jan 01 22:14:20 the-nexus kernel: checking generic (c0000000 7f0000) vs hw (c0000000 10000000) Jan 01 22:14:20 the-nexus kernel: fb0: switching to i915 from EFI VGA Jan 01 22:14:20 the-nexus kernel: Console: switching to colour dummy device 80x25 Jan 01 22:14:20 the-nexus kernel: i915 0000:00:02.0: vgaarb: deactivate vga console Jan 01 22:14:20 the-nexus kernel: Intel(R) Wireless WiFi driver for Linux Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: enabling device (0000 -> 0002) Jan 01 22:14:20 the-nexus kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=mem Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 0 Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 1 Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 2 Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 3 Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 4 Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 6 Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 8 Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 9 Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 10 Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 11 Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 15 Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 16 Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 18 Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 19 Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 20 Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 21 Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: WRT: Overriding region id 28 Jan 01 22:14:20 the-nexus kernel: tpm_tis STM7364:00: 2.0 TPM (device-id 0x0, rev-id 78) Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: loaded firmware version 46.6b541b68.0 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm Jan 01 22:14:20 the-nexus kernel: mei_me 0000:00:16.0: enabling device (0000 -> 0002) Jan 01 22:14:20 the-nexus kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Jan 01 22:14:20 the-nexus kernel: idma64 idma64.1: Found Intel integrated DMA 64-bit Jan 01 22:14:20 the-nexus kernel: ACPI: bus type thunderbolt registered Jan 01 22:14:20 the-nexus kernel: usbcore: registered new interface driver btusb Jan 01 22:14:20 the-nexus kernel: Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015 Jan 01 22:14:20 the-nexus kernel: Bluetooth: hci0: Device revision is 2 Jan 01 22:14:20 the-nexus kernel: Bluetooth: hci0: Secure boot is enabled Jan 01 22:14:20 the-nexus kernel: Bluetooth: hci0: OTP lock is enabled Jan 01 22:14:20 the-nexus kernel: Bluetooth: hci0: API lock is enabled Jan 01 22:14:20 the-nexus kernel: Bluetooth: hci0: Debug lock is disabled Jan 01 22:14:20 the-nexus kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 Jan 01 22:14:20 the-nexus kernel: Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi Jan 01 22:14:20 the-nexus kernel: i915 0000:00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it Jan 01 22:14:20 the-nexus kernel: i915 0000:00:02.0: [drm] [ENCODER:118:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it Jan 01 22:14:20 the-nexus kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0 Jan 01 22:14:20 the-nexus kernel: ACPI: video: Video Device [GFX0] (multi-head: yes rom: no post: no) Jan 01 22:14:20 the-nexus kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6 Jan 01 22:14:20 the-nexus systemd[1]: Found device ADATA SWORDFISH NO_LABEL. Jan 01 22:14:20 the-nexus systemd[1]: Starting File System Check on /dev/disk/by-uuid/FDD7-0CF2... Jan 01 22:14:20 the-nexus kernel: fbcon: i915drmfb (fb0) is primary device Jan 01 22:14:20 the-nexus kernel: Console: switching to colour frame buffer device 240x67 Jan 01 22:14:20 the-nexus systemd-fsck[372]: fsck.fat 4.2 (2021-01-31) Jan 01 22:14:20 the-nexus systemd-fsck[372]: There are differences between boot sector and its backup. Jan 01 22:14:20 the-nexus systemd-fsck[372]: This is mostly harmless. Differences: (offset:original/backup) Jan 01 22:14:20 the-nexus systemd-fsck[372]: 65:01/00 Jan 01 22:14:20 the-nexus systemd-fsck[372]: Not automatically fixing this. Jan 01 22:14:20 the-nexus systemd-fsck[372]: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt. Jan 01 22:14:20 the-nexus systemd-fsck[372]: Automatically removing dirty bit. Jan 01 22:14:20 the-nexus systemd-fsck[372]: *** Filesystem was changed *** Jan 01 22:14:20 the-nexus systemd-fsck[372]: Writing changes. Jan 01 22:14:20 the-nexus systemd-fsck[372]: /dev/nvme0n1p1: 10 files, 6205/76646 clusters Jan 01 22:14:20 the-nexus systemd[1]: Finished File System Check on /dev/disk/by-uuid/FDD7-0CF2. Jan 01 22:14:20 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-FDD7\x2d0CF2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus systemd[1]: Mounting /boot/efi... Jan 01 22:14:20 the-nexus kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device Jan 01 22:14:20 the-nexus kernel: usb 1-8: Found UVC 1.00 device Integrated Camera (04f2:b67d) Jan 01 22:14:20 the-nexus kernel: input: Integrated Camera: Integrated C as /devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.0/input/input7 Jan 01 22:14:20 the-nexus kernel: usbcore: registered new interface driver uvcvideo Jan 01 22:14:20 the-nexus kernel: i801_smbus 0000:00:1f.4: enabling device (0000 -> 0003) Jan 01 22:14:20 the-nexus kernel: i801_smbus 0000:00:1f.4: SPD Write Disable is set Jan 01 22:14:20 the-nexus kernel: i801_smbus 0000:00:1f.4: SMBus using PCI interrupt Jan 01 22:14:20 the-nexus kernel: i2c i2c-9: 2/2 memory slots populated (from DMI) Jan 01 22:14:20 the-nexus kernel: input: SYNA8004:00 06CB:CD8B Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-5/i2c-SYNA8004:00/0018:06CB:CD8B.0001/input/input8 Jan 01 22:14:20 the-nexus kernel: input: SYNA8004:00 06CB:CD8B Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-5/i2c-SYNA8004:00/0018:06CB:CD8B.0001/input/input9 Jan 01 22:14:20 the-nexus kernel: hid-generic 0018:06CB:CD8B.0001: input,hidraw0: I2C HID v1.00 Mouse [SYNA8004:00 06CB:CD8B] on i2c-SYNA8004:00 Jan 01 22:14:20 the-nexus kernel: e1000e: Intel(R) PRO/1000 Network Driver Jan 01 22:14:20 the-nexus kernel: e1000e: Copyright(c) 1999 - 2015 Intel Corporation. Jan 01 22:14:20 the-nexus kernel: input: PC Speaker as /devices/platform/pcspkr/input/input11 Jan 01 22:14:20 the-nexus kernel: e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode Jan 01 22:14:20 the-nexus kernel: resource sanity check: requesting [mem 0xfed10000-0xfed15fff], which spans more than pnp 00:07 [mem 0xfed10000-0xfed13fff] Jan 01 22:14:20 the-nexus kernel: caller snb_uncore_imc_init_box+0x82/0xd0 [intel_uncore] mapping multiple BARs Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: Detected Intel(R) Wireless-AC 9560 160MHz, REV=0x318 Jan 01 22:14:20 the-nexus kernel: thermal thermal_zone6: failed to read out thermal zone (-61) Jan 01 22:14:20 the-nexus systemd[1]: Mounted /boot/efi. Jan 01 22:14:20 the-nexus systemd[1]: Reached target Local File Systems. Jan 01 22:14:20 the-nexus systemd[1]: Rebuild Dynamic Linker Cache was skipped because all trigger condition checks failed. Jan 01 22:14:20 the-nexus systemd[1]: Set Up Additional Binary Formats was skipped because all trigger condition checks failed. Jan 01 22:14:20 the-nexus systemd[1]: Starting Create Volatile Files and Directories... Jan 01 22:14:20 the-nexus systemd[1]: Finished Load/Save Random Seed. Jan 01 22:14:20 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes). Jan 01 22:14:20 the-nexus systemd[1]: Store a System Token in an EFI Variable was skipped because of a failed condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderFeatures-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f). Jan 01 22:14:20 the-nexus systemd[1]: Commit a transient machine-id on disk was skipped because of a failed condition check (ConditionPathIsMountPoint=/etc/machine-id). Jan 01 22:14:20 the-nexus kernel: random: crng init done Jan 01 22:14:20 the-nexus kernel: iwlwifi 0000:00:14.3: base HW address: cc:d9:ac:19:44:b1 Jan 01 22:14:20 the-nexus kernel: RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer Jan 01 22:14:20 the-nexus kernel: RAPL PMU: hw unit of domain pp0-core 2^-14 Joules Jan 01 22:14:20 the-nexus kernel: RAPL PMU: hw unit of domain package 2^-14 Joules Jan 01 22:14:20 the-nexus kernel: RAPL PMU: hw unit of domain dram 2^-14 Joules Jan 01 22:14:20 the-nexus kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules Jan 01 22:14:20 the-nexus kernel: RAPL PMU: hw unit of domain psys 2^-14 Joules Jan 01 22:14:20 the-nexus systemd[1]: Finished Create Volatile Files and Directories. Jan 01 22:14:20 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus systemd[1]: Rebuild Journal Catalog was skipped because of a failed condition check (ConditionNeedsUpdate=/var). Jan 01 22:14:20 the-nexus audit: BPF prog-id=17 op=LOAD Jan 01 22:14:20 the-nexus systemd[1]: Starting Network Time Synchronization... Jan 01 22:14:20 the-nexus systemd[1]: Update is Completed was skipped because all trigger condition checks failed. Jan 01 22:14:20 the-nexus systemd[1]: Starting Record System Boot/Shutdown in UTMP... Jan 01 22:14:20 the-nexus audit[385]: SYSTEM_BOOT pid=385 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus kernel: cryptd: max_cpu_qlen set to 1000 Jan 01 22:14:20 the-nexus systemd[1]: Finished Record System Boot/Shutdown in UTMP. Jan 01 22:14:20 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus systemd[1]: Started Network Time Synchronization. Jan 01 22:14:20 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timesyncd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus systemd[1]: Reached target System Initialization. Jan 01 22:14:20 the-nexus systemd[1]: Started Daily Cleanup of Temporary Directories. Jan 01 22:14:20 the-nexus systemd[1]: Reached target System Time Set. Jan 01 22:14:20 the-nexus systemd[1]: Started Discard unused blocks once a week. Jan 01 22:14:20 the-nexus systemd[1]: Started Daily rotation of log files. Jan 01 22:14:20 the-nexus systemd[1]: Started Daily man-db regeneration. Jan 01 22:14:20 the-nexus systemd[1]: Started Daily verification of password and group files. Jan 01 22:14:20 the-nexus systemd[1]: Started Daily locate database update. Jan 01 22:14:20 the-nexus systemd[1]: Reached target Timer Units. Jan 01 22:14:20 the-nexus systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket. Jan 01 22:14:20 the-nexus systemd[1]: Listening on D-Bus System Message Bus Socket. Jan 01 22:14:20 the-nexus systemd[1]: Starting Socket activation for snappy daemon... Jan 01 22:14:20 the-nexus systemd[1]: Listening on Socket activation for snappy daemon. Jan 01 22:14:20 the-nexus systemd[1]: Reached target Socket Units. Jan 01 22:14:20 the-nexus systemd[1]: Reached target Basic System. Jan 01 22:14:20 the-nexus systemd[1]: Starting Avahi mDNS/DNS-SD Stack... Jan 01 22:14:20 the-nexus systemd[1]: Started D-Bus System Message Bus. Jan 01 22:14:20 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus systemd[1]: Starting Network Manager... Jan 01 22:14:20 the-nexus audit: BPF prog-id=18 op=LOAD Jan 01 22:14:20 the-nexus audit: BPF prog-id=19 op=LOAD Jan 01 22:14:20 the-nexus audit: BPF prog-id=20 op=LOAD Jan 01 22:14:20 the-nexus systemd[1]: Starting User Login Management... Jan 01 22:14:20 the-nexus avahi-daemon[394]: Found user 'avahi' (UID 975) and group 'avahi' (GID 975). Jan 01 22:14:20 the-nexus avahi-daemon[394]: Successfully dropped root privileges. Jan 01 22:14:20 the-nexus avahi-daemon[394]: avahi-daemon 0.8 starting up. Jan 01 22:14:20 the-nexus systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. Jan 01 22:14:20 the-nexus systemd[1]: Starting Load/Save RF Kill Switch Status... Jan 01 22:14:20 the-nexus kernel: AVX2 version of gcm_enc/dec engaged. Jan 01 22:14:20 the-nexus kernel: AES CTR mode by8 optimization enabled Jan 01 22:14:20 the-nexus kernel: ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' Jan 01 22:14:20 the-nexus kernel: intel_rapl_common: Found RAPL domain package Jan 01 22:14:20 the-nexus kernel: intel_rapl_common: Found RAPL domain core Jan 01 22:14:20 the-nexus kernel: intel_rapl_common: Found RAPL domain uncore Jan 01 22:14:20 the-nexus kernel: intel_rapl_common: Found RAPL domain dram Jan 01 22:14:20 the-nexus kernel: intel_rapl_common: Found RAPL domain psys Jan 01 22:14:20 the-nexus systemd[1]: Created slice Slice /system/systemd-backlight. Jan 01 22:14:20 the-nexus systemd[1]: Starting Load/Save Screen Backlight Brightness of leds:tpacpi::kbd_backlight... Jan 01 22:14:20 the-nexus systemd-udevd[336]: video4linux: Process '/usr/lib/snapd/snap-device-helper add snap_discord_discord /class/video4linux 0:0' failed with exit code 1. Jan 01 22:14:20 the-nexus systemd-udevd[316]: cfg80211: Process '/usr/bin/set-wireless-regdom' failed with exit code 1. Jan 01 22:14:20 the-nexus systemd[1]: Started Avahi mDNS/DNS-SD Stack. Jan 01 22:14:20 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=avahi-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus avahi-daemon[394]: Successfully called chroot(). Jan 01 22:14:20 the-nexus avahi-daemon[394]: Successfully dropped remaining capabilities. Jan 01 22:14:20 the-nexus avahi-daemon[394]: No service file found in /etc/avahi/services. Jan 01 22:14:20 the-nexus avahi-daemon[394]: Joining mDNS multicast group on interface lo.IPv6 with address ::1. Jan 01 22:14:20 the-nexus avahi-daemon[394]: New relevant interface lo.IPv6 for mDNS. Jan 01 22:14:20 the-nexus avahi-daemon[394]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1. Jan 01 22:14:20 the-nexus avahi-daemon[394]: New relevant interface lo.IPv4 for mDNS. Jan 01 22:14:20 the-nexus avahi-daemon[394]: Network interface enumeration completed. Jan 01 22:14:20 the-nexus avahi-daemon[394]: Registering new address record for ::1 on lo.*. Jan 01 22:14:20 the-nexus avahi-daemon[394]: Registering new address record for 127.0.0.1 on lo.IPv4. Jan 01 22:14:20 the-nexus systemd-logind[397]: Watching system buttons on /dev/input/event2 (Power Button) Jan 01 22:14:20 the-nexus systemd[1]: Reached target Bluetooth Support. Jan 01 22:14:20 the-nexus systemd[1]: Finished Load/Save Screen Backlight Brightness of leds:tpacpi::kbd_backlight. Jan 01 22:14:20 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-backlight@leds:tpacpi::kbd_backlight comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus systemd-logind[397]: Watching system buttons on /dev/input/event1 (Lid Switch) Jan 01 22:14:20 the-nexus systemd-logind[397]: Watching system buttons on /dev/input/event0 (Sleep Button) Jan 01 22:14:20 the-nexus systemd-logind[397]: Watching system buttons on /dev/input/event3 (AT Translated Set 2 keyboard) Jan 01 22:14:20 the-nexus systemd-logind[397]: New seat seat0. Jan 01 22:14:20 the-nexus systemd[1]: Started User Login Management. Jan 01 22:14:20 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus kernel: i801_smbus 0000:00:1f.4: Transaction timeout Jan 01 22:14:20 the-nexus kernel: i801_smbus 0000:00:1f.4: Failed terminating the transaction Jan 01 22:14:20 the-nexus kernel: i801_smbus 0000:00:1f.4: SMBus is busy, can't use it! Jan 01 22:14:20 the-nexus systemd[1]: Starting Thunderbolt system service... Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.5219] NetworkManager (version 1.32.12-2) is starting... (for the first time) Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.5220] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf) Jan 01 22:14:20 the-nexus systemd[1]: Started Network Manager. Jan 01 22:14:20 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus systemd[1]: Reached target Network. Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.5271] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager" Jan 01 22:14:20 the-nexus systemd[1]: Starting Permit User Sessions... Jan 01 22:14:20 the-nexus systemd[1]: Finished Permit User Sessions. Jan 01 22:14:20 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-user-sessions comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus systemd[1]: Reached target Multi-User System. Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.5340] manager[0x557fa1170000]: monitoring kernel firmware directory '/lib/firmware'. Jan 01 22:14:20 the-nexus systemd[1]: Starting Light Display Manager... Jan 01 22:14:20 the-nexus kernel: snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 Jan 01 22:14:20 the-nexus kernel: e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): registered PHC clock Jan 01 22:14:20 the-nexus kernel: snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver Jan 01 22:14:20 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.4' (uid=0 pid=396 comm="/usr/bin/NetworkManager --no-daemon ") Jan 01 22:14:20 the-nexus audit: BPF prog-id=21 op=LOAD Jan 01 22:14:20 the-nexus audit: BPF prog-id=22 op=LOAD Jan 01 22:14:20 the-nexus audit: BPF prog-id=23 op=LOAD Jan 01 22:14:20 the-nexus systemd[1]: Starting Hostname Service... Jan 01 22:14:20 the-nexus systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:intel_backlight... Jan 01 22:14:20 the-nexus boltd[425]: bolt 0.9.1 starting up. Jan 01 22:14:20 the-nexus boltd[425]: manager: initializing store Jan 01 22:14:20 the-nexus boltd[425]: store: located at: /var/lib/boltd Jan 01 22:14:20 the-nexus boltd[425]: config: loading user config Jan 01 22:14:20 the-nexus boltd[425]: bouncer: initializing polkit Jan 01 22:14:20 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.5' (uid=0 pid=425 comm="/usr/lib/boltd ") Jan 01 22:14:20 the-nexus systemd[1]: Starting Authorization Manager... Jan 01 22:14:20 the-nexus kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) Jan 01 22:14:20 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' requested by ':1.6' (uid=0 pid=437 comm="/usr/bin/lightdm ") Jan 01 22:14:20 the-nexus systemd[1]: Finished Load/Save Screen Backlight Brightness of backlight:intel_backlight. Jan 01 22:14:20 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-backlight@backlight:intel_backlight comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus systemd[1]: Started Light Display Manager. Jan 01 22:14:20 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus systemd[1]: Reached target Graphical Interface. Jan 01 22:14:20 the-nexus systemd[1]: Reached target User and Group Name Lookups. Jan 01 22:14:20 the-nexus systemd[1]: Starting Accounts Service... Jan 01 22:14:20 the-nexus systemd[1]: Started Load/Save RF Kill Switch Status. Jan 01 22:14:20 the-nexus systemd-udevd[323]: Using default interface naming scheme 'v250'. Jan 01 22:14:20 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus kernel: iTCO_vendor_support: vendor-support=0 Jan 01 22:14:20 the-nexus polkitd[452]: Started polkitd version 0.120 Jan 01 22:14:20 the-nexus systemd-logind[397]: Watching system buttons on /dev/input/event4 (ThinkPad Extra Buttons) Jan 01 22:14:20 the-nexus kernel: input: SYNA8004:00 06CB:CD8B Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-5/i2c-SYNA8004:00/0018:06CB:CD8B.0001/input/input13 Jan 01 22:14:20 the-nexus kernel: input: SYNA8004:00 06CB:CD8B Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-5/i2c-SYNA8004:00/0018:06CB:CD8B.0001/input/input14 Jan 01 22:14:20 the-nexus kernel: hid-multitouch 0018:06CB:CD8B.0001: input,hidraw0: I2C HID v1.00 Mouse [SYNA8004:00 06CB:CD8B] on i2c-SYNA8004:00 Jan 01 22:14:20 the-nexus dbus-daemon[395]: [system] Successfully activated service 'org.freedesktop.hostname1' Jan 01 22:14:20 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus systemd[1]: Started Hostname Service. Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6144] hostname: hostname: using hostnamed Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6144] hostname: hostname changed from (none) to "the-nexus" Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6147] dns-mgr[0x557fa1140250]: init: dns=default,systemd-resolved rc-manager=symlink Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6154] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:14.3/ieee80211/phy0/rfkill2) (driver iwlwifi) Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6156] manager[0x557fa1170000]: rfkill: Wi-Fi hardware radio set enabled Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6156] manager[0x557fa1170000]: rfkill: WWAN hardware radio set enabled Jan 01 22:14:20 the-nexus kernel: e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 00:2b:67:db:72:e4 Jan 01 22:14:20 the-nexus kernel: e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection Jan 01 22:14:20 the-nexus kernel: e1000e 0000:00:1f.6 eth0: MAC: 13, PHY: 12, PBA No: FFFFFF-0FF Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6257] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.32.12-2/libnm-device-plugin-adsl.so) Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6363] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.32.12-2/libnm-device-plugin-team.so) Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6368] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.32.12-2/libnm-device-plugin-ovs.so) Jan 01 22:14:20 the-nexus kernel: iTCO_wdt iTCO_wdt: Found a Intel PCH TCO device (Version=6, TCOBASE=0x0400) Jan 01 22:14:20 the-nexus kernel: iTCO_wdt iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) Jan 01 22:14:20 the-nexus polkitd[452]: Loading rules from directory /etc/polkit-1/rules.d Jan 01 22:14:20 the-nexus systemd-udevd[338]: Using default interface naming scheme 'v250'. Jan 01 22:14:20 the-nexus polkitd[452]: Loading rules from directory /usr/share/polkit-1/rules.d Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6461] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.32.12-2/libnm-device-plugin-wwan.so) Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6467] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.32.12-2/libnm-device-plugin-wifi.so) Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6482] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.32.12-2/libnm-device-plugin-bluetooth.so) Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6486] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6486] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6487] manager: Networking is enabled by state file Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6490] dhcp-init: Using DHCP client 'internal' Jan 01 22:14:20 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=396 comm="/usr/bin/NetworkManager --no-daemon ") Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6494] settings: Loaded settings plugin: keyfile (internal) Jan 01 22:14:20 the-nexus kernel: mousedev: PS/2 mouse device common for all mice Jan 01 22:14:20 the-nexus polkitd[452]: Finished loading, compiling and executing 7 rules Jan 01 22:14:20 the-nexus dbus-daemon[395]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' Jan 01 22:14:20 the-nexus polkitd[452]: Acquired the name org.freedesktop.PolicyKit1 on the system bus Jan 01 22:14:20 the-nexus boltd[425]: watchdog: enabled [pulse: 90s] Jan 01 22:14:20 the-nexus boltd[425]: udev: initializing udev Jan 01 22:14:20 the-nexus accounts-daemon[459]: started daemon version 0.6.55 Jan 01 22:14:20 the-nexus dbus-daemon[395]: [system] Successfully activated service 'org.freedesktop.Accounts' Jan 01 22:14:20 the-nexus boltd[425]: store: loading domains Jan 01 22:14:20 the-nexus boltd[425]: [c9030000-0080-domain? ] store: loading domain Jan 01 22:14:20 the-nexus boltd[425]: journal: opened for 'c9030000-0080'; size: 0 bytes Jan 01 22:14:20 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=polkit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=accounts-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus boltd[425]: [c9030000-0080-domain? ] domain: registered (bootacl: 16/16) Jan 01 22:14:20 the-nexus boltd[425]: store: loading devices Jan 01 22:14:20 the-nexus boltd[425]: [c9030000-0080 ] store: loading device Jan 01 22:14:20 the-nexus boltd[425]: global 'generation' set to '3' Jan 01 22:14:20 the-nexus boltd[425]: power: state located at: /run/boltd/power Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6848] device (lo): carrier: link connected Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6851] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1) Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6915] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2) Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6920] device (wlan0): driver supports Access Point (AP) mode Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.6926] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3) Jan 01 22:14:20 the-nexus systemd[1]: Starting Network Manager Script Dispatcher Service... Jan 01 22:14:20 the-nexus systemd[1]: Started Authorization Manager. Jan 01 22:14:20 the-nexus systemd[1]: Started Accounts Service. Jan 01 22:14:20 the-nexus kernel: e1000e 0000:00:1f.6 enp0s31f6: renamed from eth0 Jan 01 22:14:20 the-nexus boltd[425]: power: force power support: yes Jan 01 22:14:20 the-nexus boltd[425]: udev: found 1 domain Jan 01 22:14:20 the-nexus boltd[425]: udev: enumerating devices Jan 01 22:14:20 the-nexus boltd[425]: probing: adding /sys/devices/pci0000:00/0000:00:1d.4/0000:05:00.0 to roots Jan 01 22:14:20 the-nexus dbus-daemon[395]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 01 22:14:20 the-nexus systemd[1]: Started Network Manager Script Dispatcher Service. Jan 01 22:14:20 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus boltd[425]: [c9030000-0080-domain0 ] bootacl: synchronizing journal Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.7159] ovsdb: Could not connect: No such file or directory Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.7159] ovsdb: disconnected from ovsdb Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.7164] device (eth0): interface index 3 renamed iface from 'eth0' to 'enp0s31f6' Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.7167] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 01 22:14:20 the-nexus boltd[425]: security level set to 'none' Jan 01 22:14:20 the-nexus boltd[425]: [c9030000-0080-domain0 ] connected: as domain0 [none] (/sys/devices/pci0000:00/0000:00:1d.4/0000:05:00.0/0000:06:00.0/0000:07:00.0/domain0) Jan 01 22:14:20 the-nexus boltd[425]: [c9030000-0080-ThinkPad X1 Yoga 4th / Carb] parent is (null)... Jan 01 22:14:20 the-nexus boltd[425]: [c9030000-0080-ThinkPad X1 Yoga 4th / Carb] connected: authorized (/sys/devices/pci0000:00/0000:00:1d.4/0000:05:00.0/0000:06:00.0/0000:07:00.0/domain0/0-0) Jan 01 22:14:20 the-nexus boltd[425]: [c9030000-0080-domain0 ] dbus: exported domain at /org/freedesktop/bolt/domains/c9030000_0080_7f18_a3b2_ea3d20421101 Jan 01 22:14:20 the-nexus boltd[425]: [c9030000-0080-ThinkPad X1 Yoga 4th / Carb] dbus: exported device at /org/freedesktop/bolt/devices/c9030000_0080... Jan 01 22:14:20 the-nexus systemd[1]: Started Thunderbolt system service. Jan 01 22:14:20 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bolt comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:20 the-nexus systemd[1]: Startup finished in 6.850s (firmware) + 2.175s (loader) + 1.980s (kernel) + 2.030s (userspace) = 13.036s. Jan 01 22:14:20 the-nexus kernel: psmouse serio1: trackpoint: Elan TrackPoint firmware: 0x47, buttons: 3/3 Jan 01 22:14:20 the-nexus kernel: input: TPPS/2 Elan TrackPoint as /devices/platform/i8042/serio1/input/input12 Jan 01 22:14:20 the-nexus kernel: intel_tcc_cooling: Programmable TCC Offset detected Jan 01 22:14:20 the-nexus kernel: snd_soc_skl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 Jan 01 22:14:20 the-nexus kernel: snd_soc_skl 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver Jan 01 22:14:20 the-nexus systemd-udevd[339]: Using default interface naming scheme 'v250'. Jan 01 22:14:20 the-nexus NetworkManager[396]: [1641093260.9317] device (wlan0): set-hw-addr: set MAC address to EA:D7:8B:52:01:28 (scanning) Jan 01 22:14:21 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' requested by ':1.4' (uid=0 pid=396 comm="/usr/bin/NetworkManager --no-daemon ") Jan 01 22:14:21 the-nexus NetworkManager[396]: [1641093261.1299] device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 01 22:14:21 the-nexus systemd[1]: Starting WPA supplicant... Jan 01 22:14:21 the-nexus kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 Jan 01 22:14:21 the-nexus kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver Jan 01 22:14:21 the-nexus kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 Jan 01 22:14:21 the-nexus kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Jan 01 22:14:21 the-nexus dbus-daemon[395]: [system] Successfully activated service 'fi.w1.wpa_supplicant1' Jan 01 22:14:21 the-nexus systemd[1]: Started WPA supplicant. Jan 01 22:14:21 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=wpa_supplicant comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:21 the-nexus wpa_supplicant[519]: Successfully initialized wpa_supplicant Jan 01 22:14:21 the-nexus kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: use msi interrupt mode Jan 01 22:14:21 the-nexus kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: hda codecs found, mask 5 Jan 01 22:14:21 the-nexus kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now Jan 01 22:14:21 the-nexus kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: DMICs detected in NHLT tables: 4 Jan 01 22:14:21 the-nexus kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware info: version 2:0:0-b678a Jan 01 22:14:21 the-nexus kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware: ABI 3:20:0 Kernel ABI 3:18:0 Jan 01 22:14:21 the-nexus kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: warn: FW ABI is more recent than kernel Jan 01 22:14:21 the-nexus kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: unknown sof_ext_man header type 3 size 0x30 Jan 01 22:14:21 the-nexus avahi-daemon[394]: Server startup complete. Host name is the-nexus.local. Local service cookie is 2329376736. Jan 01 22:14:21 the-nexus kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware info: version 2:0:0-b678a Jan 01 22:14:21 the-nexus kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware: ABI 3:20:0 Kernel ABI 3:18:0 Jan 01 22:14:21 the-nexus kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: warn: FW ABI is more recent than kernel Jan 01 22:14:21 the-nexus NetworkManager[396]: [1641093261.3222] settings: (enp0s31f6): created default wired connection 'Wired connection 1' Jan 01 22:14:21 the-nexus kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: Topology: ABI 3:20:0 Kernel ABI 3:18:0 Jan 01 22:14:21 the-nexus kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: warn: topology ABI is more recent than kernel Jan 01 22:14:21 the-nexus audit[525]: CRED_ACQ pid=525 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_env,pam_permit acct="lightdm" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success' Jan 01 22:14:21 the-nexus lightdm[525]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=970) by (uid=0) Jan 01 22:14:21 the-nexus systemd[1]: Created slice User Slice of UID 970. Jan 01 22:14:21 the-nexus systemd[1]: Starting User Runtime Directory /run/user/970... Jan 01 22:14:21 the-nexus systemd-logind[397]: New session c1 of user lightdm. Jan 01 22:14:21 the-nexus kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: ASoC: Parent card not yet available, widget card binding deferred Jan 01 22:14:21 the-nexus systemd[1]: Finished User Runtime Directory /run/user/970. Jan 01 22:14:21 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@970 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:21 the-nexus systemd[1]: Starting User Manager for UID 970... Jan 01 22:14:21 the-nexus NetworkManager[396]: [1641093261.3693] device (wlan0): supplicant interface state: internal-starting -> disconnected Jan 01 22:14:21 the-nexus NetworkManager[396]: [1641093261.3694] Wi-Fi P2P device controlled by interface wlan0 created Jan 01 22:14:21 the-nexus NetworkManager[396]: [1641093261.3696] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4) Jan 01 22:14:21 the-nexus NetworkManager[396]: [1641093261.3698] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 01 22:14:21 the-nexus NetworkManager[396]: [1641093261.3703] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Jan 01 22:14:21 the-nexus NetworkManager[396]: [1641093261.3709] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') Jan 01 22:14:21 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.16' (uid=0 pid=531 comm="(systemd) ") Jan 01 22:14:21 the-nexus dbus-daemon[395]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found. Jan 01 22:14:21 the-nexus systemd[531]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found. Jan 01 22:14:21 the-nexus audit[531]: USER_ACCT pid=531 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="lightdm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:21 the-nexus audit[531]: CRED_ACQ pid=531 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="lightdm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Jan 01 22:14:21 the-nexus audit[531]: SYSCALL arch=c000003e syscall=1 success=yes exit=3 a0=9 a1=7ffc889a1590 a2=3 a3=3ca items=0 ppid=1 pid=531 auid=970 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1 comm="(systemd)" exe="/usr/lib/systemd/systemd" key=(null) Jan 01 22:14:21 the-nexus audit: PROCTITLE proctitle="(systemd)" Jan 01 22:14:21 the-nexus systemd[531]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[lightdm] ruser=[] rhost=[] Jan 01 22:14:21 the-nexus systemd[531]: pam_unix(systemd-user:session): session opened for user lightdm(uid=970) by (uid=0) Jan 01 22:14:21 the-nexus systemd[531]: pam_env(systemd-user:session): deprecated reading of user environment enabled Jan 01 22:14:21 the-nexus audit[531]: USER_START pid=531 uid=0 auid=970 ses=1 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_systemd_home,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="lightdm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:21 the-nexus kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC285: line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker Jan 01 22:14:21 the-nexus kernel: snd_hda_codec_realtek ehdaudio0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) Jan 01 22:14:21 the-nexus kernel: snd_hda_codec_realtek ehdaudio0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0) Jan 01 22:14:21 the-nexus kernel: snd_hda_codec_realtek ehdaudio0D0: mono: mono_out=0x0 Jan 01 22:14:21 the-nexus kernel: snd_hda_codec_realtek ehdaudio0D0: inputs: Jan 01 22:14:21 the-nexus kernel: snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 Jan 01 22:14:21 the-nexus audit: BPF prog-id=24 op=LOAD Jan 01 22:14:21 the-nexus audit[531]: SYSCALL arch=c000003e syscall=321 success=yes exit=8 a0=5 a1=7ffd9982fac0 a2=78 a3=7ffd9982fac0 items=0 ppid=1 pid=531 auid=970 uid=970 gid=970 euid=970 suid=970 fsuid=970 egid=970 sgid=970 fsgid=970 tty=(none) ses=1 comm="systemd" exe="/usr/lib/systemd/systemd" key=(null) Jan 01 22:14:21 the-nexus audit: PROCTITLE proctitle="(systemd)" Jan 01 22:14:21 the-nexus audit: BPF prog-id=0 op=UNLOAD Jan 01 22:14:21 the-nexus systemd[531]: Queued start job for default target Main User Target. Jan 01 22:14:21 the-nexus systemd[531]: Created slice User Application Slice. Jan 01 22:14:21 the-nexus systemd[531]: Reached target Paths. Jan 01 22:14:21 the-nexus systemd[531]: Reached target Timers. Jan 01 22:14:21 the-nexus systemd[531]: Starting D-Bus User Message Bus Socket... Jan 01 22:14:21 the-nexus systemd[531]: Listening on GnuPG network certificate management daemon. Jan 01 22:14:21 the-nexus systemd[531]: Listening on GCR ssh-agent wrapper. Jan 01 22:14:21 the-nexus systemd[531]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). Jan 01 22:14:21 the-nexus systemd[531]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Jan 01 22:14:21 the-nexus systemd[531]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Jan 01 22:14:21 the-nexus systemd[531]: Listening on GnuPG cryptographic agent and passphrase cache. Jan 01 22:14:21 the-nexus systemd[531]: Listening on p11-kit server. Jan 01 22:14:21 the-nexus systemd[531]: Listening on PipeWire PulseAudio. Jan 01 22:14:21 the-nexus systemd[531]: Listening on PipeWire Multimedia System Socket. Jan 01 22:14:21 the-nexus systemd[531]: Listening on D-Bus User Message Bus Socket. Jan 01 22:14:21 the-nexus systemd[531]: Reached target Sockets. Jan 01 22:14:21 the-nexus systemd[531]: Reached target Basic System. Jan 01 22:14:21 the-nexus systemd[1]: Started User Manager for UID 970. Jan 01 22:14:21 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@970 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:21 the-nexus systemd[1]: Started Session c1 of User lightdm. Jan 01 22:14:21 the-nexus systemd[531]: Starting Update XDG user dir configuration... Jan 01 22:14:21 the-nexus systemd[531]: Finished Update XDG user dir configuration. Jan 01 22:14:21 the-nexus systemd[531]: Reached target Main User Target. Jan 01 22:14:21 the-nexus systemd[531]: Startup finished in 113ms. Jan 01 22:14:21 the-nexus audit[525]: USER_START pid=525 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_unix,pam_systemd acct="lightdm" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success' Jan 01 22:14:21 the-nexus systemd[531]: Started D-Bus User Message Bus. Jan 01 22:14:21 the-nexus dbus-daemon[544]: [session uid=970 pid=544] Activating via systemd: service name='ca.desrt.dconf' unit='dconf.service' requested by ':1.1' (uid=970 pid=540 comm="/usr/bin/slick-greeter ") Jan 01 22:14:21 the-nexus systemd[531]: Starting User preferences database... Jan 01 22:14:21 the-nexus dbus-daemon[544]: [session uid=970 pid=544] Successfully activated service 'ca.desrt.dconf' Jan 01 22:14:21 the-nexus systemd[531]: Started User preferences database. Jan 01 22:14:21 the-nexus kernel: Bluetooth: hci0: Waiting for firmware download to complete Jan 01 22:14:21 the-nexus kernel: Bluetooth: hci0: Firmware loaded in 1570814 usecs Jan 01 22:14:21 the-nexus kernel: Bluetooth: hci0: Waiting for device to boot Jan 01 22:14:21 the-nexus kernel: Bluetooth: hci0: Device booted in 13282 usecs Jan 01 22:14:21 the-nexus kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-17-16-1.ddc Jan 01 22:14:21 the-nexus kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Jan 01 22:14:21 the-nexus kernel: Bluetooth: hci0: Firmware revision 0.1 build 207 week 35 2021 Jan 01 22:14:21 the-nexus kernel: Bluetooth: hci0: MSFT filter_enable is already on Jan 01 22:14:21 the-nexus slick-greeter-check-hidpi[543]: Window scale: 1 Jan 01 22:14:21 the-nexus slick-greeter-set-keyboard-layout[557]: Current keyboard configuration: rules: evdev model: pc105 layout: us Jan 01 22:14:21 the-nexus slick-greeter-set-keyboard-layout[557]: Applying keyboard configuration: ['setxkbmap', '-model', 'pc105', '-layout', 'us', '-variant', '', '-option', '', '-v'] Jan 01 22:14:21 the-nexus slick-greeter-set-keyboard-layout[557]: Result: Warning! Multiple definitions of keyboard model Using command line, ignoring X server Warning! Multiple definitions of keyboard layout Using command line, ignoring X server Trying to build keymap using the following components: keycodes: evdev+aliases(qwerty) types: complete compat: complete symbols: pc+us+inet(evdev) geometry: pc(pc105) Jan 01 22:14:21 the-nexus slick-greeter-set-keyboard-layout[557]: New keyboard configuration: rules: evdev model: pc105 layout: us Jan 01 22:14:22 the-nexus dbus-daemon[544]: [session uid=970 pid=544] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.3' (uid=970 pid=540 comm="/usr/bin/slick-greeter ") Jan 01 22:14:22 the-nexus systemd[531]: Starting Accessibility services bus... Jan 01 22:14:22 the-nexus dbus-daemon[544]: [session uid=970 pid=544] Successfully activated service 'org.a11y.Bus' Jan 01 22:14:22 the-nexus systemd[531]: Started Accessibility services bus. Jan 01 22:14:22 the-nexus kernel: snd_hda_codec_realtek ehdaudio0D0: ASoC: sink widget AIF1TX overwritten Jan 01 22:14:22 the-nexus kernel: snd_hda_codec_realtek ehdaudio0D0: ASoC: source widget AIF1RX overwritten Jan 01 22:14:22 the-nexus kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi3 overwritten Jan 01 22:14:22 the-nexus kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi2 overwritten Jan 01 22:14:22 the-nexus kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi1 overwritten Jan 01 22:14:22 the-nexus kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Codec Output Pin1 overwritten Jan 01 22:14:22 the-nexus kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Codec Input Pin1 overwritten Jan 01 22:14:22 the-nexus kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Analog Codec Playback overwritten Jan 01 22:14:22 the-nexus kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Digital Codec Playback overwritten Jan 01 22:14:22 the-nexus kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Alt Analog Codec Playback overwritten Jan 01 22:14:22 the-nexus kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Analog Codec Capture overwritten Jan 01 22:14:22 the-nexus kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Digital Codec Capture overwritten Jan 01 22:14:22 the-nexus kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Alt Analog Codec Capture overwritten Jan 01 22:14:22 the-nexus dbus-daemon[544]: [session uid=970 pid=544] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.1' (uid=970 pid=540 comm="/usr/bin/slick-greeter ") Jan 01 22:14:22 the-nexus systemd[531]: Starting Virtual filesystem service... Jan 01 22:14:22 the-nexus kernel: input: sof-hda-dsp Mic as /devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input16 Jan 01 22:14:22 the-nexus kernel: input: sof-hda-dsp Headphone as /devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input17 Jan 01 22:14:22 the-nexus kernel: input: sof-hda-dsp HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input18 Jan 01 22:14:22 the-nexus kernel: input: sof-hda-dsp HDMI/DP,pcm=4 as /devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input19 Jan 01 22:14:22 the-nexus kernel: input: sof-hda-dsp HDMI/DP,pcm=5 as /devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input20 Jan 01 22:14:22 the-nexus dbus-daemon[544]: [session uid=970 pid=544] Successfully activated service 'org.gtk.vfs.Daemon' Jan 01 22:14:22 the-nexus systemd[531]: Started Virtual filesystem service. Jan 01 22:14:22 the-nexus systemd[531]: Reached target Sound Card. Jan 01 22:14:22 the-nexus systemd[1]: Starting Save/Restore Sound Card State... Jan 01 22:14:22 the-nexus systemd[1]: Manage Sound Card State (restore and store) was skipped because of a failed condition check (ConditionPathExists=/etc/alsa/state-daemon.conf). Jan 01 22:14:22 the-nexus systemd[1]: Finished Save/Restore Sound Card State. Jan 01 22:14:22 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=alsa-restore comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:22 the-nexus systemd[1]: Reached target Sound Card. Jan 01 22:14:22 the-nexus kernel: kauditd_printk_skb: 46 callbacks suppressed Jan 01 22:14:22 the-nexus kernel: audit: type=1130 audit(1641093262.107:53): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=alsa-restore comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:22 the-nexus polkitd[452]: :3: action=[Action id='org.freedesktop.login1.suspend'] Jan 01 22:14:22 the-nexus polkitd[452]: :4: subject=[Subject pid=540 user='lightdm' groups=lightdm seat='seat0' session='c1' local=true active=true] Jan 01 22:14:22 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.18' (uid=970 pid=540 comm="/usr/bin/slick-greeter ") Jan 01 22:14:22 the-nexus audit: BPF prog-id=25 op=LOAD Jan 01 22:14:22 the-nexus kernel: audit: type=1334 audit(1641093262.540:54): prog-id=25 op=LOAD Jan 01 22:14:22 the-nexus kernel: audit: type=1334 audit(1641093262.543:55): prog-id=26 op=LOAD Jan 01 22:14:22 the-nexus audit: BPF prog-id=26 op=LOAD Jan 01 22:14:22 the-nexus systemd[1]: Starting Daemon for power management... Jan 01 22:14:22 the-nexus upowerd[594]: energy_full (51.990000) is greater than energy_full_design (51.000000) Jan 01 22:14:22 the-nexus upowerd[594]: did not recognise USB path /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:001, please report Jan 01 22:14:22 the-nexus upowerd[594]: did not recognise USB path /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:002, please report Jan 01 22:14:22 the-nexus dbus-daemon[395]: [system] Successfully activated service 'org.freedesktop.UPower' Jan 01 22:14:22 the-nexus systemd[1]: Started Daemon for power management. Jan 01 22:14:22 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=upower comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:22 the-nexus kernel: audit: type=1130 audit(1641093262.650:56): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=upower comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:22 the-nexus polkitd[452]: :3: action=[Action id='org.freedesktop.DisplayManager.AccountsService.ReadAny'] Jan 01 22:14:22 the-nexus polkitd[452]: :4: subject=[Subject pid=540 user='lightdm' groups=lightdm seat='seat0' session='c1' local=true active=true] Jan 01 22:14:22 the-nexus at-spi-bus-launcher[568]: dbus-daemon[568]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=970 pid=540 comm="/usr/bin/slick-greeter ") Jan 01 22:14:22 the-nexus at-spi-bus-launcher[611]: dbus-daemon[611]: writing oom_score_adj error: Permission denied Jan 01 22:14:22 the-nexus at-spi-bus-launcher[568]: dbus-daemon[568]: Successfully activated service 'org.a11y.atspi.Registry' Jan 01 22:14:22 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.20' (uid=0 pid=609 comm="lightdm --session-child 12 19 ") Jan 01 22:14:22 the-nexus dbus-daemon[395]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found. Jan 01 22:14:22 the-nexus lightdm[609]: pam_systemd_home(lightdm:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found. Jan 01 22:14:22 the-nexus at-spi-bus-launcher[611]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Jan 01 22:14:24 the-nexus kernel: Bluetooth: hci0: setting interface failed (71) Jan 01 22:14:24 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7162] policy: auto-activating connection 'NiceMagnolia' (1f6b04ef-bb63-4102-a785-c1fc54dfb549) Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7168] device (wlan0): Activation: starting connection 'NiceMagnolia' (1f6b04ef-bb63-4102-a785-c1fc54dfb549) Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7169] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7171] manager: NetworkManager state is now CONNECTING Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7188] device (wlan0): set-hw-addr: reset MAC address to CC:D9:AC:19:44:B1 (preserve) Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7269] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7274] device (wlan0): Activation: (wifi) access point 'NiceMagnolia' has security, but secrets are required. Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7275] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7277] sup-iface[85e0803a962bd8a2,0,wlan0]: wps: type pbc start... Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7298] device (wlan0): supplicant interface state: disconnected -> interface_disabled Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7298] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> interface_disabled Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7316] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7321] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7325] device (wlan0): Activation: (wifi) connection 'NiceMagnolia' has security, and secrets exist. No new secrets needed. Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7326] Config: added 'ssid' value 'NiceMagnolia' Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7326] Config: added 'scan_ssid' value '1' Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7327] Config: added 'bgscan' value 'simple:30:-70:86400' Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7327] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK' Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7327] Config: added 'auth_alg' value 'OPEN' Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7327] Config: added 'psk' value '' Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7859] device (wlan0): supplicant interface state: interface_disabled -> inactive Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.7860] device (p2p-dev-wlan0): supplicant management interface state: interface_disabled -> inactive Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.8080] device (wlan0): supplicant interface state: inactive -> scanning Jan 01 22:14:24 the-nexus NetworkManager[396]: [1641093264.8081] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning Jan 01 22:14:25 the-nexus systemd[1]: systemd-rfkill.service: Deactivated successfully. Jan 01 22:14:25 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:25 the-nexus kernel: audit: type=1131 audit(1641093265.577:57): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:26 the-nexus wpa_supplicant[519]: wlan0: SME: Trying to authenticate with 98:da:c4:0d:90:d6 (SSID='NiceMagnolia' freq=5745 MHz) Jan 01 22:14:26 the-nexus kernel: wlan0: authenticate with 98:da:c4:0d:90:d6 Jan 01 22:14:26 the-nexus kernel: wlan0: send auth to 98:da:c4:0d:90:d6 (try 1/3) Jan 01 22:14:26 the-nexus NetworkManager[396]: [1641093266.7752] device (wlan0): supplicant interface state: scanning -> authenticating Jan 01 22:14:26 the-nexus NetworkManager[396]: [1641093266.7753] device (p2p-dev-wlan0): supplicant management interface state: scanning -> authenticating Jan 01 22:14:26 the-nexus wpa_supplicant[519]: wlan0: Trying to associate with 98:da:c4:0d:90:d6 (SSID='NiceMagnolia' freq=5745 MHz) Jan 01 22:14:26 the-nexus kernel: wlan0: authenticated Jan 01 22:14:26 the-nexus kernel: wlan0: associate with 98:da:c4:0d:90:d6 (try 1/3) Jan 01 22:14:26 the-nexus NetworkManager[396]: [1641093266.8136] device (wlan0): supplicant interface state: authenticating -> associating Jan 01 22:14:26 the-nexus NetworkManager[396]: [1641093266.8137] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating Jan 01 22:14:26 the-nexus kernel: wlan0: RX AssocResp from 98:da:c4:0d:90:d6 (capab=0x1411 status=0 aid=6) Jan 01 22:14:26 the-nexus wpa_supplicant[519]: wlan0: Associated with 98:da:c4:0d:90:d6 Jan 01 22:14:26 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Jan 01 22:14:26 the-nexus kernel: wlan0: associated Jan 01 22:14:26 the-nexus wpa_supplicant[519]: wlan0: WPA: Key negotiation completed with 98:da:c4:0d:90:d6 [PTK=CCMP GTK=CCMP] Jan 01 22:14:26 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-CONNECTED - Connection to 98:da:c4:0d:90:d6 completed [id=0 id_str=] Jan 01 22:14:26 the-nexus kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Jan 01 22:14:26 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-52 noise=9999 txrate=6000 Jan 01 22:14:26 the-nexus NetworkManager[396]: [1641093266.9088] device (wlan0): supplicant interface state: associating -> completed Jan 01 22:14:26 the-nexus NetworkManager[396]: [1641093266.9089] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "NiceMagnolia" Jan 01 22:14:26 the-nexus NetworkManager[396]: [1641093266.9090] device (p2p-dev-wlan0): supplicant management interface state: associating -> completed Jan 01 22:14:26 the-nexus NetworkManager[396]: [1641093266.9099] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Jan 01 22:14:26 the-nexus NetworkManager[396]: [1641093266.9109] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds) Jan 01 22:14:26 the-nexus avahi-daemon[394]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::aa95:e5f4:7984:863d. Jan 01 22:14:26 the-nexus avahi-daemon[394]: New relevant interface wlan0.IPv6 for mDNS. Jan 01 22:14:26 the-nexus avahi-daemon[394]: Registering new address record for fe80::aa95:e5f4:7984:863d on wlan0.*. Jan 01 22:14:26 the-nexus NetworkManager[396]: [1641093266.9366] dhcp4 (wlan0): state changed unknown -> bound, address=192.168.0.146 Jan 01 22:14:26 the-nexus avahi-daemon[394]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.146. Jan 01 22:14:26 the-nexus avahi-daemon[394]: New relevant interface wlan0.IPv4 for mDNS. Jan 01 22:14:26 the-nexus avahi-daemon[394]: Registering new address record for 192.168.0.146 on wlan0.IPv4. Jan 01 22:14:26 the-nexus NetworkManager[396]: [1641093266.9395] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Jan 01 22:14:26 the-nexus NetworkManager[396]: [1641093266.9447] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Jan 01 22:14:26 the-nexus NetworkManager[396]: [1641093266.9452] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Jan 01 22:14:26 the-nexus NetworkManager[396]: [1641093266.9462] manager: NetworkManager state is now CONNECTED_LOCAL Jan 01 22:14:26 the-nexus NetworkManager[396]: [1641093266.9482] manager: NetworkManager state is now CONNECTED_SITE Jan 01 22:14:26 the-nexus NetworkManager[396]: [1641093266.9485] policy: set 'NiceMagnolia' (wlan0) as default for IPv4 routing and DNS Jan 01 22:14:26 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.4' (uid=0 pid=396 comm="/usr/bin/NetworkManager --no-daemon ") Jan 01 22:14:26 the-nexus dbus-daemon[395]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found. Jan 01 22:14:26 the-nexus NetworkManager[396]: [1641093266.9518] device (wlan0): Activation: successful, device activated. Jan 01 22:14:26 the-nexus NetworkManager[396]: [1641093266.9536] manager: NetworkManager state is now CONNECTED_GLOBAL Jan 01 22:14:27 the-nexus NetworkManager[396]: [1641093267.3220] manager: startup complete Jan 01 22:14:28 the-nexus lightdm[609]: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=synth Jan 01 22:14:28 the-nexus audit[609]: USER_AUTH pid=609 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=? acct="synth" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=failed' Jan 01 22:14:28 the-nexus kernel: audit: type=1100 audit(1641093268.693:58): pid=609 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=? acct="synth" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=failed' Jan 01 22:14:29 the-nexus audit[609]: USER_LOGIN pid=609 uid=0 auid=4294967295 ses=4294967295 msg='op=login acct="synth" exe="/usr/bin/lightdm" hostname=the-nexus addr=? terminal=/dev/tty7 res=failed' Jan 01 22:14:29 the-nexus kernel: audit: type=1112 audit(1641093269.850:59): pid=609 uid=0 auid=4294967295 ses=4294967295 msg='op=login acct="synth" exe="/usr/bin/lightdm" hostname=the-nexus addr=? terminal=/dev/tty7 res=failed' Jan 01 22:14:29 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.21' (uid=0 pid=634 comm="lightdm --session-child 12 21 ") Jan 01 22:14:29 the-nexus dbus-daemon[395]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found. Jan 01 22:14:29 the-nexus lightdm[634]: pam_systemd_home(lightdm:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found. Jan 01 22:14:30 the-nexus systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Jan 01 22:14:30 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:30 the-nexus kernel: audit: type=1131 audit(1641093270.807:60): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:35 the-nexus lightdm[634]: gkr-pam: unable to locate daemon control file Jan 01 22:14:35 the-nexus audit[634]: USER_AUTH pid=634 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="synth" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success' Jan 01 22:14:35 the-nexus lightdm[634]: gkr-pam: stashed password to try later in open session Jan 01 22:14:35 the-nexus audit[634]: USER_ACCT pid=634 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="synth" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success' Jan 01 22:14:35 the-nexus kernel: audit: type=1100 audit(1641093275.467:61): pid=634 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="synth" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success' Jan 01 22:14:35 the-nexus kernel: audit: type=1101 audit(1641093275.467:62): pid=634 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="synth" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success' Jan 01 22:14:35 the-nexus systemd[1]: Stopping Session c1 of User lightdm... Jan 01 22:14:35 the-nexus lightdm[525]: pam_unix(lightdm-greeter:session): session closed for user lightdm Jan 01 22:14:35 the-nexus audit[525]: USER_END pid=525 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_unix,pam_systemd acct="lightdm" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success' Jan 01 22:14:35 the-nexus audit[525]: CRED_DISP pid=525 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_env,pam_permit acct="lightdm" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success' Jan 01 22:14:35 the-nexus systemd[1]: session-c1.scope: Deactivated successfully. Jan 01 22:14:35 the-nexus systemd[1]: Stopped Session c1 of User lightdm. Jan 01 22:14:35 the-nexus systemd[1]: session-c1.scope: Consumed 1.070s CPU time. Jan 01 22:14:35 the-nexus kernel: audit: type=1106 audit(1641093275.523:63): pid=525 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_unix,pam_systemd acct="lightdm" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success' Jan 01 22:14:35 the-nexus kernel: audit: type=1104 audit(1641093275.523:64): pid=525 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_env,pam_permit acct="lightdm" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success' Jan 01 22:14:35 the-nexus systemd-logind[397]: Removed session c1. Jan 01 22:14:35 the-nexus audit[634]: CRED_ACQ pid=634 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="synth" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success' Jan 01 22:14:35 the-nexus audit[634]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=9 a1=7ffe70984cb0 a2=4 a3=3e8 items=0 ppid=437 pid=634 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=2 comm="lightdm" exe="/usr/bin/lightdm" key=(null) Jan 01 22:14:35 the-nexus audit: PROCTITLE proctitle=6C69676874646D002D2D73657373696F6E2D6368696C64003132003231 Jan 01 22:14:35 the-nexus lightdm[634]: pam_unix(lightdm:session): session opened for user synth(uid=1000) by (uid=0) Jan 01 22:14:35 the-nexus kernel: audit: type=1103 audit(1641093275.527:65): pid=634 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct="synth" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success' Jan 01 22:14:35 the-nexus kernel: audit: type=1006 audit(1641093275.527:66): pid=634 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=2 res=1 Jan 01 22:14:35 the-nexus kernel: audit: type=1300 audit(1641093275.527:66): arch=c000003e syscall=1 success=yes exit=4 a0=9 a1=7ffe70984cb0 a2=4 a3=3e8 items=0 ppid=437 pid=634 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=2 comm="lightdm" exe="/usr/bin/lightdm" key=(null) Jan 01 22:14:35 the-nexus kernel: audit: type=1327 audit(1641093275.527:66): proctitle=6C69676874646D002D2D73657373696F6E2D6368696C64003132003231 Jan 01 22:14:35 the-nexus systemd[1]: Created slice User Slice of UID 1000. Jan 01 22:14:35 the-nexus systemd[1]: Starting User Runtime Directory /run/user/1000... Jan 01 22:14:35 the-nexus systemd-logind[397]: New session 2 of user synth. Jan 01 22:14:35 the-nexus systemd[1]: Finished User Runtime Directory /run/user/1000. Jan 01 22:14:35 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:35 the-nexus systemd[1]: Starting User Manager for UID 1000... Jan 01 22:14:35 the-nexus kernel: audit: type=1130 audit(1641093275.537:67): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:35 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.25' (uid=0 pid=643 comm="(systemd) ") Jan 01 22:14:35 the-nexus dbus-daemon[395]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found. Jan 01 22:14:35 the-nexus systemd[643]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found. Jan 01 22:14:35 the-nexus systemd[643]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[synth] ruser=[] rhost=[] Jan 01 22:14:35 the-nexus kernel: audit: type=1101 audit(1641093275.540:68): pid=643 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="synth" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:35 the-nexus audit[643]: USER_ACCT pid=643 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="synth" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:35 the-nexus audit[643]: CRED_ACQ pid=643 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="synth" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Jan 01 22:14:35 the-nexus audit[643]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=9 a1=7ffc889a1590 a2=4 a3=3e8 items=0 ppid=1 pid=643 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=3 comm="(systemd)" exe="/usr/lib/systemd/systemd" key=(null) Jan 01 22:14:35 the-nexus audit: PROCTITLE proctitle="(systemd)" Jan 01 22:14:35 the-nexus systemd[643]: pam_unix(systemd-user:session): session opened for user synth(uid=1000) by (uid=0) Jan 01 22:14:35 the-nexus systemd[643]: pam_env(systemd-user:session): deprecated reading of user environment enabled Jan 01 22:14:35 the-nexus audit[643]: USER_START pid=643 uid=0 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_systemd_home,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="synth" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:35 the-nexus audit: BPF prog-id=27 op=LOAD Jan 01 22:14:35 the-nexus audit[643]: SYSCALL arch=c000003e syscall=321 success=yes exit=8 a0=5 a1=7ffc11049d80 a2=78 a3=7ffc11049d80 items=0 ppid=1 pid=643 auid=1000 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 tty=(none) ses=3 comm="systemd" exe="/usr/lib/systemd/systemd" key=(null) Jan 01 22:14:35 the-nexus audit: PROCTITLE proctitle="(systemd)" Jan 01 22:14:35 the-nexus audit: BPF prog-id=0 op=UNLOAD Jan 01 22:14:35 the-nexus systemd[643]: Queued start job for default target Main User Target. Jan 01 22:14:35 the-nexus systemd-journald[277]: File /var/log/journal/e97781e181ab43d29f2117e6a7be514f/user-1000.journal corrupted or uncleanly shut down, renaming and replacing. Jan 01 22:14:35 the-nexus systemd[643]: Created slice User Application Slice. Jan 01 22:14:35 the-nexus systemd[643]: Started Run EOS update notifier periodically. Jan 01 22:14:35 the-nexus systemd[643]: Reached target Paths. Jan 01 22:14:35 the-nexus systemd[643]: Reached target Timers. Jan 01 22:14:35 the-nexus systemd[643]: Starting D-Bus User Message Bus Socket... Jan 01 22:14:35 the-nexus systemd[643]: Listening on GnuPG network certificate management daemon. Jan 01 22:14:35 the-nexus systemd[643]: Listening on GCR ssh-agent wrapper. Jan 01 22:14:35 the-nexus systemd[643]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). Jan 01 22:14:35 the-nexus systemd[643]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Jan 01 22:14:35 the-nexus systemd[643]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Jan 01 22:14:35 the-nexus systemd[643]: Listening on GnuPG cryptographic agent and passphrase cache. Jan 01 22:14:35 the-nexus systemd[643]: Listening on p11-kit server. Jan 01 22:14:35 the-nexus systemd[643]: Listening on PipeWire PulseAudio. Jan 01 22:14:35 the-nexus systemd[643]: Listening on PipeWire Multimedia System Socket. Jan 01 22:14:35 the-nexus systemd[643]: Listening on D-Bus User Message Bus Socket. Jan 01 22:14:35 the-nexus systemd[643]: Reached target Sockets. Jan 01 22:14:35 the-nexus systemd[643]: Reached target Basic System. Jan 01 22:14:35 the-nexus systemd[1]: Started User Manager for UID 1000. Jan 01 22:14:35 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:35 the-nexus systemd[643]: Starting Update XDG user dir configuration... Jan 01 22:14:35 the-nexus systemd[1]: Started Session 2 of User synth. Jan 01 22:14:35 the-nexus systemd[643]: Finished Update XDG user dir configuration. Jan 01 22:14:35 the-nexus systemd[643]: Reached target Main User Target. Jan 01 22:14:35 the-nexus systemd[643]: Startup finished in 71ms. Jan 01 22:14:35 the-nexus lightdm[634]: pam_env(lightdm:session): deprecated reading of user environment enabled Jan 01 22:14:35 the-nexus lightdm[634]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring Jan 01 22:14:35 the-nexus audit[634]: USER_START pid=634 uid=0 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_systemd_home,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring acct="synth" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success' Jan 01 22:14:35 the-nexus audit[634]: USER_LOGIN pid=634 uid=0 auid=1000 ses=2 msg='op=login id=1000 exe="/usr/bin/lightdm" hostname=the-nexus addr=? terminal=/dev/tty7 res=success' Jan 01 22:14:35 the-nexus systemd[643]: Started D-Bus User Message Bus. Jan 01 22:14:35 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.2' (uid=1000 pid=664 comm="/usr/lib/gnome-session-check-accelerated ") Jan 01 22:14:35 the-nexus systemd[643]: Starting Virtual filesystem service... Jan 01 22:14:35 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Successfully activated service 'org.gtk.vfs.Daemon' Jan 01 22:14:35 the-nexus systemd[643]: Started Virtual filesystem service. Jan 01 22:14:35 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.5' (uid=1000 pid=664 comm="/usr/lib/gnome-session-check-accelerated ") Jan 01 22:14:35 the-nexus systemd[643]: Starting Accessibility services bus... Jan 01 22:14:35 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Successfully activated service 'org.a11y.Bus' Jan 01 22:14:35 the-nexus systemd[643]: Started Accessibility services bus. Jan 01 22:14:35 the-nexus gnome-keyring-ssh.desktop[704]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh Jan 01 22:14:35 the-nexus gnome-keyring-secrets.desktop[705]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh Jan 01 22:14:35 the-nexus gnome-keyring-pkcs11.desktop[706]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh Jan 01 22:14:35 the-nexus gsd-usb-protect[733]: Failed to get screen saver status: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.ScreenSaver was not provided by any .service files Jan 01 22:14:35 the-nexus kernel: rfkill: input handler disabled Jan 01 22:14:35 the-nexus gsd-usb-protect[733]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.usbguard1 was not provided by any .service files Jan 01 22:14:35 the-nexus at-spi-bus-launcher[686]: dbus-daemon[686]: Activating service name='org.a11y.atspi.Registry' requested by ':1.1' (uid=1000 pid=713 comm="/usr/lib/gsd-power ") Jan 01 22:14:35 the-nexus at-spi-bus-launcher[795]: dbus-daemon[795]: writing oom_score_adj error: Permission denied Jan 01 22:14:35 the-nexus at-spi-bus-launcher[686]: dbus-daemon[686]: Successfully activated service 'org.a11y.atspi.Registry' Jan 01 22:14:35 the-nexus at-spi-bus-launcher[795]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Jan 01 22:14:35 the-nexus systemd[643]: Created slice User Core Session Slice. Jan 01 22:14:35 the-nexus systemd[643]: Started PipeWire Multimedia Service. Jan 01 22:14:35 the-nexus systemd[643]: Started PipeWire Media Session Manager. Jan 01 22:14:35 the-nexus gsd-xsettings[741]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist Jan 01 22:14:35 the-nexus systemd[643]: Started PipeWire PulseAudio. Jan 01 22:14:35 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.37' (uid=1000 pid=722 comm="/usr/lib/gsd-keyboard ") Jan 01 22:14:35 the-nexus audit: BPF prog-id=28 op=LOAD Jan 01 22:14:35 the-nexus audit: BPF prog-id=29 op=LOAD Jan 01 22:14:35 the-nexus audit: BPF prog-id=30 op=LOAD Jan 01 22:14:35 the-nexus systemd[1]: Starting Locale Service... Jan 01 22:14:35 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.39' (uid=1000 pid=806 comm="/usr/bin/pipewire ") Jan 01 22:14:35 the-nexus systemd[1]: Starting RealtimeKit Scheduling Policy Service... Jan 01 22:14:35 the-nexus dbus-daemon[395]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1' Jan 01 22:14:35 the-nexus systemd[1]: Started RealtimeKit Scheduling Policy Service. Jan 01 22:14:35 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rtkit-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Successfully called chroot. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Successfully dropped privileges. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Successfully limited resources. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Canary thread running. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Running. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Watchdog thread running. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Successfully made thread 806 of process 806 owned by '1000' high priority at nice level -11. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Supervising 1 threads of 1 processes of 1 users. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Successfully made thread 808 of process 808 owned by '1000' high priority at nice level -11. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Supervising 2 threads of 2 processes of 1 users. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Successfully made thread 807 of process 807 owned by '1000' high priority at nice level -11. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Supervising 3 threads of 3 processes of 1 users. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Supervising 3 threads of 3 processes of 1 users. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Supervising 3 threads of 3 processes of 1 users. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Supervising 3 threads of 3 processes of 1 users. Jan 01 22:14:35 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.43' (uid=1000 pid=748 comm="/usr/lib/gsd-color ") Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Supervising 3 threads of 3 processes of 1 users. Jan 01 22:14:35 the-nexus systemd[1]: Starting Manage, Install and Generate Color Profiles... Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Successfully made thread 822 of process 807 owned by '1000' RT at priority 20. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Supervising 4 threads of 3 processes of 1 users. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Supervising 4 threads of 3 processes of 1 users. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Supervising 4 threads of 3 processes of 1 users. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Successfully made thread 823 of process 808 owned by '1000' RT at priority 20. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Supervising 5 threads of 3 processes of 1 users. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Successfully made thread 825 of process 806 owned by '1000' RT at priority 20. Jan 01 22:14:35 the-nexus rtkit-daemon[815]: Supervising 6 threads of 3 processes of 1 users. Jan 01 22:14:35 the-nexus dbus-daemon[395]: [system] Successfully activated service 'org.freedesktop.ColorManager' Jan 01 22:14:35 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=colord comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:35 the-nexus systemd[1]: Started Manage, Install and Generate Color Profiles. Jan 01 22:14:35 the-nexus dbus-daemon[395]: [system] Successfully activated service 'org.freedesktop.locale1' Jan 01 22:14:35 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:35 the-nexus systemd[1]: Started Locale Service. Jan 01 22:14:36 the-nexus budgie-wm[831]: Running Mutter(Budgie) (using mutter 41.2) as a X11 window and compositing manager Jan 01 22:14:36 the-nexus budgie-wm[831]: ibus.vala:47: ibus-daemon unsupported on this system Jan 01 22:14:36 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Activating via systemd: service name='ca.desrt.dconf' unit='dconf.service' requested by ':1.35' (uid=1000 pid=831 comm="budgie-wm ") Jan 01 22:14:36 the-nexus systemd[643]: Starting User preferences database... Jan 01 22:14:36 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Successfully activated service 'ca.desrt.dconf' Jan 01 22:14:36 the-nexus systemd[643]: Started User preferences database. Jan 01 22:14:36 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='net.hadess.PowerProfiles' unit='power-profiles-daemon.service' requested by ':1.35' (uid=1000 pid=713 comm="/usr/lib/gsd-power ") Jan 01 22:14:36 the-nexus systemd[1]: Starting Power Profiles daemon... Jan 01 22:14:36 the-nexus gsd-media-keys[710]: Failed to grab accelerator for keybinding settings:playback-random Jan 01 22:14:36 the-nexus gsd-media-keys[710]: Failed to grab accelerator for keybinding settings:hibernate Jan 01 22:14:36 the-nexus gsd-media-keys[710]: Failed to grab accelerator for keybinding settings:playback-repeat Jan 01 22:14:36 the-nexus gsd-media-keys[710]: Failed to grab accelerator for keybinding settings:rotate-video-lock Jan 01 22:14:36 the-nexus dbus-daemon[395]: [system] Successfully activated service 'net.hadess.PowerProfiles' Jan 01 22:14:36 the-nexus systemd[1]: Started Power Profiles daemon. Jan 01 22:14:36 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=power-profiles-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:36 the-nexus budgie-wm.desktop[831]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). Jan 01 22:14:36 the-nexus budgie-wm.desktop[831]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). Jan 01 22:14:36 the-nexus budgie-wm.desktop[831]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). Jan 01 22:14:36 the-nexus polkitd[452]: Registered Authentication Agent for unix-session:2 (system bus name :1.50 [budgie-polkit-dialog], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Jan 01 22:14:37 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Activating via systemd: service name='org.gnome.zeitgeist.Engine' unit='zeitgeist.service' requested by ':1.44' (uid=1000 pid=917 comm="zeitgeist-datahub ") Jan 01 22:14:37 the-nexus systemd[643]: Starting Zeitgeist activity log service... Jan 01 22:14:37 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Activating via systemd: service name='org.gnome.zeitgeist.SimpleIndexer' unit='zeitgeist-fts.service' requested by ':1.46' (uid=1000 pid=951 comm="/usr/bin/zeitgeist-daemon ") Jan 01 22:14:37 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Successfully activated service 'org.gnome.zeitgeist.Engine' Jan 01 22:14:37 the-nexus systemd[643]: Started Zeitgeist activity log service. Jan 01 22:14:37 the-nexus systemd[643]: Starting Zeitgeist full-text search indexer... Jan 01 22:14:37 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' requested by ':1.52' (uid=1000 pid=938 comm="/usr/lib/gsd-disk-utility-notify ") Jan 01 22:14:37 the-nexus systemd[1]: Starting Disk Manager... Jan 01 22:14:37 the-nexus gnome-session-binary[656]: Entering running state Jan 01 22:14:37 the-nexus udisksd[972]: udisks daemon version 2.9.4 starting Jan 01 22:14:37 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Successfully activated service 'org.gnome.zeitgeist.SimpleIndexer' Jan 01 22:14:37 the-nexus systemd[643]: Started Zeitgeist full-text search indexer. Jan 01 22:14:37 the-nexus zeitgeist-datah[970]: zeitgeist-datahub.vala:224: Unable to get name "org.gnome.zeitgeist.datahub" on the bus! Jan 01 22:14:37 the-nexus NetworkManager[396]: [1641093277.1925] agent-manager: agent[0c3e3bce5bc549e6,:1.54/org.freedesktop.nm-applet/1000]: agent registered Jan 01 22:14:37 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.40' (uid=1000 pid=912 comm="us.getsol.budgie-desktop-view ") Jan 01 22:14:37 the-nexus systemd[643]: Starting Virtual filesystem service - disk device monitor... Jan 01 22:14:37 the-nexus dbus-daemon[395]: [system] Successfully activated service 'org.freedesktop.UDisks2' Jan 01 22:14:37 the-nexus systemd[1]: Started Disk Manager. Jan 01 22:14:37 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=udisks2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:37 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975640 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:14:37 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385601: comm zeitgeist-datah: reading directory lblock 0 Jan 01 22:14:37 the-nexus udisksd[972]: Acquired the name org.freedesktop.UDisks2 on the system message bus Jan 01 22:14:37 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor' Jan 01 22:14:37 the-nexus systemd[643]: Started Virtual filesystem service - disk device monitor. Jan 01 22:14:37 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.40' (uid=1000 pid=912 comm="us.getsol.budgie-desktop-view ") Jan 01 22:14:37 the-nexus systemd[643]: Starting Virtual filesystem service - Apple File Conduit monitor... Jan 01 22:14:37 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor' Jan 01 22:14:37 the-nexus systemd[643]: Started Virtual filesystem service - Apple File Conduit monitor. Jan 01 22:14:37 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.40' (uid=1000 pid=912 comm="us.getsol.budgie-desktop-view ") Jan 01 22:14:38 the-nexus systemd[643]: Starting Virtual filesystem service - digital camera monitor... Jan 01 22:14:38 the-nexus budgie-extras-d[926]: Binding 'dead_grave' failed! Jan 01 22:14:38 the-nexus budgie-extras-d[926]: Binding 'dead_grave' failed! Jan 01 22:14:38 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor' Jan 01 22:14:38 the-nexus systemd[643]: Started Virtual filesystem service - digital camera monitor. Jan 01 22:14:38 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.40' (uid=1000 pid=912 comm="us.getsol.budgie-desktop-view ") Jan 01 22:14:38 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975640 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:14:38 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385601: comm zeitgeist-datah: reading directory lblock 0 Jan 01 22:14:38 the-nexus systemd[643]: Starting Virtual filesystem service - Media Transfer Protocol monitor... Jan 01 22:14:38 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor' Jan 01 22:14:38 the-nexus systemd[643]: Started Virtual filesystem service - Media Transfer Protocol monitor. Jan 01 22:14:38 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Activating via systemd: service name='org.gnome.evolution.dataserver.Sources5' unit='evolution-source-registry.service' requested by ':1.60' (uid=1000 pid=915 comm="/usr/lib/evolution-data-server/evolution-alarm-not") Jan 01 22:14:38 the-nexus systemd[643]: Starting Evolution source registry... Jan 01 22:14:38 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975640 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:14:39 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385601: comm zeitgeist-datah: reading directory lblock 0 Jan 01 22:14:39 the-nexus redshift-gtk[911]: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed Jan 01 22:14:39 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975640 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:14:39 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385601: comm zeitgeist-datah: reading directory lblock 0 Jan 01 22:14:40 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Activating service name='org.gnome.OnlineAccounts' requested by ':1.61' (uid=1000 pid=1082 comm="/usr/lib/evolution-source-registry ") Jan 01 22:14:40 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975640 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:14:40 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385601: comm zeitgeist-datah: reading directory lblock 0 Jan 01 22:14:40 the-nexus dbus-daemon[1100]: writing oom_score_adj error: Permission denied Jan 01 22:14:40 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975640 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:14:41 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385601: comm zeitgeist-datah: reading directory lblock 0 Jan 01 22:14:40 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Activating service name='org.gnome.Identity' requested by ':1.62' (uid=1000 pid=1100 comm="/usr/lib/goa-daemon ") Jan 01 22:14:40 the-nexus goa-daemon[1100]: goa-daemon version 3.40.1 starting Jan 01 22:14:40 the-nexus dbus-daemon[1111]: writing oom_score_adj error: Permission denied Jan 01 22:14:40 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Successfully activated service 'org.gnome.OnlineAccounts' Jan 01 22:14:40 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Successfully activated service 'org.gnome.Identity' Jan 01 22:14:41 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975640 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:14:41 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385601: comm zeitgeist-datah: reading directory lblock 0 Jan 01 22:14:42 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975640 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:14:42 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385601: comm zeitgeist-datah: reading directory lblock 0 Jan 01 22:14:42 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Successfully activated service 'org.gnome.evolution.dataserver.Sources5' Jan 01 22:14:42 the-nexus systemd[643]: Started Evolution source registry. Jan 01 22:14:42 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975640 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:14:42 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385601: comm zeitgeist-datah: reading directory lblock 0 Jan 01 22:14:43 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975640 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:14:43 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385601: comm zeitgeist-datah: reading directory lblock 0 Jan 01 22:14:43 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975640 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:14:43 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385601: comm zeitgeist-datah: reading directory lblock 0 Jan 01 22:14:44 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Activating via systemd: service name='org.gnome.evolution.dataserver.Calendar8' unit='evolution-calendar-factory.service' requested by ':1.60' (uid=1000 pid=915 comm="/usr/lib/evolution-data-server/evolution-alarm-not") Jan 01 22:14:44 the-nexus systemd[643]: Starting Evolution calendar service... Jan 01 22:14:44 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Successfully activated service 'org.gnome.evolution.dataserver.Calendar8' Jan 01 22:14:44 the-nexus systemd[643]: Started Evolution calendar service. Jan 01 22:14:44 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Activating via systemd: service name='org.gnome.evolution.dataserver.AddressBook10' unit='evolution-addressbook-factory.service' requested by ':1.65' (uid=1000 pid=1157 comm="/usr/lib/evolution-calendar-factory ") Jan 01 22:14:44 the-nexus systemd[643]: Starting Evolution address book service... Jan 01 22:14:44 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Successfully activated service 'org.gnome.evolution.dataserver.AddressBook10' Jan 01 22:14:44 the-nexus systemd[643]: Started Evolution address book service. Jan 01 22:14:44 the-nexus budgie-panel.desktop[1096]: ATTENTION: default value of option mesa_glthread overridden by environment. Jan 01 22:14:45 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975240 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:14:45 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386973: comm StreamTrans #3: reading directory lblock 0 Jan 01 22:14:45 the-nexus systemd[1]: Stopping User Manager for UID 970... Jan 01 22:14:45 the-nexus kernel: kauditd_printk_skb: 20 callbacks suppressed Jan 01 22:14:45 the-nexus kernel: audit: type=1131 audit(1641093285.777:85): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@970 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:45 the-nexus kernel: audit: type=1131 audit(1641093285.793:86): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@970 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:45 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975240 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:14:45 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386973: comm StreamTrans #2: reading directory lblock 0 Jan 01 22:14:45 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@970 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:45 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@970 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:14:45 the-nexus systemd[531]: Activating special unit Exit the Session... Jan 01 22:14:45 the-nexus gvfsd[569]: A connection to the bus can't be made Jan 01 22:14:45 the-nexus systemd[532]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[lightdm] ruser=[] rhost=[] Jan 01 22:14:45 the-nexus systemd[531]: Stopped target Main User Target. Jan 01 22:14:45 the-nexus systemd[531]: Stopped target Sound Card. Jan 01 22:14:45 the-nexus systemd[531]: Stopping Accessibility services bus... Jan 01 22:14:45 the-nexus systemd[531]: Stopping D-Bus User Message Bus... Jan 01 22:14:45 the-nexus systemd[531]: Stopping User preferences database... Jan 01 22:14:45 the-nexus systemd[531]: Stopping Virtual filesystem service... Jan 01 22:14:45 the-nexus systemd[531]: Stopped D-Bus User Message Bus. Jan 01 22:14:45 the-nexus systemd[531]: Stopped User preferences database. Jan 01 22:14:45 the-nexus systemd[531]: Stopped Accessibility services bus. Jan 01 22:14:45 the-nexus systemd[1]: run-user-970-gvfs.mount: Deactivated successfully. Jan 01 22:14:45 the-nexus systemd[531]: Stopped Virtual filesystem service. Jan 01 22:14:45 the-nexus systemd[531]: Stopped target Basic System. Jan 01 22:14:45 the-nexus systemd[531]: Stopped target Paths. Jan 01 22:14:45 the-nexus systemd[531]: Stopped target Sockets. Jan 01 22:14:45 the-nexus systemd[531]: Stopped target Timers. Jan 01 22:14:45 the-nexus systemd[531]: Closed D-Bus User Message Bus Socket. Jan 01 22:14:45 the-nexus systemd[531]: Closed GnuPG network certificate management daemon. Jan 01 22:14:45 the-nexus systemd[531]: Closed GCR ssh-agent wrapper. Jan 01 22:14:45 the-nexus systemd[531]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers). Jan 01 22:14:45 the-nexus systemd[531]: Closed GnuPG cryptographic agent and passphrase cache (restricted). Jan 01 22:14:45 the-nexus systemd[531]: Closed GnuPG cryptographic agent (ssh-agent emulation). Jan 01 22:14:45 the-nexus systemd[531]: Closed GnuPG cryptographic agent and passphrase cache. Jan 01 22:14:45 the-nexus systemd[531]: Closed p11-kit server. Jan 01 22:14:45 the-nexus systemd[531]: Closed PipeWire PulseAudio. Jan 01 22:14:45 the-nexus systemd[531]: Closed PipeWire Multimedia System Socket. Jan 01 22:14:45 the-nexus systemd[531]: Removed slice User Application Slice. Jan 01 22:14:45 the-nexus systemd[531]: Reached target Shutdown. Jan 01 22:14:45 the-nexus systemd[531]: Finished Exit the Session. Jan 01 22:14:45 the-nexus systemd[531]: Reached target Exit the Session. Jan 01 22:14:45 the-nexus systemd[1]: user@970.service: Deactivated successfully. Jan 01 22:14:45 the-nexus systemd[1]: Stopped User Manager for UID 970. Jan 01 22:14:45 the-nexus systemd[1]: Stopping User Runtime Directory /run/user/970... Jan 01 22:14:45 the-nexus systemd[1]: run-user-970.mount: Deactivated successfully. Jan 01 22:14:45 the-nexus systemd[1]: user-runtime-dir@970.service: Deactivated successfully. Jan 01 22:14:45 the-nexus systemd[1]: Stopped User Runtime Directory /run/user/970. Jan 01 22:14:45 the-nexus systemd[1]: Removed slice User Slice of UID 970. Jan 01 22:14:45 the-nexus systemd[1]: user-970.slice: Consumed 1.338s CPU time. Jan 01 22:14:46 the-nexus rtkit-daemon[815]: Supervising 6 threads of 3 processes of 1 users. Jan 01 22:14:46 the-nexus rtkit-daemon[815]: Supervising 6 threads of 3 processes of 1 users. Jan 01 22:14:46 the-nexus rtkit-daemon[815]: Supervising 6 threads of 3 processes of 1 users. Jan 01 22:14:46 the-nexus rtkit-daemon[815]: Supervising 6 threads of 3 processes of 1 users. Jan 01 22:14:46 the-nexus rtkit-daemon[815]: Supervising 6 threads of 3 processes of 1 users. Jan 01 22:14:46 the-nexus rtkit-daemon[815]: Supervising 6 threads of 3 processes of 1 users. Jan 01 22:14:46 the-nexus rtkit-daemon[815]: Successfully made thread 1326 of process 1096 owned by '1000' RT at priority 10. Jan 01 22:14:46 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:14:46 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975240 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:14:46 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386973: lblock 0: comm GeckoMain: error -5 reading directory block Jan 01 22:14:46 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:14:46 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:14:47 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:14:47 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:14:47 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975240 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:14:47 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386973: comm GeckoMain: reading directory lblock 0 Jan 01 22:14:48 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975240 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:14:48 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386973: comm GeckoMain: reading directory lblock 0 Jan 01 22:14:48 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:14:48 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:14:48 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:14:48 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:14:48 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975240 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:14:48 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386973: comm GeckoMain: reading directory lblock 0 Jan 01 22:14:49 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975240 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:14:49 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386973: comm GeckoMain: reading directory lblock 0 Jan 01 22:14:50 the-nexus welcome.desktop[971]: Welcome app is disabled. To start it anyway, use option --enable. Jan 01 22:14:50 the-nexus systemd-timesyncd[384]: Initial synchronization to time server 23.157.160.168:123 (2.arch.pool.ntp.org). Jan 01 22:14:51 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.42' (uid=1000 pid=916 comm="/usr/lib/tracker-miner-fs-3 ") Jan 01 22:14:51 the-nexus systemd[643]: Created slice User Background Tasks Slice. Jan 01 22:14:51 the-nexus systemd[643]: Starting Tracker metadata extractor... Jan 01 22:14:51 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract' Jan 01 22:14:51 the-nexus systemd[643]: Started Tracker metadata extractor. Jan 01 22:14:51 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:14:51 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:14:54 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:14:54 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:15:05 the-nexus systemd[1]: systemd-hostnamed.service: Deactivated successfully. Jan 01 22:15:05 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:15:05 the-nexus kernel: audit: type=1131 audit(1641093305.961:87): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:15:06 the-nexus audit: BPF prog-id=0 op=UNLOAD Jan 01 22:15:06 the-nexus audit: BPF prog-id=0 op=UNLOAD Jan 01 22:15:06 the-nexus audit: BPF prog-id=0 op=UNLOAD Jan 01 22:15:06 the-nexus kernel: audit: type=1334 audit(1641093306.075:88): prog-id=0 op=UNLOAD Jan 01 22:15:06 the-nexus kernel: audit: type=1334 audit(1641093306.075:89): prog-id=0 op=UNLOAD Jan 01 22:15:06 the-nexus kernel: audit: type=1334 audit(1641093306.075:90): prog-id=0 op=UNLOAD Jan 01 22:15:14 the-nexus systemd[1]: systemd-localed.service: Deactivated successfully. Jan 01 22:15:14 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:15:14 the-nexus kernel: audit: type=1131 audit(1641093314.210:91): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:15:14 the-nexus audit: BPF prog-id=0 op=UNLOAD Jan 01 22:15:14 the-nexus audit: BPF prog-id=0 op=UNLOAD Jan 01 22:15:14 the-nexus audit: BPF prog-id=0 op=UNLOAD Jan 01 22:15:14 the-nexus kernel: audit: type=1334 audit(1641093314.330:92): prog-id=0 op=UNLOAD Jan 01 22:15:14 the-nexus kernel: audit: type=1334 audit(1641093314.330:93): prog-id=0 op=UNLOAD Jan 01 22:15:14 the-nexus kernel: audit: type=1334 audit(1641093314.330:94): prog-id=0 op=UNLOAD Jan 01 22:15:37 the-nexus systemd[643]: Starting EOS update notifier service... Jan 01 22:15:43 the-nexus eos-update-notifier[1749]: Checking for updates ... Jan 01 22:15:46 the-nexus eos-update-notifier[1749]: Checking AUR updates ... Jan 01 22:15:47 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975688 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:15:47 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386541: comm yay: reading directory lblock 0 Jan 01 22:15:47 the-nexus eos-update-notifier[1809]: -> could not open file /var/lib/pacman/local/nvm-0.39.1-1/desc: Input/output error Jan 01 22:15:48 the-nexus systemd[643]: Finished EOS update notifier service. Jan 01 22:15:54 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.70' (uid=1000 pid=1837 comm="gnome-terminal ") Jan 01 22:15:54 the-nexus systemd[643]: Created slice Slice /app/org.gnome.Terminal. Jan 01 22:15:54 the-nexus systemd[643]: Starting GNOME Terminal Server... Jan 01 22:15:54 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Successfully activated service 'org.gnome.Terminal' Jan 01 22:15:54 the-nexus systemd[643]: Started GNOME Terminal Server. Jan 01 22:15:54 the-nexus systemd[643]: Started VTE child process 1863 launched by gnome-terminal-server process 1842. Jan 01 22:15:59 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.73' (uid=0 pid=1875 comm="sudo pacman -S -y -u --config /etc/pacman.conf -- ") Jan 01 22:15:59 the-nexus dbus-daemon[395]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found. Jan 01 22:15:59 the-nexus sudo[1875]: pam_systemd_home(sudo:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found. Jan 01 22:16:05 the-nexus audit[1875]: USER_AUTH pid=1875 uid=1000 auid=1000 ses=3 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="synth" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:16:05 the-nexus audit[1875]: USER_ACCT pid=1875 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="synth" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:16:05 the-nexus sudo[1875]: synth : TTY=pts/0 ; PWD=/home/synth ; USER=root ; COMMAND=/usr/bin/pacman -S -y -u --config /etc/pacman.conf -- Jan 01 22:16:05 the-nexus audit[1875]: CRED_REFR pid=1875 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:16:05 the-nexus kernel: audit: type=1100 audit(1641093365.875:95): pid=1875 uid=1000 auid=1000 ses=3 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="synth" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:16:05 the-nexus kernel: audit: type=1101 audit(1641093365.875:96): pid=1875 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="synth" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:16:05 the-nexus kernel: audit: type=1110 audit(1641093365.875:97): pid=1875 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:16:05 the-nexus sudo[1875]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Jan 01 22:16:05 the-nexus audit[1875]: USER_START pid=1875 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:16:05 the-nexus kernel: audit: type=1105 audit(1641093365.882:98): pid=1875 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:16:07 the-nexus sudo[1875]: pam_unix(sudo:session): session closed for user root Jan 01 22:16:07 the-nexus audit[1875]: USER_END pid=1875 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:16:07 the-nexus audit[1875]: CRED_DISP pid=1875 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:16:07 the-nexus kernel: audit: type=1106 audit(1641093367.576:99): pid=1875 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:16:07 the-nexus kernel: audit: type=1104 audit(1641093367.576:100): pid=1875 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:16:08 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975688 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:08 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386541: comm yay: reading directory lblock 0 Jan 01 22:16:20 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974264 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:20 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386165: comm yay: reading directory lblock 0 Jan 01 22:16:20 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973360 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:20 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386242: comm yay: reading directory lblock 0 Jan 01 22:16:21 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972504 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:21 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385465: comm yay: reading directory lblock 0 Jan 01 22:16:21 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973368 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:21 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386246: comm yay: reading directory lblock 0 Jan 01 22:16:22 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972536 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:22 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385469: comm yay: reading directory lblock 0 Jan 01 22:16:23 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973376 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:23 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386250: comm yay: reading directory lblock 0 Jan 01 22:16:23 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972720 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:23 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385499: comm yay: reading directory lblock 0 Jan 01 22:16:24 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972768 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:24 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385503: comm yay: reading directory lblock 0 Jan 01 22:16:25 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972800 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:25 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385507: comm yay: reading directory lblock 0 Jan 01 22:16:25 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973312 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:25 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386254: comm yay: reading directory lblock 0 Jan 01 22:16:26 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972416 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:26 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385436: comm yay: reading directory lblock 0 Jan 01 22:16:26 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973408 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:26 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386266: comm yay: reading directory lblock 0 Jan 01 22:16:27 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973240 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:27 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386181: comm yay: reading directory lblock 0 Jan 01 22:16:28 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972816 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:28 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385511: comm yay: reading directory lblock 0 Jan 01 22:16:28 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972848 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:28 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385516: comm yay: reading directory lblock 0 Jan 01 22:16:29 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972864 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:29 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385520: comm yay: reading directory lblock 0 Jan 01 22:16:29 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973400 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:30 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386275: comm yay: reading directory lblock 0 Jan 01 22:16:30 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973328 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:30 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385541: comm yay: reading directory lblock 0 Jan 01 22:16:31 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972896 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:31 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385525: comm yay: reading directory lblock 0 Jan 01 22:16:31 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972616 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:31 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385477: comm yay: reading directory lblock 0 Jan 01 22:16:32 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973432 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:32 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386279: comm yay: reading directory lblock 0 Jan 01 22:16:33 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972984 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:33 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385533: comm yay: reading directory lblock 0 Jan 01 22:16:33 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973416 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:33 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386283: comm yay: reading directory lblock 0 Jan 01 22:16:34 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973448 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:34 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386287: comm yay: reading directory lblock 0 Jan 01 22:16:34 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975184 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:34 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385545: comm yay: reading directory lblock 0 Jan 01 22:16:35 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973456 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:35 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386291: comm yay: reading directory lblock 0 Jan 01 22:16:36 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973464 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:36 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386295: comm yay: reading directory lblock 0 Jan 01 22:16:36 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972448 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:36 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385460: comm yay: reading directory lblock 0 Jan 01 22:16:37 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973264 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:37 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385537: comm yay: reading directory lblock 0 Jan 01 22:16:37 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972432 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:38 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385549: comm yay: reading directory lblock 0 Jan 01 22:16:38 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972440 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:38 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385553: comm yay: reading directory lblock 0 Jan 01 22:16:39 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972464 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:39 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385557: comm yay: reading directory lblock 0 Jan 01 22:16:39 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972480 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:39 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385565: comm yay: reading directory lblock 0 Jan 01 22:16:40 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:40 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386299: comm yay: reading directory lblock 0 Jan 01 22:16:41 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:41 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385561: comm yay: reading directory lblock 0 Jan 01 22:16:41 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973496 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:41 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386311: comm yay: reading directory lblock 0 Jan 01 22:16:42 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973504 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:42 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386315: comm yay: reading directory lblock 0 Jan 01 22:16:42 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973480 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:42 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386303: comm yay: reading directory lblock 0 Jan 01 22:16:43 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972488 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:43 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385569: comm yay: reading directory lblock 0 Jan 01 22:16:44 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972624 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:44 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385481: comm yay: reading directory lblock 0 Jan 01 22:16:44 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975536 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:44 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385574: comm yay: reading directory lblock 0 Jan 01 22:16:45 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973520 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:45 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386323: comm yay: reading directory lblock 0 Jan 01 22:16:45 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975616 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:45 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385582: comm yay: reading directory lblock 0 Jan 01 22:16:46 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973536 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:46 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386331: comm yay: reading directory lblock 0 Jan 01 22:16:47 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973320 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:47 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386222: comm yay: reading directory lblock 0 Jan 01 22:16:47 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975704 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:47 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385586: comm yay: reading directory lblock 0 Jan 01 22:16:48 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973304 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:48 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386214: comm yay: reading directory lblock 0 Jan 01 22:16:49 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972336 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:49 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386152: comm yay: reading directory lblock 0 Jan 01 22:16:49 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972568 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:49 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385473: comm yay: reading directory lblock 0 Jan 01 22:16:50 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972512 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:50 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385590: comm yay: reading directory lblock 0 Jan 01 22:16:50 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972520 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:50 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385597: comm yay: reading directory lblock 0 Jan 01 22:16:51 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:16:51 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:16:51 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972640 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:51 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385486: comm yay: reading directory lblock 0 Jan 01 22:16:52 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972544 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:52 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385602: comm yay: reading directory lblock 0 Jan 01 22:16:52 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973560 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:52 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386343: comm yay: reading directory lblock 0 Jan 01 22:16:53 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973352 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:53 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386238: comm yay: reading directory lblock 0 Jan 01 22:16:53 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974592 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:53 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386347: comm yay: reading directory lblock 0 Jan 01 22:16:54 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974600 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:54 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386351: comm yay: reading directory lblock 0 Jan 01 22:16:54 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:16:54 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:16:55 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975528 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:55 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385614: comm yay: reading directory lblock 0 Jan 01 22:16:55 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974608 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:55 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386355: comm yay: reading directory lblock 0 Jan 01 22:16:56 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973288 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:56 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386206: comm yay: reading directory lblock 0 Jan 01 22:16:57 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973296 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:57 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386210: comm yay: reading directory lblock 0 Jan 01 22:16:57 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975520 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:57 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385610: comm yay: reading directory lblock 0 Jan 01 22:16:58 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973176 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:58 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386161: comm yay: reading directory lblock 0 Jan 01 22:16:58 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974616 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:58 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386359: comm yay: reading directory lblock 0 Jan 01 22:16:59 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973440 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:16:59 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386690: comm yay: reading directory lblock 0 Jan 01 22:17:00 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973344 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:00 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385618: comm yay: reading directory lblock 0 Jan 01 22:17:00 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973544 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:00 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386698: comm yay: reading directory lblock 0 Jan 01 22:17:01 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973424 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:01 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385622: comm yay: reading directory lblock 0 Jan 01 22:17:01 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973528 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:01 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386694: comm yay: reading directory lblock 0 Jan 01 22:17:02 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973384 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:02 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386270: comm yay: reading directory lblock 0 Jan 01 22:17:03 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973552 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:03 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386364: comm yay: reading directory lblock 0 Jan 01 22:17:03 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973488 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:03 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385626: comm yay: reading directory lblock 0 Jan 01 22:17:04 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973336 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:04 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386230: comm yay: reading directory lblock 0 Jan 01 22:17:05 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972688 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:05 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385495: comm yay: reading directory lblock 0 Jan 01 22:17:05 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974648 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:05 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386377: comm yay: reading directory lblock 0 Jan 01 22:17:06 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973216 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:06 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386169: comm yay: reading directory lblock 0 Jan 01 22:17:06 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973512 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:06 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385630: comm yay: reading directory lblock 0 Jan 01 22:17:07 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973224 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:07 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386173: comm yay: reading directory lblock 0 Jan 01 22:17:08 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973256 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:08 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386190: comm yay: reading directory lblock 0 Jan 01 22:17:08 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973232 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:08 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386177: comm yay: reading directory lblock 0 Jan 01 22:17:09 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975888 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:09 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385634: comm yay: reading directory lblock 0 Jan 01 22:17:09 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973248 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:09 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386186: comm yay: reading directory lblock 0 Jan 01 22:17:10 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973272 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:10 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386198: comm yay: reading directory lblock 0 Jan 01 22:17:11 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975896 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:11 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385638: comm yay: reading directory lblock 0 Jan 01 22:17:11 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975552 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:11 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385578: comm yay: reading directory lblock 0 Jan 01 22:17:12 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972656 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:12 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385490: comm yay: reading directory lblock 0 Jan 01 22:17:12 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972576 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:12 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385650: comm yay: reading directory lblock 0 Jan 01 22:17:13 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972552 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:13 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385606: comm yay: reading directory lblock 0 Jan 01 22:17:14 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974656 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:14 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386381: comm yay: reading directory lblock 0 Jan 01 22:17:14 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972584 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:14 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385654: comm yay: reading directory lblock 0 Jan 01 22:17:15 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972592 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:15 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385659: comm yay: reading directory lblock 0 Jan 01 22:17:16 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973392 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:16 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386258: comm yay: reading directory lblock 0 Jan 01 22:17:16 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974672 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:16 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386389: comm yay: reading directory lblock 0 Jan 01 22:17:17 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972600 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:17 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385664: comm yay: reading directory lblock 0 Jan 01 22:17:17 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974688 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:18 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386397: comm yay: reading directory lblock 0 Jan 01 22:17:18 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974680 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:18 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386393: comm yay: reading directory lblock 0 Jan 01 22:17:18 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:17:18 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:17:19 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974696 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:19 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386402: comm yay: reading directory lblock 0 Jan 01 22:17:19 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972952 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:19 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385529: comm yay: reading directory lblock 0 Jan 01 22:17:29 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974632 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:29 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386791: comm git: reading directory lblock 0 Jan 01 22:17:29 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974960 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:29 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386472: comm git: reading directory lblock 0 Jan 01 22:17:30 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974960 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:30 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386472: comm git: reading directory lblock 0 Jan 01 22:17:30 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974968 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:31 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386474: comm git: reading directory lblock 0 Jan 01 22:17:31 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974968 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:31 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386474: comm git: reading directory lblock 0 Jan 01 22:17:32 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974976 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:32 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386476: comm git: reading directory lblock 0 Jan 01 22:17:32 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974976 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:32 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386476: comm git: reading directory lblock 0 Jan 01 22:17:33 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974984 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:33 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386478: comm git: reading directory lblock 0 Jan 01 22:17:34 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974984 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:34 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386478: comm git: reading directory lblock 0 Jan 01 22:17:34 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974992 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:34 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386480: comm git: reading directory lblock 0 Jan 01 22:17:35 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974992 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:35 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386480: comm git: reading directory lblock 0 Jan 01 22:17:35 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975000 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:35 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386482: comm git: reading directory lblock 0 Jan 01 22:17:36 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975000 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:36 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386482: comm git: reading directory lblock 0 Jan 01 22:17:36 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:17:36 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:17:36 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:17:36 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:17:37 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974632 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:37 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386791: lblock 0: comm git: error -5 reading directory block Jan 01 22:17:37 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974968 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:37 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386474: lblock 0: comm git: error -5 reading directory block Jan 01 22:17:38 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974984 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:38 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386478: lblock 0: comm git: error -5 reading directory block Jan 01 22:17:38 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974960 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:38 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386472: lblock 0: comm git: error -5 reading directory block Jan 01 22:17:39 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974992 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:39 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386480: lblock 0: comm git: error -5 reading directory block Jan 01 22:17:40 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974976 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:40 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386476: lblock 0: comm git: error -5 reading directory block Jan 01 22:17:40 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975000 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:40 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386482: lblock 0: comm git: error -5 reading directory block Jan 01 22:17:41 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:41 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386412: comm git: reading directory lblock 0 Jan 01 22:17:41 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:41 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386412: lblock 0: comm git: error -5 reading directory block Jan 01 22:17:42 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:17:42 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:17:42 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:17:42 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:17:42 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974704 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:42 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386406: lblock 0: comm git: error -5 reading directory block Jan 01 22:17:42 the-nexus budgie-panel.desktop[1096]: ###!!! [Parent][DispatchAsyncMessage] Error: PBackgroundIDBDatabase::Msg_PBackgroundIDBTransactionConstructor Value error: message was deserialized, but contained an illegal value Jan 01 22:17:42 the-nexus budgie-panel.desktop[1096]: ###!!! [Parent][DispatchAsyncMessage] Error: PBackgroundIDBDatabase::Msg_PBackgroundIDBTransactionConstructor Value error: message was deserialized, but contained an illegal value Jan 01 22:17:43 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974752 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:43 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386418: lblock 0: comm git: error -5 reading directory block Jan 01 22:17:43 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:43 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386412: comm git: reading directory lblock 0 Jan 01 22:17:43 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:17:43 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:17:44 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974704 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:44 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386406: comm git: reading directory lblock 0 Jan 01 22:17:45 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:45 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386412: comm git: reading directory lblock 0 Jan 01 22:17:45 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974752 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:45 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386418: comm git: reading directory lblock 0 Jan 01 22:17:46 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974704 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:46 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386406: comm git: reading directory lblock 0 Jan 01 22:17:46 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974704 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:46 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386406: comm git: reading directory lblock 0 Jan 01 22:17:47 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:17:47 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:17:47 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:17:47 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:17:47 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:47 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386412: comm git: reading directory lblock 0 Jan 01 22:17:48 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974704 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:48 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386406: comm git: reading directory lblock 0 Jan 01 22:17:48 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974760 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:48 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386420: comm git: reading directory lblock 0 Jan 01 22:17:49 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974760 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:49 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386420: comm git: reading directory lblock 0 Jan 01 22:17:49 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:50 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386412: comm git: reading directory lblock 0 Jan 01 22:17:50 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:17:50 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:17:50 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974704 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:50 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386406: comm git: reading directory lblock 0 Jan 01 22:17:51 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974704 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:51 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386406: comm git: reading directory lblock 0 Jan 01 22:17:51 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:51 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386412: comm git: reading directory lblock 0 Jan 01 22:17:52 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:52 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386412: comm git: reading directory lblock 0 Jan 01 22:17:52 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974752 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:52 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386418: comm git: reading directory lblock 0 Jan 01 22:17:53 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:53 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386412: comm git: reading directory lblock 0 Jan 01 22:17:54 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974704 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:54 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386406: comm git: reading directory lblock 0 Jan 01 22:17:54 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:54 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386412: comm git: reading directory lblock 0 Jan 01 22:17:55 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974752 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:55 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386418: comm git: reading directory lblock 0 Jan 01 22:17:56 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974952 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:56 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386470: comm git: reading directory lblock 0 Jan 01 22:17:57 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974952 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:57 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386470: comm git: reading directory lblock 0 Jan 01 22:17:57 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974952 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:58 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386470: comm git: reading directory lblock 0 Jan 01 22:17:58 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974952 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:58 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386470: comm git: reading directory lblock 0 Jan 01 22:17:59 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974952 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:59 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386470: comm git: reading directory lblock 0 Jan 01 22:17:59 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974952 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:17:59 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386470: comm git: reading directory lblock 0 Jan 01 22:18:01 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975016 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:01 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386487: comm git: reading directory lblock 0 Jan 01 22:18:02 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975016 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:02 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386487: comm git: reading directory lblock 0 Jan 01 22:18:02 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975024 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:02 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386490: comm git: reading directory lblock 0 Jan 01 22:18:03 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975024 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:03 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386490: comm git: reading directory lblock 0 Jan 01 22:18:04 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975032 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:04 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386493: comm git: reading directory lblock 0 Jan 01 22:18:04 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975032 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:04 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386493: comm git: reading directory lblock 0 Jan 01 22:18:05 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975040 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:05 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386496: comm git: reading directory lblock 0 Jan 01 22:18:05 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975040 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:05 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386496: comm git: reading directory lblock 0 Jan 01 22:18:06 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975048 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:06 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386499: comm git: reading directory lblock 0 Jan 01 22:18:07 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975056 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:07 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386502: comm git: reading directory lblock 0 Jan 01 22:18:07 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975056 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:07 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386502: comm git: reading directory lblock 0 Jan 01 22:18:08 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975064 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:08 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386505: comm git: reading directory lblock 0 Jan 01 22:18:08 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975072 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:09 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386507: comm git: reading directory lblock 0 Jan 01 22:18:09 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975080 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:09 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386510: comm git: reading directory lblock 0 Jan 01 22:18:10 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975088 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:10 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386512: comm git: reading directory lblock 0 Jan 01 22:18:10 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975096 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:10 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386514: comm git: reading directory lblock 0 Jan 01 22:18:11 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975104 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:11 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386516: comm git: reading directory lblock 0 Jan 01 22:18:11 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975104 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:12 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386516: comm git: reading directory lblock 0 Jan 01 22:18:12 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975112 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:12 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386519: comm git: reading directory lblock 0 Jan 01 22:18:13 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975120 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:13 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386521: comm git: reading directory lblock 0 Jan 01 22:18:13 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975128 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:13 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386523: comm git: reading directory lblock 0 Jan 01 22:18:14 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975136 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:14 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386525: comm git: reading directory lblock 0 Jan 01 22:18:15 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975144 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:15 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386527: comm git: reading directory lblock 0 Jan 01 22:18:15 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975144 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:15 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386527: comm git: reading directory lblock 0 Jan 01 22:18:16 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975152 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:16 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386530: comm git: reading directory lblock 0 Jan 01 22:18:16 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975160 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:16 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386532: comm git: reading directory lblock 0 Jan 01 22:18:17 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975160 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:17 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386532: comm git: reading directory lblock 0 Jan 01 22:18:18 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975168 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:18 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386535: comm git: reading directory lblock 0 Jan 01 22:18:18 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975176 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:18 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386538: comm git: reading directory lblock 0 Jan 01 22:18:19 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975176 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:19 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386538: comm git: reading directory lblock 0 Jan 01 22:18:19 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975008 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:19 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386529: comm git: reading directory lblock 0 Jan 01 22:18:20 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975104 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:20 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386516: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:21 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975032 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:21 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386493: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:21 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975176 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:21 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386538: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:22 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975112 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:22 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386519: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:22 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975152 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:22 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386530: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:23 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975008 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:23 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386529: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:24 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975160 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:24 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386532: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:24 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975072 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:24 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386507: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:25 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975048 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:25 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386499: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:26 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975080 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:26 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386510: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:26 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975144 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:26 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386527: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:27 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975024 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:27 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386490: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:27 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975088 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:27 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386512: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:28 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975120 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:28 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386521: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:29 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975040 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:29 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386496: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:29 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975128 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:29 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386523: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:30 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975064 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:30 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386505: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:30 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975168 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:30 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386535: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:31 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975056 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:31 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386502: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:32 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975016 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:32 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386487: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:32 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975136 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:32 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386525: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:33 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975096 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:33 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386514: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:33 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975104 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:33 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386516: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:34 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975032 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:34 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386493: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:35 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975176 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:35 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386538: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:35 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975112 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:35 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386519: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:36 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975152 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:36 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386530: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:37 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975008 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:37 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386529: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:37 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975160 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:37 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386532: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:38 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975072 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:38 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386507: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:38 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975048 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:38 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386499: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:39 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:18:39 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:18:39 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975080 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:39 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386510: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:40 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975144 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:40 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386527: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:40 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975024 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:40 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386490: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:41 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975088 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:41 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386512: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:41 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975120 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:41 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386521: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:42 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:18:42 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:18:42 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975040 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:42 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386496: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:43 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975128 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:43 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386523: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:43 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975064 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:43 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386505: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:44 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975168 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:44 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386535: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:44 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975056 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:44 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386502: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:45 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975016 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:45 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386487: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:46 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975136 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:46 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386525: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:46 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975096 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:46 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386514: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:47 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:18:47 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:18:48 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975104 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:48 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386516: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:48 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975032 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:48 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386493: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:49 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975176 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:49 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386538: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:50 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975112 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:50 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386519: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:50 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975152 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:50 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386530: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:51 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975008 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:51 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386529: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:51 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975160 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:51 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386532: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:52 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975072 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:52 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386507: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:53 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975048 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:53 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386499: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:53 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975080 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:53 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386510: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:54 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975144 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:54 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386527: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:54 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975024 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:54 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386490: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:55 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975088 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:55 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386512: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:56 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975120 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:56 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386521: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:56 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975040 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:56 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386496: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:57 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975128 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:57 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386523: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:58 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975064 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:58 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386505: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:58 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975168 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:58 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386535: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:59 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975056 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:59 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386502: lblock 0: comm git: error -5 reading directory block Jan 01 22:18:59 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975016 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:18:59 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386487: lblock 0: comm git: error -5 reading directory block Jan 01 22:19:00 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975136 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:00 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386525: lblock 0: comm git: error -5 reading directory block Jan 01 22:19:01 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975096 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:01 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386514: lblock 0: comm git: error -5 reading directory block Jan 01 22:19:01 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975016 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:01 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386487: comm git: reading directory lblock 0 Jan 01 22:19:02 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975016 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:02 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386487: comm git: reading directory lblock 0 Jan 01 22:19:02 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975024 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:03 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386490: comm git: reading directory lblock 0 Jan 01 22:19:03 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975024 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:03 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386490: comm git: reading directory lblock 0 Jan 01 22:19:04 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975032 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:04 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386493: comm git: reading directory lblock 0 Jan 01 22:19:04 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975032 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:04 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386493: comm git: reading directory lblock 0 Jan 01 22:19:05 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975040 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:05 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386496: comm git: reading directory lblock 0 Jan 01 22:19:05 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975040 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:06 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386496: comm git: reading directory lblock 0 Jan 01 22:19:06 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975048 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:06 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386499: comm git: reading directory lblock 0 Jan 01 22:19:07 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975056 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:07 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386502: comm git: reading directory lblock 0 Jan 01 22:19:07 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975056 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:07 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386502: comm git: reading directory lblock 0 Jan 01 22:19:08 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975064 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:08 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386505: comm git: reading directory lblock 0 Jan 01 22:19:09 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975072 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:09 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386507: comm git: reading directory lblock 0 Jan 01 22:19:09 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975080 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:09 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386510: comm git: reading directory lblock 0 Jan 01 22:19:10 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975088 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:10 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386512: comm git: reading directory lblock 0 Jan 01 22:19:10 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975096 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:10 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386514: comm git: reading directory lblock 0 Jan 01 22:19:11 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975104 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:11 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386516: comm git: reading directory lblock 0 Jan 01 22:19:12 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975104 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:12 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386516: comm git: reading directory lblock 0 Jan 01 22:19:12 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975112 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:12 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386519: comm git: reading directory lblock 0 Jan 01 22:19:13 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975120 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:13 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386521: comm git: reading directory lblock 0 Jan 01 22:19:13 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975128 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:13 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386523: comm git: reading directory lblock 0 Jan 01 22:19:14 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975136 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:14 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386525: comm git: reading directory lblock 0 Jan 01 22:19:15 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975144 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:15 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386527: comm git: reading directory lblock 0 Jan 01 22:19:15 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975144 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:15 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386527: comm git: reading directory lblock 0 Jan 01 22:19:16 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975152 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:16 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386530: comm git: reading directory lblock 0 Jan 01 22:19:17 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975160 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:17 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386532: comm git: reading directory lblock 0 Jan 01 22:19:17 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975160 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:17 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386532: comm git: reading directory lblock 0 Jan 01 22:19:18 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975168 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:18 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386535: comm git: reading directory lblock 0 Jan 01 22:19:18 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975176 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:18 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386538: comm git: reading directory lblock 0 Jan 01 22:19:19 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975176 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:19 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386538: comm git: reading directory lblock 0 Jan 01 22:19:20 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975008 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:19:20 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386529: comm git: reading directory lblock 0 Jan 01 22:20:51 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:20:51 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:22:04 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.89' (uid=0 pid=7874 comm="sudo pacman -S -y -u --config /etc/pacman.conf -- ") Jan 01 22:22:04 the-nexus dbus-daemon[395]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found. Jan 01 22:22:04 the-nexus sudo[7874]: pam_systemd_home(sudo:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found. Jan 01 22:22:08 the-nexus sudo[7874]: pam_unix(sudo:auth): authentication failure; logname= uid=1000 euid=0 tty=/dev/pts/0 ruser=synth rhost= user=synth Jan 01 22:22:08 the-nexus audit[7874]: USER_AUTH pid=7874 uid=1000 auid=1000 ses=3 msg='op=PAM:authentication grantors=? acct="synth" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=failed' Jan 01 22:22:08 the-nexus kernel: audit: type=1100 audit(1641093728.963:101): pid=7874 uid=1000 auid=1000 ses=3 msg='op=PAM:authentication grantors=? acct="synth" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=failed' Jan 01 22:22:15 the-nexus audit[7874]: USER_AUTH pid=7874 uid=1000 auid=1000 ses=3 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="synth" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:22:15 the-nexus audit[7874]: USER_ACCT pid=7874 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="synth" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:22:15 the-nexus sudo[7874]: synth : TTY=pts/0 ; PWD=/home/synth ; USER=root ; COMMAND=/usr/bin/pacman -S -y -u --config /etc/pacman.conf -- Jan 01 22:22:15 the-nexus audit[7874]: CRED_REFR pid=7874 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:22:15 the-nexus kernel: audit: type=1100 audit(1641093735.415:102): pid=7874 uid=1000 auid=1000 ses=3 msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct="synth" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:22:15 the-nexus kernel: audit: type=1101 audit(1641093735.415:103): pid=7874 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="synth" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:22:15 the-nexus kernel: audit: type=1110 audit(1641093735.415:104): pid=7874 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:22:15 the-nexus sudo[7874]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Jan 01 22:22:15 the-nexus audit[7874]: USER_START pid=7874 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:22:15 the-nexus kernel: audit: type=1105 audit(1641093735.418:105): pid=7874 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:22:16 the-nexus sudo[7874]: pam_unix(sudo:session): session closed for user root Jan 01 22:22:16 the-nexus audit[7874]: USER_END pid=7874 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:22:16 the-nexus audit[7874]: CRED_DISP pid=7874 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:22:16 the-nexus kernel: audit: type=1106 audit(1641093736.655:106): pid=7874 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:22:16 the-nexus kernel: audit: type=1104 audit(1641093736.655:107): pid=7874 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success' Jan 01 22:22:17 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975688 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:17 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386541: comm yay: reading directory lblock 0 Jan 01 22:22:24 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974264 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:24 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386165: comm yay: reading directory lblock 0 Jan 01 22:22:24 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973360 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:24 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386242: comm yay: reading directory lblock 0 Jan 01 22:22:25 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972504 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:25 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385465: comm yay: reading directory lblock 0 Jan 01 22:22:26 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973368 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:26 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386246: comm yay: reading directory lblock 0 Jan 01 22:22:26 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972536 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:26 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385469: comm yay: reading directory lblock 0 Jan 01 22:22:27 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973376 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:27 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386250: comm yay: reading directory lblock 0 Jan 01 22:22:27 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972720 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:27 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385499: comm yay: reading directory lblock 0 Jan 01 22:22:28 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972768 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:28 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385503: comm yay: reading directory lblock 0 Jan 01 22:22:29 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972800 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:29 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385507: comm yay: reading directory lblock 0 Jan 01 22:22:29 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973312 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:29 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386254: comm yay: reading directory lblock 0 Jan 01 22:22:30 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972416 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:30 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385436: comm yay: reading directory lblock 0 Jan 01 22:22:30 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973408 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:30 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386266: comm yay: reading directory lblock 0 Jan 01 22:22:31 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973240 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:31 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386181: comm yay: reading directory lblock 0 Jan 01 22:22:32 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972816 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:32 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385511: comm yay: reading directory lblock 0 Jan 01 22:22:32 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972848 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:32 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385516: comm yay: reading directory lblock 0 Jan 01 22:22:33 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972864 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:33 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385520: comm yay: reading directory lblock 0 Jan 01 22:22:33 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973400 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:34 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386275: comm yay: reading directory lblock 0 Jan 01 22:22:34 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973328 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:34 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385541: comm yay: reading directory lblock 0 Jan 01 22:22:35 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972896 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:35 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385525: comm yay: reading directory lblock 0 Jan 01 22:22:35 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972616 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:35 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385477: comm yay: reading directory lblock 0 Jan 01 22:22:36 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973432 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:36 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386279: comm yay: reading directory lblock 0 Jan 01 22:22:37 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972984 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:37 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385533: comm yay: reading directory lblock 0 Jan 01 22:22:37 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973416 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:37 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386283: comm yay: reading directory lblock 0 Jan 01 22:22:38 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973448 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:38 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386287: comm yay: reading directory lblock 0 Jan 01 22:22:38 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975184 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:38 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385545: comm yay: reading directory lblock 0 Jan 01 22:22:39 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973456 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:39 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386291: comm yay: reading directory lblock 0 Jan 01 22:22:40 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973464 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:40 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386295: comm yay: reading directory lblock 0 Jan 01 22:22:40 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972448 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:40 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385460: comm yay: reading directory lblock 0 Jan 01 22:22:41 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973264 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:41 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385537: comm yay: reading directory lblock 0 Jan 01 22:22:41 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972432 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:41 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385549: comm yay: reading directory lblock 0 Jan 01 22:22:42 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972440 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:42 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385553: comm yay: reading directory lblock 0 Jan 01 22:22:43 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972464 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:43 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385557: comm yay: reading directory lblock 0 Jan 01 22:22:43 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972480 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:43 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385565: comm yay: reading directory lblock 0 Jan 01 22:22:44 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:44 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386299: comm yay: reading directory lblock 0 Jan 01 22:22:44 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:45 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385561: comm yay: reading directory lblock 0 Jan 01 22:22:45 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973496 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:45 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386311: comm yay: reading directory lblock 0 Jan 01 22:22:46 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973504 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:46 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386315: comm yay: reading directory lblock 0 Jan 01 22:22:46 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973480 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:46 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386303: comm yay: reading directory lblock 0 Jan 01 22:22:47 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972488 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:47 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385569: comm yay: reading directory lblock 0 Jan 01 22:22:47 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972624 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:48 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385481: comm yay: reading directory lblock 0 Jan 01 22:22:48 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975536 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:48 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385574: comm yay: reading directory lblock 0 Jan 01 22:22:49 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973520 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:49 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386323: comm yay: reading directory lblock 0 Jan 01 22:22:49 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975616 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:49 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385582: comm yay: reading directory lblock 0 Jan 01 22:22:50 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973536 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:50 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386331: comm yay: reading directory lblock 0 Jan 01 22:22:51 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973320 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:51 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386222: comm yay: reading directory lblock 0 Jan 01 22:22:51 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975704 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:51 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385586: comm yay: reading directory lblock 0 Jan 01 22:22:52 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973304 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:52 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386214: comm yay: reading directory lblock 0 Jan 01 22:22:52 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972336 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:52 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386152: comm yay: reading directory lblock 0 Jan 01 22:22:53 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972568 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:53 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385473: comm yay: reading directory lblock 0 Jan 01 22:22:54 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972512 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:54 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385590: comm yay: reading directory lblock 0 Jan 01 22:22:54 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972520 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:54 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385597: comm yay: reading directory lblock 0 Jan 01 22:22:55 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972640 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:55 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385486: comm yay: reading directory lblock 0 Jan 01 22:22:55 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972544 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:55 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385602: comm yay: reading directory lblock 0 Jan 01 22:22:56 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973560 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:56 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386343: comm yay: reading directory lblock 0 Jan 01 22:22:57 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973352 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:57 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386238: comm yay: reading directory lblock 0 Jan 01 22:22:57 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974592 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:57 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386347: comm yay: reading directory lblock 0 Jan 01 22:22:58 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974600 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:58 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386351: comm yay: reading directory lblock 0 Jan 01 22:22:59 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975528 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:59 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385614: comm yay: reading directory lblock 0 Jan 01 22:22:59 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974608 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:22:59 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386355: comm yay: reading directory lblock 0 Jan 01 22:23:00 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973288 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:00 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386206: comm yay: reading directory lblock 0 Jan 01 22:23:00 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973296 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:00 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386210: comm yay: reading directory lblock 0 Jan 01 22:23:01 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975520 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:01 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385610: comm yay: reading directory lblock 0 Jan 01 22:23:02 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973176 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:02 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386161: comm yay: reading directory lblock 0 Jan 01 22:23:02 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974616 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:02 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386359: comm yay: reading directory lblock 0 Jan 01 22:23:03 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973440 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:03 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386690: comm yay: reading directory lblock 0 Jan 01 22:23:03 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973344 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:03 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385618: comm yay: reading directory lblock 0 Jan 01 22:23:04 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973544 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:04 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386698: comm yay: reading directory lblock 0 Jan 01 22:23:05 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973424 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:05 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385622: comm yay: reading directory lblock 0 Jan 01 22:23:05 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973528 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:05 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386694: comm yay: reading directory lblock 0 Jan 01 22:23:06 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973384 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:06 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386270: comm yay: reading directory lblock 0 Jan 01 22:23:06 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973552 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:07 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386364: comm yay: reading directory lblock 0 Jan 01 22:23:07 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973488 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:07 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385626: comm yay: reading directory lblock 0 Jan 01 22:23:08 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973336 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:08 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386230: comm yay: reading directory lblock 0 Jan 01 22:23:08 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972688 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:08 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385495: comm yay: reading directory lblock 0 Jan 01 22:23:09 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974648 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:09 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386377: comm yay: reading directory lblock 0 Jan 01 22:23:09 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973216 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:09 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386169: comm yay: reading directory lblock 0 Jan 01 22:23:10 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973512 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:10 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385630: comm yay: reading directory lblock 0 Jan 01 22:23:11 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973224 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:11 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386173: comm yay: reading directory lblock 0 Jan 01 22:23:11 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973256 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:11 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386190: comm yay: reading directory lblock 0 Jan 01 22:23:12 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973232 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:12 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386177: comm yay: reading directory lblock 0 Jan 01 22:23:13 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975888 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:13 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385634: comm yay: reading directory lblock 0 Jan 01 22:23:13 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973248 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:13 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386186: comm yay: reading directory lblock 0 Jan 01 22:23:14 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973272 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:14 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386198: comm yay: reading directory lblock 0 Jan 01 22:23:14 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975896 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:14 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385638: comm yay: reading directory lblock 0 Jan 01 22:23:15 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975552 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:15 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385578: comm yay: reading directory lblock 0 Jan 01 22:23:16 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972656 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:16 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385490: comm yay: reading directory lblock 0 Jan 01 22:23:16 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972576 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:16 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385650: comm yay: reading directory lblock 0 Jan 01 22:23:17 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972552 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:17 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385606: comm yay: reading directory lblock 0 Jan 01 22:23:17 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974656 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:17 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386381: comm yay: reading directory lblock 0 Jan 01 22:23:18 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972584 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:18 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385654: comm yay: reading directory lblock 0 Jan 01 22:23:19 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972592 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:19 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385659: comm yay: reading directory lblock 0 Jan 01 22:23:19 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973392 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:19 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386258: comm yay: reading directory lblock 0 Jan 01 22:23:20 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974672 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:20 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386389: comm yay: reading directory lblock 0 Jan 01 22:23:20 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972600 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:20 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385664: comm yay: reading directory lblock 0 Jan 01 22:23:21 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974688 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:21 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386397: comm yay: reading directory lblock 0 Jan 01 22:23:22 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974680 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:22 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386393: comm yay: reading directory lblock 0 Jan 01 22:23:22 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974696 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:22 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386402: comm yay: reading directory lblock 0 Jan 01 22:23:23 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972952 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:23 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385529: comm yay: reading directory lblock 0 Jan 01 22:23:52 the-nexus systemd[643]: Started snap.spotify.spotify.376eae4a-705d-4a18-a610-2a31f37e9258.scope. Jan 01 22:23:52 the-nexus audit: BPF prog-id=31 op=LOAD Jan 01 22:23:52 the-nexus audit[8013]: SYSCALL arch=c000003e syscall=321 success=yes exit=9 a0=5 a1=7ffd0fade510 a2=78 a3=1000 items=0 ppid=1 pid=8013 auid=1000 uid=1000 gid=1000 euid=0 suid=0 fsuid=0 egid=0 sgid=1000 fsgid=0 tty=(none) ses=2 comm="snap-confine" exe="/usr/lib/snapd/snap-confine" key=(null) Jan 01 22:23:52 the-nexus audit: PROCTITLE proctitle=2F7573722F6C69622F736E6170642F736E61702D636F6E66696E65002D2D6261736500636F7265313800736E61702E73706F746966792E73706F74696679002F7573722F6C69622F736E6170642F736E61702D657865630073706F74696679 Jan 01 22:23:52 the-nexus kernel: audit: type=1334 audit(1641093832.464:108): prog-id=31 op=LOAD Jan 01 22:23:52 the-nexus kernel: audit: type=1300 audit(1641093832.464:108): arch=c000003e syscall=321 success=yes exit=9 a0=5 a1=7ffd0fade510 a2=78 a3=1000 items=0 ppid=1 pid=8013 auid=1000 uid=1000 gid=1000 euid=0 suid=0 fsuid=0 egid=0 sgid=1000 fsgid=0 tty=(none) ses=2 comm="snap-confine" exe="/usr/lib/snapd/snap-confine" key=(null) Jan 01 22:23:52 the-nexus kernel: audit: type=1327 audit(1641093832.464:108): proctitle=2F7573722F6C69622F736E6170642F736E61702D636F6E66696E65002D2D6261736500636F7265313800736E61702E73706F746966792E73706F74696679002F7573722F6C69622F736E6170642F736E61702D657865630073706F74696679 Jan 01 22:23:52 the-nexus systemd[1]: tmp-snap.rootfs_TTc5XF.mount: Deactivated successfully. Jan 01 22:23:52 the-nexus systemd[1]: Starting Snap Daemon... Jan 01 22:23:52 the-nexus snapd[8070]: AppArmor status: apparmor not enabled Jan 01 22:23:52 the-nexus snapd[8070]: daemon.go:242: started snapd/2.53.4-1 (series 16; classic; devmode) endeavouros/ (amd64) linux/5.15.12-arch1-1. Jan 01 22:23:52 the-nexus kernel: loop8: detected capacity change from 0 to 8 Jan 01 22:23:52 the-nexus snapd[8070]: daemon.go:335: adjusting startup timeout by 1m5s (pessimistic estimate of 30s plus 5s per snap) Jan 01 22:23:53 the-nexus systemd[1]: Started Snap Daemon. Jan 01 22:23:53 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=snapd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:23:53 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.90' (uid=0 pid=8070 comm="/usr/lib/snapd/snapd ") Jan 01 22:23:53 the-nexus kernel: audit: type=1130 audit(1641093833.028:109): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=snapd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:23:53 the-nexus audit: BPF prog-id=32 op=LOAD Jan 01 22:23:53 the-nexus audit: BPF prog-id=33 op=LOAD Jan 01 22:23:53 the-nexus audit: BPF prog-id=34 op=LOAD Jan 01 22:23:53 the-nexus systemd[1]: Starting Time & Date Service... Jan 01 22:23:53 the-nexus kernel: audit: type=1334 audit(1641093833.031:110): prog-id=32 op=LOAD Jan 01 22:23:53 the-nexus kernel: audit: type=1334 audit(1641093833.031:111): prog-id=33 op=LOAD Jan 01 22:23:53 the-nexus kernel: audit: type=1334 audit(1641093833.031:112): prog-id=34 op=LOAD Jan 01 22:23:53 the-nexus dbus-daemon[395]: [system] Successfully activated service 'org.freedesktop.timedate1' Jan 01 22:23:53 the-nexus systemd[1]: Started Time & Date Service. Jan 01 22:23:53 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:23:53 the-nexus kernel: audit: type=1130 audit(1641093833.068:113): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:23:53 the-nexus systemd[1]: tmp-sanity\x2dmountpoint\x2d2008541400.mount: Deactivated successfully. Jan 01 22:23:54 the-nexus spotify[8013]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-PqBUrbuVoK: No such file or directory Jan 01 22:23:54 the-nexus audit[8143]: SECCOMP auid=1000 uid=1000 gid=1000 ses=2 pid=8143 comm="spotify" exe="/snap/spotify/56/usr/share/spotify/spotify" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7fb45d500c7f code=0x50000 Jan 01 22:23:54 the-nexus audit[8143]: SECCOMP auid=1000 uid=1000 gid=1000 ses=2 pid=8143 comm="spotify" exe="/snap/spotify/56/usr/share/spotify/spotify" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7fb45d500c7f code=0x50000 Jan 01 22:23:54 the-nexus audit[8143]: SECCOMP auid=1000 uid=1000 gid=1000 ses=2 pid=8143 comm="spotify" exe="/snap/spotify/56/usr/share/spotify/spotify" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7fb45d500c7f code=0x50000 Jan 01 22:23:54 the-nexus kernel: audit: type=1326 audit(1641093834.269:114): auid=1000 uid=1000 gid=1000 ses=2 pid=8143 comm="spotify" exe="/snap/spotify/56/usr/share/spotify/spotify" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7fb45d500c7f code=0x50000 Jan 01 22:23:54 the-nexus kernel: audit: type=1326 audit(1641093834.269:115): auid=1000 uid=1000 gid=1000 ses=2 pid=8143 comm="spotify" exe="/snap/spotify/56/usr/share/spotify/spotify" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7fb45d500c7f code=0x50000 Jan 01 22:23:54 the-nexus audit[8143]: SECCOMP auid=1000 uid=1000 gid=1000 ses=2 pid=8143 comm="spotify" exe="/snap/spotify/56/usr/share/spotify/spotify" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7fb45d500c7f code=0x50000 Jan 01 22:23:54 the-nexus snapd[8070]: storehelpers.go:710: cannot refresh: snap has no updates available: "bare", "core18", "discord", "gnome-3-28-1804", "gtk-common-themes", "snapd", "spotify" Jan 01 22:23:54 the-nexus snapd[8070]: autorefresh.go:536: auto-refresh: all snaps are up-to-date Jan 01 22:23:55 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972736 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:55 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16387201: comm Core Thread: reading directory lblock 0 Jan 01 22:23:56 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972736 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:56 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16387201: comm threaded-ml: reading directory lblock 0 Jan 01 22:23:57 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972736 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:23:57 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16387201: comm threaded-ml: reading directory lblock 0 Jan 01 22:23:57 the-nexus budgie-panel.desktop[8013]: Failed to load cookie file from cookie: Input/output error Jan 01 22:23:57 the-nexus gnome-keyring-daemon[653]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered Jan 01 22:24:23 the-nexus systemd[1]: systemd-timedated.service: Deactivated successfully. Jan 01 22:24:23 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:24:23 the-nexus kernel: kauditd_printk_skb: 2 callbacks suppressed Jan 01 22:24:23 the-nexus kernel: audit: type=1131 audit(1641093863.101:118): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:24:23 the-nexus audit: BPF prog-id=0 op=UNLOAD Jan 01 22:24:23 the-nexus audit: BPF prog-id=0 op=UNLOAD Jan 01 22:24:23 the-nexus audit: BPF prog-id=0 op=UNLOAD Jan 01 22:24:23 the-nexus kernel: audit: type=1334 audit(1641093863.124:119): prog-id=0 op=UNLOAD Jan 01 22:24:23 the-nexus kernel: audit: type=1334 audit(1641093863.124:120): prog-id=0 op=UNLOAD Jan 01 22:24:23 the-nexus kernel: audit: type=1334 audit(1641093863.124:121): prog-id=0 op=UNLOAD Jan 01 22:29:20 the-nexus systemd[1]: Starting Cleanup of Temporary Directories... Jan 01 22:29:21 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973576 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:21 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385795: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:22 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973616 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:22 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385801: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:22 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974160 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:22 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385806: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:23 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974176 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:23 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385809: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:24 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974192 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:24 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385812: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:24 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974272 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:24 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385815: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:25 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974288 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:25 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385818: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:25 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974304 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:25 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385821: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:26 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974328 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:26 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385825: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:27 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972424 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:27 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385828: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:27 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972456 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:27 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385833: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:28 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972496 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:28 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385839: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:28 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972528 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:28 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385844: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:29 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974336 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:29 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385847: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:30 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974352 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:30 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385850: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:30 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974368 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:30 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385853: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:31 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974400 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:31 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385858: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:31 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974432 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:31 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385570: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:32 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:32 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385869: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:33 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974496 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:33 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385873: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:33 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974512 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:33 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385876: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:34 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974528 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:34 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385879: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:34 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974560 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:34 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385884: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:35 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974576 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:35 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385887: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:36 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972560 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:36 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385894: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:36 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972608 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:36 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385902: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:37 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972648 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:37 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385908: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:38 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972664 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:38 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385911: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:38 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972696 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:38 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385916: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:39 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:39 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385921: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:39 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972744 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:39 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385924: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:40 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972776 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:40 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385929: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:41 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972808 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:41 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385934: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:41 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972824 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:41 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385937: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:42 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972856 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:42 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385942: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:42 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972872 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:42 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385945: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:43 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972904 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:43 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385950: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:44 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972944 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:44 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385956: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:44 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972976 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:44 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385961: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:45 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973016 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:45 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385967: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:45 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973048 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:45 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385972: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:46 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973064 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:46 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385975: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:47 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973080 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:47 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385978: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:47 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973096 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:47 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385981: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:48 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973112 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:48 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385984: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:49 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973152 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 22:29:49 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385990: lblock 0: comm systemd-tmpfile: error -5 reading directory block Jan 01 22:29:49 the-nexus systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jan 01 22:29:49 the-nexus systemd[1]: Finished Cleanup of Temporary Directories. Jan 01 22:29:49 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:29:49 the-nexus kernel: audit: type=1130 audit(1641094189.053:122): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:29:49 the-nexus kernel: audit: type=1131 audit(1641094189.053:123): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:29:49 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 22:33:17 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-54 noise=9999 txrate=650000 Jan 01 22:46:09 the-nexus budgie-panel.desktop[1096]: ###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv Jan 01 22:46:09 the-nexus budgie-panel.desktop[1096]: ###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv Jan 01 22:46:09 the-nexus budgie-panel.desktop[1096]: ###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv Jan 01 22:46:09 the-nexus budgie-panel.desktop[1096]: ###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv Jan 01 22:46:09 the-nexus budgie-panel.desktop[1096]: ###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv Jan 01 22:46:11 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:46:11 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:46:11 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:46:11 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:46:17 the-nexus budgie-panel.desktop[8599]: ATTENTION: default value of option mesa_glthread overridden by environment. Jan 01 22:46:17 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:46:17 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:46:17 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:46:17 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:46:26 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:46:26 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:46:30 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:46:30 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:48:08 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:48:08 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:48:08 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:48:08 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:48:10 the-nexus budgie-panel.desktop[8751]: ATTENTION: default value of option mesa_glthread overridden by environment. Jan 01 22:48:10 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:48:10 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:48:16 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:48:16 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:48:20 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:48:20 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:48:22 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:48:22 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:48:28 the-nexus budgie-panel.desktop[9004]: ATTENTION: default value of option mesa_glthread overridden by environment. Jan 01 22:48:28 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:48:28 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:50:07 the-nexus budgie-panel.desktop[9079]: ATTENTION: default value of option mesa_glthread overridden by environment. Jan 01 22:50:07 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:50:07 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:50:07 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:50:07 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:50:46 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:50:46 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:50:48 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:50:48 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:52:42 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:52:42 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:52:48 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:52:48 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:53:20 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:53:20 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:53:26 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:53:26 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:53:49 the-nexus budgie-panel.desktop[9472]: ATTENTION: default value of option mesa_glthread overridden by environment. Jan 01 22:55:34 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:55:34 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:55:36 the-nexus budgie-panel.desktop[1096]: ###!!! [Parent][MessageChannel] Error: (msgtype=0x390078,name=PContent::Msg_DestroyBrowsingContextGroup) Closed channel: cannot send/recv Jan 01 22:55:41 the-nexus budgie-panel.desktop[9228]: ATTENTION: default value of option mesa_glthread overridden by environment. Jan 01 22:59:40 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:59:40 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 22:59:42 the-nexus budgie-panel.desktop[9566]: ATTENTION: default value of option mesa_glthread overridden by environment. Jan 01 22:59:55 the-nexus budgie-panel.desktop[9566]: ATTENTION: default value of option mesa_glthread overridden by environment. Jan 01 23:00:18 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:00:18 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:00:18 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:00:18 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:00:18 the-nexus budgie-panel.desktop[9718]: ATTENTION: default value of option mesa_glthread overridden by environment. Jan 01 23:03:38 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:03:38 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:03:46 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:03:46 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:03:54 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:03:54 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:03:57 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:03:57 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:04:27 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:04:27 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:04:34 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:04:34 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:04:36 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:04:36 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:05:29 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:05:29 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:13:29 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:13:29 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:13:36 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:13:36 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:14:26 the-nexus NetworkManager[396]: [1641096866.9660] dhcp4 (wlan0): state changed bound -> extended, address=192.168.0.146 Jan 01 23:14:26 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=396 comm="/usr/bin/NetworkManager --no-daemon ") Jan 01 23:14:26 the-nexus systemd[1]: Starting Network Manager Script Dispatcher Service... Jan 01 23:14:26 the-nexus dbus-daemon[395]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 01 23:14:26 the-nexus systemd[1]: Started Network Manager Script Dispatcher Service. Jan 01 23:14:26 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 23:14:26 the-nexus kernel: audit: type=1130 audit(1641096866.992:124): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 23:14:36 the-nexus systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Jan 01 23:14:36 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 23:14:36 the-nexus kernel: audit: type=1131 audit(1641096876.789:125): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 23:20:58 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:20:58 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:21:07 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:21:07 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:21:08 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:21:08 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:21:09 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:21:09 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:21:09 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:21:09 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:21:09 the-nexus rtkit-daemon[815]: Successfully made thread 11003 of process 10662 owned by '1000' RT at priority 10. Jan 01 23:21:09 the-nexus rtkit-daemon[815]: Supervising 8 threads of 5 processes of 1 users. Jan 01 23:21:22 the-nexus budgie-wm.desktop[831]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). Jan 01 23:21:22 the-nexus budgie-wm.desktop[831]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). Jan 01 23:21:22 the-nexus budgie-wm.desktop[831]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). Jan 01 23:22:09 the-nexus budgie-wm[831]: Can't update stage views actor [:0x5620a2a77330] is on because it needs an allocation. Jan 01 23:22:09 the-nexus budgie-wm[831]: Can't update stage views actor [:0x5620a31cc360] is on because it needs an allocation. Jan 01 23:22:09 the-nexus budgie-wm[831]: Can't update stage views actor [:0x5620a336d720] is on because it needs an allocation. Jan 01 23:22:09 the-nexus budgie-wm[831]: Can't update stage views actor [:0x5620a31d74c0] is on because it needs an allocation. Jan 01 23:25:49 the-nexus budgie-wm.desktop[831]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). Jan 01 23:25:49 the-nexus budgie-wm.desktop[831]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). Jan 01 23:25:49 the-nexus budgie-wm.desktop[831]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). Jan 01 23:27:19 the-nexus budgie-wm[831]: Can't update stage views actor [:0x5620a2a77330] is on because it needs an allocation. Jan 01 23:27:19 the-nexus budgie-wm[831]: Can't update stage views actor [:0x5620a31cc360] is on because it needs an allocation. Jan 01 23:27:19 the-nexus budgie-wm[831]: Can't update stage views actor [:0x5620a336d720] is on because it needs an allocation. Jan 01 23:27:19 the-nexus budgie-wm[831]: Can't update stage views actor [:0x5620a31d74c0] is on because it needs an allocation. Jan 01 23:28:03 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:28:03 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:28:03 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:28:03 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:28:17 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974632 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:17 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386791: comm git: reading directory lblock 0 Jan 01 23:28:18 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974960 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:18 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386472: comm git: reading directory lblock 0 Jan 01 23:28:18 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974960 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:18 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386472: comm git: reading directory lblock 0 Jan 01 23:28:19 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974968 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:19 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386474: comm git: reading directory lblock 0 Jan 01 23:28:20 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974968 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:20 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386474: comm git: reading directory lblock 0 Jan 01 23:28:20 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974976 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:20 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386476: comm git: reading directory lblock 0 Jan 01 23:28:21 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974976 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:21 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386476: comm git: reading directory lblock 0 Jan 01 23:28:21 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974984 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:22 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386478: comm git: reading directory lblock 0 Jan 01 23:28:22 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974984 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:22 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386478: comm git: reading directory lblock 0 Jan 01 23:28:23 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974992 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:23 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386480: comm git: reading directory lblock 0 Jan 01 23:28:23 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974992 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:23 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386480: comm git: reading directory lblock 0 Jan 01 23:28:24 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975000 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:24 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386482: comm git: reading directory lblock 0 Jan 01 23:28:24 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975000 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:24 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386482: comm git: reading directory lblock 0 Jan 01 23:28:25 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974632 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:25 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386791: lblock 0: comm git: error -5 reading directory block Jan 01 23:28:26 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974968 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:26 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386474: lblock 0: comm git: error -5 reading directory block Jan 01 23:28:26 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974984 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:26 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386478: lblock 0: comm git: error -5 reading directory block Jan 01 23:28:27 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974960 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:27 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386472: lblock 0: comm git: error -5 reading directory block Jan 01 23:28:28 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974992 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:28 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386480: lblock 0: comm git: error -5 reading directory block Jan 01 23:28:28 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974976 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:28 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386476: lblock 0: comm git: error -5 reading directory block Jan 01 23:28:29 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975000 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:29 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386482: lblock 0: comm git: error -5 reading directory block Jan 01 23:28:29 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:29 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386412: comm git: reading directory lblock 0 Jan 01 23:28:30 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:30 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386412: lblock 0: comm git: error -5 reading directory block Jan 01 23:28:31 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974704 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:31 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386406: lblock 0: comm git: error -5 reading directory block Jan 01 23:28:31 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974752 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:31 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386418: lblock 0: comm git: error -5 reading directory block Jan 01 23:28:32 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:32 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386412: comm git: reading directory lblock 0 Jan 01 23:28:32 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974704 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:33 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386406: comm git: reading directory lblock 0 Jan 01 23:28:33 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:33 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386412: comm git: reading directory lblock 0 Jan 01 23:28:34 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974752 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:34 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386418: comm git: reading directory lblock 0 Jan 01 23:28:34 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974704 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:34 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386406: comm git: reading directory lblock 0 Jan 01 23:28:35 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974704 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:35 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386406: comm git: reading directory lblock 0 Jan 01 23:28:35 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:36 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386412: comm git: reading directory lblock 0 Jan 01 23:28:36 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974704 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:36 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386406: comm git: reading directory lblock 0 Jan 01 23:28:37 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974760 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:37 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386420: comm git: reading directory lblock 0 Jan 01 23:28:37 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974760 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:37 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386420: comm git: reading directory lblock 0 Jan 01 23:28:38 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:38 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386412: comm git: reading directory lblock 0 Jan 01 23:28:39 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974704 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:39 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386406: comm git: reading directory lblock 0 Jan 01 23:28:39 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974704 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:39 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386406: comm git: reading directory lblock 0 Jan 01 23:28:40 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:40 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386412: comm git: reading directory lblock 0 Jan 01 23:28:40 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:40 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386412: comm git: reading directory lblock 0 Jan 01 23:28:41 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974752 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:41 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386418: comm git: reading directory lblock 0 Jan 01 23:28:42 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:42 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386412: comm git: reading directory lblock 0 Jan 01 23:28:42 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974704 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:42 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386406: comm git: reading directory lblock 0 Jan 01 23:28:43 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:43 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386412: comm git: reading directory lblock 0 Jan 01 23:28:43 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974752 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:43 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386418: comm git: reading directory lblock 0 Jan 01 23:28:44 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974952 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:44 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386470: comm git: reading directory lblock 0 Jan 01 23:28:45 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974952 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:45 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386470: comm git: reading directory lblock 0 Jan 01 23:28:45 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974952 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:45 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386470: comm git: reading directory lblock 0 Jan 01 23:28:46 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974952 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:46 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386470: comm git: reading directory lblock 0 Jan 01 23:28:47 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974952 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:47 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386470: comm git: reading directory lblock 0 Jan 01 23:28:47 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974952 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:47 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386470: comm git: reading directory lblock 0 Jan 01 23:28:48 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975016 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:48 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386487: comm git: reading directory lblock 0 Jan 01 23:28:49 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975016 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:49 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386487: comm git: reading directory lblock 0 Jan 01 23:28:50 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975024 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:50 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386490: comm git: reading directory lblock 0 Jan 01 23:28:50 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975024 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:50 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386490: comm git: reading directory lblock 0 Jan 01 23:28:51 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975032 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:51 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386493: comm git: reading directory lblock 0 Jan 01 23:28:51 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975032 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:51 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386493: comm git: reading directory lblock 0 Jan 01 23:28:52 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975040 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:52 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386496: comm git: reading directory lblock 0 Jan 01 23:28:53 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975040 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:53 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386496: comm git: reading directory lblock 0 Jan 01 23:28:53 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975048 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:53 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386499: comm git: reading directory lblock 0 Jan 01 23:28:54 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975056 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:54 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386502: comm git: reading directory lblock 0 Jan 01 23:28:54 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975056 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:55 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386502: comm git: reading directory lblock 0 Jan 01 23:28:55 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975064 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:55 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386505: comm git: reading directory lblock 0 Jan 01 23:28:56 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975072 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:56 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386507: comm git: reading directory lblock 0 Jan 01 23:28:56 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975080 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:56 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386510: comm git: reading directory lblock 0 Jan 01 23:28:57 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975088 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:57 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386512: comm git: reading directory lblock 0 Jan 01 23:28:57 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975096 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:58 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386514: comm git: reading directory lblock 0 Jan 01 23:28:58 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975104 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:58 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386516: comm git: reading directory lblock 0 Jan 01 23:28:59 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975104 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:59 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386516: comm git: reading directory lblock 0 Jan 01 23:28:59 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975112 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:28:59 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386519: comm git: reading directory lblock 0 Jan 01 23:29:00 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975120 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:00 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386521: comm git: reading directory lblock 0 Jan 01 23:29:01 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975128 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:01 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386523: comm git: reading directory lblock 0 Jan 01 23:29:01 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975136 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:01 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386525: comm git: reading directory lblock 0 Jan 01 23:29:02 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975144 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:02 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386527: comm git: reading directory lblock 0 Jan 01 23:29:02 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975144 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:02 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386527: comm git: reading directory lblock 0 Jan 01 23:29:03 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975152 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:03 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386530: comm git: reading directory lblock 0 Jan 01 23:29:04 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975160 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:04 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386532: comm git: reading directory lblock 0 Jan 01 23:29:04 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975160 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:04 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386532: comm git: reading directory lblock 0 Jan 01 23:29:05 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975168 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:05 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386535: comm git: reading directory lblock 0 Jan 01 23:29:05 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975176 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:06 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386538: comm git: reading directory lblock 0 Jan 01 23:29:06 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975176 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:06 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386538: comm git: reading directory lblock 0 Jan 01 23:29:07 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975008 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:07 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386529: comm git: reading directory lblock 0 Jan 01 23:29:07 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975104 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:07 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386516: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:08 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975032 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:08 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386493: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:08 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975176 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:08 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386538: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:09 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975112 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:09 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386519: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:10 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975152 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:10 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386530: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:10 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975008 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:10 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386529: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:11 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975160 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:11 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386532: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:12 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975072 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:12 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386507: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:12 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975048 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:12 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386499: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:13 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975080 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:13 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386510: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:13 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975144 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:13 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386527: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:14 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975024 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:14 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386490: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:15 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975088 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:15 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386512: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:15 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975120 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:15 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386521: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:16 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975040 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:16 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386496: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:16 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975128 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:16 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386523: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:17 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975064 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:17 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386505: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:18 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975168 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:18 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386535: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:18 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975056 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:18 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386502: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:19 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975016 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:19 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386487: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:19 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975136 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:19 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386525: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:20 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975096 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:20 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386514: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:21 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975104 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:21 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386516: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:21 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975032 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:21 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386493: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:22 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975176 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:22 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386538: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:23 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975112 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:23 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386519: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:23 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975152 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:23 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386530: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:24 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975008 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:24 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386529: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:24 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975160 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:24 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386532: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:25 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975072 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:25 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386507: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:26 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975048 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:26 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386499: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:26 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975080 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:26 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386510: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:27 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975144 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:27 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386527: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:27 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975024 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:27 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386490: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:28 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975088 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:28 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386512: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:29 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975120 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:29 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386521: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:29 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975040 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:29 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386496: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:30 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975128 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:30 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386523: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:30 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975064 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:30 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386505: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:31 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975168 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:31 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386535: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:32 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975056 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:32 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386502: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:32 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975016 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:32 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386487: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:33 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975136 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:33 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386525: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:34 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975096 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:34 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16386514: lblock 0: comm git: error -5 reading directory block Jan 01 23:29:34 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975016 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:34 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386487: comm git: reading directory lblock 0 Jan 01 23:29:35 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975016 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:35 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386487: comm git: reading directory lblock 0 Jan 01 23:29:35 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975024 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:36 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386490: comm git: reading directory lblock 0 Jan 01 23:29:36 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975024 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:36 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386490: comm git: reading directory lblock 0 Jan 01 23:29:37 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975032 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:37 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386493: comm git: reading directory lblock 0 Jan 01 23:29:37 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975032 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:37 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386493: comm git: reading directory lblock 0 Jan 01 23:29:38 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975040 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:38 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386496: comm git: reading directory lblock 0 Jan 01 23:29:38 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975040 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:39 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386496: comm git: reading directory lblock 0 Jan 01 23:29:39 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975048 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:39 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386499: comm git: reading directory lblock 0 Jan 01 23:29:40 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975056 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:40 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386502: comm git: reading directory lblock 0 Jan 01 23:29:40 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975056 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:40 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386502: comm git: reading directory lblock 0 Jan 01 23:29:41 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975064 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:41 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386505: comm git: reading directory lblock 0 Jan 01 23:29:42 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975072 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:42 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386507: comm git: reading directory lblock 0 Jan 01 23:29:42 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975080 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:42 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386510: comm git: reading directory lblock 0 Jan 01 23:29:43 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975088 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:43 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386512: comm git: reading directory lblock 0 Jan 01 23:29:43 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975096 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:43 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386514: comm git: reading directory lblock 0 Jan 01 23:29:44 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975104 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:44 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386516: comm git: reading directory lblock 0 Jan 01 23:29:45 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975104 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:45 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386516: comm git: reading directory lblock 0 Jan 01 23:29:45 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975112 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:45 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386519: comm git: reading directory lblock 0 Jan 01 23:29:46 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975120 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:46 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386521: comm git: reading directory lblock 0 Jan 01 23:29:46 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975128 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:47 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386523: comm git: reading directory lblock 0 Jan 01 23:29:47 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975136 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:47 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386525: comm git: reading directory lblock 0 Jan 01 23:29:48 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975144 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:48 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386527: comm git: reading directory lblock 0 Jan 01 23:29:48 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975144 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:48 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386527: comm git: reading directory lblock 0 Jan 01 23:29:49 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975152 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:49 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386530: comm git: reading directory lblock 0 Jan 01 23:29:49 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975160 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:50 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386532: comm git: reading directory lblock 0 Jan 01 23:29:50 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975160 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:50 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386532: comm git: reading directory lblock 0 Jan 01 23:29:51 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975168 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:51 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386535: comm git: reading directory lblock 0 Jan 01 23:29:51 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975176 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:51 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386538: comm git: reading directory lblock 0 Jan 01 23:29:52 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975176 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:52 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386538: comm git: reading directory lblock 0 Jan 01 23:29:53 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975008 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 01 23:29:53 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386529: comm git: reading directory lblock 0 Jan 01 23:30:26 the-nexus budgie-panel.desktop[9228]: ATTENTION: default value of option mesa_glthread overridden by environment. Jan 01 23:32:18 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:32:18 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:32:39 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:32:39 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:32:44 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:32:44 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:33:18 the-nexus budgie-panel.desktop[1096]: ###!!! [Parent][MessageChannel] Error: (msgtype=0x390078,name=PContent::Msg_DestroyBrowsingContextGroup) Closed channel: cannot send/recv Jan 01 23:33:28 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:33:28 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:33:29 the-nexus budgie-panel.desktop[15906]: ATTENTION: default value of option mesa_glthread overridden by environment. Jan 01 23:33:48 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:33:48 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:33:48 the-nexus budgie-panel.desktop[15968]: ATTENTION: default value of option mesa_glthread overridden by environment. Jan 01 23:33:54 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:33:54 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:33:54 the-nexus budgie-panel.desktop[16016]: ATTENTION: default value of option mesa_glthread overridden by environment. Jan 01 23:34:01 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:34:01 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:34:01 the-nexus budgie-panel.desktop[16076]: ATTENTION: default value of option mesa_glthread overridden by environment. Jan 01 23:34:16 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:34:16 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:34:21 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:34:21 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:34:33 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:34:33 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:35:02 the-nexus budgie-panel.desktop[16252]: ATTENTION: default value of option mesa_glthread overridden by environment. Jan 01 23:44:00 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:44:00 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:44:06 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:44:06 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:47:04 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:47:04 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:47:14 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:47:14 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:47:50 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:47:50 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:47:51 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:47:51 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:49:43 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:49:43 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:49:45 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:49:45 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:53:44 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:53:44 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:54:55 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.53' (uid=1000 pid=944 comm="/usr/lib/budgie-previews/previews_creator ") Jan 01 23:54:55 the-nexus systemd[643]: Starting Virtual filesystem metadata service... Jan 01 23:54:55 the-nexus systemd[643]: snap.spotify.spotify.376eae4a-705d-4a18-a610-2a31f37e9258.scope: Consumed 29min 37.589s CPU time. Jan 01 23:54:55 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Successfully activated service 'org.gtk.vfs.Metadata' Jan 01 23:54:55 the-nexus systemd[643]: Started Virtual filesystem metadata service. Jan 01 23:54:55 the-nexus audit: BPF prog-id=0 op=UNLOAD Jan 01 23:54:55 the-nexus kernel: audit: type=1334 audit(1641099295.155:126): prog-id=0 op=UNLOAD Jan 01 23:55:09 the-nexus systemd[643]: vte-spawn-da9a9921-291c-415c-8b62-10d29c4c5acb.scope: Consumed 13.803s CPU time. Jan 01 23:55:09 the-nexus systemd[643]: gnome-terminal-server.service: Consumed 2.608s CPU time. Jan 01 23:57:22 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:57:22 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:57:22 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:57:22 the-nexus rtkit-daemon[815]: Supervising 7 threads of 4 processes of 1 users. Jan 01 23:58:47 the-nexus systemd-logind[397]: Lid closed. Jan 01 23:58:47 the-nexus systemd-logind[397]: Suspending... Jan 01 23:58:47 the-nexus NetworkManager[396]: [1641099527.2184] manager: sleep: sleep requested (sleeping: no enabled: yes) Jan 01 23:58:47 the-nexus NetworkManager[396]: [1641099527.2187] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Jan 01 23:58:47 the-nexus NetworkManager[396]: [1641099527.2193] manager: NetworkManager state is now ASLEEP Jan 01 23:58:47 the-nexus NetworkManager[396]: [1641099527.2195] device (wlan0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed') Jan 01 23:58:47 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=396 comm="/usr/bin/NetworkManager --no-daemon ") Jan 01 23:58:47 the-nexus systemd[1]: Starting Network Manager Script Dispatcher Service... Jan 01 23:58:47 the-nexus dbus-daemon[395]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 01 23:58:47 the-nexus systemd[1]: Started Network Manager Script Dispatcher Service. Jan 01 23:58:47 the-nexus kernel: audit: type=1130 audit(1641099527.233:127): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 23:58:47 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 23:58:47 the-nexus kernel: wlan0: deauthenticating from 98:da:c4:0d:90:d6 by local choice (Reason: 3=DEAUTH_LEAVING) Jan 01 23:58:47 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-DISCONNECTED bssid=98:da:c4:0d:90:d6 reason=3 locally_generated=1 Jan 01 23:58:47 the-nexus NetworkManager[396]: [1641099527.4918] device (wlan0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed') Jan 01 23:58:47 the-nexus avahi-daemon[394]: Withdrawing address record for fe80::aa95:e5f4:7984:863d on wlan0. Jan 01 23:58:47 the-nexus avahi-daemon[394]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::aa95:e5f4:7984:863d. Jan 01 23:58:47 the-nexus NetworkManager[396]: [1641099527.4927] dhcp4 (wlan0): canceled DHCP transaction Jan 01 23:58:47 the-nexus avahi-daemon[394]: Interface wlan0.IPv6 no longer relevant for mDNS. Jan 01 23:58:47 the-nexus NetworkManager[396]: [1641099527.4928] dhcp4 (wlan0): state changed extended -> terminated Jan 01 23:58:47 the-nexus avahi-daemon[394]: Interface wlan0.IPv4 no longer relevant for mDNS. Jan 01 23:58:47 the-nexus avahi-daemon[394]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.146. Jan 01 23:58:47 the-nexus avahi-daemon[394]: Withdrawing address record for 192.168.0.146 on wlan0. Jan 01 23:58:47 the-nexus NetworkManager[396]: [1641099527.4975] device (wlan0): set-hw-addr: set MAC address to 92:B7:A2:18:2D:0B (scanning) Jan 01 23:58:47 the-nexus avahi-daemon[394]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.146. Jan 01 23:58:47 the-nexus avahi-daemon[394]: New relevant interface wlan0.IPv4 for mDNS. Jan 01 23:58:47 the-nexus avahi-daemon[394]: Registering new address record for 192.168.0.146 on wlan0.IPv4. Jan 01 23:58:47 the-nexus avahi-daemon[394]: Withdrawing address record for 192.168.0.146 on wlan0. Jan 01 23:58:47 the-nexus avahi-daemon[394]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.146. Jan 01 23:58:47 the-nexus avahi-daemon[394]: Interface wlan0.IPv4 no longer relevant for mDNS. Jan 01 23:58:47 the-nexus NetworkManager[396]: [1641099527.5083] device (wlan0): supplicant interface state: completed -> disconnected Jan 01 23:58:47 the-nexus NetworkManager[396]: [1641099527.5094] device (wlan0): supplicant interface state: disconnected -> interface_disabled Jan 01 23:58:47 the-nexus NetworkManager[396]: [1641099527.5096] device (wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Jan 01 23:58:47 the-nexus NetworkManager[396]: [1641099527.5128] device (wlan0): set-hw-addr: reset MAC address to CC:D9:AC:19:44:B1 (unmanage) Jan 01 23:58:47 the-nexus systemd[1]: Reached target Sleep. Jan 01 23:58:47 the-nexus systemd[1]: Starting System Suspend... Jan 01 23:58:47 the-nexus systemd-sleep[17439]: Entering sleep state 'suspend'... Jan 01 23:58:47 the-nexus kernel: PM: suspend entry (s2idle) Jan 01 23:59:33 the-nexus kernel: Filesystems sync: 0.002 seconds Jan 01 23:59:33 the-nexus kernel: Freezing user space processes ... (elapsed 0.072 seconds) done. Jan 01 23:59:33 the-nexus kernel: OOM killer disabled. Jan 01 23:59:33 the-nexus kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jan 01 23:59:33 the-nexus kernel: printk: Suspending console(s) (use no_console_suspend to debug) Jan 01 23:59:33 the-nexus kernel: e1000e: EEE TX LPI TIMER: 00000011 Jan 01 23:59:33 the-nexus kernel: intel_pch_thermal 0000:00:12.0: CPU-PCH current temp [51C] higher than the threshold temp [50C], sleep 1 times for 100 ms duration Jan 01 23:59:33 the-nexus kernel: intel_pch_thermal 0000:00:12.0: CPU-PCH current temp [51C] higher than the threshold temp [50C], sleep 2 times for 100 ms duration Jan 01 23:59:33 the-nexus kernel: intel_pch_thermal 0000:00:12.0: CPU-PCH current temp [51C] higher than the threshold temp [50C], sleep 3 times for 100 ms duration Jan 01 23:59:33 the-nexus kernel: intel_pch_thermal 0000:00:12.0: CPU-PCH current temp [51C] higher than the threshold temp [50C], sleep 4 times for 100 ms duration Jan 01 23:59:33 the-nexus kernel: intel_pch_thermal 0000:00:12.0: CPU-PCH is cool [50C], continue to suspend Jan 01 23:59:33 the-nexus kernel: ACPI: EC: interrupt blocked Jan 01 23:59:33 the-nexus kernel: ACPI: EC: interrupt unblocked Jan 01 23:59:33 the-nexus kernel: OOM killer enabled. Jan 01 23:59:33 the-nexus kernel: Restarting tasks ... Jan 01 23:59:33 the-nexus kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) Jan 01 23:59:33 the-nexus wpa_supplicant[519]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0 Jan 01 23:59:33 the-nexus kernel: done. Jan 01 23:59:33 the-nexus systemd-sleep[17439]: System returned from sleep state. Jan 01 23:59:33 the-nexus kernel: PM: suspend exit Jan 01 23:59:33 the-nexus systemd[1]: systemd-suspend.service: Deactivated successfully. Jan 01 23:59:33 the-nexus systemd[1]: Finished System Suspend. Jan 01 23:59:33 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 23:59:33 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 23:59:33 the-nexus systemd[1]: Stopped target Sleep. Jan 01 23:59:33 the-nexus systemd[1]: Reached target Suspend. Jan 01 23:59:33 the-nexus systemd[1]: Stopped target Suspend. Jan 01 23:59:33 the-nexus systemd-logind[397]: Operation 'sleep' finished. Jan 01 23:59:33 the-nexus NetworkManager[396]: [1641099573.5345] manager: sleep: wake requested (sleeping: yes enabled: yes) Jan 01 23:59:33 the-nexus kernel: audit: type=1130 audit(1641099573.529:128): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 23:59:33 the-nexus kernel: audit: type=1131 audit(1641099573.529:129): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 23:59:33 the-nexus NetworkManager[396]: [1641099573.5345] device (enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Jan 01 23:59:33 the-nexus wpa_supplicant[519]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0 Jan 01 23:59:33 the-nexus NetworkManager[396]: [1641099573.6139] device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 01 23:59:33 the-nexus kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down Jan 01 23:59:33 the-nexus NetworkManager[396]: [1641099573.8038] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 01 23:59:33 the-nexus NetworkManager[396]: [1641099573.8065] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 01 23:59:33 the-nexus NetworkManager[396]: [1641099573.8079] manager: NetworkManager state is now DISCONNECTED Jan 01 23:59:33 the-nexus NetworkManager[396]: [1641099573.9066] device (wlan0): supplicant interface state: internal-starting -> disconnected Jan 01 23:59:33 the-nexus NetworkManager[396]: [1641099573.9067] device (p2p-dev-wlan0): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed') Jan 01 23:59:33 the-nexus NetworkManager[396]: [1641099573.9082] Wi-Fi P2P device controlled by interface wlan0 created Jan 01 23:59:33 the-nexus NetworkManager[396]: [1641099573.9090] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/5) Jan 01 23:59:33 the-nexus NetworkManager[396]: [1641099573.9096] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 01 23:59:33 the-nexus NetworkManager[396]: [1641099573.9113] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Jan 01 23:59:33 the-nexus NetworkManager[396]: [1641099573.9130] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') Jan 01 23:59:36 the-nexus systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Jan 01 23:59:36 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 23:59:36 the-nexus kernel: audit: type=1131 audit(1641099576.046:130): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 23:59:37 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.2716] policy: auto-activating connection 'NiceMagnolia' (1f6b04ef-bb63-4102-a785-c1fc54dfb549) Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.2726] device (wlan0): Activation: starting connection 'NiceMagnolia' (1f6b04ef-bb63-4102-a785-c1fc54dfb549) Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.2727] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.2730] manager: NetworkManager state is now CONNECTING Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.2733] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.2736] device (wlan0): Activation: (wifi) access point 'NiceMagnolia' has security, but secrets are required. Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.2736] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.2738] sup-iface[af077d6cbd64cc7c,1,wlan0]: wps: type pbc start... Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.2750] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.2753] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.2756] device (wlan0): Activation: (wifi) connection 'NiceMagnolia' has security, and secrets exist. No new secrets needed. Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.2756] Config: added 'ssid' value 'NiceMagnolia' Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.2756] Config: added 'scan_ssid' value '1' Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.2756] Config: added 'bgscan' value 'simple:30:-70:86400' Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.2756] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK' Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.2756] Config: added 'auth_alg' value 'OPEN' Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.2756] Config: added 'psk' value '' Jan 01 23:59:37 the-nexus wpa_supplicant[519]: wlan0: SME: Trying to authenticate with 98:da:c4:0d:90:d6 (SSID='NiceMagnolia' freq=5745 MHz) Jan 01 23:59:37 the-nexus kernel: wlan0: authenticate with 98:da:c4:0d:90:d6 Jan 01 23:59:37 the-nexus kernel: wlan0: send auth to 98:da:c4:0d:90:d6 (try 1/3) Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.2921] device (wlan0): supplicant interface state: disconnected -> authenticating Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.2922] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> authenticating Jan 01 23:59:37 the-nexus wpa_supplicant[519]: wlan0: Trying to associate with 98:da:c4:0d:90:d6 (SSID='NiceMagnolia' freq=5745 MHz) Jan 01 23:59:37 the-nexus kernel: wlan0: authenticated Jan 01 23:59:37 the-nexus kernel: wlan0: associate with 98:da:c4:0d:90:d6 (try 1/3) Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.4392] device (wlan0): supplicant interface state: authenticating -> associating Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.4392] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating Jan 01 23:59:37 the-nexus kernel: wlan0: RX AssocResp from 98:da:c4:0d:90:d6 (capab=0x1411 status=0 aid=6) Jan 01 23:59:37 the-nexus wpa_supplicant[519]: wlan0: Associated with 98:da:c4:0d:90:d6 Jan 01 23:59:37 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Jan 01 23:59:37 the-nexus kernel: wlan0: associated Jan 01 23:59:37 the-nexus wpa_supplicant[519]: wlan0: WPA: Key negotiation completed with 98:da:c4:0d:90:d6 [PTK=CCMP GTK=CCMP] Jan 01 23:59:37 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-CONNECTED - Connection to 98:da:c4:0d:90:d6 completed [id=0 id_str=] Jan 01 23:59:37 the-nexus kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Jan 01 23:59:37 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-49 noise=9999 txrate=6000 Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.5231] device (wlan0): supplicant interface state: associating -> completed Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.5232] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "NiceMagnolia" Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.5233] device (p2p-dev-wlan0): supplicant management interface state: associating -> completed Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.5236] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.5245] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds) Jan 01 23:59:37 the-nexus avahi-daemon[394]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::aa95:e5f4:7984:863d. Jan 01 23:59:37 the-nexus avahi-daemon[394]: New relevant interface wlan0.IPv6 for mDNS. Jan 01 23:59:37 the-nexus avahi-daemon[394]: Registering new address record for fe80::aa95:e5f4:7984:863d on wlan0.*. Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.5358] dhcp4 (wlan0): state changed unknown -> bound, address=192.168.0.146 Jan 01 23:59:37 the-nexus avahi-daemon[394]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.146. Jan 01 23:59:37 the-nexus avahi-daemon[394]: New relevant interface wlan0.IPv4 for mDNS. Jan 01 23:59:37 the-nexus avahi-daemon[394]: Registering new address record for 192.168.0.146 on wlan0.IPv4. Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.5391] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Jan 01 23:59:37 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=396 comm="/usr/bin/NetworkManager --no-daemon ") Jan 01 23:59:37 the-nexus systemd[1]: Starting Network Manager Script Dispatcher Service... Jan 01 23:59:37 the-nexus dbus-daemon[395]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 01 23:59:37 the-nexus systemd[1]: Started Network Manager Script Dispatcher Service. Jan 01 23:59:37 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.5663] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.5666] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.5672] manager: NetworkManager state is now CONNECTED_LOCAL Jan 01 23:59:37 the-nexus kernel: audit: type=1130 audit(1641099577.563:131): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.5684] manager: NetworkManager state is now CONNECTED_SITE Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.5686] policy: set 'NiceMagnolia' (wlan0) as default for IPv4 routing and DNS Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.5707] device (wlan0): Activation: successful, device activated. Jan 01 23:59:37 the-nexus NetworkManager[396]: [1641099577.5716] manager: NetworkManager state is now CONNECTED_GLOBAL Jan 01 23:59:48 the-nexus systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Jan 01 23:59:48 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 23:59:48 the-nexus kernel: audit: type=1131 audit(1641099588.053:132): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 23:59:55 the-nexus systemd-logind[397]: Suspending... Jan 01 23:59:55 the-nexus NetworkManager[396]: [1641099595.9179] manager: sleep: sleep requested (sleeping: no enabled: yes) Jan 01 23:59:55 the-nexus NetworkManager[396]: [1641099595.9182] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Jan 01 23:59:55 the-nexus NetworkManager[396]: [1641099595.9192] manager: NetworkManager state is now ASLEEP Jan 01 23:59:55 the-nexus NetworkManager[396]: [1641099595.9196] device (wlan0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed') Jan 01 23:59:55 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=396 comm="/usr/bin/NetworkManager --no-daemon ") Jan 01 23:59:55 the-nexus systemd[1]: Starting Network Manager Script Dispatcher Service... Jan 01 23:59:55 the-nexus dbus-daemon[395]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 01 23:59:55 the-nexus systemd[1]: Started Network Manager Script Dispatcher Service. Jan 01 23:59:55 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 23:59:55 the-nexus kernel: audit: type=1130 audit(1641099595.926:133): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 01 23:59:55 the-nexus kernel: wlan0: deauthenticating from 98:da:c4:0d:90:d6 by local choice (Reason: 3=DEAUTH_LEAVING) Jan 01 23:59:56 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-DISCONNECTED bssid=98:da:c4:0d:90:d6 reason=3 locally_generated=1 Jan 01 23:59:56 the-nexus NetworkManager[396]: [1641099596.0901] device (wlan0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed') Jan 01 23:59:56 the-nexus avahi-daemon[394]: Withdrawing address record for fe80::aa95:e5f4:7984:863d on wlan0. Jan 01 23:59:56 the-nexus avahi-daemon[394]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::aa95:e5f4:7984:863d. Jan 01 23:59:56 the-nexus avahi-daemon[394]: Interface wlan0.IPv6 no longer relevant for mDNS. Jan 01 23:59:56 the-nexus NetworkManager[396]: [1641099596.1429] dhcp4 (wlan0): canceled DHCP transaction Jan 01 23:59:56 the-nexus NetworkManager[396]: [1641099596.1431] dhcp4 (wlan0): state changed bound -> terminated Jan 01 23:59:56 the-nexus avahi-daemon[394]: Interface wlan0.IPv4 no longer relevant for mDNS. Jan 01 23:59:56 the-nexus avahi-daemon[394]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.146. Jan 01 23:59:56 the-nexus avahi-daemon[394]: Withdrawing address record for 192.168.0.146 on wlan0. Jan 01 23:59:56 the-nexus NetworkManager[396]: [1641099596.1473] device (wlan0): set-hw-addr: set MAC address to 76:95:B6:32:74:7B (scanning) Jan 01 23:59:56 the-nexus avahi-daemon[394]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.146. Jan 01 23:59:56 the-nexus avahi-daemon[394]: New relevant interface wlan0.IPv4 for mDNS. Jan 01 23:59:56 the-nexus avahi-daemon[394]: Registering new address record for 192.168.0.146 on wlan0.IPv4. Jan 01 23:59:56 the-nexus avahi-daemon[394]: Withdrawing address record for 192.168.0.146 on wlan0. Jan 01 23:59:56 the-nexus avahi-daemon[394]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.146. Jan 01 23:59:56 the-nexus avahi-daemon[394]: Interface wlan0.IPv4 no longer relevant for mDNS. Jan 01 23:59:56 the-nexus NetworkManager[396]: [1641099596.1628] device (wlan0): supplicant interface state: completed -> disconnected Jan 01 23:59:56 the-nexus NetworkManager[396]: [1641099596.1638] device (wlan0): supplicant interface state: disconnected -> interface_disabled Jan 01 23:59:56 the-nexus NetworkManager[396]: [1641099596.1639] device (wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Jan 01 23:59:56 the-nexus NetworkManager[396]: [1641099596.1659] device (wlan0): set-hw-addr: reset MAC address to CC:D9:AC:19:44:B1 (unmanage) Jan 01 23:59:56 the-nexus systemd[1]: Reached target Sleep. Jan 01 23:59:56 the-nexus systemd[1]: Starting System Suspend... Jan 01 23:59:56 the-nexus systemd-sleep[17583]: Entering sleep state 'suspend'... Jan 01 23:59:56 the-nexus kernel: PM: suspend entry (s2idle) Jan 02 00:00:43 the-nexus kernel: Filesystems sync: 0.003 seconds Jan 02 00:00:43 the-nexus kernel: Freezing user space processes ... (elapsed 0.032 seconds) done. Jan 02 00:00:43 the-nexus kernel: OOM killer disabled. Jan 02 00:00:43 the-nexus kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jan 02 00:00:43 the-nexus kernel: printk: Suspending console(s) (use no_console_suspend to debug) Jan 02 00:00:43 the-nexus kernel: e1000e: EEE TX LPI TIMER: 00000011 Jan 02 00:00:43 the-nexus kernel: intel_pch_thermal 0000:00:12.0: CPU-PCH is cool [44C], continue to suspend Jan 02 00:00:43 the-nexus kernel: ACPI: EC: interrupt blocked Jan 02 00:00:43 the-nexus kernel: ACPI: EC: interrupt unblocked Jan 02 00:00:43 the-nexus kernel: OOM killer enabled. Jan 02 00:00:43 the-nexus kernel: Restarting tasks ... Jan 02 00:00:43 the-nexus kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) Jan 02 00:00:43 the-nexus kernel: done. Jan 02 00:00:43 the-nexus kernel: audit: type=1334 audit(1641099643.493:134): prog-id=35 op=LOAD Jan 02 00:00:43 the-nexus kernel: audit: type=1130 audit(1641099643.506:135): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=shadow comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:00:43 the-nexus audit: BPF prog-id=35 op=LOAD Jan 02 00:00:43 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=shadow comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:00:43 the-nexus wpa_supplicant[519]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0 Jan 02 00:00:43 the-nexus systemd[643]: Starting EOS update notifier service... Jan 02 00:00:43 the-nexus systemd[1]: Starting Rotate log files... Jan 02 00:00:43 the-nexus systemd[1]: Starting Daily man-db regeneration... Jan 02 00:00:43 the-nexus systemd[1]: Started Verify integrity of password and group files. Jan 02 00:00:43 the-nexus systemd-sleep[17583]: System returned from sleep state. Jan 02 00:00:43 the-nexus systemd[1]: systemd-suspend.service: Deactivated successfully. Jan 02 00:00:43 the-nexus systemd[1]: Finished System Suspend. Jan 02 00:00:43 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:00:43 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:00:43 the-nexus systemd[1]: Stopped target Sleep. Jan 02 00:00:43 the-nexus systemd[1]: Reached target Suspend. Jan 02 00:00:43 the-nexus systemd[1]: Stopped target Suspend. Jan 02 00:00:43 the-nexus systemd-logind[397]: Operation 'sleep' finished. Jan 02 00:00:43 the-nexus kernel: PM: suspend exit Jan 02 00:00:43 the-nexus kernel: audit: type=1130 audit(1641099643.519:136): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:00:43 the-nexus kernel: audit: type=1131 audit(1641099643.519:137): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:00:43 the-nexus NetworkManager[396]: [1641099643.5254] manager: sleep: wake requested (sleeping: yes enabled: yes) Jan 02 00:00:43 the-nexus NetworkManager[396]: [1641099643.5255] device (enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Jan 02 00:00:43 the-nexus wpa_supplicant[519]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0 Jan 02 00:00:43 the-nexus NetworkManager[396]: [1641099643.6074] device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 02 00:00:43 the-nexus kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down Jan 02 00:00:43 the-nexus systemd[1]: shadow.service: Deactivated successfully. Jan 02 00:00:43 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=shadow comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:00:43 the-nexus kernel: audit: type=1131 audit(1641099643.739:138): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=shadow comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:00:43 the-nexus NetworkManager[396]: [1641099643.8006] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 02 00:00:43 the-nexus NetworkManager[396]: [1641099643.8044] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 02 00:00:43 the-nexus NetworkManager[396]: [1641099643.8060] manager: NetworkManager state is now DISCONNECTED Jan 02 00:00:43 the-nexus systemd[1]: logrotate.service: Deactivated successfully. Jan 02 00:00:43 the-nexus systemd[1]: Finished Rotate log files. Jan 02 00:00:43 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=logrotate comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:00:43 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=logrotate comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:00:43 the-nexus kernel: audit: type=1130 audit(1641099643.836:139): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=logrotate comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:00:43 the-nexus kernel: audit: type=1131 audit(1641099643.836:140): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=logrotate comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:00:43 the-nexus NetworkManager[396]: [1641099643.8605] device (wlan0): supplicant interface state: internal-starting -> disconnected Jan 02 00:00:43 the-nexus NetworkManager[396]: [1641099643.8605] device (p2p-dev-wlan0): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed') Jan 02 00:00:43 the-nexus audit: BPF prog-id=0 op=UNLOAD Jan 02 00:00:43 the-nexus NetworkManager[396]: [1641099643.8609] Wi-Fi P2P device controlled by interface wlan0 created Jan 02 00:00:43 the-nexus NetworkManager[396]: [1641099643.8610] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/6) Jan 02 00:00:43 the-nexus NetworkManager[396]: [1641099643.8612] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 02 00:00:43 the-nexus NetworkManager[396]: [1641099643.8616] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Jan 02 00:00:43 the-nexus kernel: audit: type=1334 audit(1641099643.856:141): prog-id=0 op=UNLOAD Jan 02 00:00:43 the-nexus NetworkManager[396]: [1641099643.8620] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') Jan 02 00:00:44 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973576 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:44 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385795: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:44 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/fr’: Input/output error Jan 02 00:00:44 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973616 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:44 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385801: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:44 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/tr’: Input/output error Jan 02 00:00:45 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974160 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:45 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385806: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:45 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/bg’: Input/output error Jan 02 00:00:45 the-nexus systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Jan 02 00:00:45 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:00:45 the-nexus kernel: audit: type=1131 audit(1641099645.726:142): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:00:45 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974176 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:45 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385809: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:45 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/lt’: Input/output error Jan 02 00:00:46 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974192 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:46 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385812: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:46 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/ar’: Input/output error Jan 02 00:00:47 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.1829] policy: auto-activating connection 'NiceMagnolia' (1f6b04ef-bb63-4102-a785-c1fc54dfb549) Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.1837] device (wlan0): Activation: starting connection 'NiceMagnolia' (1f6b04ef-bb63-4102-a785-c1fc54dfb549) Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.1839] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.1844] manager: NetworkManager state is now CONNECTING Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.1849] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.1853] device (wlan0): Activation: (wifi) access point 'NiceMagnolia' has security, but secrets are required. Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.1854] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.1857] sup-iface[5cd177416b1d4877,2,wlan0]: wps: type pbc start... Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.1885] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.1893] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.1898] device (wlan0): Activation: (wifi) connection 'NiceMagnolia' has security, and secrets exist. No new secrets needed. Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.1899] Config: added 'ssid' value 'NiceMagnolia' Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.1899] Config: added 'scan_ssid' value '1' Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.1899] Config: added 'bgscan' value 'simple:30:-70:86400' Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.1900] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK' Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.1900] Config: added 'auth_alg' value 'OPEN' Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.1900] Config: added 'psk' value '' Jan 02 00:00:47 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/vi’: Input/output error Jan 02 00:00:47 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974272 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:47 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385815: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:47 the-nexus wpa_supplicant[519]: wlan0: SME: Trying to authenticate with 98:da:c4:0d:90:d6 (SSID='NiceMagnolia' freq=5745 MHz) Jan 02 00:00:47 the-nexus kernel: wlan0: authenticate with 98:da:c4:0d:90:d6 Jan 02 00:00:47 the-nexus kernel: wlan0: send auth to 98:da:c4:0d:90:d6 (try 1/3) Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.2178] device (wlan0): supplicant interface state: disconnected -> authenticating Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.2179] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> authenticating Jan 02 00:00:47 the-nexus wpa_supplicant[519]: wlan0: Trying to associate with 98:da:c4:0d:90:d6 (SSID='NiceMagnolia' freq=5745 MHz) Jan 02 00:00:47 the-nexus kernel: wlan0: authenticated Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.3553] device (wlan0): supplicant interface state: authenticating -> associating Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.3554] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating Jan 02 00:00:47 the-nexus kernel: wlan0: associate with 98:da:c4:0d:90:d6 (try 1/3) Jan 02 00:00:47 the-nexus kernel: wlan0: RX AssocResp from 98:da:c4:0d:90:d6 (capab=0x1411 status=0 aid=6) Jan 02 00:00:47 the-nexus wpa_supplicant[519]: wlan0: Associated with 98:da:c4:0d:90:d6 Jan 02 00:00:47 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Jan 02 00:00:47 the-nexus kernel: wlan0: associated Jan 02 00:00:47 the-nexus wpa_supplicant[519]: wlan0: WPA: Key negotiation completed with 98:da:c4:0d:90:d6 [PTK=CCMP GTK=CCMP] Jan 02 00:00:47 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-CONNECTED - Connection to 98:da:c4:0d:90:d6 completed [id=0 id_str=] Jan 02 00:00:47 the-nexus kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Jan 02 00:00:47 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-50 noise=9999 txrate=6000 Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.4802] device (wlan0): supplicant interface state: associating -> completed Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.4802] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "NiceMagnolia" Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.4803] device (p2p-dev-wlan0): supplicant management interface state: associating -> completed Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.4806] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.4813] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds) Jan 02 00:00:47 the-nexus avahi-daemon[394]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::aa95:e5f4:7984:863d. Jan 02 00:00:47 the-nexus avahi-daemon[394]: New relevant interface wlan0.IPv6 for mDNS. Jan 02 00:00:47 the-nexus avahi-daemon[394]: Registering new address record for fe80::aa95:e5f4:7984:863d on wlan0.*. Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.7075] dhcp4 (wlan0): state changed unknown -> bound, address=192.168.0.146 Jan 02 00:00:47 the-nexus avahi-daemon[394]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.146. Jan 02 00:00:47 the-nexus avahi-daemon[394]: New relevant interface wlan0.IPv4 for mDNS. Jan 02 00:00:47 the-nexus avahi-daemon[394]: Registering new address record for 192.168.0.146 on wlan0.IPv4. Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.7123] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Jan 02 00:00:47 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=396 comm="/usr/bin/NetworkManager --no-daemon ") Jan 02 00:00:47 the-nexus systemd[1]: Starting Network Manager Script Dispatcher Service... Jan 02 00:00:47 the-nexus dbus-daemon[395]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 02 00:00:47 the-nexus systemd[1]: Started Network Manager Script Dispatcher Service. Jan 02 00:00:47 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.7268] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.7271] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.7277] manager: NetworkManager state is now CONNECTED_LOCAL Jan 02 00:00:47 the-nexus kernel: audit: type=1130 audit(1641099647.723:143): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.7289] manager: NetworkManager state is now CONNECTED_SITE Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.7290] policy: set 'NiceMagnolia' (wlan0) as default for IPv4 routing and DNS Jan 02 00:00:47 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/et’: Input/output error Jan 02 00:00:47 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974288 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:47 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385818: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.9136] device (wlan0): Activation: successful, device activated. Jan 02 00:00:47 the-nexus NetworkManager[396]: [1641099647.9157] manager: NetworkManager state is now CONNECTED_GLOBAL Jan 02 00:00:48 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974304 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:48 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385821: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:48 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/ko’: Input/output error Jan 02 00:00:49 the-nexus eos-update-notifier[17589]: Checking for updates ... Jan 02 00:00:49 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974328 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:49 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385825: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:49 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/pt_PT’: Input/output error Jan 02 00:00:49 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972424 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:49 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385828: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:49 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/sr’: Input/output error Jan 02 00:00:50 the-nexus eos-update-notifier[17589]: Checking AUR updates ... Jan 02 00:00:50 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972456 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:50 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385833: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:50 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/it’: Input/output error Jan 02 00:00:51 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524975688 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:51 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16386541: comm yay: reading directory lblock 0 Jan 02 00:00:51 the-nexus eos-update-notifier[17690]: -> could not open file /var/lib/pacman/local/nvm-0.39.1-1/desc: Input/output error Jan 02 00:00:51 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972496 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:52 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385839: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:52 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972528 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:52 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385844: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:52 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974336 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:52 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385847: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:52 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/pt’: Input/output error Jan 02 00:00:52 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/he’: Input/output error Jan 02 00:00:52 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/nb’: Input/output error Jan 02 00:00:52 the-nexus systemd[643]: Finished EOS update notifier service. Jan 02 00:00:53 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974352 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:53 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385850: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:53 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/fa’: Input/output error Jan 02 00:00:53 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/da’: Input/output error Jan 02 00:00:53 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974368 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:53 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385853: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:54 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974400 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:54 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385858: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:54 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/ja’: Input/output error Jan 02 00:00:55 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974432 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:55 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385570: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:55 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/sv’: Input/output error Jan 02 00:00:55 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:55 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385869: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:55 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/sl’: Input/output error Jan 02 00:00:56 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974496 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:56 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385873: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:56 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/el’: Input/output error Jan 02 00:00:56 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974512 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:56 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385876: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:56 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/fi’: Input/output error Jan 02 00:00:57 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974528 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:57 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385879: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:57 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/hu’: Input/output error Jan 02 00:00:57 the-nexus systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Jan 02 00:00:57 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:00:57 the-nexus kernel: audit: type=1131 audit(1641099657.736:144): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:00:58 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974560 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:58 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385884: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:58 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/lv’: Input/output error Jan 02 00:00:58 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974576 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:58 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385887: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:58 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/uk’: Input/output error Jan 02 00:00:59 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972560 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:59 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385894: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:59 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/de’: Input/output error Jan 02 00:00:59 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972608 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:00:59 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385902: lblock 0: comm find: error -5 reading directory block Jan 02 00:00:59 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/pl’: Input/output error Jan 02 00:01:00 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972648 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:01:00 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385908: lblock 0: comm find: error -5 reading directory block Jan 02 00:01:00 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/ms’: Input/output error Jan 02 00:01:01 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972664 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:01:01 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385911: lblock 0: comm find: error -5 reading directory block Jan 02 00:01:01 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/fr.ISO8859-1’: Input/output error Jan 02 00:01:01 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972696 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:01:01 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385916: lblock 0: comm find: error -5 reading directory block Jan 02 00:01:01 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/fr.UTF-8’: Input/output error Jan 02 00:01:02 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:01:02 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385921: lblock 0: comm find: error -5 reading directory block Jan 02 00:01:02 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/is’: Input/output error Jan 02 00:01:03 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972744 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:01:03 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385924: lblock 0: comm find: error -5 reading directory block Jan 02 00:01:03 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/pt_BR’: Input/output error Jan 02 00:01:03 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972776 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:01:03 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385929: lblock 0: comm find: error -5 reading directory block Jan 02 00:01:03 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/zh_TW’: Input/output error Jan 02 00:01:04 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972808 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:01:04 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385934: lblock 0: comm find: error -5 reading directory block Jan 02 00:01:04 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/sk’: Input/output error Jan 02 00:01:04 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972824 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:01:04 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385937: lblock 0: comm find: error -5 reading directory block Jan 02 00:01:04 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/id’: Input/output error Jan 02 00:01:05 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972856 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:01:05 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385942: lblock 0: comm find: error -5 reading directory block Jan 02 00:01:05 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/hr’: Input/output error Jan 02 00:01:06 the-nexus systemd-logind[397]: Suspending... Jan 02 00:01:06 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972872 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:01:06 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385945: lblock 0: comm find: error -5 reading directory block Jan 02 00:01:06 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/es’: Input/output error Jan 02 00:01:06 the-nexus NetworkManager[396]: [1641099666.0999] manager: sleep: sleep requested (sleeping: no enabled: yes) Jan 02 00:01:06 the-nexus NetworkManager[396]: [1641099666.1004] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Jan 02 00:01:06 the-nexus NetworkManager[396]: [1641099666.1012] manager: NetworkManager state is now ASLEEP Jan 02 00:01:06 the-nexus NetworkManager[396]: [1641099666.1017] device (wlan0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed') Jan 02 00:01:06 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=396 comm="/usr/bin/NetworkManager --no-daemon ") Jan 02 00:01:06 the-nexus systemd[1]: Starting Network Manager Script Dispatcher Service... Jan 02 00:01:06 the-nexus dbus-daemon[395]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 02 00:01:06 the-nexus systemd[1]: Started Network Manager Script Dispatcher Service. Jan 02 00:01:06 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:01:06 the-nexus kernel: audit: type=1130 audit(1641099666.113:145): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 00:01:06 the-nexus kernel: wlan0: deauthenticating from 98:da:c4:0d:90:d6 by local choice (Reason: 3=DEAUTH_LEAVING) Jan 02 00:01:06 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-DISCONNECTED bssid=98:da:c4:0d:90:d6 reason=3 locally_generated=1 Jan 02 00:01:06 the-nexus NetworkManager[396]: [1641099666.6086] device (wlan0): supplicant interface state: completed -> disconnected Jan 02 00:01:06 the-nexus NetworkManager[396]: [1641099666.6086] device (wlan0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed') Jan 02 00:01:06 the-nexus avahi-daemon[394]: Withdrawing address record for fe80::aa95:e5f4:7984:863d on wlan0. Jan 02 00:01:06 the-nexus avahi-daemon[394]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::aa95:e5f4:7984:863d. Jan 02 00:01:06 the-nexus avahi-daemon[394]: Interface wlan0.IPv6 no longer relevant for mDNS. Jan 02 00:01:06 the-nexus NetworkManager[396]: [1641099666.6483] dhcp4 (wlan0): canceled DHCP transaction Jan 02 00:01:06 the-nexus NetworkManager[396]: [1641099666.6483] dhcp4 (wlan0): state changed bound -> terminated Jan 02 00:01:06 the-nexus avahi-daemon[394]: Interface wlan0.IPv4 no longer relevant for mDNS. Jan 02 00:01:06 the-nexus avahi-daemon[394]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.146. Jan 02 00:01:06 the-nexus avahi-daemon[394]: Withdrawing address record for 192.168.0.146 on wlan0. Jan 02 00:01:06 the-nexus NetworkManager[396]: [1641099666.6506] device (wlan0): set-hw-addr: set MAC address to 46:14:63:7F:CE:62 (scanning) Jan 02 00:01:06 the-nexus avahi-daemon[394]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.146. Jan 02 00:01:06 the-nexus avahi-daemon[394]: New relevant interface wlan0.IPv4 for mDNS. Jan 02 00:01:06 the-nexus avahi-daemon[394]: Registering new address record for 192.168.0.146 on wlan0.IPv4. Jan 02 00:01:06 the-nexus avahi-daemon[394]: Withdrawing address record for 192.168.0.146 on wlan0. Jan 02 00:01:06 the-nexus avahi-daemon[394]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.146. Jan 02 00:01:06 the-nexus avahi-daemon[394]: Interface wlan0.IPv4 no longer relevant for mDNS. Jan 02 00:01:06 the-nexus NetworkManager[396]: [1641099666.6560] device (wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Jan 02 00:01:06 the-nexus NetworkManager[396]: [1641099666.6578] device (wlan0): set-hw-addr: reset MAC address to CC:D9:AC:19:44:B1 (unmanage) Jan 02 00:01:06 the-nexus systemd[1]: Reached target Sleep. Jan 02 00:01:06 the-nexus systemd[1]: Starting System Suspend... Jan 02 00:01:06 the-nexus systemd-sleep[17741]: Entering sleep state 'suspend'... Jan 02 00:01:06 the-nexus kernel: PM: suspend entry (s2idle) Jan 02 00:01:06 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972904 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:01:06 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385950: lblock 0: comm find: error -5 reading directory block Jan 02 00:01:06 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/ru’: Input/output error Jan 02 00:01:06 the-nexus wpa_supplicant[519]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0 Jan 02 00:01:06 the-nexus wpa_supplicant[519]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0 Jan 02 00:01:07 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972944 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:01:07 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385956: lblock 0: comm find: error -5 reading directory block Jan 02 00:01:07 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/nl’: Input/output error Jan 02 00:01:07 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972976 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 00:01:07 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385961: lblock 0: comm find: error -5 reading directory block Jan 02 00:01:07 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/cs’: Input/output error Jan 02 12:15:02 the-nexus kernel: Filesystems sync: 1.602 seconds Jan 02 12:15:02 the-nexus kernel: Freezing user space processes ... Jan 02 12:15:02 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973016 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:02 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385967: lblock 0: comm find: error -5 reading directory block Jan 02 12:15:02 the-nexus kernel: (elapsed 0.280 seconds) done. Jan 02 12:15:02 the-nexus kernel: OOM killer disabled. Jan 02 12:15:02 the-nexus kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jan 02 12:15:02 the-nexus kernel: printk: Suspending console(s) (use no_console_suspend to debug) Jan 02 12:15:02 the-nexus kernel: e1000e: EEE TX LPI TIMER: 00000011 Jan 02 12:15:02 the-nexus kernel: intel_pch_thermal 0000:00:12.0: CPU-PCH is cool [46C], continue to suspend Jan 02 12:15:02 the-nexus kernel: ACPI: EC: interrupt blocked Jan 02 12:15:02 the-nexus kernel: ACPI: EC: interrupt unblocked Jan 02 12:15:02 the-nexus kernel: pcieport 0000:00:1d.4: Data Link Layer Link Active not set in 1000 msec Jan 02 12:15:02 the-nexus kernel: pcieport 0000:05:00.0: can't change power state from D3cold to D0 (config space inaccessible) Jan 02 12:15:02 the-nexus kernel: pcieport 0000:06:01.0: can't change power state from D3cold to D0 (config space inaccessible) Jan 02 12:15:02 the-nexus kernel: pcieport 0000:06:02.0: can't change power state from D3cold to D0 (config space inaccessible) Jan 02 12:15:02 the-nexus kernel: pcieport 0000:06:00.0: can't change power state from D3cold to D0 (config space inaccessible) Jan 02 12:15:02 the-nexus kernel: pcieport 0000:06:04.0: can't change power state from D3cold to D0 (config space inaccessible) Jan 02 12:15:02 the-nexus kernel: xhci_hcd 0000:2d:00.0: can't change power state from D3cold to D0 (config space inaccessible) Jan 02 12:15:02 the-nexus kernel: thunderbolt 0000:07:00.0: can't change power state from D3cold to D0 (config space inaccessible) Jan 02 12:15:02 the-nexus kernel: pcieport 0000:00:1d.4: pciehp: Slot(12): Card not present Jan 02 12:15:02 the-nexus kernel: xhci_hcd 0000:2d:00.0: can't change power state from D3cold to D0 (config space inaccessible) Jan 02 12:15:02 the-nexus kernel: xhci_hcd 0000:2d:00.0: Controller not ready at resume -19 Jan 02 12:15:02 the-nexus kernel: xhci_hcd 0000:2d:00.0: PCI post-resume error -19! Jan 02 12:15:02 the-nexus kernel: xhci_hcd 0000:2d:00.0: HC died; cleaning up Jan 02 12:15:02 the-nexus kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0xe0 returns -19 Jan 02 12:15:02 the-nexus kernel: xhci_hcd 0000:2d:00.0: PM: failed to resume async: error -19 Jan 02 12:15:02 the-nexus kernel: xhci_hcd 0000:2d:00.0: remove, state 4 Jan 02 12:15:02 the-nexus kernel: usb usb4: USB disconnect, device number 1 Jan 02 12:15:02 the-nexus kernel: pci 0000:06:04.0: can't change power state from D3cold to D0 (config space inaccessible) Jan 02 12:15:02 the-nexus kernel: xhci_hcd 0000:2d:00.0: USB bus 4 deregistered Jan 02 12:15:02 the-nexus kernel: xhci_hcd 0000:2d:00.0: remove, state 4 Jan 02 12:15:02 the-nexus kernel: usb usb3: USB disconnect, device number 1 Jan 02 12:15:02 the-nexus kernel: xhci_hcd 0000:2d:00.0: Host halt failed, -19 Jan 02 12:15:02 the-nexus kernel: xhci_hcd 0000:2d:00.0: Host not accessible, reset failed. Jan 02 12:15:02 the-nexus kernel: xhci_hcd 0000:2d:00.0: USB bus 3 deregistered Jan 02 12:15:02 the-nexus kernel: pci 0000:07:00.0: Removing from iommu group 14 Jan 02 12:15:02 the-nexus kernel: pci_bus 0000:07: busn_res: [bus 07] is released Jan 02 12:15:02 the-nexus kernel: pci 0000:06:00.0: Removing from iommu group 14 Jan 02 12:15:02 the-nexus kernel: pci_bus 0000:08: busn_res: [bus 08-2c] is released Jan 02 12:15:02 the-nexus kernel: pci 0000:06:01.0: Removing from iommu group 15 Jan 02 12:15:02 the-nexus kernel: pci 0000:2d:00.0: Removing from iommu group 16 Jan 02 12:15:02 the-nexus kernel: pci_bus 0000:2d: busn_res: [bus 2d] is released Jan 02 12:15:02 the-nexus kernel: pci 0000:06:02.0: Removing from iommu group 16 Jan 02 12:15:02 the-nexus kernel: pci_bus 0000:2e: busn_res: [bus 2e-52] is released Jan 02 12:15:02 the-nexus kernel: pci 0000:06:04.0: Removing from iommu group 17 Jan 02 12:15:02 the-nexus kernel: pci_bus 0000:06: busn_res: [bus 06-52] is released Jan 02 12:15:02 the-nexus kernel: pci 0000:05:00.0: Removing from iommu group 13 Jan 02 12:15:02 the-nexus kernel: OOM killer enabled. Jan 02 12:15:02 the-nexus kernel: Restarting tasks ... done. Jan 02 12:15:02 the-nexus kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) Jan 02 12:15:02 the-nexus systemd-logind[397]: Lid opened. Jan 02 12:15:02 the-nexus rtkit-daemon[815]: The canary thread is apparently starving. Taking action. Jan 02 12:15:02 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/ro’: Input/output error Jan 02 12:15:02 the-nexus systemd-logind[397]: Lid closed. Jan 02 12:15:02 the-nexus rtkit-daemon[815]: Demoting known real-time threads. Jan 02 12:15:02 the-nexus systemd-logind[397]: Lid opened. Jan 02 12:15:02 the-nexus rtkit-daemon[815]: Successfully demoted thread 1326 of process 1096. Jan 02 12:15:02 the-nexus systemd[1]: Starting Update locate database... Jan 02 12:15:02 the-nexus audit: BPF prog-id=36 op=LOAD Jan 02 12:15:02 the-nexus rtkit-daemon[815]: Successfully demoted thread 822 of process 807. Jan 02 12:15:02 the-nexus rtkit-daemon[815]: Successfully demoted thread 807 of process 807. Jan 02 12:15:02 the-nexus kernel: audit: type=1334 audit(1641143702.249:146): prog-id=36 op=LOAD Jan 02 12:15:02 the-nexus rtkit-daemon[815]: Successfully demoted thread 823 of process 808. Jan 02 12:15:02 the-nexus rtkit-daemon[815]: Successfully demoted thread 808 of process 808. Jan 02 12:15:02 the-nexus rtkit-daemon[815]: Successfully demoted thread 825 of process 806. Jan 02 12:15:02 the-nexus rtkit-daemon[815]: Successfully demoted thread 806 of process 806. Jan 02 12:15:02 the-nexus rtkit-daemon[815]: Demoted 7 threads. Jan 02 12:15:02 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 12:15:02 the-nexus systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Jan 02 12:15:02 the-nexus kernel: audit: type=1131 audit(1641143702.256:147): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 12:15:02 the-nexus systemd-sleep[17741]: System returned from sleep state. Jan 02 12:15:02 the-nexus kernel: PM: suspend exit Jan 02 12:15:02 the-nexus systemd[1]: systemd-suspend.service: Deactivated successfully. Jan 02 12:15:02 the-nexus systemd[1]: Finished System Suspend. Jan 02 12:15:02 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 12:15:02 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 12:15:02 the-nexus systemd[1]: Stopped target Sleep. Jan 02 12:15:02 the-nexus systemd[1]: Reached target Suspend. Jan 02 12:15:02 the-nexus systemd[1]: Stopped target Suspend. Jan 02 12:15:02 the-nexus boltd[425]: [c9030000-0080-ThinkPad X1 Yoga 4th / Carb] disconnected (/sys/devices/pci0000:00/0000:00:1d.4/0000:05:00.0/0000:06:00.0/0000:07:00.0/domain0/0-0) Jan 02 12:15:02 the-nexus kernel: audit: type=1130 audit(1641143702.336:148): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 12:15:02 the-nexus kernel: audit: type=1131 audit(1641143702.336:149): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 12:15:02 the-nexus systemd-logind[397]: Operation 'sleep' finished. Jan 02 12:15:02 the-nexus NetworkManager[396]: [1641143702.3430] manager: sleep: wake requested (sleeping: yes enabled: yes) Jan 02 12:15:02 the-nexus NetworkManager[396]: [1641143702.3431] device (enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Jan 02 12:15:02 the-nexus boltd[425]: [c9030000-0080-domain0 ] disconnected from /sys/devices/pci0000:00/0000:00:1d.4/0000:05:00.0/0000:06:00.0/0000:07:00.0/domain0 Jan 02 12:15:02 the-nexus boltd[425]: probing: removing /sys/devices/pci0000:00/0000:00:1d.4/0000:05:00.0 from roots Jan 02 12:15:02 the-nexus NetworkManager[396]: [1641143702.4244] device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 02 12:15:02 the-nexus kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down Jan 02 12:15:02 the-nexus NetworkManager[396]: [1641143702.6125] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 02 12:15:02 the-nexus NetworkManager[396]: [1641143702.6270] device (wlan0): set-hw-addr: set MAC address to 52:C7:02:A5:C3:FB (scanning) Jan 02 12:15:02 the-nexus NetworkManager[396]: [1641143702.8301] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 02 12:15:02 the-nexus NetworkManager[396]: [1641143702.8318] manager: NetworkManager state is now DISCONNECTED Jan 02 12:15:02 the-nexus NetworkManager[396]: [1641143702.8879] device (wlan0): supplicant interface state: internal-starting -> disconnected Jan 02 12:15:02 the-nexus NetworkManager[396]: [1641143702.8879] device (p2p-dev-wlan0): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed') Jan 02 12:15:02 the-nexus NetworkManager[396]: [1641143702.8883] Wi-Fi P2P device controlled by interface wlan0 created Jan 02 12:15:02 the-nexus NetworkManager[396]: [1641143702.8884] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/7) Jan 02 12:15:02 the-nexus NetworkManager[396]: [1641143702.8885] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 02 12:15:02 the-nexus NetworkManager[396]: [1641143702.8889] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Jan 02 12:15:02 the-nexus NetworkManager[396]: [1641143702.8894] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') Jan 02 12:15:02 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/ca’: Input/output error Jan 02 12:15:02 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973048 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:02 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385972: lblock 0: comm find: error -5 reading directory block Jan 02 12:15:03 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.168' (uid=1000 pid=17772 comm="/usr/lib/budgie-screensaver/budgie-screensaver-dia") Jan 02 12:15:03 the-nexus dbus-daemon[395]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found. Jan 02 12:15:03 the-nexus budgie-screensaver-dialog[17772]: pam_systemd_home(budgie-screensaver:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found. Jan 02 12:15:03 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973064 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:03 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385975: lblock 0: comm find: error -5 reading directory block Jan 02 12:15:03 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/gl’: Input/output error Jan 02 12:15:04 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973080 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:04 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385978: lblock 0: comm find: error -5 reading directory block Jan 02 12:15:04 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/jp’: Input/output error Jan 02 12:15:04 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973096 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:04 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385981: lblock 0: comm find: error -5 reading directory block Jan 02 12:15:04 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/eu’: Input/output error Jan 02 12:15:05 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973112 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:05 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385984: lblock 0: comm find: error -5 reading directory block Jan 02 12:15:05 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/zh_CN’: Input/output error Jan 02 12:15:05 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973152 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:05 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16385990: lblock 0: comm find: error -5 reading directory block Jan 02 12:15:05 the-nexus find[17616]: /usr/bin/find: ‘/var/cache/man/zh’: Input/output error Jan 02 12:15:05 the-nexus systemd[1]: man-db.service: Main process exited, code=exited, status=1/FAILURE Jan 02 12:15:05 the-nexus systemd[1]: man-db.service: Failed with result 'exit-code'. Jan 02 12:15:05 the-nexus systemd[1]: Failed to start Daily man-db regeneration. Jan 02 12:15:05 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=man-db comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Jan 02 12:15:05 the-nexus kernel: audit: type=1130 audit(1641143705.989:150): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=man-db comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Jan 02 12:15:06 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2202] policy: auto-activating connection 'NiceMagnolia' (1f6b04ef-bb63-4102-a785-c1fc54dfb549) Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2212] device (wlan0): Activation: starting connection 'NiceMagnolia' (1f6b04ef-bb63-4102-a785-c1fc54dfb549) Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2214] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2219] manager: NetworkManager state is now CONNECTING Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2240] device (wlan0): set-hw-addr: reset MAC address to CC:D9:AC:19:44:B1 (preserve) Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2251] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2256] device (wlan0): Activation: (wifi) access point 'NiceMagnolia' has security, but secrets are required. Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2257] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2260] sup-iface[dfc2b5e37b202c86,3,wlan0]: wps: type pbc start... Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2287] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2294] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2298] device (wlan0): Activation: (wifi) connection 'NiceMagnolia' has security, and secrets exist. No new secrets needed. Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2298] Config: added 'ssid' value 'NiceMagnolia' Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2299] Config: added 'scan_ssid' value '1' Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2299] Config: added 'bgscan' value 'simple:30:-70:86400' Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2299] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK' Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2299] Config: added 'auth_alg' value 'OPEN' Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2299] Config: added 'psk' value '' Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2782] device (wlan0): supplicant interface state: disconnected -> scanning Jan 02 12:15:06 the-nexus NetworkManager[396]: [1641143706.2783] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning Jan 02 12:15:07 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972672 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:07 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16387214: lblock 0: comm updatedb: error -5 reading directory block Jan 02 12:15:08 the-nexus wpa_supplicant[519]: wlan0: SME: Trying to authenticate with 98:da:c4:0d:90:d6 (SSID='NiceMagnolia' freq=5745 MHz) Jan 02 12:15:08 the-nexus kernel: wlan0: authenticate with 98:da:c4:0d:90:d6 Jan 02 12:15:08 the-nexus kernel: wlan0: send auth to 98:da:c4:0d:90:d6 (try 1/3) Jan 02 12:15:08 the-nexus NetworkManager[396]: [1641143708.3856] device (wlan0): supplicant interface state: scanning -> authenticating Jan 02 12:15:08 the-nexus NetworkManager[396]: [1641143708.3857] device (p2p-dev-wlan0): supplicant management interface state: scanning -> authenticating Jan 02 12:15:08 the-nexus wpa_supplicant[519]: wlan0: Trying to associate with 98:da:c4:0d:90:d6 (SSID='NiceMagnolia' freq=5745 MHz) Jan 02 12:15:08 the-nexus NetworkManager[396]: [1641143708.4241] device (wlan0): supplicant interface state: authenticating -> associating Jan 02 12:15:08 the-nexus NetworkManager[396]: [1641143708.4242] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating Jan 02 12:15:08 the-nexus kernel: wlan0: authenticated Jan 02 12:15:08 the-nexus kernel: wlan0: associate with 98:da:c4:0d:90:d6 (try 1/3) Jan 02 12:15:08 the-nexus kernel: wlan0: RX AssocResp from 98:da:c4:0d:90:d6 (capab=0x1411 status=0 aid=1) Jan 02 12:15:08 the-nexus wpa_supplicant[519]: wlan0: Associated with 98:da:c4:0d:90:d6 Jan 02 12:15:08 the-nexus kernel: wlan0: associated Jan 02 12:15:08 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Jan 02 12:15:08 the-nexus NetworkManager[396]: [1641143708.4442] device (wlan0): supplicant interface state: associating -> 4way_handshake Jan 02 12:15:08 the-nexus NetworkManager[396]: [1641143708.4443] device (p2p-dev-wlan0): supplicant management interface state: associating -> 4way_handshake Jan 02 12:15:08 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972736 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:08 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16387201: lblock 0: comm updatedb: error -5 reading directory block Jan 02 12:15:08 the-nexus wpa_supplicant[519]: wlan0: WPA: Key negotiation completed with 98:da:c4:0d:90:d6 [PTK=CCMP GTK=CCMP] Jan 02 12:15:08 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-CONNECTED - Connection to 98:da:c4:0d:90:d6 completed [id=0 id_str=] Jan 02 12:15:08 the-nexus kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Jan 02 12:15:08 the-nexus wpa_supplicant[519]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=9999 txrate=6000 Jan 02 12:15:08 the-nexus NetworkManager[396]: [1641143708.5216] device (wlan0): supplicant interface state: 4way_handshake -> completed Jan 02 12:15:08 the-nexus NetworkManager[396]: [1641143708.5216] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "NiceMagnolia" Jan 02 12:15:08 the-nexus NetworkManager[396]: [1641143708.5217] device (p2p-dev-wlan0): supplicant management interface state: 4way_handshake -> completed Jan 02 12:15:08 the-nexus NetworkManager[396]: [1641143708.5218] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Jan 02 12:15:08 the-nexus NetworkManager[396]: [1641143708.5223] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds) Jan 02 12:15:08 the-nexus avahi-daemon[394]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::aa95:e5f4:7984:863d. Jan 02 12:15:08 the-nexus avahi-daemon[394]: New relevant interface wlan0.IPv6 for mDNS. Jan 02 12:15:08 the-nexus avahi-daemon[394]: Registering new address record for fe80::aa95:e5f4:7984:863d on wlan0.*. Jan 02 12:15:08 the-nexus audit[17806]: USER_AUTH pid=17806 uid=1000 auid=1000 ses=2 msg='op=PAM:unix_chkpwd acct="synth" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success' Jan 02 12:15:08 the-nexus budgie-screensaver-dialog[17772]: gkr-pam: unlocked login keyring Jan 02 12:15:08 the-nexus kernel: audit: type=1100 audit(1641143708.986:151): pid=17806 uid=1000 auid=1000 ses=2 msg='op=PAM:unix_chkpwd acct="synth" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success' Jan 02 12:15:09 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973632 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:09 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16384001: comm updatedb: reading directory lblock 0 Jan 02 12:15:10 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973632 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:12 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16384001: comm updatedb: reading directory lblock 0 Jan 02 12:15:12 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973632 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:12 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16384001: comm updatedb: reading directory lblock 0 Jan 02 12:15:12 the-nexus kernel: audit: type=1130 audit(1641143710.886:152): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 12:15:12 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973632 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:12 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16384001: comm updatedb: reading directory lblock 0 Jan 02 12:15:12 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973632 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:12 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16384001: comm updatedb: reading directory lblock 0 Jan 02 12:15:10 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 12:15:12 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973752 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:12 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16384535: comm updatedb: reading directory lblock 0 Jan 02 12:15:10 the-nexus NetworkManager[396]: [1641143710.8563] dhcp4 (wlan0): state changed unknown -> bound, address=192.168.0.146 Jan 02 12:15:10 the-nexus avahi-daemon[394]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.146. Jan 02 12:15:10 the-nexus NetworkManager[396]: [1641143710.8601] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Jan 02 12:15:10 the-nexus avahi-daemon[394]: New relevant interface wlan0.IPv4 for mDNS. Jan 02 12:15:10 the-nexus systemd[1]: Starting Network Manager Script Dispatcher Service... Jan 02 12:15:10 the-nexus avahi-daemon[394]: Registering new address record for 192.168.0.146 on wlan0.IPv4. Jan 02 12:15:10 the-nexus systemd[1]: Started Network Manager Script Dispatcher Service. Jan 02 12:15:10 the-nexus dbus-daemon[395]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=396 comm="/usr/bin/NetworkManager --no-daemon ") Jan 02 12:15:10 the-nexus NetworkManager[396]: [1641143710.8906] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Jan 02 12:15:10 the-nexus dbus-daemon[395]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 02 12:15:10 the-nexus NetworkManager[396]: [1641143710.8910] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Jan 02 12:15:10 the-nexus NetworkManager[396]: [1641143710.8921] manager: NetworkManager state is now CONNECTED_LOCAL Jan 02 12:15:10 the-nexus NetworkManager[396]: [1641143710.8936] manager: NetworkManager state is now CONNECTED_SITE Jan 02 12:15:10 the-nexus NetworkManager[396]: [1641143710.8939] policy: set 'NiceMagnolia' (wlan0) as default for IPv4 routing and DNS Jan 02 12:15:11 the-nexus NetworkManager[396]: [1641143711.1634] device (wlan0): Activation: successful, device activated. Jan 02 12:15:11 the-nexus NetworkManager[396]: [1641143711.1657] manager: NetworkManager state is now CONNECTED_GLOBAL Jan 02 12:15:13 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973768 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:13 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16384555: comm updatedb: reading directory lblock 0 Jan 02 12:15:13 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973768 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:14 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16384555: comm updatedb: reading directory lblock 0 Jan 02 12:15:14 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973816 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:14 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16384603: comm updatedb: reading directory lblock 0 Jan 02 12:15:15 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973816 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:15 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16384603: comm updatedb: reading directory lblock 0 Jan 02 12:15:15 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973816 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:15 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16384603: comm updatedb: reading directory lblock 0 Jan 02 12:15:16 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973816 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:16 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16384603: comm updatedb: reading directory lblock 0 Jan 02 12:15:16 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973816 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:17 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16384603: comm updatedb: reading directory lblock 0 Jan 02 12:15:17 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973816 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:17 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16384603: comm updatedb: reading directory lblock 0 Jan 02 12:15:18 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524973816 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:18 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16384603: comm updatedb: reading directory lblock 0 Jan 02 12:15:18 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974064 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:18 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385267: comm updatedb: reading directory lblock 0 Jan 02 12:15:19 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974064 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:19 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385267: comm updatedb: reading directory lblock 0 Jan 02 12:15:20 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974064 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:20 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385267: comm updatedb: reading directory lblock 0 Jan 02 12:15:20 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974112 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:20 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385342: comm updatedb: reading directory lblock 0 Jan 02 12:15:21 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524974112 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:21 the-nexus kernel: EXT4-fs error (device nvme0n1p2): __ext4_find_entry:1612: inode #16385342: comm updatedb: reading directory lblock 0 Jan 02 12:15:21 the-nexus systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Jan 02 12:15:21 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 12:15:21 the-nexus kernel: audit: type=1131 audit(1641143721.336:153): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 12:15:21 the-nexus rtkit-daemon[815]: Supervising 0 threads of 0 processes of 0 users. Jan 02 12:15:21 the-nexus rtkit-daemon[815]: Supervising 0 threads of 0 processes of 0 users. Jan 02 12:15:22 the-nexus kernel: blk_update_request: critical medium error, dev nvme0n1, sector 524972632 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 02 12:15:22 the-nexus kernel: EXT4-fs warning (device nvme0n1p2): htree_dirblock_to_tree:1028: inode #16387211: lblock 0: comm updatedb: error -5 reading directory block Jan 02 12:15:22 the-nexus systemd[1]: updatedb.service: Deactivated successfully. Jan 02 12:15:22 the-nexus systemd[1]: Finished Update locate database. Jan 02 12:15:22 the-nexus systemd[1]: updatedb.service: Consumed 1.066s CPU time. Jan 02 12:15:22 the-nexus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=updatedb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 12:15:22 the-nexus audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=updatedb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 12:15:22 the-nexus kernel: audit: type=1130 audit(1641143722.493:154): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=updatedb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 12:15:22 the-nexus kernel: audit: type=1131 audit(1641143722.493:155): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=updatedb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 02 12:15:22 the-nexus audit: BPF prog-id=0 op=UNLOAD Jan 02 12:15:22 the-nexus kernel: audit: type=1334 audit(1641143722.593:156): prog-id=0 op=UNLOAD Jan 02 12:15:24 the-nexus rtkit-daemon[815]: Supervising 0 threads of 0 processes of 0 users. Jan 02 12:15:24 the-nexus rtkit-daemon[815]: Supervising 0 threads of 0 processes of 0 users. Jan 02 12:15:24 the-nexus rtkit-daemon[815]: Supervising 0 threads of 0 processes of 0 users. Jan 02 12:15:24 the-nexus rtkit-daemon[815]: Supervising 0 threads of 0 processes of 0 users. Jan 02 12:15:29 the-nexus rtkit-daemon[815]: Supervising 0 threads of 0 processes of 0 users. Jan 02 12:15:29 the-nexus rtkit-daemon[815]: Supervising 0 threads of 0 processes of 0 users. Jan 02 12:15:29 the-nexus rtkit-daemon[815]: Supervising 0 threads of 0 processes of 0 users. Jan 02 12:15:29 the-nexus rtkit-daemon[815]: Supervising 0 threads of 0 processes of 0 users. Jan 02 12:15:32 the-nexus rtkit-daemon[815]: Supervising 0 threads of 0 processes of 0 users. Jan 02 12:15:32 the-nexus rtkit-daemon[815]: Supervising 0 threads of 0 processes of 0 users. Jan 02 12:17:48 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.80' (uid=1000 pid=18128 comm="gnome-terminal ") Jan 02 12:17:48 the-nexus systemd[643]: Starting GNOME Terminal Server... Jan 02 12:17:48 the-nexus dbus-daemon[660]: [session uid=1000 pid=660] Successfully activated service 'org.gnome.Terminal' Jan 02 12:17:48 the-nexus systemd[643]: Started GNOME Terminal Server. Jan 02 12:17:48 the-nexus systemd[643]: Started VTE child process 18154 launched by gnome-terminal-server process 18133.