[SOLVED] installing nvidia on arch install causes freezes at boot / Newbie Corner / Arch Linux Forums\n» [SOLVED] installing nvidia on arch install causes freezes at boot\n#1 2021-06-08 22:40:24\n[SOLVED] installing nvidia on arch install causes freezes at boot\nI have been using linux systems for a few years now but I decided to jump into arch over the weekend. Everything was going great until I tried to install the nvidia drivers. I have an nvidia 1070\nWhatever method I try to install them, either using the pacman package or downloading the drivers from nvidia and running them I get the same result. when I try to start gnome with either gdm or startx it freezes. By freezing I mean it wont accept any input, I get a white bar at the top left that is static and I cant open another teminal with\nor anything and I have to reboot\nI assumed I was doing something wrong so I decided to script my install to as bare bones as I could to ensure I could replicate it without adding in mistakes and to show people what I am doing.\nSo i created a live USB with arch and I can boot into that fine.\nI then whipe partition 2 on my 1tb nvme and apply an empty partition. (full discolsue I leave partition 1 as it is the boot partition from my old ubuntu install, it contains my windows boot info and the last time I wiped it out I couldnt get my dual boot windows 10 install back)\nI then format it with mkfs.ext4 to get an ext4 partion,\nI then mount that at /mnt and run the following script\npacstrap /mnt base linux linux-firmware xorg gnome gnome-extra sudo git ntfs-3g grub efibootmgr linux-headers nvidia\ngenfstab /mnt >> /mnt/etc/fstab\nafter that I can arch-chroot into /mnt and run the following script\necho "root:$passwd" | chpasswd\necho 'en_GB.UTF-8 UTF-8' > /etc/locale.gen\necho 'LANG=en_GB.UTF-8' > /etc/locale.conf\n# set uk keyboard language\necho 'KEYMAP=uk' > /etc/vconsole.conf\necho 'pitt-arch' > /etc/hostname\n# add hosts\ncat <<EOF > /etc/hosts\n# alias vi\nln -s /usr/bin/vim /usr/bin/vi\nuseradd -m acleveland\nusermod -aG wheel acleveland\necho "acleveland:$passwd" | chpasswd\n# setup grub\ngrub-install --target=x86_64-efi --bootloader-id=ARCH --efi-directory=/boot/efi\n# enable gnome desktop manager and NetworkManager\n# disable vim mouse integration so rightclicking works\necho 'set mouse-=a' >> /root/.vimrc\necho 'set mouse-=a' >> /home/acleveland/.vimrc\n# allow user to run sudo without needing a password\necho '%wheel ALL=(ALL) NOPASSWD: ALL' >> /etc/sudoers\nIn the script above I have commented out the\nbecuase if I do that it just locks up and I have to boot in via the usb stick again and ruh arch-chroot.\nso when I login with root and password (Don't worry thats not actually my password, I just picked a random one for anyone that wants to try and replicate my issue with the same script) and run either\nit freezes. By freezing I mean it wont accept any input, I get a white bar at the top left that is static and I cant open another teminal with\nI have spent the last three days gooling and following suggestions for similar issues I can find and here is a quick list of the things I have tried so far:\n- I assumed it was a problem with gdm so I tried using startx, but that requires the xorg-xinit package. so I installed that, it prints a couple of lines and then it freezes too.\n- I tried install cinnamon, incase it was just a gnome issue. But that made no difference,\n- I tried using lightdm incase gdm was the problem, it freezes the same as with gdm.\n- I uncommented the\noption in /etc/gdm/custom.conf but that had no effect\n- I installed zen-linux with the zen-linux-headers incase it was a kernet issue\n- I installed linux-lts too, again the same result.\n- I downloaded the driver from nvida website and ran that with bash, it caused the same freeze at boot.\nI am not sure what more to try, I am hoping I have just missed something really simple that someone can point out.\nif there are any log entries that would be helpful to see I can extract them, at the moment I am using my windows OS to write this up as I have no gui on arch atm which makes things a bit of a pain but I can copy them around disks and get them out.\nI should add that if I do the exact same steps but take out the nvidia package from the pacstrap then everything works flawlessly. Its just the nvidia drivers that cuase everything to fall over\nLast edited by grimvoodoo (2021-06-09 22:18:23)\n#2 2021-06-08 22:58:55\nRe: [SOLVED] installing nvidia on arch install causes freezes at boot\nCan you boot the system to multi-user.target? If not use the installation media then chroot in.\nThen please post the journal for a boot that ended in a freeze.\n#3 2021-06-09 19:00:46\n-- Journal begins at Tue 2021-06-08 23:07:39 BST, ends at Wed 2021-06-09 19:47:11 BST. --\nJun 09 19:37:24 pitt-arch kernel: Linux version 5.12.9-arch1-1 (linux@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Thu, 03 Jun 2021 11:36:13 +0000\nJun 09 19:37:24 pitt-arch kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=b285af18-bfb6-4d95-9986-e1cb71bfb91f rw loglevel=3 quiet\nJun 09 19:37:24 pitt-arch kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'\nJun 09 19:37:24 pitt-arch kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'\nJun 09 19:37:24 pitt-arch kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'\nJun 09 19:37:24 pitt-arch kernel: x86/fpu: xstate_offset:  576, xstate_sizes:  256\nJun 09 19:37:24 pitt-arch kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.\nJun 09 19:37:24 pitt-arch kernel: BIOS-provided physical RAM map:\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009d81fff] usable\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x0000000009d82000-0x0000000009ffffff] reserved\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20ffff] ACPI NVS\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x000000000a210000-0x00000000cb48ffff] usable\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000cb490000-0x00000000cb837fff] reserved\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000cb838000-0x00000000cb887fff] ACPI data\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000cb888000-0x00000000cce53fff] ACPI NVS\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000cce54000-0x00000000cdd63fff] reserved\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000cdd64000-0x00000000cddfefff] type 20\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000cddff000-0x00000000ceffffff] usable\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000cf000000-0x00000000cfffffff] reserved\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000fd200000-0x00000000fd2fffff] reserved\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000fd400000-0x00000000fd5fffff] reserved\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x0000000100000000-0x000000082f2fffff] usable\nJun 09 19:37:24 pitt-arch kernel: BIOS-e820: [mem 0x000000082f300000-0x000000082fffffff] reserved\nJun 09 19:37:24 pitt-arch kernel: NX (Execute Disable) protection: active\nJun 09 19:37:24 pitt-arch kernel: efi: EFI v2.70 by American Megatrends\nJun 09 19:37:24 pitt-arch kernel: efi: ACPI=0xcce3b000 ACPI 2.0=0xcce3b014 SMBIOS=0xcdc14000 MEMATTR=0xc6b7a018\nJun 09 19:37:24 pitt-arch kernel: SMBIOS 2.8 present.\nJun 09 19:37:24 pitt-arch kernel: DMI: Micro-Star International Co., Ltd. MS-7C84/MAG X570 TOMAHAWK WIFI (MS-7C84), BIOS 1.10 07/14/2020\nJun 09 19:37:24 pitt-arch kernel: tsc: Fast TSC calibration using PIT\nJun 09 19:37:24 pitt-arch kernel: tsc: Detected 3800.051 MHz processor\nJun 09 19:37:24 pitt-arch kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved\nJun 09 19:37:24 pitt-arch kernel: e820: remove [mem 0x000a0000-0x000fffff] usable\nJun 09 19:37:24 pitt-arch kernel: last_pfn = 0x82f300 max_arch_pfn = 0x400000000\nJun 09 19:37:24 pitt-arch kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT\nJun 09 19:37:24 pitt-arch kernel: total RAM covered: 3327M\nJun 09 19:37:24 pitt-arch kernel: Found optimal setting for mtrr clean up\nJun 09 19:37:24 pitt-arch kernel:  gran_size: 64K         chunk_size: 64M         num_reg: 4          lose cover RAM: 0G\nJun 09 19:37:24 pitt-arch kernel: e820: update [mem 0xcd500000-0xcd50ffff] usable ==> reserved\nJun 09 19:37:24 pitt-arch kernel: e820: update [mem 0xd0000000-0xffffffff] usable ==> reserved\nJun 09 19:37:24 pitt-arch kernel: last_pfn = 0xcf000 max_arch_pfn = 0x400000000\nJun 09 19:37:24 pitt-arch kernel: check: Scanning 1 areas for low memory corruption\nJun 09 19:37:24 pitt-arch kernel: Using GB pages for direct mapping\nJun 09 19:37:24 pitt-arch kernel: Secure boot could not be determined\nJun 09 19:37:24 pitt-arch kernel: RAMDISK: [mem 0x37089000-0x3783bfff]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Early table checksum verification disabled\nJun 09 19:37:24 pitt-arch kernel: ACPI: RSDP 0x00000000CCE3B014 000024 (v02 ALASKA)\nJun 09 19:37:24 pitt-arch kernel: ACPI: XSDT 0x00000000CCE3A728 0000BC (v01 ALASKA A M I    01072009 AMI  01000013)\nJun 09 19:37:24 pitt-arch kernel: ACPI: FACP 0x00000000CB879000 000114 (v06 ALASKA A M I    01072009 AMI  00010013)\nJun 09 19:37:24 pitt-arch kernel: ACPI: DSDT 0x00000000CB871000 007B30 (v02 ALASKA A M I    01072009 INTL 20120913)\nJun 09 19:37:24 pitt-arch kernel: ACPI: FACS 0x00000000CCE35000 000040\nJun 09 19:37:24 pitt-arch kernel: ACPI: SSDT 0x00000000CB87F000 008C98 (v02 AMD    AmdTable 00000002 MSFT 04000000)\nJun 09 19:37:24 pitt-arch kernel: ACPI: SSDT 0x00000000CB87B000 003A78 (v01 AMD    AMD AOD  00000001 INTL 20120913)\nJun 09 19:37:24 pitt-arch kernel: ACPI: SSDT 0x00000000CB87A000 000164 (v02 ALASKA CPUSSDT  01072009 AMI  01072009)\nJun 09 19:37:24 pitt-arch kernel: ACPI: FIDT 0x00000000CB870000 00009C (v01 ALASKA A M I    01072009 AMI  00010013)\nJun 09 19:37:24 pitt-arch kernel: ACPI: MCFG 0x00000000CB86F000 00003C (v01 ALASKA A M I    01072009 MSFT 00010013)\nJun 09 19:37:24 pitt-arch kernel: ACPI: HPET 0x00000000CB86E000 000038 (v01 ALASKA A M I    01072009 AMI  00000005)\nJun 09 19:37:24 pitt-arch kernel: ACPI: SSDT 0x00000000CB86D000 000024 (v01 AMD    BIXBY    00001000 INTL 20120913)\nJun 09 19:37:24 pitt-arch kernel: ACPI: IVRS 0x00000000CB86C000 0000D0 (v02 AMD    AmdTable 00000001 AMD  00000000)\nJun 09 19:37:24 pitt-arch kernel: ACPI: PCCT 0x00000000CB86B000 00006E (v02 AMD    AmdTable 00000001 AMD  00000000)\nJun 09 19:37:24 pitt-arch kernel: ACPI: SSDT 0x00000000CB865000 005E09 (v02 AMD    AmdTable 00000001 AMD  00000001)\nJun 09 19:37:24 pitt-arch kernel: ACPI: CRAT 0x00000000CB863000 001658 (v01 AMD    AmdTable 00000001 AMD  00000001)\nJun 09 19:37:24 pitt-arch kernel: ACPI: CDIT 0x00000000CB862000 000029 (v01 AMD    AmdTable 00000001 AMD  00000001)\nJun 09 19:37:24 pitt-arch kernel: ACPI: BGRT 0x00000000CB861000 000038 (v01 ALASKA A M I    01072009 AMI  00010013)\nJun 09 19:37:24 pitt-arch kernel: ACPI: SSDT 0x00000000CB85D000 003282 (v01 AMD    AmdTable 00000001 INTL 20120913)\nJun 09 19:37:24 pitt-arch kernel: ACPI: WSMT 0x00000000CB85C000 000028 (v01 ALASKA A M I    01072009 AMI  00010013)\nJun 09 19:37:24 pitt-arch kernel: ACPI: APIC 0x00000000CB85B000 00015E (v03 ALASKA A M I    01072009 AMI  00010013)\nJun 09 19:37:24 pitt-arch kernel: ACPI: SSDT 0x00000000CB859000 0010AF (v01 AMD    AmdTable 00000001 INTL 20120913)\nJun 09 19:37:24 pitt-arch kernel: ACPI: FPDT 0x00000000CB858000 000044 (v01 ALASKA A M I    01072009 AMI  01000013)\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving FACP table memory at [mem 0xcb879000-0xcb879113]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving DSDT table memory at [mem 0xcb871000-0xcb878b2f]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving FACS table memory at [mem 0xcce35000-0xcce3503f]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving SSDT table memory at [mem 0xcb87f000-0xcb887c97]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving SSDT table memory at [mem 0xcb87b000-0xcb87ea77]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving SSDT table memory at [mem 0xcb87a000-0xcb87a163]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving FIDT table memory at [mem 0xcb870000-0xcb87009b]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving MCFG table memory at [mem 0xcb86f000-0xcb86f03b]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving HPET table memory at [mem 0xcb86e000-0xcb86e037]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving SSDT table memory at [mem 0xcb86d000-0xcb86d023]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving IVRS table memory at [mem 0xcb86c000-0xcb86c0cf]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving PCCT table memory at [mem 0xcb86b000-0xcb86b06d]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving SSDT table memory at [mem 0xcb865000-0xcb86ae08]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving CRAT table memory at [mem 0xcb863000-0xcb864657]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving CDIT table memory at [mem 0xcb862000-0xcb862028]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving BGRT table memory at [mem 0xcb861000-0xcb861037]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving SSDT table memory at [mem 0xcb85d000-0xcb860281]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving WSMT table memory at [mem 0xcb85c000-0xcb85c027]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving APIC table memory at [mem 0xcb85b000-0xcb85b15d]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving SSDT table memory at [mem 0xcb859000-0xcb85a0ae]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Reserving FPDT table memory at [mem 0xcb858000-0xcb858043]\nJun 09 19:37:24 pitt-arch kernel: ACPI: Local APIC address 0xfee00000\nJun 09 19:37:24 pitt-arch kernel: No NUMA configuration found\nJun 09 19:37:24 pitt-arch kernel: Faking a node at [mem 0x0000000000000000-0x000000082f2fffff]\nJun 09 19:37:24 pitt-arch kernel: NODE_DATA(0) allocated [mem 0x82f2fc000-0x82f2fffff]\nJun 09 19:37:24 pitt-arch kernel: Zone ranges:\nJun 09 19:37:24 pitt-arch kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]\nJun 09 19:37:24 pitt-arch kernel:   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]\nJun 09 19:37:24 pitt-arch kernel:   Normal   [mem 0x0000000100000000-0x000000082f2fffff]\nJun 09 19:37:24 pitt-arch kernel:   Device   empty\nJun 09 19:37:24 pitt-arch kernel: Movable zone start for each node\nJun 09 19:37:24 pitt-arch kernel: Early memory node ranges\nJun 09 19:37:24 pitt-arch kernel:   node   0: [mem 0x0000000000001000-0x000000000009ffff]\nJun 09 19:37:24 pitt-arch kernel:   node   0: [mem 0x0000000000100000-0x0000000009d81fff]\nJun 09 19:37:24 pitt-arch kernel:   node   0: [mem 0x000000000a000000-0x000000000a1fffff]\nJun 09 19:37:24 pitt-arch kernel:   node   0: [mem 0x000000000a210000-0x00000000cb48ffff]\nJun 09 19:37:24 pitt-arch kernel:   node   0: [mem 0x00000000cddff000-0x00000000ceffffff]\nJun 09 19:37:24 pitt-arch kernel:   node   0: [mem 0x0000000100000000-0x000000082f2fffff]\nJun 09 19:37:24 pitt-arch kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000082f2fffff]\nJun 09 19:37:24 pitt-arch kernel: On node 0 totalpages: 8369826\nJun 09 19:37:24 pitt-arch kernel:   DMA zone: 64 pages used for memmap\nJun 09 19:37:24 pitt-arch kernel:   DMA zone: 29 pages reserved\nJun 09 19:37:24 pitt-arch kernel:   DMA zone: 3999 pages, LIFO batch:0\nJun 09 19:37:24 pitt-arch kernel:   DMA zone: 28769 pages in unavailable ranges\nJun 09 19:37:24 pitt-arch kernel:   DMA32 zone: 13009 pages used for memmap\nJun 09 19:37:24 pitt-arch kernel:   DMA32 zone: 832515 pages, LIFO batch:63\nJun 09 19:37:24 pitt-arch kernel:   DMA32 zone: 15357 pages in unavailable ranges\nJun 09 19:37:24 pitt-arch kernel:   Normal zone: 117708 pages used for memmap\nJun 09 19:37:24 pitt-arch kernel:   Normal zone: 7533312 pages, LIFO batch:63\nJun 09 19:37:24 pitt-arch kernel:   Normal zone: 3328 pages in unavailable ranges\nJun 09 19:37:24 pitt-arch kernel: ACPI: PM-Timer IO Port: 0x808\nJun 09 19:37:24 pitt-arch kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])\nJun 09 19:37:24 pitt-arch kernel: IOAPIC: apic_id 25, version 33, address 0xfec00000, GSI 0-23\nJun 09 19:37:24 pitt-arch kernel: IOAPIC: apic_id 26, version 33, address 0xfec01000, GSI 24-55\nJun 09 19:37:24 pitt-arch kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)\nJun 09 19:37:24 pitt-arch kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)\nJun 09 19:37:24 pitt-arch kernel: ACPI: IRQ0 used by override.\nJun 09 19:37:24 pitt-arch kernel: ACPI: IRQ9 used by override.\nJun 09 19:37:24 pitt-arch kernel: Using ACPI (MADT) for SMP configuration information\nJun 09 19:37:24 pitt-arch kernel: ACPI: HPET id: 0x10228201 base: 0xfed00000\nJun 09 19:37:24 pitt-arch kernel: e820: update [mem 0xc6a8d000-0xc6ae9fff] usable ==> reserved\nJun 09 19:37:24 pitt-arch kernel: smpboot: Allowing 32 CPUs, 8 hotplug CPUs\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000fffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0x09d82000-0x09ffffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0x0a200000-0x0a20ffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xc6a8d000-0xc6ae9fff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xcb490000-0xcb837fff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xcb838000-0xcb887fff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xcb888000-0xcce53fff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xcce54000-0xcdd63fff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xcdd64000-0xcddfefff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xcf000000-0xcfffffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xd0000000-0xefffffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xf0000000-0xf7ffffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xf8000000-0xfd1fffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfd200000-0xfd2fffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfd300000-0xfd3fffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfd400000-0xfd5fffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfd600000-0xfe9fffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfea00000-0xfea0ffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfea10000-0xfeb7ffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfeb80000-0xfec01fff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfec02000-0xfec0ffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfec10000-0xfec10fff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfec11000-0xfecfffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfed00000-0xfed00fff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfed01000-0xfed3ffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfed40000-0xfed44fff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfed45000-0xfed7ffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfed80000-0xfed8ffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfed90000-0xfedc1fff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfedc2000-0xfedcffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfedd0000-0xfedd3fff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfedd4000-0xfedd5fff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xfedd6000-0xfeffffff]\nJun 09 19:37:24 pitt-arch kernel: PM: hibernation: Registered nosave memory: [mem 0xff000000-0xffffffff]\nJun 09 19:37:24 pitt-arch kernel: [mem 0xd0000000-0xefffffff] available for PCI devices\nJun 09 19:37:24 pitt-arch kernel: Booting paravirtualized kernel on bare hardware\nJun 09 19:37:24 pitt-arch kernel: clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370452778343963 ns\nJun 09 19:37:24 pitt-arch kernel: setup_percpu: NR_CPUS:320 nr_cpumask_bits:320 nr_cpu_ids:32 nr_node_ids:1\nJun 09 19:37:24 pitt-arch kernel: percpu: Embedded 56 pages/cpu s192512 r8192 d28672 u262144\nJun 09 19:37:24 pitt-arch kernel: pcpu-alloc: s192512 r8192 d28672 u262144 alloc=1*2097152\nJun 09 19:37:24 pitt-arch kernel: pcpu-alloc:  00 01 02 03 04 05 06 07  08 09 10 11 12 13 14 15\nJun 09 19:37:24 pitt-arch kernel: pcpu-alloc:  16 17 18 19 20 21 22 23  24 25 26 27 28 29 30 31\nJun 09 19:37:24 pitt-arch kernel: Built 1 zonelists, mobility grouping on.  Total pages: 8239016\nJun 09 19:37:24 pitt-arch kernel: Policy zone: Normal\nJun 09 19:37:24 pitt-arch kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=b285af18-bfb6-4d95-9986-e1cb71bfb91f rw loglevel=3 quiet\nJun 09 19:37:24 pitt-arch kernel: printk: log_buf_len individual max cpu contribution: 4096 bytes\nJun 09 19:37:24 pitt-arch kernel: printk: log_buf_len total cpu_extra contributions: 126976 bytes\nJun 09 19:37:24 pitt-arch kernel: printk: log_buf_len min size: 131072 bytes\nJun 09 19:37:24 pitt-arch kernel: printk: log_buf_len: 262144 bytes\nJun 09 19:37:24 pitt-arch kernel: printk: early log buf free: 117256(89%)\nJun 09 19:37:24 pitt-arch kernel: Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear)\nJun 09 19:37:24 pitt-arch kernel: Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)\nJun 09 19:37:24 pitt-arch kernel: mem auto-init: stack:byref_all(zero), heap alloc:on, heap free:off\nJun 09 19:37:24 pitt-arch kernel: Memory: 32690012K/33479304K available (14344K kernel code, 2040K rwdata, 8988K rodata, 1652K init, 4372K bss, 789032K reserved, 0K cma-reserved)\nJun 09 19:37:24 pitt-arch kernel: random: get_random_u64 called from __kmem_cache_create+0x22/0x530 with crng_init=0\nJun 09 19:37:24 pitt-arch kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=32, Nodes=1\nJun 09 19:37:24 pitt-arch kernel: ftrace: allocating 41904 entries in 164 pages\nJun 09 19:37:24 pitt-arch kernel: ftrace: allocated 164 pages with 3 groups\nJun 09 19:37:24 pitt-arch kernel: rcu: Preemptible hierarchical RCU implementation.\nJun 09 19:37:24 pitt-arch kernel: rcu:         RCU dyntick-idle grace-period acceleration is enabled.\nJun 09 19:37:24 pitt-arch kernel: rcu:         RCU restricting CPUs from NR_CPUS=320 to nr_cpu_ids=32.\nJun 09 19:37:24 pitt-arch kernel: rcu:         RCU priority boosting: priority 1 delay 500 ms.\nJun 09 19:37:24 pitt-arch kernel:         Trampoline variant of Tasks RCU enabled.\nJun 09 19:37:24 pitt-arch kernel:         Rude variant of Tasks RCU enabled.\nJun 09 19:37:24 pitt-arch kernel:         Tracing variant of Tasks RCU enabled.\nJun 09 19:37:24 pitt-arch kernel: rcu: RCU calculated value of scheduler-enlistment delay is 30 jiffies.\nJun 09 19:37:24 pitt-arch kernel: rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=32\nJun 09 19:37:24 pitt-arch kernel: NR_IRQS: 20736, nr_irqs: 1224, preallocated irqs: 16\nJun 09 19:37:24 pitt-arch kernel: Console: colour dummy device 80x25\nJun 09 19:37:24 pitt-arch kernel: printk: console [tty0] enabled\nJun 09 19:37:24 pitt-arch kernel: ACPI: Core revision 20210105\nJun 09 19:37:24 pitt-arch kernel: clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484873504 ns\nJun 09 19:37:24 pitt-arch kernel: APIC: Switch to symmetric I/O mode setup\nJun 09 19:37:24 pitt-arch kernel: Switched APIC routing to physical flat.\nJun 09 19:37:24 pitt-arch kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1\nJun 09 19:37:24 pitt-arch kernel: clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x6d8d1192ae4, max_idle_ns: 881591123823 ns\nJun 09 19:37:24 pitt-arch kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 7603.77 BogoMIPS (lpj=12666836)\nJun 09 19:37:24 pitt-arch kernel: pid_max: default: 32768 minimum: 301\nJun 09 19:37:24 pitt-arch kernel: LSM: Security Framework initializing\nJun 09 19:37:24 pitt-arch kernel: Yama: becoming mindful.\nJun 09 19:37:24 pitt-arch kernel: LSM support for eBPF active\nJun 09 19:37:24 pitt-arch kernel: Mount-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)\nJun 09 19:37:24 pitt-arch kernel: Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)\nJun 09 19:37:24 pitt-arch kernel: x86/cpu: User Mode Instruction Prevention (UMIP) activated\nJun 09 19:37:24 pitt-arch kernel: LVT offset 1 assigned for vector 0xf9\nJun 09 19:37:24 pitt-arch kernel: LVT offset 2 assigned for vector 0xf4\nJun 09 19:37:24 pitt-arch kernel: Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 512\nJun 09 19:37:24 pitt-arch kernel: Last level dTLB entries: 4KB 2048, 2MB 2048, 4MB 1024, 1GB 0\nJun 09 19:37:24 pitt-arch kernel: Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization\nJun 09 19:37:24 pitt-arch kernel: Spectre V2 : Mitigation: Full AMD retpoline\nJun 09 19:37:24 pitt-arch kernel: Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch\nJun 09 19:37:24 pitt-arch kernel: Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier\nJun 09 19:37:24 pitt-arch kernel: Spectre V2 : User space: Mitigation: STIBP via seccomp and prctl\nJun 09 19:37:24 pitt-arch kernel: Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp\nJun 09 19:37:24 pitt-arch kernel: Freeing SMP alternatives memory: 36K\nJun 09 19:37:24 pitt-arch kernel: smpboot: CPU0: AMD Ryzen 9 3900X 12-Core Processor (family: 0x17, model: 0x71, stepping: 0x0)\nJun 09 19:37:24 pitt-arch kernel: Performance Events: Fam17h+ core perfctr, AMD PMU driver.\nJun 09 19:37:24 pitt-arch kernel: ... version:                0\nJun 09 19:37:24 pitt-arch kernel: ... bit width:              48\nJun 09 19:37:24 pitt-arch kernel: ... generic registers:      6\nJun 09 19:37:24 pitt-arch kernel: ... value mask:             0000ffffffffffff\nJun 09 19:37:24 pitt-arch kernel: ... max period:             00007fffffffffff\nJun 09 19:37:24 pitt-arch kernel: ... fixed-purpose events:   0\nJun 09 19:37:24 pitt-arch kernel: ... event mask:             000000000000003f\nJun 09 19:37:24 pitt-arch kernel: rcu: Hierarchical SRCU implementation.\nJun 09 19:37:24 pitt-arch kernel: NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.\nJun 09 19:37:24 pitt-arch kernel: smp: Bringing up secondary CPUs ...\nJun 09 19:37:24 pitt-arch kernel: x86: Booting SMP configuration:\nJun 09 19:37:24 pitt-arch kernel: .... node  #0, CPUs:        #1\nJun 09 19:37:24 pitt-arch kernel: __common_interrupt: 1.55 No irq handler for vector\nJun 09 19:37:24 pitt-arch kernel:   #2\nJun 09 19:37:24 pitt-arch kernel: __common_interrupt: 2.55 No irq handler for vector\nJun 09 19:37:24 pitt-arch kernel:   #3\nJun 09 19:37:24 pitt-arch kernel: __common_interrupt: 3.55 No irq handler for vector\nJun 09 19:37:24 pitt-arch kernel:   #4\nJun 09 19:37:24 pitt-arch kernel: __common_interrupt: 4.55 No irq handler for vector\nJun 09 19:37:24 pitt-arch kernel:   #5\nJun 09 19:37:24 pitt-arch kernel: __common_interrupt: 5.55 No irq handler for vector\nJun 09 19:37:24 pitt-arch kernel:   #6\nJun 09 19:37:24 pitt-arch kernel: __common_interrupt: 6.55 No irq handler for vector\nJun 09 19:37:24 pitt-arch kernel:   #7\nJun 09 19:37:24 pitt-arch kernel: __common_interrupt: 7.55 No irq handler for vector\nJun 09 19:37:24 pitt-arch kernel:   #8\nJun 09 19:37:24 pitt-arch kernel: __common_interrupt: 8.55 No irq handler for vector\nJun 09 19:37:24 pitt-arch kernel:   #9\nJun 09 19:37:24 pitt-arch kernel: __common_interrupt: 9.55 No irq handler for vector\nJun 09 19:37:24 pitt-arch kernel:  #10\nJun 09 19:37:24 pitt-arch kernel: __common_interrupt: 10.55 No irq handler for vector\nJun 09 19:37:24 pitt-arch kernel:  #11 #12 #13 #14 #15 #16 #17 #18 #19 #20 #21 #22 #23\nJun 09 19:37:24 pitt-arch kernel: smp: Brought up 1 node, 24 CPUs\nJun 09 19:37:24 pitt-arch kernel: smpboot: Max logical packages: 2\nJun 09 19:37:24 pitt-arch kernel: smpboot: Total of 24 processors activated (182475.54 BogoMIPS)\nJun 09 19:37:24 pitt-arch kernel: devtmpfs: initialized\nJun 09 19:37:24 pitt-arch kernel: x86/mm: Memory block size: 128MB\nJun 09 19:37:24 pitt-arch kernel: PM: Registering ACPI NVS region [mem 0x0a200000-0x0a20ffff] (65536 bytes)\nJun 09 19:37:24 pitt-arch kernel: PM: Registering ACPI NVS region [mem 0xcb888000-0xcce53fff] (22855680 bytes)\nJun 09 19:37:24 pitt-arch kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370867519511994 ns\nJun 09 19:37:24 pitt-arch kernel: futex hash table entries: 8192 (order: 7, 524288 bytes, linear)\nJun 09 19:37:24 pitt-arch kernel: pinctrl core: initialized pinctrl subsystem\nJun 09 19:37:24 pitt-arch kernel: PM: RTC time: 18:37:21, date: 2021-06-09\nJun 09 19:37:24 pitt-arch kernel: NET: Registered protocol family 16\nJun 09 19:37:24 pitt-arch kernel: DMA: preallocated 4096 KiB GFP_KERNEL pool for atomic allocations\nJun 09 19:37:24 pitt-arch kernel: DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations\nJun 09 19:37:24 pitt-arch kernel: DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations\nJun 09 19:37:24 pitt-arch kernel: audit: initializing netlink subsys (disabled)\nJun 09 19:37:24 pitt-arch kernel: audit: type=2000 audit(1623263841.183:1): state=initialized audit_enabled=0 res=1\nJun 09 19:37:24 pitt-arch kernel: thermal_sys: Registered thermal governor 'fair_share'\nJun 09 19:37:24 pitt-arch kernel: thermal_sys: Registered thermal governor 'bang_bang'\nJun 09 19:37:24 pitt-arch kernel: thermal_sys: Registered thermal governor 'step_wise'\nJun 09 19:37:24 pitt-arch kernel: thermal_sys: Registered thermal governor 'user_space'\nJun 09 19:37:24 pitt-arch kernel: thermal_sys: Registered thermal governor 'power_allocator'\nJun 09 19:37:24 pitt-arch kernel: cpuidle: using governor ladder\nJun 09 19:37:24 pitt-arch kernel: cpuidle: using governor menu\nJun 09 19:37:24 pitt-arch kernel: Detected 1 PCC Subspaces\nJun 09 19:37:24 pitt-arch kernel: Registering PCC driver as Mailbox controller\nJun 09 19:37:24 pitt-arch kernel: ACPI: bus type PCI registered\nJun 09 19:37:24 pitt-arch kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5\nJun 09 19:37:24 pitt-arch kernel: PCI: MMCONFIG for domain 0000 [bus 00-7f] at [mem 0xf0000000-0xf7ffffff] (base 0xf0000000)\nJun 09 19:37:24 pitt-arch kernel: PCI: MMCONFIG at [mem 0xf0000000-0xf7ffffff] reserved in E820\nJun 09 19:37:24 pitt-arch kernel: PCI: Using configuration type 1 for base access\nJun 09 19:37:24 pitt-arch kernel: Kprobes globally optimized\nJun 09 19:37:24 pitt-arch kernel: HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages\nJun 09 19:37:24 pitt-arch kernel: HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages\nJun 09 19:37:24 pitt-arch kernel: fbcon: Taking over console\nJun 09 19:37:24 pitt-arch kernel: ACPI: Added _OSI(Module Device)\nJun 09 19:37:24 pitt-arch kernel: ACPI: Added _OSI(Processor Device)\nJun 09 19:37:24 pitt-arch kernel: ACPI: Added _OSI(3.0 _SCP Extensions)\nJun 09 19:37:24 pitt-arch kernel: ACPI: Added _OSI(Processor Aggregator Device)\nJun 09 19:37:24 pitt-arch kernel: ACPI: Added _OSI(Linux-Dell-Video)\nJun 09 19:37:24 pitt-arch kernel: ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)\nJun 09 19:37:24 pitt-arch kernel: ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)\nJun 09 19:37:24 pitt-arch kernel: ACPI: 8 ACPI AML tables successfully acquired and loaded\nJun 09 19:37:24 pitt-arch kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored\nJun 09 19:37:24 pitt-arch kernel: ACPI: Interpreter enabled\nJun 09 19:37:24 pitt-arch kernel: ACPI: (supports S0 S3 S4 S5)\nJun 09 19:37:24 pitt-arch kernel: ACPI: Using IOAPIC for interrupt routing\nJun 09 19:37:24 pitt-arch kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug\nJun 09 19:37:24 pitt-arch kernel: ACPI: Enabled 2 GPEs in block 00 to 1F\nJun 09 19:37:24 pitt-arch kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])\nJun 09 19:37:24 pitt-arch kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI EDR HPX-Type3]\nJun 09 19:37:24 pitt-arch kernel: acpi PNP0A08:00: _OSC: platform does not support [SHPCHotplug PME LTR DPC]\nJun 09 19:37:24 pitt-arch kernel: acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug AER PCIeCapability]\nJun 09 19:37:24 pitt-arch kernel: acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-7f] only partially covers this bridge\nJun 09 19:37:24 pitt-arch kernel: PCI host bridge to bus 0000:00\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:00: root bus resource [io  0x0000-0x03af window]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7 window]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:00: root bus resource [io  0x03b0-0x03df window]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff window]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:00: root bus resource [mem 0xd0000000-0xfec02fff window]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:00: root bus resource [mem 0xfee00000-0xffffffff window]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:00: root bus resource [bus 00-ff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:00.0: [1022:1480] type 00 class 0x060000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:00.2: [1022:1481] type 00 class 0x080600\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:01.0: [1022:1482] type 00 class 0x060000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:01.1: [1022:1483] type 01 class 0x060400\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:01.1: PME# supported from D0 D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:01.2: [1022:1483] type 01 class 0x060400\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:01.2: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:01.2: PME# supported from D0 D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:02.0: [1022:1482] type 00 class 0x060000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:03.0: [1022:1482] type 00 class 0x060000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:03.1: [1022:1483] type 01 class 0x060400\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:03.1: PME# supported from D0 D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:04.0: [1022:1482] type 00 class 0x060000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:05.0: [1022:1482] type 00 class 0x060000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:07.0: [1022:1482] type 00 class 0x060000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:07.1: [1022:1484] type 01 class 0x060400\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:07.1: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:07.1: PME# supported from D0 D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:08.0: [1022:1482] type 00 class 0x060000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:08.1: [1022:1484] type 01 class 0x060400\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:08.1: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:08.1: PME# supported from D0 D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:14.0: [1022:790b] type 00 class 0x0c0500\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:14.3: [1022:790e] type 00 class 0x060100\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:18.0: [1022:1440] type 00 class 0x060000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:18.1: [1022:1441] type 00 class 0x060000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:18.2: [1022:1442] type 00 class 0x060000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:18.3: [1022:1443] type 00 class 0x060000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:18.4: [1022:1444] type 00 class 0x060000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:18.5: [1022:1445] type 00 class 0x060000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:18.6: [1022:1446] type 00 class 0x060000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:18.7: [1022:1447] type 00 class 0x060000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:01:00.0: [144d:a80a] type 00 class 0x010802\nJun 09 19:37:24 pitt-arch kernel: pci 0000:01:00.0: reg 0x10: [mem 0xfcc00000-0xfcc03fff 64bit]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:01.1: PCI bridge to [bus 01]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:01.1:   bridge window [mem 0xfcc00000-0xfccfffff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:20:00.0: [1022:57ad] type 01 class 0x060400\nJun 09 19:37:24 pitt-arch kernel: pci 0000:20:00.0: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:20:00.0: PME# supported from D0 D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:20:00.0: 63.012 Gb/s available PCIe bandwidth, limited by 16.0 GT/s PCIe x4 link at 0000:00:01.2 (capable of 126.024 Gb/s with 16.0 GT/s PCIe x8 link)\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:01.2: PCI bridge to [bus 20-2c]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:01.2:   bridge window [io  0xf000-0xffff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:01.2:   bridge window [mem 0xfc200000-0xfc8fffff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:01.0: [1022:57a3] type 01 class 0x060400\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:01.0: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:01.0: PME# supported from D0 D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:04.0: [1022:57a3] type 01 class 0x060400\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:04.0: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:04.0: PME# supported from D0 D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:06.0: [1022:57a3] type 01 class 0x060400\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:06.0: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:06.0: PME# supported from D0 D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:08.0: [1022:57a4] type 01 class 0x060400\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:08.0: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:08.0: PME# supported from D0 D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:09.0: [1022:57a4] type 01 class 0x060400\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:09.0: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:09.0: PME# supported from D0 D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:0a.0: [1022:57a4] type 01 class 0x060400\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:0a.0: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:0a.0: PME# supported from D0 D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:20:00.0: PCI bridge to [bus 21-2c]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:20:00.0:   bridge window [io  0xf000-0xffff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:20:00.0:   bridge window [mem 0xfc200000-0xfc8fffff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:23:00.0: [15b7:5002] type 00 class 0x010802\nJun 09 19:37:24 pitt-arch kernel: pci 0000:23:00.0: reg 0x10: [mem 0xfc800000-0xfc803fff 64bit]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:23:00.0: reg 0x20: [mem 0xfc804000-0xfc8040ff 64bit]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:01.0: PCI bridge to [bus 23]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:01.0:   bridge window [mem 0xfc800000-0xfc8fffff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:26:00.0: [10ec:8125] type 00 class 0x020000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:26:00.0: reg 0x10: [io  0xf000-0xf0ff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:26:00.0: reg 0x18: [mem 0xfc700000-0xfc70ffff 64bit]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:26:00.0: reg 0x20: [mem 0xfc710000-0xfc713fff 64bit]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:26:00.0: supports D1 D2\nJun 09 19:37:24 pitt-arch kernel: pci 0000:26:00.0: PME# supported from D0 D1 D2 D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:04.0: PCI bridge to [bus 26]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:04.0:   bridge window [io  0xf000-0xffff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:04.0:   bridge window [mem 0xfc700000-0xfc7fffff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:28:00.0: [8086:2723] type 00 class 0x028000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:28:00.0: reg 0x10: [mem 0xfc600000-0xfc603fff 64bit]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:28:00.0: PME# supported from D0 D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:06.0: PCI bridge to [bus 28]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:06.0:   bridge window [mem 0xfc600000-0xfc6fffff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2a:00.0: [1022:1485] type 00 class 0x130000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2a:00.0: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2a:00.0: 63.012 Gb/s available PCIe bandwidth, limited by 16.0 GT/s PCIe x4 link at 0000:00:01.2 (capable of 252.048 Gb/s with 16.0 GT/s PCIe x16 link)\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2a:00.1: [1022:149c] type 00 class 0x0c0330\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2a:00.1: reg 0x10: [mem 0xfc300000-0xfc3fffff 64bit]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2a:00.1: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2a:00.1: PME# supported from D0 D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2a:00.3: [1022:149c] type 00 class 0x0c0330\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2a:00.3: reg 0x10: [mem 0xfc200000-0xfc2fffff 64bit]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2a:00.3: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2a:00.3: PME# supported from D0 D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:08.0: PCI bridge to [bus 2a]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:08.0:   bridge window [mem 0xfc200000-0xfc3fffff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2b:00.0: [1022:7901] type 00 class 0x010601\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2b:00.0: reg 0x24: [mem 0xfc500000-0xfc5007ff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2b:00.0: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2b:00.0: PME# supported from D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2b:00.0: 63.012 Gb/s available PCIe bandwidth, limited by 16.0 GT/s PCIe x4 link at 0000:00:01.2 (capable of 252.048 Gb/s with 16.0 GT/s PCIe x16 link)\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:09.0: PCI bridge to [bus 2b]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:09.0:   bridge window [mem 0xfc500000-0xfc5fffff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2c:00.0: [1022:7901] type 00 class 0x010601\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2c:00.0: reg 0x24: [mem 0xfc400000-0xfc4007ff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2c:00.0: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2c:00.0: PME# supported from D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2c:00.0: 63.012 Gb/s available PCIe bandwidth, limited by 16.0 GT/s PCIe x4 link at 0000:00:01.2 (capable of 252.048 Gb/s with 16.0 GT/s PCIe x16 link)\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:0a.0: PCI bridge to [bus 2c]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:0a.0:   bridge window [mem 0xfc400000-0xfc4fffff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2d:00.0: [10de:1b81] type 00 class 0x030000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2d:00.0: reg 0x10: [mem 0xfb000000-0xfbffffff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2d:00.0: reg 0x14: [mem 0xd0000000-0xdfffffff 64bit pref]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2d:00.0: reg 0x1c: [mem 0xe0000000-0xe1ffffff 64bit pref]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2d:00.0: reg 0x24: [io  0xe000-0xe07f]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2d:00.0: reg 0x30: [mem 0xfc000000-0xfc07ffff pref]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2d:00.0: BAR 3: assigned to efifb\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2d:00.0: 32.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x16 link at 0000:00:03.1 (capable of 126.016 Gb/s with 8.0 GT/s PCIe x16 link)\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2d:00.1: [10de:10f0] type 00 class 0x040300\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2d:00.1: reg 0x10: [mem 0xfc080000-0xfc083fff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:03.1: ASPM: current common clock configuration is inconsistent, reconfiguring\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:03.1: PCI bridge to [bus 2d]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:03.1:   bridge window [io  0xe000-0xefff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:03.1:   bridge window [mem 0xfb000000-0xfc0fffff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:03.1:   bridge window [mem 0xd0000000-0xe1ffffff 64bit pref]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2e:00.0: [1022:148a] type 00 class 0x130000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2e:00.0: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:07.1: PCI bridge to [bus 2e]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2f:00.0: [1022:1485] type 00 class 0x130000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2f:00.0: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2f:00.1: [1022:1486] type 00 class 0x108000\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2f:00.1: reg 0x18: [mem 0xfca00000-0xfcafffff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2f:00.1: reg 0x24: [mem 0xfcb08000-0xfcb09fff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2f:00.1: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2f:00.3: [1022:149c] type 00 class 0x0c0330\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2f:00.3: reg 0x10: [mem 0xfc900000-0xfc9fffff 64bit]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2f:00.3: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2f:00.3: PME# supported from D0 D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2f:00.4: [1022:1487] type 00 class 0x040300\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2f:00.4: reg 0x10: [mem 0xfcb00000-0xfcb07fff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2f:00.4: enabling Extended Tags\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2f:00.4: PME# supported from D0 D3hot D3cold\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:08.1: PCI bridge to [bus 2f]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:08.1:   bridge window [mem 0xfc900000-0xfcbfffff]\nJun 09 19:37:24 pitt-arch kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 4 5 7 10 11 14 15) *0\nJun 09 19:37:24 pitt-arch kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 4 5 7 10 11 14 15) *0\nJun 09 19:37:24 pitt-arch kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 4 5 7 10 11 14 15) *0\nJun 09 19:37:24 pitt-arch kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 4 5 7 10 11 14 15) *0\nJun 09 19:37:24 pitt-arch kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 4 5 7 10 11 14 15) *0\nJun 09 19:37:24 pitt-arch kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 7 10 11 14 15) *0\nJun 09 19:37:24 pitt-arch kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 4 5 7 10 11 14 15) *0\nJun 09 19:37:24 pitt-arch kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 7 10 11 14 15) *0\nJun 09 19:37:24 pitt-arch kernel: iommu: Default domain type: Translated\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2d:00.0: vgaarb: setting as boot VGA device\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2d:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2d:00.0: vgaarb: bridge control possible\nJun 09 19:37:24 pitt-arch kernel: vgaarb: loaded\nJun 09 19:37:24 pitt-arch kernel: SCSI subsystem initialized\nJun 09 19:37:24 pitt-arch kernel: libata version 3.00 loaded.\nJun 09 19:37:24 pitt-arch kernel: ACPI: bus type USB registered\nJun 09 19:37:24 pitt-arch kernel: usbcore: registered new interface driver usbfs\nJun 09 19:37:24 pitt-arch kernel: usbcore: registered new interface driver hub\nJun 09 19:37:24 pitt-arch kernel: usbcore: registered new device driver usb\nJun 09 19:37:24 pitt-arch kernel: pps_core: LinuxPPS API ver. 1 registered\nJun 09 19:37:24 pitt-arch kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>\nJun 09 19:37:24 pitt-arch kernel: PTP clock support registered\nJun 09 19:37:24 pitt-arch kernel: EDAC MC: Ver: 3.0.0\nJun 09 19:37:24 pitt-arch kernel: Registered efivars operations\nJun 09 19:37:24 pitt-arch kernel: NetLabel: Initializing\nJun 09 19:37:24 pitt-arch kernel: NetLabel:  domain hash size = 128\nJun 09 19:37:24 pitt-arch kernel: NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO\nJun 09 19:37:24 pitt-arch kernel: NetLabel:  unlabeled traffic allowed by default\nJun 09 19:37:24 pitt-arch kernel: PCI: Using ACPI for IRQ routing\nJun 09 19:37:24 pitt-arch kernel: PCI: pci_cache_line_size set to 64 bytes\nJun 09 19:37:24 pitt-arch kernel: e820: reserve RAM buffer [mem 0x09d82000-0x0bffffff]\nJun 09 19:37:24 pitt-arch kernel: e820: reserve RAM buffer [mem 0x0a200000-0x0bffffff]\nJun 09 19:37:24 pitt-arch kernel: e820: reserve RAM buffer [mem 0xc6a8d000-0xc7ffffff]\nJun 09 19:37:24 pitt-arch kernel: e820: reserve RAM buffer [mem 0xcb490000-0xcbffffff]\nJun 09 19:37:24 pitt-arch kernel: e820: reserve RAM buffer [mem 0xcf000000-0xcfffffff]\nJun 09 19:37:24 pitt-arch kernel: e820: reserve RAM buffer [mem 0x82f300000-0x82fffffff]\nJun 09 19:37:24 pitt-arch kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0\nJun 09 19:37:24 pitt-arch kernel: hpet0: 3 comparators, 32-bit 14.318180 MHz counter\nJun 09 19:37:24 pitt-arch kernel: clocksource: Switched to clocksource tsc-early\nJun 09 19:37:24 pitt-arch kernel: VFS: Disk quotas dquot_6.6.0\nJun 09 19:37:24 pitt-arch kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)\nJun 09 19:37:24 pitt-arch kernel: pnp: PnP ACPI init\nJun 09 19:37:24 pitt-arch kernel: system 00:00: [mem 0xf0000000-0xf7ffffff] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)\nJun 09 19:37:24 pitt-arch kernel: system 00:01: [mem 0xfd200000-0xfd2fffff] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)\nJun 09 19:37:24 pitt-arch kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)\nJun 09 19:37:24 pitt-arch kernel: system 00:03: [io  0x0a00-0x0a0f] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:03: [io  0x0a10-0x0a1f] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:03: [io  0x0a20-0x0a2f] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:03: [io  0x0a30-0x0a3f] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:03: Plug and Play ACPI device, IDs PNP0c02 (active)\nJun 09 19:37:24 pitt-arch kernel: pnp 00:04: [dma 0 disabled]\nJun 09 19:37:24 pitt-arch kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0501 (active)\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [io  0x04d0-0x04d1] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [io  0x040b] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [io  0x04d6] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [io  0x0c00-0x0c01] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [io  0x0c14] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [io  0x0c50-0x0c51] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [io  0x0c52] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [io  0x0c6c] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [io  0x0c6f] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [io  0x0cd0-0x0cd1] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [io  0x0cd2-0x0cd3] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [io  0x0cd4-0x0cd5] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [io  0x0cd6-0x0cd7] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [io  0x0cd8-0x0cdf] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [io  0x0800-0x089f] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [io  0x0b00-0x0b0f] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [io  0x0b20-0x0b3f] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [io  0x0900-0x090f] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [io  0x0910-0x091f] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [mem 0xfec00000-0xfec00fff] could not be reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [mem 0xfec01000-0xfec01fff] could not be reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [mem 0xfedc0000-0xfedc0fff] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [mem 0xfee00000-0xfee00fff] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [mem 0xfed80000-0xfed8ffff] could not be reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [mem 0xfec10000-0xfec10fff] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: [mem 0xff000000-0xffffffff] has been reserved\nJun 09 19:37:24 pitt-arch kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)\nJun 09 19:37:24 pitt-arch kernel: pnp: PnP ACPI: found 6 devices\nJun 09 19:37:24 pitt-arch kernel: clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns\nJun 09 19:37:24 pitt-arch kernel: NET: Registered protocol family 2\nJun 09 19:37:24 pitt-arch kernel: IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear)\nJun 09 19:37:24 pitt-arch kernel: tcp_listen_portaddr_hash hash table entries: 16384 (order: 6, 262144 bytes, linear)\nJun 09 19:37:24 pitt-arch kernel: TCP established hash table entries: 262144 (order: 9, 2097152 bytes, linear)\nJun 09 19:37:24 pitt-arch kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)\nJun 09 19:37:24 pitt-arch kernel: TCP: Hash tables configured (established 262144 bind 65536)\nJun 09 19:37:24 pitt-arch kernel: MPTCP token hash table entries: 32768 (order: 7, 786432 bytes, linear)\nJun 09 19:37:24 pitt-arch kernel: UDP hash table entries: 16384 (order: 7, 524288 bytes, linear)\nJun 09 19:37:24 pitt-arch kernel: UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes, linear)\nJun 09 19:37:24 pitt-arch kernel: NET: Registered protocol family 1\nJun 09 19:37:24 pitt-arch kernel: NET: Registered protocol family 44\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x03af window]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7 window]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:00: resource 6 [io  0x03b0-0x03df window]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:00: resource 7 [io  0x0d00-0xffff window]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff window]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:00: resource 9 [mem 0x000c0000-0x000dffff window]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:00: resource 10 [mem 0xd0000000-0xfec02fff window]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:00: resource 11 [mem 0xfee00000-0xffffffff window]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:01: resource 1 [mem 0xfcc00000-0xfccfffff]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:20: resource 0 [io  0xf000-0xffff]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:20: resource 1 [mem 0xfc200000-0xfc8fffff]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:21: resource 0 [io  0xf000-0xffff]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:21: resource 1 [mem 0xfc200000-0xfc8fffff]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:23: resource 1 [mem 0xfc800000-0xfc8fffff]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:26: resource 0 [io  0xf000-0xffff]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:26: resource 1 [mem 0xfc700000-0xfc7fffff]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:28: resource 1 [mem 0xfc600000-0xfc6fffff]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:2a: resource 1 [mem 0xfc200000-0xfc3fffff]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:2b: resource 1 [mem 0xfc500000-0xfc5fffff]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:2c: resource 1 [mem 0xfc400000-0xfc4fffff]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:2d: resource 0 [io  0xe000-0xefff]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:2d: resource 1 [mem 0xfb000000-0xfc0fffff]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:2d: resource 2 [mem 0xd0000000-0xe1ffffff 64bit pref]\nJun 09 19:37:24 pitt-arch kernel: pci_bus 0000:2f: resource 1 [mem 0xfc900000-0xfcbfffff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2d:00.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2d:00.1: D0 power state depends on 0000:2d:00.0\nJun 09 19:37:24 pitt-arch kernel: PCI: CLS 64 bytes, default 64\nJun 09 19:37:24 pitt-arch kernel: Trying to unpack rootfs image as initramfs...\nJun 09 19:37:24 pitt-arch kernel: Freeing initrd memory: 7884K\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:01.0: Adding to iommu group 0\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:01.1: Adding to iommu group 1\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:01.2: Adding to iommu group 2\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:02.0: Adding to iommu group 3\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:03.0: Adding to iommu group 4\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:03.1: Adding to iommu group 5\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:04.0: Adding to iommu group 6\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:05.0: Adding to iommu group 7\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:07.0: Adding to iommu group 8\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:07.1: Adding to iommu group 9\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:08.0: Adding to iommu group 10\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:08.1: Adding to iommu group 11\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:14.0: Adding to iommu group 12\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:14.3: Adding to iommu group 12\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:18.0: Adding to iommu group 13\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:18.1: Adding to iommu group 13\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:18.2: Adding to iommu group 13\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:18.3: Adding to iommu group 13\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:18.4: Adding to iommu group 13\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:18.5: Adding to iommu group 13\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:18.6: Adding to iommu group 13\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:18.7: Adding to iommu group 13\nJun 09 19:37:24 pitt-arch kernel: pci 0000:01:00.0: Adding to iommu group 14\nJun 09 19:37:24 pitt-arch kernel: pci 0000:20:00.0: Adding to iommu group 15\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:01.0: Adding to iommu group 16\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:04.0: Adding to iommu group 17\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:06.0: Adding to iommu group 18\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:08.0: Adding to iommu group 19\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:09.0: Adding to iommu group 20\nJun 09 19:37:24 pitt-arch kernel: pci 0000:21:0a.0: Adding to iommu group 21\nJun 09 19:37:24 pitt-arch kernel: pci 0000:23:00.0: Adding to iommu group 22\nJun 09 19:37:24 pitt-arch kernel: pci 0000:26:00.0: Adding to iommu group 23\nJun 09 19:37:24 pitt-arch kernel: pci 0000:28:00.0: Adding to iommu group 24\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2a:00.0: Adding to iommu group 19\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2a:00.1: Adding to iommu group 19\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2a:00.3: Adding to iommu group 19\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2b:00.0: Adding to iommu group 20\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2c:00.0: Adding to iommu group 21\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2d:00.0: Adding to iommu group 25\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2d:00.1: Adding to iommu group 25\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2e:00.0: Adding to iommu group 26\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2f:00.0: Adding to iommu group 27\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2f:00.1: Adding to iommu group 28\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2f:00.3: Adding to iommu group 29\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2f:00.4: Adding to iommu group 30\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40\nJun 09 19:37:24 pitt-arch kernel: pci 0000:00:00.2: AMD-Vi: Extended features (0x58f77ef22294ade):\nJun 09 19:37:24 pitt-arch kernel:  PPR X2APIC NX GT IA GA PC GA_vAPIC\nJun 09 19:37:24 pitt-arch kernel: AMD-Vi: Interrupt remapping enabled\nJun 09 19:37:24 pitt-arch kernel: AMD-Vi: Virtual APIC enabled\nJun 09 19:37:24 pitt-arch kernel: AMD-Vi: X2APIC enabled\nJun 09 19:37:24 pitt-arch kernel: AMD-Vi: Lazy IO/TLB flushing enabled\nJun 09 19:37:24 pitt-arch kernel: amd_uncore: 4  amd_df counters detected\nJun 09 19:37:24 pitt-arch kernel: amd_uncore: 6  amd_l3 counters detected\nJun 09 19:37:24 pitt-arch kernel: LVT offset 0 assigned for vector 0x400\nJun 09 19:37:24 pitt-arch kernel: perf: AMD IBS detected (0x000003ff)\nJun 09 19:37:24 pitt-arch kernel: perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank).\nJun 09 19:37:24 pitt-arch kernel: check: Scanning for low memory corruption every 60 seconds\nJun 09 19:37:24 pitt-arch kernel: Initialise system trusted keyrings\nJun 09 19:37:24 pitt-arch kernel: Key type blacklist registered\nJun 09 19:37:24 pitt-arch kernel: workingset: timestamp_bits=41 max_order=23 bucket_order=0\nJun 09 19:37:24 pitt-arch kernel: zbud: loaded\nJun 09 19:37:24 pitt-arch kernel: Key type asymmetric registered\nJun 09 19:37:24 pitt-arch kernel: Asymmetric key parser 'x509' registered\nJun 09 19:37:24 pitt-arch kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243)\nJun 09 19:37:24 pitt-arch kernel: io scheduler mq-deadline registered\nJun 09 19:37:24 pitt-arch kernel: io scheduler kyber registered\nJun 09 19:37:24 pitt-arch kernel: io scheduler bfq registered\nJun 09 19:37:24 pitt-arch kernel: pcieport 0000:00:01.1: AER: enabled with IRQ 27\nJun 09 19:37:24 pitt-arch kernel: pcieport 0000:00:01.2: AER: enabled with IRQ 28\nJun 09 19:37:24 pitt-arch kernel: pcieport 0000:00:03.1: AER: enabled with IRQ 29\nJun 09 19:37:24 pitt-arch kernel: pcieport 0000:00:07.1: AER: enabled with IRQ 31\nJun 09 19:37:24 pitt-arch kernel: pcieport 0000:00:08.1: AER: enabled with IRQ 32\nJun 09 19:37:24 pitt-arch kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4\nJun 09 19:37:24 pitt-arch kernel: efifb: probing for efifb\nJun 09 19:37:24 pitt-arch kernel: efifb: showing boot graphics\nJun 09 19:37:24 pitt-arch kernel: efifb: framebuffer at 0xe1000000, using 3072k, total 3072k\nJun 09 19:37:24 pitt-arch kernel: efifb: mode is 1024x768x32, linelength=4096, pages=1\nJun 09 19:37:24 pitt-arch kernel: efifb: scrolling: redraw\nJun 09 19:37:24 pitt-arch kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0\nJun 09 19:37:24 pitt-arch kernel: Console: switching to colour frame buffer device 128x48\nJun 09 19:37:24 pitt-arch kernel: fb0: EFI VGA frame buffer device\nJun 09 19:37:24 pitt-arch kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0\nJun 09 19:37:24 pitt-arch kernel: ACPI: button: Power Button [PWRB]\nJun 09 19:37:24 pitt-arch kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1\nJun 09 19:37:24 pitt-arch kernel: ACPI: button: Power Button [PWRF]\nJun 09 19:37:24 pitt-arch kernel: smpboot: Estimated ratio of average max frequency by base frequency (times 1024): 1141\nJun 09 19:37:24 pitt-arch kernel: Monitor-Mwait will be used to enter C-1 state\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C000: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C002: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C004: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C006: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C008: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C00A: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C00C: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C00E: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C010: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C012: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C014: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C016: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C001: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C003: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C005: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C007: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C009: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C00B: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C00D: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C00F: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C011: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C013: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C015: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: ACPI: \__PR_.C017: Found 2 idle states\nJun 09 19:37:24 pitt-arch kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled\nJun 09 19:37:24 pitt-arch kernel: 00:04: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A\nJun 09 19:37:24 pitt-arch kernel: Non-volatile memory driver v1.3\nJun 09 19:37:24 pitt-arch kernel: AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>\nJun 09 19:37:24 pitt-arch kernel: nvme nvme0: pci function 0000:01:00.0\nJun 09 19:37:24 pitt-arch kernel: nvme nvme1: pci function 0000:23:00.0\nJun 09 19:37:24 pitt-arch kernel: ahci 0000:2b:00.0: version 3.0\nJun 09 19:37:24 pitt-arch kernel: ahci 0000:2b:00.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x4 impl SATA mode\nJun 09 19:37:24 pitt-arch kernel: ahci 0000:2b:00.0: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part\nJun 09 19:37:24 pitt-arch kernel: scsi host0: ahci\nJun 09 19:37:24 pitt-arch kernel: scsi host1: ahci\nJun 09 19:37:24 pitt-arch kernel: scsi host2: ahci\nJun 09 19:37:24 pitt-arch kernel: ata1: DUMMY\nJun 09 19:37:24 pitt-arch kernel: ata2: DUMMY\nJun 09 19:37:24 pitt-arch kernel: ata3: SATA max UDMA/133 abar m2048@0xfc500000 port 0xfc500200 irq 45\nJun 09 19:37:24 pitt-arch kernel: ahci 0000:2c:00.0: AHCI 0001.0301 32 slots 2 ports 6 Gbps 0x30 impl SATA mode\nJun 09 19:37:24 pitt-arch kernel: ahci 0000:2c:00.0: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part\nJun 09 19:37:24 pitt-arch kernel: scsi host3: ahci\nJun 09 19:37:24 pitt-arch kernel: scsi host4: ahci\nJun 09 19:37:24 pitt-arch kernel: scsi host5: ahci\nJun 09 19:37:24 pitt-arch kernel: scsi host6: ahci\nJun 09 19:37:24 pitt-arch kernel: scsi host7: ahci\nJun 09 19:37:24 pitt-arch kernel: scsi host8: ahci\nJun 09 19:37:24 pitt-arch kernel: ata4: DUMMY\nJun 09 19:37:24 pitt-arch kernel: ata5: DUMMY\nJun 09 19:37:24 pitt-arch kernel: ata6: DUMMY\nJun 09 19:37:24 pitt-arch kernel: ata7: DUMMY\nJun 09 19:37:24 pitt-arch kernel: ata8: SATA max UDMA/133 abar m2048@0xfc400000 port 0xfc400300 irq 64\nJun 09 19:37:24 pitt-arch kernel: ata9: SATA max UDMA/133 abar m2048@0xfc400000 port 0xfc400380 irq 65\nJun 09 19:37:24 pitt-arch kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver\nJun 09 19:37:24 pitt-arch kernel: ehci-pci: EHCI PCI platform driver\nJun 09 19:37:24 pitt-arch kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver\nJun 09 19:37:24 pitt-arch kernel: ohci-pci: OHCI PCI platform driver\nJun 09 19:37:24 pitt-arch kernel: uhci_hcd: USB Universal Host Controller Interface driver\nJun 09 19:37:24 pitt-arch kernel: usbcore: registered new interface driver usbserial_generic\nJun 09 19:37:24 pitt-arch kernel: usbserial: USB Serial support registered for generic\nJun 09 19:37:24 pitt-arch kernel: rtc_cmos 00:02: RTC can wake from S4\nJun 09 19:37:24 pitt-arch kernel: rtc_cmos 00:02: registered as rtc0\nJun 09 19:37:24 pitt-arch kernel: rtc_cmos 00:02: setting system clock to 2021-06-09T18:37:21 UTC (1623263841)\nJun 09 19:37:24 pitt-arch kernel: rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs\nJun 09 19:37:24 pitt-arch kernel: ledtrig-cpu: registered to indicate activity on CPUs\nJun 09 19:37:24 pitt-arch kernel: hid: raw HID events driver (C) Jiri Kosina\nJun 09 19:37:24 pitt-arch kernel: drop_monitor: Initializing network drop monitor service\nJun 09 19:37:24 pitt-arch kernel: Initializing XFRM netlink socket\nJun 09 19:37:24 pitt-arch kernel: NET: Registered protocol family 10\nJun 09 19:37:24 pitt-arch kernel: Segment Routing with IPv6\nJun 09 19:37:24 pitt-arch kernel: RPL Segment Routing with IPv6\nJun 09 19:37:24 pitt-arch kernel: NET: Registered protocol family 17\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU0: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU1: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU2: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU3: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU4: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU5: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU6: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU7: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU8: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU9: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU10: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU11: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU12: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU13: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU14: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU15: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU16: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU17: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU18: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU19: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU20: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU21: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU22: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: CPU23: patch_level=0x08701021\nJun 09 19:37:24 pitt-arch kernel: microcode: Microcode Update Driver: v2.2.\nJun 09 19:37:24 pitt-arch kernel: resctrl: L3 allocation detected\nJun 09 19:37:24 pitt-arch kernel: resctrl: L3DATA allocation detected\nJun 09 19:37:24 pitt-arch kernel: resctrl: L3CODE allocation detected\nJun 09 19:37:24 pitt-arch kernel: resctrl: MB allocation detected\nJun 09 19:37:24 pitt-arch kernel: resctrl: L3 monitoring detected\nJun 09 19:37:24 pitt-arch kernel: IPI shorthand broadcast: enabled\nJun 09 19:37:24 pitt-arch kernel: sched_clock: Marking stable (433896924, 263886)->(440616106, -6455296)\nJun 09 19:37:24 pitt-arch kernel: registered taskstats version 1\nJun 09 19:37:24 pitt-arch kernel: Loading compiled-in X.509 certificates\nJun 09 19:37:24 pitt-arch kernel: Loaded X.509 cert 'Build time autogenerated kernel key: d9d024d9261cff33010eb85ec1ff59abcf0a533d'\nJun 09 19:37:24 pitt-arch kernel: zswap: loaded using pool lz4/z3fold\nJun 09 19:37:24 pitt-arch kernel: Key type ._fscrypt registered\nJun 09 19:37:24 pitt-arch kernel: Key type .fscrypt registered\nJun 09 19:37:24 pitt-arch kernel: Key type fscrypt-provisioning registered\nJun 09 19:37:24 pitt-arch kernel: PM:   Magic number: 9:167:645\nJun 09 19:37:24 pitt-arch kernel: pci 0000:2f:00.0: hash matches\nJun 09 19:37:24 pitt-arch kernel: RAS: Correctable Errors collector initialized.\nJun 09 19:37:24 pitt-arch kernel: nvme nvme1: 32/0/0 default/read/poll queues\nJun 09 19:37:24 pitt-arch kernel:  nvme1n1: p1 p2\nJun 09 19:37:24 pitt-arch kernel: nvme nvme0: Shutdown timeout set to 10 seconds\nJun 09 19:37:24 pitt-arch kernel: nvme nvme0: 32/0/0 default/read/poll queues\nJun 09 19:37:24 pitt-arch kernel:  nvme0n1: p1 p2\nJun 09 19:37:24 pitt-arch kernel: ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300)\nJun 09 19:37:24 pitt-arch kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)\nJun 09 19:37:24 pitt-arch kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)\nJun 09 19:37:24 pitt-arch kernel: ata9.00: ATA-9: SanDisk SSD PLUS 480GB, UG4500RL, max UDMA/133\nJun 09 19:37:24 pitt-arch kernel: ata9.00: 937721856 sectors, multi 1: LBA48 NCQ (depth 32)\nJun 09 19:37:24 pitt-arch kernel: ata3.00: ATA-10: ST4000DM005-2DP166, 0001, max UDMA/133\nJun 09 19:37:24 pitt-arch kernel: ata3.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA\nJun 09 19:37:24 pitt-arch kernel: ata8.00: ATAPI: HL-DT-ST DVDRWBD GBC-H20N, C102, max UDMA/133\nJun 09 19:37:24 pitt-arch kernel: ata3.00: configured for UDMA/133\nJun 09 19:37:24 pitt-arch kernel: scsi 2:0:0:0: Direct-Access     ATA      ST4000DM005-2DP1 0001 PQ: 0 ANSI: 5\nJun 09 19:37:24 pitt-arch kernel: sd 2:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)\nJun 09 19:37:24 pitt-arch kernel: sd 2:0:0:0: [sda] 4096-byte physical blocks\nJun 09 19:37:24 pitt-arch kernel: sd 2:0:0:0: [sda] Write Protect is off\nJun 09 19:37:24 pitt-arch kernel: sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00\nJun 09 19:37:24 pitt-arch kernel: sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA\nJun 09 19:37:24 pitt-arch kernel: ata9.00: configured for UDMA/133\nJun 09 19:37:24 pitt-arch kernel: ata8.00: configured for UDMA/133\nJun 09 19:37:24 pitt-arch kernel:  sda: sda1\nJun 09 19:37:24 pitt-arch kernel: sd 2:0:0:0: [sda] Attached SCSI disk\nJun 09 19:37:24 pitt-arch kernel: scsi 7:0:0:0: CD-ROM            HL-DT-ST DVDRWBD GBC-H20N C102 PQ: 0 ANSI: 5\nJun 09 19:37:24 pitt-arch kernel: scsi 8:0:0:0: Direct-Access     ATA      SanDisk SSD PLUS 00RL PQ: 0 ANSI: 5\nJun 09 19:37:24 pitt-arch kernel: sd 8:0:0:0: [sdb] 937721856 512-byte logical blocks: (480 GB/447 GiB)\nJun 09 19:37:24 pitt-arch kernel: sd 8:0:0:0: [sdb] Write Protect is off\nJun 09 19:37:24 pitt-arch kernel: sd 8:0:0:0: [sdb] Mode Sense: 00 3a 00 00\nJun 09 19:37:24 pitt-arch kernel: sd 8:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA\nJun 09 19:37:24 pitt-arch kernel:  sdb: sdb1\nJun 09 19:37:24 pitt-arch kernel: sd 8:0:0:0: [sdb] Attached SCSI disk\nJun 09 19:37:24 pitt-arch kernel: Freeing unused decrypted memory: 2036K\nJun 09 19:37:24 pitt-arch kernel: Freeing unused kernel image (initmem) memory: 1652K\nJun 09 19:37:24 pitt-arch kernel: Write protecting the kernel read-only data: 26624k\nJun 09 19:37:24 pitt-arch kernel: Freeing unused kernel image (text/rodata gap) memory: 2036K\nJun 09 19:37:24 pitt-arch kernel: Freeing unused kernel image (rodata/data gap) memory: 1252K\nJun 09 19:37:24 pitt-arch kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.\nJun 09 19:37:24 pitt-arch kernel: rodata_test: all tests were successful\nJun 09 19:37:24 pitt-arch kernel: Run /init as init process\nJun 09 19:37:24 pitt-arch kernel:   with arguments:\nJun 09 19:37:24 pitt-arch kernel:     /init\nJun 09 19:37:24 pitt-arch kernel:   with environment:\nJun 09 19:37:24 pitt-arch kernel:     HOME=/\nJun 09 19:37:24 pitt-arch kernel:     TERM=linux\nJun 09 19:37:24 pitt-arch kernel:     BOOT_IMAGE=/boot/vmlinuz-linux\nJun 09 19:37:24 pitt-arch kernel: xhci_hcd 0000:2a:00.1: xHCI Host Controller\nJun 09 19:37:24 pitt-arch kernel: xhci_hcd 0000:2a:00.1: new USB bus registered, assigned bus number 1\nJun 09 19:37:24 pitt-arch kernel: xhci_hcd 0000:2a:00.1: hcc params 0x0278ffe5 hci version 0x110 quirks 0x0000000000000410\nJun 09 19:37:24 pitt-arch kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.12\nJun 09 19:37:24 pitt-arch kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1\nJun 09 19:37:24 pitt-arch kernel: usb usb1: Product: xHCI Host Controller\nJun 09 19:37:24 pitt-arch kernel: usb usb1: Manufacturer: Linux 5.12.9-arch1-1 xhci-hcd\nJun 09 19:37:24 pitt-arch kernel: usb usb1: SerialNumber: 0000:2a:00.1\nJun 09 19:37:24 pitt-arch kernel: hub 1-0:1.0: USB hub found\nJun 09 19:37:24 pitt-arch kernel: hub 1-0:1.0: 6 ports detected\nJun 09 19:37:24 pitt-arch kernel: xhci_hcd 0000:2a:00.1: new USB bus registered, assigned bus number 2\nJun 09 19:37:24 pitt-arch kernel: xhci_hcd 0000:2a:00.1: Host supports USB 3.1 Enhanced SuperSpeed\nJun 09 19:37:24 pitt-arch kernel: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.\nJun 09 19:37:24 pitt-arch kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.12\nJun 09 19:37:24 pitt-arch kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1\nJun 09 19:37:24 pitt-arch kernel: usb usb2: Product: xHCI Host Controller\nJun 09 19:37:24 pitt-arch kernel: usb usb2: Manufacturer: Linux 5.12.9-arch1-1 xhci-hcd\nJun 09 19:37:24 pitt-arch kernel: usb usb2: SerialNumber: 0000:2a:00.1\nJun 09 19:37:24 pitt-arch kernel: hub 2-0:1.0: USB hub found\nJun 09 19:37:24 pitt-arch kernel: hub 2-0:1.0: 4 ports detected\nJun 09 19:37:24 pitt-arch kernel: random: fast init done\nJun 09 19:37:24 pitt-arch kernel: usb: port power management may be unreliable\nJun 09 19:37:24 pitt-arch kernel: xhci_hcd 0000:2a:00.3: xHCI Host Controller\nJun 09 19:37:24 pitt-arch kernel: xhci_hcd 0000:2a:00.3: new USB bus registered, assigned bus number 3\nJun 09 19:37:24 pitt-arch kernel: xhci_hcd 0000:2a:00.3: hcc params 0x0278ffe5 hci version 0x110 quirks 0x0000000000000410\nJun 09 19:37:24 pitt-arch kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.12\nJun 09 19:37:24 pitt-arch kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1\nJun 09 19:37:24 pitt-arch kernel: usb usb3: Product: xHCI Host Controller\nJun 09 19:37:24 pitt-arch kernel: usb usb3: Manufacturer: Linux 5.12.9-arch1-1 xhci-hcd\nJun 09 19:37:24 pitt-arch kernel: usb usb3: SerialNumber: 0000:2a:00.3\nJun 09 19:37:24 pitt-arch kernel: hub 3-0:1.0: USB hub found\nJun 09 19:37:24 pitt-arch kernel: hub 3-0:1.0: 6 ports detected\nJun 09 19:37:24 pitt-arch kernel: xhci_hcd 0000:2a:00.3: new USB bus registered, assigned bus number 4\nJun 09 19:37:24 pitt-arch kernel: xhci_hcd 0000:2a:00.3: Host supports USB 3.1 Enhanced SuperSpeed\nJun 09 19:37:24 pitt-arch kernel: usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.\nJun 09 19:37:24 pitt-arch kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.12\nJun 09 19:37:24 pitt-arch kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1\nJun 09 19:37:24 pitt-arch kernel: usb usb4: Product: xHCI Host Controller\nJun 09 19:37:24 pitt-arch kernel: usb usb4: Manufacturer: Linux 5.12.9-arch1-1 xhci-hcd\nJun 09 19:37:24 pitt-arch kernel: usb usb4: SerialNumber: 0000:2a:00.3\nJun 09 19:37:24 pitt-arch kernel: hub 4-0:1.0: USB hub found\nJun 09 19:37:24 pitt-arch kernel: hub 4-0:1.0: 4 ports detected\nJun 09 19:37:24 pitt-arch kernel: xhci_hcd 0000:2f:00.3: xHCI Host Controller\nJun 09 19:37:24 pitt-arch kernel: xhci_hcd 0000:2f:00.3: new USB bus registered, assigned bus number 5\nJun 09 19:37:24 pitt-arch kernel: xhci_hcd 0000:2f:00.3: hcc params 0x0278ffe5 hci version 0x110 quirks 0x0000000000000410\nJun 09 19:37:24 pitt-arch kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.12\nJun 09 19:37:24 pitt-arch kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1\nJun 09 19:37:24 pitt-arch kernel: usb usb5: Product: xHCI Host Controller\nJun 09 19:37:24 pitt-arch kernel: usb usb5: Manufacturer: Linux 5.12.9-arch1-1 xhci-hcd\nJun 09 19:37:24 pitt-arch kernel: usb usb5: SerialNumber: 0000:2f:00.3\nJun 09 19:37:24 pitt-arch kernel: hub 5-0:1.0: USB hub found\nJun 09 19:37:24 pitt-arch kernel: hub 5-0:1.0: 4 ports detected\nJun 09 19:37:24 pitt-arch kernel: xhci_hcd 0000:2f:00.3: new USB bus registered, assigned bus number 6\nJun 09 19:37:24 pitt-arch kernel: xhci_hcd 0000:2f:00.3: Host supports USB 3.1 Enhanced SuperSpeed\nJun 09 19:37:24 pitt-arch kernel: usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.\nJun 09 19:37:24 pitt-arch kernel: usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.12\nJun 09 19:37:24 pitt-arch kernel: usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1\nJun 09 19:37:24 pitt-arch kernel: usb usb6: Product: xHCI Host Controller\nJun 09 19:37:24 pitt-arch kernel: usb usb6: Manufacturer: Linux 5.12.9-arch1-1 xhci-hcd\nJun 09 19:37:24 pitt-arch kernel: usb usb6: SerialNumber: 0000:2f:00.3\nJun 09 19:37:24 pitt-arch kernel: hub 6-0:1.0: USB hub found\nJun 09 19:37:24 pitt-arch kernel: hub 6-0:1.0: 4 ports detected\nJun 09 19:37:24 pitt-arch kernel: sr 7:0:0:0: [sr0] scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray\nJun 09 19:37:24 pitt-arch kernel: cdrom: Uniform CD-ROM driver Revision: 3.20\nJun 09 19:37:24 pitt-arch kernel: tsc: Refined TSC clocksource calibration: 3799.999 MHz\nJun 09 19:37:24 pitt-arch kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x6d8cadf3fd9, max_idle_ns: 881590557866 ns\nJun 09 19:37:24 pitt-arch kernel: clocksource: Switched to clocksource tsc\nJun 09 19:37:24 pitt-arch kernel: usb 5-3: new full-speed USB device number 2 using xhci_hcd\nJun 09 19:37:24 pitt-arch kernel: usb 1-1: new full-speed USB device number 2 using xhci_hcd\nJun 09 19:37:24 pitt-arch kernel: usb 3-5: new full-speed USB device number 2 using xhci_hcd\nJun 09 19:37:24 pitt-arch kernel: sr 7:0:0:0: Attached scsi CD-ROM sr0\nJun 09 19:37:24 pitt-arch kernel: usb 1-1: New USB device found, idVendor=3938, idProduct=1031, bcdDevice= 2.06\nJun 09 19:37:24 pitt-arch kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0\nJun 09 19:37:24 pitt-arch kernel: usb 1-1: Product: 2.4G Wireless Mouse\nJun 09 19:37:24 pitt-arch kernel: usb 1-1: Manufacturer: MOSART Semi.\nJun 09 19:37:24 pitt-arch kernel: usb 3-5: New USB device found, idVendor=1462, idProduct=7c84, bcdDevice= 0.01\nJun 09 19:37:24 pitt-arch kernel: usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3\nJun 09 19:37:24 pitt-arch kernel: usb 3-5: Product: MYSTIC LIGHT\nJun 09 19:37:24 pitt-arch kernel: usb 3-5: Manufacturer: MSI\nJun 09 19:37:24 pitt-arch kernel: usb 3-5: SerialNumber: A02019122002\nJun 09 19:37:24 pitt-arch kernel: usb 5-3: New USB device found, idVendor=045e, idProduct=0724, bcdDevice= 2.25\nJun 09 19:37:24 pitt-arch kernel: usb 5-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0\nJun 09 19:37:24 pitt-arch kernel: usb 5-3: Product: SideWinder™ Mouse\nJun 09 19:37:24 pitt-arch kernel: usb 5-3: Manufacturer: Microsoft\nJun 09 19:37:24 pitt-arch kernel: input: MOSART Semi. 2.4G Wireless Mouse as /devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.1/usb1/1-1/1-1:1.0/0003:3938:1031.0001/input/input2\nJun 09 19:37:24 pitt-arch kernel: input: MOSART Semi. 2.4G Wireless Mouse as /devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.1/usb1/1-1/1-1:1.0/0003:3938:1031.0001/input/input3\nJun 09 19:37:24 pitt-arch kernel: hid-generic 0003:3938:1031.0001: input,hiddev96,hidraw0: USB HID v1.10 Mouse [MOSART Semi. 2.4G Wireless Mouse] on usb-0000:2a:00.1-1/input0\nJun 09 19:37:24 pitt-arch kernel: input: Microsoft SideWinder™ Mouse as /devices/pci0000:00/0000:00:08.1/0000:2f:00.3/usb5/5-3/5-3:1.0/0003:045E:0724.0002/input/input4\nJun 09 19:37:24 pitt-arch kernel: input: Microsoft SideWinder™ Mouse Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:2f:00.3/usb5/5-3/5-3:1.0/0003:045E:0724.0002/input/input5\nJun 09 19:37:24 pitt-arch kernel: input: MSI MYSTIC LIGHT  as /devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.3/usb3/3-5/3-5:1.0/0003:1462:7C84.0003/input/input6\nJun 09 19:37:24 pitt-arch kernel: hid-generic 0003:045E:0724.0002: input,hidraw1: USB HID v1.11 Mouse [Microsoft SideWinder™ Mouse] on usb-0000:2f:00.3-3/input0\nJun 09 19:37:24 pitt-arch kernel: hid-generic 0003:1462:7C84.0003: input,hiddev97,hidraw2: USB HID v1.10 Device [MSI MYSTIC LIGHT ] on usb-0000:2a:00.3-5/input0\nJun 09 19:37:24 pitt-arch kernel: usbcore: registered new interface driver usbhid\nJun 09 19:37:24 pitt-arch kernel: usbhid: USB HID core driver\nJun 09 19:37:24 pitt-arch kernel: usb 1-2: new full-speed USB device number 3 using xhci_hcd\nJun 09 19:37:24 pitt-arch kernel: usb 3-6: new high-speed USB device number 3 using xhci_hcd\nJun 09 19:37:24 pitt-arch kernel: usb 3-6: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=60.70\nJun 09 19:37:24 pitt-arch kernel: usb 3-6: New USB device strings: Mfr=0, Product=1, SerialNumber=0\nJun 09 19:37:24 pitt-arch kernel: usb 3-6: Product: USB2.0 Hub\nJun 09 19:37:24 pitt-arch kernel: hub 3-6:1.0: USB hub found\nJun 09 19:37:24 pitt-arch kernel: hub 3-6:1.0: 4 ports detected\nJun 09 19:37:24 pitt-arch kernel: EXT4-fs (nvme0n1p2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.\nJun 09 19:37:24 pitt-arch systemd: systemd 248.3-2-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 +XKBCOMMON +UTMP -SYSVINIT default-hierarchy=unified)\nJun 09 19:37:24 pitt-arch systemd: Detected architecture x86-64.\nJun 09 19:37:24 pitt-arch systemd: Hostname set to <pitt-arch>.\nJun 09 19:37:24 pitt-arch kernel: random: lvmconfig: uninitialized urandom read (4 bytes read)\nJun 09 19:37:24 pitt-arch systemd: Queued start job for default target Graphical Interface.\nJun 09 19:37:24 pitt-arch systemd: Created slice system-getty.slice.\nJun 09 19:37:24 pitt-arch systemd: Created slice system-modprobe.slice.\nJun 09 19:37:24 pitt-arch systemd: Created slice User and Session Slice.\nJun 09 19:37:24 pitt-arch systemd: Started Dispatch Password Requests to Console Directory Watch.\nJun 09 19:37:24 pitt-arch systemd: Started Forward Password Requests to Wall Directory Watch.\nJun 09 19:37:24 pitt-arch systemd: Set up automount Arbitrary Executable File Formats File System Automount Point.\nJun 09 19:37:24 pitt-arch systemd: Reached target Local Encrypted Volumes.\nJun 09 19:37:24 pitt-arch systemd: Reached target Paths.\nJun 09 19:37:24 pitt-arch systemd: Reached target Remote File Systems.\nJun 09 19:37:24 pitt-arch systemd: Reached target Slices.\nJun 09 19:37:24 pitt-arch systemd: Reached target Swap.\nJun 09 19:37:24 pitt-arch systemd: Reached target Local Verity Integrity Protected Volumes.\nJun 09 19:37:24 pitt-arch systemd: Listening on Device-mapper event daemon FIFOs.\nJun 09 19:37:24 pitt-arch systemd: Listening on LVM2 poll daemon socket.\nJun 09 19:37:24 pitt-arch systemd: Listening on Process Core Dump Socket.\nJun 09 19:37:24 pitt-arch systemd: Listening on Journal Audit Socket.\nJun 09 19:37:24 pitt-arch systemd: Listening on Journal Socket (/dev/log).\nJun 09 19:37:24 pitt-arch systemd: Listening on Journal Socket.\nJun 09 19:37:24 pitt-arch systemd: Listening on udev Control Socket.\nJun 09 19:37:24 pitt-arch systemd: Listening on udev Kernel Socket.\nJun 09 19:37:24 pitt-arch systemd: Mounting Huge Pages File System...\nJun 09 19:37:24 pitt-arch systemd: Mounting POSIX Message Queue File System...\nJun 09 19:37:24 pitt-arch systemd: Mounting Kernel Debug File System...\nJun 09 19:37:24 pitt-arch systemd: Mounting Kernel Trace File System...\nJun 09 19:37:24 pitt-arch systemd: Mounting Temporary Directory (/tmp)...\nJun 09 19:37:24 pitt-arch systemd: Starting Create list of static device nodes for the current kernel...\nJun 09 19:37:24 pitt-arch systemd: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...\nJun 09 19:37:24 pitt-arch systemd: Starting Load Kernel Module configfs...\nJun 09 19:37:24 pitt-arch systemd: Starting Load Kernel Module drm...\nJun 09 19:37:24 pitt-arch systemd: Starting Load Kernel Module fuse...\nJun 09 19:37:24 pitt-arch systemd: Condition check resulted in Set Up Additional Binary Formats being skipped.\nJun 09 19:37:24 pitt-arch kernel: random: lvm: uninitialized urandom read (4 bytes read)\nJun 09 19:37:24 pitt-arch systemd: Starting Journal Service...\nJun 09 19:37:24 pitt-arch systemd: Starting Load Kernel Modules...\nJun 09 19:37:24 pitt-arch systemd: Starting Remount Root and Kernel File Systems...\nJun 09 19:37:24 pitt-arch systemd: Condition check resulted in Repartition Root Disk being skipped.\nJun 09 19:37:24 pitt-arch kernel: Linux agpgart interface v0.103\nJun 09 19:37:24 pitt-arch systemd: Starting Coldplug All udev Devices...\nJun 09 19:37:24 pitt-arch systemd: Mounted Huge Pages File System.\nJun 09 19:37:24 pitt-arch systemd: Mounted POSIX Message Queue File System.\nJun 09 19:37:24 pitt-arch systemd: Mounted Kernel Debug File System.\nJun 09 19:37:24 pitt-arch systemd: Mounted Kernel Trace File System.\nJun 09 19:37:24 pitt-arch systemd: Mounted Temporary Directory (/tmp).\nJun 09 19:37:24 pitt-arch systemd: Finished Create list of static device nodes for the current kernel.\nJun 09 19:37:24 pitt-arch systemd: modprobe@configfs.service: Deactivated successfully.\nJun 09 19:37:24 pitt-arch systemd: Finished Load Kernel Module configfs.\nJun 09 19:37:24 pitt-arch systemd: Mounting Kernel Configuration File System...\nJun 09 19:37:24 pitt-arch systemd: Finished Remount Root and Kernel File Systems.\nJun 09 19:37:24 pitt-arch systemd: Condition check resulted in First Boot Wizard being skipped.\nJun 09 19:37:24 pitt-arch systemd: Condition check resulted in Rebuild Hardware Database being skipped.\nJun 09 19:37:24 pitt-arch systemd: Starting Load/Save Random Seed...\nJun 09 19:37:24 pitt-arch systemd: Condition check resulted in Create System Users being skipped.\nJun 09 19:37:24 pitt-arch systemd: Starting Create Static Device Nodes in /dev...\nJun 09 19:37:24 pitt-arch systemd: Mounted Kernel Configuration File System.\nJun 09 19:37:24 pitt-arch kernel: fuse: init (API version 7.33)\nJun 09 19:37:24 pitt-arch kernel: sd 2:0:0:0: Attached scsi generic sg0 type 0\nJun 09 19:37:24 pitt-arch kernel: sr 7:0:0:0: Attached scsi generic sg1 type 5\nJun 09 19:37:24 pitt-arch kernel: sd 8:0:0:0: Attached scsi generic sg2 type 0\nJun 09 19:37:24 pitt-arch systemd: modprobe@fuse.service: Deactivated successfully.\nJun 09 19:37:24 pitt-arch systemd: Finished Load Kernel Module fuse.\nJun 09 19:37:24 pitt-arch kernel: audit: type=1130 audit(1623263844.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'\nJun 09 19:37:24 pitt-arch kernel: audit: type=1131 audit(1623263844.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'\nJun 09 19:37:24 pitt-arch systemd: Finished Load Kernel Modules.\nJun 09 19:37:24 pitt-arch kernel: audit: type=1130 audit(1623263844.000:4): 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'\nJun 09 19:37:24 pitt-arch systemd: Mounting FUSE Control File System...\nJun 09 19:37:24 pitt-arch systemd: Starting Apply Kernel Variables...\nJun 09 19:37:24 pitt-arch systemd: Mounted FUSE Control File System.\nJun 09 19:37:24 pitt-arch systemd: Finished Apply Kernel Variables.\nJun 09 19:37:24 pitt-arch kernel: audit: type=1130 audit(1623263844.003:5): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:24 pitt-arch systemd: Finished Create Static Device Nodes in /dev.\nJun 09 19:37:24 pitt-arch kernel: audit: type=1130 audit(1623263844.007:6): 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'\nJun 09 19:37:24 pitt-arch kernel: audit: type=1334 audit(1623263844.007:7): prog-id=14 op=LOAD\nJun 09 19:37:24 pitt-arch kernel: audit: type=1334 audit(1623263844.007:8): prog-id=15 op=LOAD\nJun 09 19:37:24 pitt-arch kernel: audit: type=1334 audit(1623263844.007:9): prog-id=16 op=LOAD\nJun 09 19:37:24 pitt-arch systemd: Starting Rule-based Manager for Device Events and Files...\nJun 09 19:37:24 pitt-arch systemd: modprobe@drm.service: Deactivated successfully.\nJun 09 19:37:24 pitt-arch systemd: Finished Load Kernel Module drm.\nJun 09 19:37:24 pitt-arch kernel: audit: type=1130 audit(1623263844.013:10): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:24 pitt-arch systemd-journald: Journal started\nJun 09 19:37:24 pitt-arch systemd-journald: Runtime Journal (/run/log/journal/3b719d0832ac426998bbbc9d23f2916b) is 8.0M, max 1.5G, 1.5G free.\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch audit: BPF prog-id=14 op=LOAD\nJun 09 19:37:24 pitt-arch audit: BPF prog-id=15 op=LOAD\nJun 09 19:37:24 pitt-arch audit: BPF prog-id=16 op=LOAD\nJun 09 19:37:24 pitt-arch audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:24 pitt-arch audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch systemd-modules-load: Inserted module 'crypto_user'\nJun 09 19:37:24 pitt-arch systemd-modules-load: Inserted module 'sg'\nJun 09 19:37:24 pitt-arch systemd-random-seed: Kernel entropy pool is not initialized yet, waiting until it is.\nJun 09 19:37:24 pitt-arch systemd: Started Journal Service.\nJun 09 19:37:24 pitt-arch systemd: Started Rule-based Manager for Device Events and Files.\nJun 09 19:37:24 pitt-arch systemd: Starting Flush Journal to Persistent Storage...\nJun 09 19:37:24 pitt-arch systemd-journald: Time spent on flushing to /var/log/journal/3b719d0832ac426998bbbc9d23f2916b is 6.067ms for 1090 entries.\nJun 09 19:37:24 pitt-arch systemd-journald: System Journal (/var/log/journal/3b719d0832ac426998bbbc9d23f2916b) is 16.0M, max 4.0G, 3.9G free.\nJun 09 19:37:24 pitt-arch kernel: acpi_cpufreq: overriding BIOS provided _PSD data\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch systemd: Finished Coldplug All udev Devices.\nJun 09 19:37:24 pitt-arch systemd: Finished Flush Journal to Persistent Storage.\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)\nJun 09 19:37:24 pitt-arch mtp-probe: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.3/usb3/3-5"\nJun 09 19:37:24 pitt-arch mtp-probe: bus: 3, device: 2 was not an MTP device\nJun 09 19:37:24 pitt-arch mtp-probe: checking bus 5, device 2: "/sys/devices/pci0000:00/0000:00:08.1/0000:2f:00.3/usb5/5-3"\nJun 09 19:37:24 pitt-arch mtp-probe: bus: 5, device: 2 was not an MTP device\nJun 09 19:37:24 pitt-arch kernel: input: PC Speaker as /devices/platform/pcspkr/input/input7\nJun 09 19:37:24 pitt-arch kernel: RAPL PMU: API unit is 2^-32 Joules, 1 fixed counters, 163840 ms ovfl timer\nJun 09 19:37:24 pitt-arch kernel: RAPL PMU: hw unit of domain package 2^-16 Joules\nJun 09 19:37:24 pitt-arch kernel: piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0\nJun 09 19:37:24 pitt-arch kernel: piix4_smbus 0000:00:14.0: Using register 0x02 for SMBus port selection\nJun 09 19:37:24 pitt-arch kernel: piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20\nJun 09 19:37:24 pitt-arch kernel: mousedev: PS/2 mouse device common for all mice\nJun 09 19:37:24 pitt-arch kernel: cryptd: max_cpu_qlen set to 1000\nJun 09 19:37:24 pitt-arch kernel: sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver\nJun 09 19:37:24 pitt-arch kernel: sp5100-tco sp5100-tco: Using 0xfeb00000 for watchdog MMIO address\nJun 09 19:37:24 pitt-arch kernel: sp5100-tco sp5100-tco: initialized. heartbeat=60 sec (nowayout=0)\nJun 09 19:37:24 pitt-arch kernel: ccp 0000:2f:00.1: enabling device (0000 -> 0002)\nJun 09 19:37:24 pitt-arch kernel: ccp 0000:2f:00.1: ccp: unable to access the device: you might be running a broken BIOS.\nJun 09 19:37:24 pitt-arch kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database\nJun 09 19:37:24 pitt-arch kernel: AVX2 version of gcm_enc/dec engaged.\nJun 09 19:37:24 pitt-arch kernel: AES CTR mode by8 optimization enabled\nJun 09 19:37:24 pitt-arch kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'\nJun 09 19:37:24 pitt-arch kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2\nJun 09 19:37:24 pitt-arch kernel: cfg80211: failed to load regulatory.db\nJun 09 19:37:24 pitt-arch kernel: libphy: r8169: probed\nJun 09 19:37:24 pitt-arch kernel: r8169 0000:26:00.0 eth0: RTL8125B, 2c:f0:5d:7b:dd:41, XID 641, IRQ 161\nJun 09 19:37:24 pitt-arch kernel: r8169 0000:26:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]\nJun 09 19:37:24 pitt-arch systemd: Finished Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch systemd: Reached target Local File Systems (Pre).\nJun 09 19:37:24 pitt-arch systemd: Condition check resulted in Virtual Machine and Container Storage (Compatibility) being skipped.\nJun 09 19:37:24 pitt-arch systemd: Reached target Local File Systems.\nJun 09 19:37:24 pitt-arch systemd: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.\nJun 09 19:37:24 pitt-arch systemd: Starting Create Volatile Files and Directories...\nJun 09 19:37:24 pitt-arch systemd: Finished Create Volatile Files and Directories.\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch systemd: Condition check resulted in Rebuild Journal Catalog being skipped.\nJun 09 19:37:24 pitt-arch systemd: Condition check resulted in Update is Completed being skipped.\nJun 09 19:37:24 pitt-arch systemd: Starting Update UTMP about System Boot/Shutdown...\nJun 09 19:37:24 pitt-arch audit: SYSTEM_BOOT pid=553 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:24 pitt-arch systemd: Finished Update UTMP about System Boot/Shutdown.\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch systemd: Reached target System Initialization.\nJun 09 19:37:24 pitt-arch systemd: Started Daily man-db regeneration.\nJun 09 19:37:24 pitt-arch systemd: Started Daily verification of password and group files.\nJun 09 19:37:24 pitt-arch systemd: Started Daily Cleanup of Temporary Directories.\nJun 09 19:37:24 pitt-arch systemd: Reached target Timers.\nJun 09 19:37:24 pitt-arch systemd: Listening on D-Bus System Message Bus Socket.\nJun 09 19:37:24 pitt-arch systemd: Reached target Sockets.\nJun 09 19:37:24 pitt-arch systemd: Reached target Basic System.\nJun 09 19:37:24 pitt-arch systemd: Started D-Bus System Message Bus.\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch systemd: Starting Network Manager...\nJun 09 19:37:24 pitt-arch audit: BPF prog-id=17 op=LOAD\nJun 09 19:37:24 pitt-arch audit: BPF prog-id=18 op=LOAD\nJun 09 19:37:24 pitt-arch audit: BPF prog-id=19 op=LOAD\nJun 09 19:37:24 pitt-arch systemd: Starting User Login Management...\nJun 09 19:37:24 pitt-arch systemd: Starting Daily man-db regeneration...\nJun 09 19:37:24 pitt-arch systemd: Started Verify integrity of password and group files.\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch kernel: random: dbus-daemon: uninitialized urandom read (12 bytes read)\nJun 09 19:37:24 pitt-arch kernel: Intel(R) Wireless WiFi driver for Linux\nJun 09 19:37:24 pitt-arch kernel: iwlwifi 0000:28:00.0: enabling device (0000 -> 0002)\nJun 09 19:37:24 pitt-arch kernel: iwlwifi 0000:28:00.0: api flags index 2 larger than supported by driver\nJun 09 19:37:24 pitt-arch kernel: iwlwifi 0000:28:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37\nJun 09 19:37:24 pitt-arch kernel: iwlwifi 0000:28:00.0: loaded firmware version 62.49eeb572.0 cc-a0-62.ucode op_mode iwlmvm\nJun 09 19:37:24 pitt-arch systemd: shadow.service: Deactivated successfully.\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3399] NetworkManager (version 1.30.4-3) is starting... (for the first time)\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3401] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)\nJun 09 19:37:24 pitt-arch systemd: Started Network Manager.\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3415] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"\nJun 09 19:37:24 pitt-arch systemd: Reached target Network.\nJun 09 19:37:24 pitt-arch systemd: Starting Permit User Sessions...\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3441] manager[0x559c5edf90c0]: monitoring kernel firmware directory '/lib/firmware'.\nJun 09 19:37:24 pitt-arch dbus-daemon: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1' (uid=0 pid=555 comm="/usr/bin/NetworkManager --no-daemon ")\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch systemd: Finished Permit User Sessions.\nJun 09 19:37:24 pitt-arch systemd: Started Getty on tty1.\nJun 09 19:37:24 pitt-arch audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:24 pitt-arch systemd: Reached target Login Prompts.\nJun 09 19:37:24 pitt-arch audit: BPF prog-id=20 op=LOAD\nJun 09 19:37:24 pitt-arch audit: BPF prog-id=21 op=LOAD\nJun 09 19:37:24 pitt-arch audit: BPF prog-id=22 op=LOAD\nJun 09 19:37:24 pitt-arch systemd: Starting Hostname Service...\nJun 09 19:37:24 pitt-arch systemd-logind: Watching system buttons on /dev/input/event1 (Power Button)\nJun 09 19:37:24 pitt-arch systemd-logind: Watching system buttons on /dev/input/event0 (Power Button)\nJun 09 19:37:24 pitt-arch systemd-logind: Watching system buttons on /dev/input/event5 (Microsoft SideWinder™ Mouse Consumer Control)\nJun 09 19:37:24 pitt-arch systemd-logind: New seat seat0.\nJun 09 19:37:24 pitt-arch systemd: Started User Login Management.\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch systemd: Reached target Multi-User System.\nJun 09 19:37:24 pitt-arch systemd: Reached target Graphical Interface.\nJun 09 19:37:24 pitt-arch systemd-udevd: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.\nJun 09 19:37:24 pitt-arch dbus-daemon: [system] Successfully activated service 'org.freedesktop.hostname1'\nJun 09 19:37:24 pitt-arch systemd: Started Hostname Service.\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch systemd: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.\nJun 09 19:37:24 pitt-arch systemd-udevd: Using default interface naming scheme 'v247'.\nJun 09 19:37:24 pitt-arch kernel: r8169 0000:26:00.0 enp38s0: renamed from eth0\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3842] hostname: hostname: using hostnamed\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3843] hostname: hostname changed from (none) to "pitt-arch"\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3844] dns-mgr[0x559c5edee110]: init: dns=default,systemd-resolved rc-manager=symlink\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3846] manager[0x559c5edf90c0]: rfkill: Wi-Fi hardware radio set enabled\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3846] manager[0x559c5edf90c0]: rfkill: WWAN hardware radio set enabled\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3886] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.30.4-3/libnm-device-plugin-adsl.so)\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3892] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.30.4-3/libnm-device-plugin-ovs.so)\nJun 09 19:37:24 pitt-arch kernel: kvm: Nested Virtualization enabled\nJun 09 19:37:24 pitt-arch kernel: SVM: kvm: Nested Paging enabled\nJun 09 19:37:24 pitt-arch kernel: SVM: Virtual VMLOAD VMSAVE supported\nJun 09 19:37:24 pitt-arch kernel: SVM: Virtual GIF supported\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3909] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.30.4-3/libnm-device-plugin-wwan.so)\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3916] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.30.4-3/libnm-device-plugin-bluetooth.so)\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3920] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.30.4-3/libnm-device-plugin-wifi.so)\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3957] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.30.4-3/libnm-device-plugin-team.so)\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3958] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3959] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3959] manager: Networking is enabled by state file\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3961] dhcp-init: Using DHCP client 'internal'\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.3962] settings: Loaded settings plugin: keyfile (internal)\nJun 09 19:37:24 pitt-arch dbus-daemon: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.1' (uid=0 pid=555 comm="/usr/bin/NetworkManager --no-daemon ")\nJun 09 19:37:24 pitt-arch systemd: Starting Network Manager Script Dispatcher Service...\nJun 09 19:37:24 pitt-arch dbus-daemon: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'\nJun 09 19:37:24 pitt-arch systemd: Started Network Manager Script Dispatcher Service.\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.4374] device (lo): carrier: link connected\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.4377] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.4387] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.4405] ovsdb: Could not connect: No such file or directory\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.4405] ovsdb: disconnected from ovsdb\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.4407] device (eth0): interface index 2 renamed iface from 'eth0' to 'enp38s0'\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.4415] device (enp38s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')\nJun 09 19:37:24 pitt-arch kernel: MCE: In-kernel MCE decoding enabled.\nJun 09 19:37:24 pitt-arch kernel: RTL8226B_RTL8221B 2.5Gbps PHY r8169-2600:00: attached PHY driver (mii_bus:phy_addr=r8169-2600:00, irq=MAC)\nJun 09 19:37:24 pitt-arch kernel: intel_rapl_common: Found RAPL domain package\nJun 09 19:37:24 pitt-arch kernel: intel_rapl_common: Found RAPL domain core\nJun 09 19:37:24 pitt-arch kernel: snd_hda_intel 0000:2d:00.1: Disabling MSI\nJun 09 19:37:24 pitt-arch kernel: snd_hda_intel 0000:2d:00.1: Handle vga_switcheroo audio client\nJun 09 19:37:24 pitt-arch kernel: snd_hda_intel 0000:2f:00.4: enabling device (0000 -> 0002)\nJun 09 19:37:24 pitt-arch kernel: snd_hda_codec_realtek hdaudioC1D0: ALCS1200A: SKU not ready 0x00000000\nJun 09 19:37:24 pitt-arch kernel: snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALCS1200A: line_outs=3 (0x14/0x15/0x16/0x0/0x0) type:line\nJun 09 19:37:24 pitt-arch kernel: snd_hda_codec_realtek hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)\nJun 09 19:37:24 pitt-arch kernel: snd_hda_codec_realtek hdaudioC1D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)\nJun 09 19:37:24 pitt-arch kernel: snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0\nJun 09 19:37:24 pitt-arch kernel: snd_hda_codec_realtek hdaudioC1D0:    dig-out=0x1e/0x0\nJun 09 19:37:24 pitt-arch kernel: snd_hda_codec_realtek hdaudioC1D0:    inputs:\nJun 09 19:37:24 pitt-arch kernel: snd_hda_codec_realtek hdaudioC1D0:      Front Mic=0x19\nJun 09 19:37:24 pitt-arch kernel: snd_hda_codec_realtek hdaudioC1D0:      Rear Mic=0x18\nJun 09 19:37:24 pitt-arch kernel: snd_hda_codec_realtek hdaudioC1D0:      Line=0x1a\nJun 09 19:37:24 pitt-arch kernel: input: HD-Audio Generic Front Mic as /devices/pci0000:00/0000:00:08.1/0000:2f:00.4/sound/card1/input15\nJun 09 19:37:24 pitt-arch kernel: input: HD-Audio Generic Rear Mic as /devices/pci0000:00/0000:00:08.1/0000:2f:00.4/sound/card1/input16\nJun 09 19:37:24 pitt-arch kernel: input: HD-Audio Generic Line as /devices/pci0000:00/0000:00:08.1/0000:2f:00.4/sound/card1/input17\nJun 09 19:37:24 pitt-arch kernel: input: HD-Audio Generic Line Out Front as /devices/pci0000:00/0000:00:08.1/0000:2f:00.4/sound/card1/input18\nJun 09 19:37:24 pitt-arch kernel: input: HD-Audio Generic Line Out Surround as /devices/pci0000:00/0000:00:08.1/0000:2f:00.4/sound/card1/input19\nJun 09 19:37:24 pitt-arch kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.1/0000:2d:00.1/sound/card0/input8\nJun 09 19:37:24 pitt-arch kernel: input: HD-Audio Generic Line Out CLFE as /devices/pci0000:00/0000:00:08.1/0000:2f:00.4/sound/card1/input20\nJun 09 19:37:24 pitt-arch kernel: input: HD-Audio Generic Front Headphone as /devices/pci0000:00/0000:00:08.1/0000:2f:00.4/sound/card1/input21\nJun 09 19:37:24 pitt-arch kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.1/0000:2d:00.1/sound/card0/input9\nJun 09 19:37:24 pitt-arch kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.1/0000:2d:00.1/sound/card0/input10\nJun 09 19:37:24 pitt-arch kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.1/0000:2d:00.1/sound/card0/input11\nJun 09 19:37:24 pitt-arch kernel: input: HDA NVidia HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:03.1/0000:2d:00.1/sound/card0/input12\nJun 09 19:37:24 pitt-arch kernel: input: HDA NVidia HDMI/DP,pcm=11 as /devices/pci0000:00/0000:00:03.1/0000:2d:00.1/sound/card0/input13\nJun 09 19:37:24 pitt-arch kernel: input: HDA NVidia HDMI/DP,pcm=12 as /devices/pci0000:00/0000:00:03.1/0000:2d:00.1/sound/card0/input14\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.6753] settings: (enp38s0): created default wired connection 'Wired connection 1'\nJun 09 19:37:24 pitt-arch kernel: r8169 0000:26:00.0 enp38s0: Link is Down\nJun 09 19:37:24 pitt-arch systemd: Reached target Sound Card.\nJun 09 19:37:24 pitt-arch kernel: iwlwifi 0000:28:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340\nJun 09 19:37:24 pitt-arch kernel: thermal thermal_zone0: failed to read out thermal zone (-61)\nJun 09 19:37:24 pitt-arch kernel: iwlwifi 0000:28:00.0: base HW address: 6c:6a:77:e5:28:42\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.9233] device (wlan0): driver supports Access Point (AP) mode\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.9239] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)\nJun 09 19:37:24 pitt-arch systemd: Starting Load/Save RF Kill Switch Status...\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.9245] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:06.0/0000:28:00.0/ieee80211/phy0/rfkill0) (driver iwlwifi)\nJun 09 19:37:24 pitt-arch systemd: Started Load/Save RF Kill Switch Status.\nJun 09 19:37:24 pitt-arch audit: 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'\nJun 09 19:37:24 pitt-arch kernel: iwlwifi 0000:28:00.0 wlo1: renamed from wlan0\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.9406] device (wlan0): interface index 3 renamed iface from 'wlan0' to 'wlo1'\nJun 09 19:37:24 pitt-arch NetworkManager: <info>  [1623263844.9449] device (wlo1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')\nJun 09 19:37:25 pitt-arch kernel: nvidia: loading out-of-tree module taints kernel.\nJun 09 19:37:25 pitt-arch kernel: nvidia: module license 'NVIDIA' taints kernel.\nJun 09 19:37:25 pitt-arch kernel: Disabling lock debugging due to kernel taint\nJun 09 19:37:25 pitt-arch kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel\nJun 09 19:37:25 pitt-arch kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 237\nJun 09 19:37:25 pitt-arch kernel:\nJun 09 19:37:25 pitt-arch kernel: nvidia 0000:2d:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem\nJun 09 19:37:25 pitt-arch kernel: urandom_read: 4 callbacks suppressed\nJun 09 19:37:25 pitt-arch kernel: random: NetworkManager: uninitialized urandom read (6 bytes read)\nJun 09 19:37:25 pitt-arch systemd-udevd: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.\nJun 09 19:37:25 pitt-arch NetworkManager: <info>  [1623263845.1493] device (wlo1): set-hw-addr: set MAC address to 82:EA:22:44:D1:24 (scanning)\nJun 09 19:37:25 pitt-arch kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  465.31  Thu May 13 22:24:36 UTC 2021\nJun 09 19:37:25 pitt-arch kernel: usb 1-2: New USB device found, idVendor=1b1c, idProduct=1b36, bcdDevice= 2.04\nJun 09 19:37:25 pitt-arch kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3\nJun 09 19:37:25 pitt-arch kernel: usb 1-2: Product: Corsair Gaming K70 LUX Keyboard\nJun 09 19:37:25 pitt-arch kernel: usb 1-2: Manufacturer: Corsair\nJun 09 19:37:25 pitt-arch kernel: usb 1-2: SerialNumber: 0C016028AEBD15015626CBCCF5001942\nJun 09 19:37:25 pitt-arch kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  465.31  Thu May 13 22:14:23 UTC 2021\nJun 09 19:37:25 pitt-arch kernel: [drm] [nvidia-drm] [GPU ID 0x00002d00] Loading driver\nJun 09 19:37:25 pitt-arch kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:2d:00.0 on minor 0\nJun 09 19:37:25 pitt-arch dbus-daemon: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' requested by ':1.1' (uid=0 pid=555 comm="/usr/bin/NetworkManager --no-daemon ")\nJun 09 19:37:25 pitt-arch systemd: Starting WPA supplicant...\nJun 09 19:37:25 pitt-arch kernel: input: Corsair Corsair Gaming K70 LUX Keyboard  as /devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.1/usb1/1-2/1-2:1.0/0003:1B1C:1B36.0004/input/input22\nJun 09 19:37:25 pitt-arch dbus-daemon: [system] Successfully activated service 'fi.w1.wpa_supplicant1'\nJun 09 19:37:25 pitt-arch systemd: Started WPA supplicant.\nJun 09 19:37:25 pitt-arch audit: 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'\nJun 09 19:37:25 pitt-arch wpa_supplicant: Successfully initialized wpa_supplicant\nJun 09 19:37:25 pitt-arch kernel: hid-generic 0003:1B1C:1B36.0004: input,hidraw3: USB HID v1.11 Keyboard [Corsair Corsair Gaming K70 LUX Keyboard ] on usb-0000:2a:00.1-2/input0\nJun 09 19:37:25 pitt-arch kernel: input: Corsair Corsair Gaming K70 LUX Keyboard  Keyboard as /devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.1/usb1/1-2/1-2:1.1/0003:1B1C:1B36.0005/input/input23\nJun 09 19:37:25 pitt-arch kernel: random: crng init done\nJun 09 19:37:25 pitt-arch NetworkManager: <info>  [1623263845.4413] device (wlo1): supplicant interface state: internal-starting -> disconnected\nJun 09 19:37:25 pitt-arch NetworkManager: <info>  [1623263845.4413] Wi-Fi P2P device controlled by interface wlo1 created\nJun 09 19:37:25 pitt-arch NetworkManager: <info>  [1623263845.4414] manager: (p2p-dev-wlo1): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)\nJun 09 19:37:25 pitt-arch NetworkManager: <info>  [1623263845.4416] device (p2p-dev-wlo1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')\nJun 09 19:37:25 pitt-arch NetworkManager: <warn>  [1623263845.4418] sup-iface[32a0d85b7dc696b3,0,wlo1]: call-p2p-cancel: failed with P2P cancel failed\nJun 09 19:37:25 pitt-arch NetworkManager: <info>  [1623263845.4418] device (wlo1): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')\nJun 09 19:37:25 pitt-arch NetworkManager: <info>  [1623263845.4421] device (p2p-dev-wlo1): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')\nJun 09 19:37:25 pitt-arch systemd: Finished Load/Save Random Seed.\nJun 09 19:37:25 pitt-arch audit: 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'\nJun 09 19:37:25 pitt-arch systemd: Condition check resulted in First Boot Complete being skipped.\nJun 09 19:37:25 pitt-arch systemd: Condition check resulted in Store a System Token in an EFI Variable being skipped.\nJun 09 19:37:25 pitt-arch systemd: Condition check resulted in Commit a transient machine-id on disk being skipped.\nJun 09 19:37:25 pitt-arch kernel: input: Corsair Corsair Gaming K70 LUX Keyboard  as /devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.1/usb1/1-2/1-2:1.1/0003:1B1C:1B36.0005/input/input24\nJun 09 19:37:25 pitt-arch kernel: input: Corsair Corsair Gaming K70 LUX Keyboard  as /devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.1/usb1/1-2/1-2:1.1/0003:1B1C:1B36.0005/input/input25\nJun 09 19:37:25 pitt-arch kernel: hid-generic 0003:1B1C:1B36.0005: input,hiddev98,hidraw4: USB HID v1.11 Keyboard [Corsair Corsair Gaming K70 LUX Keyboard ] on usb-0000:2a:00.1-2/input1\nJun 09 19:37:25 pitt-arch kernel: usbhid 1-2:1.2: couldn't find an input interrupt endpoint\nJun 09 19:37:25 pitt-arch kernel: usb 1-4: new full-speed USB device number 4 using xhci_hcd\nJun 09 19:37:25 pitt-arch kernel: usb 1-4: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01\nJun 09 19:37:25 pitt-arch kernel: usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0\nJun 09 19:37:25 pitt-arch kernel: usb 1-5: new high-speed USB device number 5 using xhci_hcd\nJun 09 19:37:27 pitt-arch NetworkManager: <info>  [1623263847.8667] device (enp38s0): carrier: link connected\nJun 09 19:37:27 pitt-arch kernel: r8169 0000:26:00.0 enp38s0: Link is Up - 1Gbps/Full - flow control rx/tx\nJun 09 19:37:27 pitt-arch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp38s0: link becomes ready\nJun 09 19:37:27 pitt-arch NetworkManager: <info>  [1623263847.8668] device (enp38s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')\nJun 09 19:37:27 pitt-arch NetworkManager: <info>  [1623263847.8672] policy: auto-activating connection 'Wired connection 1' (1e515707-25e4-3fd0-b9a3-1e43cea3c32f)\nJun 09 19:37:27 pitt-arch NetworkManager: <info>  [1623263847.8675] device (enp38s0): Activation: starting connection 'Wired connection 1' (1e515707-25e4-3fd0-b9a3-1e43cea3c32f)\nJun 09 19:37:27 pitt-arch NetworkManager: <info>  [1623263847.8676] device (enp38s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')\nJun 09 19:37:27 pitt-arch NetworkManager: <info>  [1623263847.8677] manager: NetworkManager state is now CONNECTING\nJun 09 19:37:27 pitt-arch NetworkManager: <info>  [1623263847.8678] device (enp38s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')\nJun 09 19:37:27 pitt-arch NetworkManager: <info>  [1623263847.8680] device (enp38s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')\nJun 09 19:37:27 pitt-arch NetworkManager: <info>  [1623263847.8682] dhcp4 (enp38s0): activation: beginning transaction (timeout in 45 seconds)\nJun 09 19:37:27 pitt-arch NetworkManager: <warn>  [1623263847.8685] secret-key: too short secret key in "/var/lib/NetworkManager/secret_key" (generate new key)\nJun 09 19:37:27 pitt-arch NetworkManager: <info>  [1623263847.8835] dhcp4 (enp38s0): state changed unknown -> bound, address=192.168.1.131\nJun 09 19:37:27 pitt-arch NetworkManager: <info>  [1623263847.8844] device (enp38s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')\nJun 09 19:37:27 pitt-arch NetworkManager: <info>  [1623263847.8857] device (enp38s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')\nJun 09 19:37:27 pitt-arch NetworkManager: <info>  [1623263847.8858] device (enp38s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')\nJun 09 19:37:27 pitt-arch NetworkManager: <info>  [1623263847.8860] manager: NetworkManager state is now CONNECTED_LOCAL\nJun 09 19:37:27 pitt-arch NetworkManager: <info>  [1623263847.8864] manager: NetworkManager state is now CONNECTED_SITE\nJun 09 19:37:27 pitt-arch NetworkManager: <info>  [1623263847.8864] policy: set 'Wired connection 1' (enp38s0) as default for IPv4 routing and DNS\nJun 09 19:37:27 pitt-arch dbus-daemon: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.1' (uid=0 pid=555 comm="/usr/bin/NetworkManager --no-daemon ")\nJun 09 19:37:27 pitt-arch dbus-daemon: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.\nJun 09 19:37:27 pitt-arch NetworkManager: <info>  [1623263847.8986] device (enp38s0): Activation: successful, device activated.\nJun 09 19:37:27 pitt-arch NetworkManager: <info>  [1623263847.9879] manager: NetworkManager state is now CONNECTED_GLOBAL\nJun 09 19:37:28 pitt-arch kernel: usb 1-5: New USB device found, idVendor=046d, idProduct=082d, bcdDevice= 0.11\nJun 09 19:37:28 pitt-arch kernel: usb 1-5: New USB device strings: Mfr=0, Product=2, SerialNumber=1\nJun 09 19:37:28 pitt-arch kernel: usb 1-5: Product: HD Pro Webcam C920\nJun 09 19:37:28 pitt-arch kernel: usb 1-5: SerialNumber: A4BD759F\nJun 09 19:37:28 pitt-arch kernel: usb 1-6: new full-speed USB device number 6 using xhci_hcd\nJun 09 19:37:28 pitt-arch kernel: usb 1-6: New USB device found, idVendor=256c, idProduct=006e, bcdDevice= 0.00\nJun 09 19:37:28 pitt-arch kernel: usb 1-6: New USB device strings: Mfr=5, Product=6, SerialNumber=0\nJun 09 19:37:28 pitt-arch kernel: hid-generic 0003:256C:006E.0006: hiddev99,hidraw5: USB HID v1.11 Device [HID 256c:006e] on usb-0000:2a:00.1-6/input0\nJun 09 19:37:28 pitt-arch kernel: input: HID 256c:006e as /devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.1/usb1/1-6/1-6:1.1/0003:256C:006E.0007/input/input26\nJun 09 19:37:28 pitt-arch kernel: hid-generic 0003:256C:006E.0007: input,hidraw6: USB HID v1.11 Device [HID 256c:006e] on usb-0000:2a:00.1-6/input1\nJun 09 19:37:28 pitt-arch mtp-probe: checking bus 1, device 2: "/sys/devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.1/usb1/1-1"\nJun 09 19:37:28 pitt-arch mtp-probe: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.1/usb1/1-5"\nJun 09 19:37:28 pitt-arch mtp-probe: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.1/usb1/1-6"\nJun 09 19:37:28 pitt-arch mtp-probe: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.1/usb1/1-2"\nJun 09 19:37:28 pitt-arch mtp-probe: bus: 1, device: 2 was not an MTP device\nJun 09 19:37:28 pitt-arch mtp-probe: bus: 1, device: 5 was not an MTP device\nJun 09 19:37:28 pitt-arch mtp-probe: bus: 1, device: 6 was not an MTP device\nJun 09 19:37:28 pitt-arch mtp-probe: bus: 1, device: 3 was not an MTP device\nJun 09 19:37:28 pitt-arch kernel: mc: Linux media interface: v0.10\nJun 09 19:37:28 pitt-arch kernel: input: HID 256c:006e Pen as /devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.1/usb1/1-6/1-6:1.0/0003:256C:006E.0006/input/input27\nJun 09 19:37:28 pitt-arch kernel: input: HID 256c:006e Pad as /devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.1/usb1/1-6/1-6:1.0/0003:256C:006E.0006/input/input28\nJun 09 19:37:28 pitt-arch kernel: uclogic 0003:256C:006E.0006: input,hidraw5: USB HID v1.11 Keypad [HID 256c:006e] on usb-0000:2a:00.1-6/input0\nJun 09 19:37:28 pitt-arch kernel: videodev: Linux video capture interface: v2.00\nJun 09 19:37:28 pitt-arch kernel: Bluetooth: Core ver 2.22\nJun 09 19:37:28 pitt-arch kernel: NET: Registered protocol family 31\nJun 09 19:37:28 pitt-arch kernel: Bluetooth: HCI device and connection manager initialized\nJun 09 19:37:28 pitt-arch kernel: Bluetooth: HCI socket layer initialized\nJun 09 19:37:28 pitt-arch kernel: Bluetooth: L2CAP socket layer initialized\nJun 09 19:37:28 pitt-arch kernel: Bluetooth: SCO socket layer initialized\nJun 09 19:37:28 pitt-arch systemd-logind: Watching system buttons on /dev/input/event23 (Corsair Corsair Gaming K70 LUX Keyboard  Keyboard)\nJun 09 19:37:28 pitt-arch systemd-logind: Watching system buttons on /dev/input/event22 (Corsair Corsair Gaming K70 LUX Keyboard )\nJun 09 19:37:28 pitt-arch kernel: uclogic 0003:256C:006E.0007: No inputs registered, leaving\nJun 09 19:37:28 pitt-arch kernel: uclogic 0003:256C:006E.0007: hidraw6: USB HID v1.11 Device [HID 256c:006e] on usb-0000:2a:00.1-6/input1\nJun 09 19:37:28 pitt-arch kernel: Bluetooth: hci0: Firmware revision 0.0 build 121 week 7 2021\nJun 09 19:37:28 pitt-arch systemd: Reached target Bluetooth.\nJun 09 19:37:28 pitt-arch kernel: usbcore: registered new interface driver btusb\nJun 09 19:37:28 pitt-arch wpa_supplicant: wlo1: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=GB\nJun 09 19:37:28 pitt-arch NetworkManager: <info>  [1623263848.7984] manager: startup complete\nJun 09 19:37:28 pitt-arch kernel: Bluetooth: hci0: MSFT filter_enable is already on\nJun 09 19:37:28 pitt-arch kernel: usbcore: registered new interface driver snd-usb-audio\nJun 09 19:37:28 pitt-arch kernel: usb 1-5: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d)\nJun 09 19:37:28 pitt-arch kernel: input: HD Pro Webcam C920 as /devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.1/usb1/1-5/1-5:1.0/input/input30\nJun 09 19:37:28 pitt-arch kernel: usbcore: registered new interface driver uvcvideo\nJun 09 19:37:33 pitt-arch systemd: systemd-rfkill.service: Deactivated successfully.\nJun 09 19:37:33 pitt-arch audit: 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'\nJun 09 19:37:33 pitt-arch kernel: kauditd_printk_skb: 27 callbacks suppressed\nJun 09 19:37:33 pitt-arch kernel: audit: type=1131 audit(1623263853.757:38): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:35 pitt-arch systemd: NetworkManager-dispatcher.service: Deactivated successfully.\nJun 09 19:37:35 pitt-arch audit: 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'\nJun 09 19:37:35 pitt-arch kernel: audit: type=1131 audit(1623263855.073:39): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:36 pitt-arch login: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=/dev/tty1 ruser= rhost=  user=root\nJun 09 19:37:36 pitt-arch audit: USER_AUTH pid=586 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=? acct="root" exe="/usr/bin/login" hostname=pitt-arch addr=? terminal=/dev/tty1 res=failed'\nJun 09 19:37:36 pitt-arch kernel: audit: type=1100 audit(1623263856.463:40): pid=586 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=? acct="root" exe="/usr/bin/login" hostname=pitt-arch addr=? terminal=/dev/tty1 res=failed'\nJun 09 19:37:37 pitt-arch login: FAILED LOGIN SESSION FROM tty1 FOR root, Permission denied\nJun 09 19:37:40 pitt-arch systemd: getty@tty1.service: Deactivated successfully.\nJun 09 19:37:40 pitt-arch audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:40 pitt-arch kernel: audit: type=1131 audit(1623263860.963:41): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:40 pitt-arch systemd: getty@tty1.service: Scheduled restart job, restart counter is at 1.\nJun 09 19:37:40 pitt-arch systemd: Stopped Getty on tty1.\nJun 09 19:37:40 pitt-arch audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:40 pitt-arch systemd: Started Getty on tty1.\nJun 09 19:37:40 pitt-arch kernel: audit: type=1130 audit(1623263860.967:42): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:40 pitt-arch kernel: audit: type=1131 audit(1623263860.967:43): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:40 pitt-arch kernel: audit: type=1130 audit(1623263860.967:44): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:53 pitt-arch audit: USER_AUTH pid=8088 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/login" hostname=pitt-arch addr=? terminal=/dev/tty1 res=success'\nJun 09 19:37:53 pitt-arch audit: USER_ACCT pid=8088 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="root" exe="/usr/bin/login" hostname=pitt-arch addr=? terminal=/dev/tty1 res=success'\nJun 09 19:37:53 pitt-arch audit: CRED_ACQ pid=8088 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/login" hostname=pitt-arch addr=? terminal=/dev/tty1 res=success'\nJun 09 19:37:53 pitt-arch audit: SYSCALL arch=c000003e syscall=1 success=yes exit=1 a0=4 a1=7ffc62544330 a2=1 a3=0 items=0 ppid=1 pid=8088 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=tty1 ses=1 comm="login" exe="/usr/bin/login" key=(null)\nJun 09 19:37:53 pitt-arch audit: PROCTITLE proctitle=2F62696E2F6C6F67696E002D70002D2D\nJun 09 19:37:53 pitt-arch login: pam_unix(login:session): session opened for user root(uid=0) by LOGIN(uid=0)\nJun 09 19:37:53 pitt-arch kernel: audit: type=1100 audit(1623263873.657:45): pid=8088 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/login" hostname=pitt-arch addr=? terminal=/dev/tty1 res=success'\nJun 09 19:37:53 pitt-arch kernel: audit: type=1101 audit(1623263873.657:46): pid=8088 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="root" exe="/usr/bin/login" hostname=pitt-arch addr=? terminal=/dev/tty1 res=success'\nJun 09 19:37:53 pitt-arch kernel: audit: type=1103 audit(1623263873.657:47): pid=8088 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/login" hostname=pitt-arch addr=? terminal=/dev/tty1 res=success'\nJun 09 19:37:53 pitt-arch kernel: audit: type=1006 audit(1623263873.657:48): pid=8088 uid=0 old-auid=4294967295 auid=0 tty=tty1 old-ses=4294967295 ses=1 res=1\nJun 09 19:37:53 pitt-arch kernel: audit: type=1300 audit(1623263873.657:48): arch=c000003e syscall=1 success=yes exit=1 a0=4 a1=7ffc62544330 a2=1 a3=0 items=0 ppid=1 pid=8088 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=tty1 ses=1 comm="login" exe="/usr/bin/login" key=(null)\nJun 09 19:37:53 pitt-arch kernel: audit: type=1327 audit(1623263873.657:48): proctitle=2F62696E2F6C6F67696E002D70002D2D\nJun 09 19:37:53 pitt-arch systemd: Created slice User Slice of UID 0.\nJun 09 19:37:53 pitt-arch systemd: Starting User Runtime Directory /run/user/0...\nJun 09 19:37:53 pitt-arch systemd-logind: New session 1 of user root.\nJun 09 19:37:53 pitt-arch systemd: Finished User Runtime Directory /run/user/0.\nJun 09 19:37:53 pitt-arch audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:53 pitt-arch systemd: Starting User Manager for UID 0...\nJun 09 19:37:53 pitt-arch kernel: audit: type=1130 audit(1623263873.663:49): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:53 pitt-arch audit: USER_ACCT pid=14216 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="root" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:53 pitt-arch audit: CRED_ACQ pid=14216 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="root" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'\nJun 09 19:37:53 pitt-arch audit: SYSCALL arch=c000003e syscall=1 success=yes exit=1 a0=9 a1=7ffd5f1b5740 a2=1 a3=0 items=0 ppid=1 pid=14216 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=2 comm="(systemd)" exe="/usr/lib/systemd/systemd" key=(null)\nJun 09 19:37:53 pitt-arch audit: PROCTITLE proctitle="(systemd)"\nJun 09 19:37:53 pitt-arch systemd: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal= user=[root] ruser=[<unknown>] rhost=[<unknown>]\nJun 09 19:37:53 pitt-arch systemd: pam_unix(systemd-user:session): session opened for user root(uid=0) by (uid=0)\nJun 09 19:37:53 pitt-arch systemd: pam_env(systemd-user:session): deprecated reading of user environment enabled\nJun 09 19:37:53 pitt-arch audit: USER_START pid=14216 uid=0 auid=0 ses=2 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="root" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:53 pitt-arch kernel: audit: type=1101 audit(1623263873.667:50): pid=14216 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="root" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:53 pitt-arch kernel: audit: type=1103 audit(1623263873.667:51): pid=14216 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="root" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'\nJun 09 19:37:53 pitt-arch kernel: audit: type=1006 audit(1623263873.667:52): pid=14216 uid=0 old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=2 res=1\nJun 09 19:37:53 pitt-arch audit: BPF prog-id=23 op=LOAD\nJun 09 19:37:53 pitt-arch audit: SYSCALL arch=c000003e syscall=321 success=yes exit=8 a0=5 a1=7ffc725ce870 a2=78 a3=7ffc725ce870 items=0 ppid=1 pid=14216 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=2 comm="systemd" exe="/usr/lib/systemd/systemd" key=(null)\nJun 09 19:37:53 pitt-arch audit: BPF prog-id=23 op=UNLOAD\nJun 09 19:37:53 pitt-arch audit: BPF prog-id=24 op=LOAD\nJun 09 19:37:53 pitt-arch audit: SYSCALL arch=c000003e syscall=321 success=yes exit=8 a0=5 a1=7ffc725ce940 a2=78 a3=7ffc725ce940 items=0 ppid=1 pid=14216 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=2 comm="systemd" exe="/usr/lib/systemd/systemd" key=(null)\nJun 09 19:37:53 pitt-arch audit: BPF prog-id=24 op=UNLOAD\nJun 09 19:37:53 pitt-arch systemd: Queued start job for default target Main User Target.\nJun 09 19:37:53 pitt-arch systemd: Created slice User Application Slice.\nJun 09 19:37:53 pitt-arch systemd: Reached target Paths.\nJun 09 19:37:53 pitt-arch systemd: Reached target Timers.\nJun 09 19:37:53 pitt-arch systemd: Starting D-Bus User Message Bus Socket.\nJun 09 19:37:53 pitt-arch systemd: Listening on GnuPG network certificate management daemon.\nJun 09 19:37:53 pitt-arch systemd: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).\nJun 09 19:37:53 pitt-arch systemd: Listening on GnuPG cryptographic agent and passphrase cache (restricted).\nJun 09 19:37:53 pitt-arch systemd: Listening on GnuPG cryptographic agent (ssh-agent emulation).\nJun 09 19:37:53 pitt-arch systemd: Listening on GnuPG cryptographic agent and passphrase cache.\nJun 09 19:37:53 pitt-arch systemd: Listening on p11-kit server.\nJun 09 19:37:53 pitt-arch systemd: Listening on Multimedia System.\nJun 09 19:37:53 pitt-arch systemd: Condition check resulted in Sound System being skipped.\nJun 09 19:37:53 pitt-arch systemd: Listening on D-Bus User Message Bus Socket.\nJun 09 19:37:53 pitt-arch systemd: Reached target Sockets.\nJun 09 19:37:53 pitt-arch systemd: Reached target Basic System.\nJun 09 19:37:53 pitt-arch systemd: Started User Manager for UID 0.\nJun 09 19:37:53 pitt-arch audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:37:53 pitt-arch systemd: Starting Update XDG user dir configuration...\nJun 09 19:37:53 pitt-arch systemd: Started Session 1 of user root.\nJun 09 19:37:53 pitt-arch systemd: xdg-user-dirs-update.service: Deactivated successfully.\nJun 09 19:37:53 pitt-arch systemd: Finished Update XDG user dir configuration.\nJun 09 19:37:53 pitt-arch systemd: Reached target Main User Target.\nJun 09 19:37:53 pitt-arch systemd: Startup finished in 81ms.\nJun 09 19:37:53 pitt-arch login: pam_env(login:session): deprecated reading of user environment enabled\nJun 09 19:37:53 pitt-arch audit: USER_START pid=8088 uid=0 auid=0 ses=1 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="root" exe="/usr/bin/login" hostname=pitt-arch addr=? terminal=/dev/tty1 res=success'\nJun 09 19:37:53 pitt-arch audit: CRED_REFR pid=8088 uid=0 auid=0 ses=1 msg='op=PAM:setcred grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/login" hostname=pitt-arch addr=? terminal=/dev/tty1 res=success'\nJun 09 19:37:53 pitt-arch login: ROOT LOGIN ON tty1\nJun 09 19:37:54 pitt-arch systemd: systemd-hostnamed.service: Deactivated successfully.\nJun 09 19:37:54 pitt-arch audit: 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'\nJun 09 19:37:54 pitt-arch audit: BPF prog-id=22 op=UNLOAD\nJun 09 19:37:54 pitt-arch audit: BPF prog-id=21 op=UNLOAD\nJun 09 19:37:54 pitt-arch audit: BPF prog-id=20 op=UNLOAD\nJun 09 19:38:05 pitt-arch dbus-daemon: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' requested by ':1.11' (uid=0 pid=19248 comm="gdm ")\nJun 09 19:38:05 pitt-arch systemd: Reached target User and Group Name Lookups.\nJun 09 19:38:05 pitt-arch systemd: Starting Accounts Service...\nJun 09 19:38:05 pitt-arch dbus-daemon: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.12' (uid=0 pid=19255 comm="/usr/lib/accounts-daemon ")\nJun 09 19:38:05 pitt-arch systemd: Starting Authorization Manager...\nJun 09 19:38:05 pitt-arch polkitd: Started polkitd version 0.119\nJun 09 19:38:05 pitt-arch polkitd: Loading rules from directory /etc/polkit-1/rules.d\nJun 09 19:38:05 pitt-arch polkitd: Loading rules from directory /usr/share/polkit-1/rules.d\nJun 09 19:38:05 pitt-arch polkitd: Finished loading, compiling and executing 8 rules\nJun 09 19:38:05 pitt-arch dbus-daemon: [system] Successfully activated service 'org.freedesktop.PolicyKit1'\nJun 09 19:38:05 pitt-arch systemd: Started Authorization Manager.\nJun 09 19:38:05 pitt-arch polkitd: Acquired the name org.freedesktop.PolicyKit1 on the system bus\nJun 09 19:38:05 pitt-arch audit: 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'\nJun 09 19:38:05 pitt-arch accounts-daemon: started daemon version 0.6.55\nJun 09 19:38:05 pitt-arch dbus-daemon: [system] Successfully activated service 'org.freedesktop.Accounts'\nJun 09 19:38:05 pitt-arch systemd: Started Accounts Service.\nJun 09 19:38:05 pitt-arch audit: 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'\nJun 09 19:38:05 pitt-arch kernel: kauditd_printk_skb: 18 callbacks suppressed\nJun 09 19:38:05 pitt-arch kernel: audit: type=1130 audit(1623263885.117:65): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=polkit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:38:05 pitt-arch kernel: audit: type=1130 audit(1623263885.117:66): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=accounts-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:38:05 pitt-arch audit: USER_AUTH pid=19291 uid=0 auid=0 ses=1 msg='op=PAM:authentication grantors=pam_succeed_if,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=pitt-arch addr=? terminal=/dev/tty1 res=success'\nJun 09 19:38:05 pitt-arch audit: USER_ACCT pid=19291 uid=0 auid=0 ses=1 msg='op=PAM:accounting grantors=pam_succeed_if,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=pitt-arch addr=? terminal=/dev/tty1 res=success'\nJun 09 19:38:05 pitt-arch audit: CRED_ACQ pid=19291 uid=0 auid=0 ses=1 msg='op=PAM:setcred grantors=pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=pitt-arch addr=? terminal=/dev/tty1 res=success'\nJun 09 19:38:05 pitt-arch kernel: audit: type=1100 audit(1623263885.127:67): pid=19291 uid=0 auid=0 ses=1 msg='op=PAM:authentication grantors=pam_succeed_if,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=pitt-arch addr=? terminal=/dev/tty1 res=success'\nJun 09 19:38:05 pitt-arch kernel: audit: type=1101 audit(1623263885.127:68): pid=19291 uid=0 auid=0 ses=1 msg='op=PAM:accounting grantors=pam_succeed_if,pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=pitt-arch addr=? terminal=/dev/tty1 res=success'\nJun 09 19:38:05 pitt-arch kernel: audit: type=1103 audit(1623263885.127:69): pid=19291 uid=0 auid=0 ses=1 msg='op=PAM:setcred grantors=pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=pitt-arch addr=? terminal=/dev/tty1 res=success'\nJun 09 19:38:05 pitt-arch audit: SYSCALL arch=c000003e syscall=1 success=yes exit=3 a0=9 a1=7ffec37b33e0 a2=3 a3=78 items=0 ppid=19248 pid=19291 auid=120 uid=0 gid=120 euid=0 suid=0 fsuid=0 egid=120 sgid=120 fsgid=120 tty=tty1 ses=3 comm="gdm-session-wor" exe="/usr/lib/gdm-session-worker" key=(null)\nJun 09 19:38:05 pitt-arch audit: PROCTITLE proctitle=67646D2D73657373696F6E2D776F726B6572205B70616D2F67646D2D6C61756E63682D656E7669726F6E6D656E745D\nJun 09 19:38:05 pitt-arch gdm-launch-environment]: pam_env(gdm-launch-environment:session): deprecated reading of user environment enabled\nJun 09 19:38:05 pitt-arch audit: USER_START pid=19291 uid=0 auid=120 ses=3 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_succeed_if,pam_permit,pam_systemd,pam_env acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=pitt-arch addr=? terminal=/dev/tty1 res=success'\nJun 09 19:38:05 pitt-arch kernel: audit: type=1006 audit(1623263885.167:70): pid=19291 uid=0 old-auid=0 auid=120 tty=tty1 old-ses=1 ses=3 res=1\nJun 09 19:38:05 pitt-arch kernel: audit: type=1300 audit(1623263885.167:70): arch=c000003e syscall=1 success=yes exit=3 a0=9 a1=7ffec37b33e0 a2=3 a3=78 items=0 ppid=19248 pid=19291 auid=120 uid=0 gid=120 euid=0 suid=0 fsuid=0 egid=120 sgid=120 fsgid=120 tty=tty1 ses=3 comm="gdm-session-wor" exe="/usr/lib/gdm-session-worker" key=(null)\nJun 09 19:38:05 pitt-arch kernel: audit: type=1327 audit(1623263885.167:70): proctitle=67646D2D73657373696F6E2D776F726B6572205B70616D2F67646D2D6C61756E63682D656E7669726F6E6D656E745D\nJun 09 19:38:05 pitt-arch kernel: audit: type=1105 audit(1623263885.167:71): pid=19291 uid=0 auid=120 ses=3 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_succeed_if,pam_permit,pam_systemd,pam_env acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=pitt-arch addr=? terminal=/dev/tty1 res=success'\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (--) Log file renamed from "/var/lib/gdm/.local/share/xorg/Xorg.pid-19323.log" to "/var/lib/gdm/.local/share/xorg/Xorg.0.log"\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (WW) Failed to open protocol names file lib/xorg/protocol.txt\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: X.Org X Server 1.20.11\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: X Protocol Version 11, Revision 0\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: Build Operating System: Linux Archlinux\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: Current Operating System: Linux pitt-arch 5.12.9-arch1-1 #1 SMP PREEMPT Thu, 03 Jun 2021 11:36:13 +0000 x86_64\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=b285af18-bfb6-4d95-9986-e1cb71bfb91f rw loglevel=3 quiet\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: Build Date: 13 April 2021  03:12:10PM\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: Current version of pixman: 0.40.0\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:         Before reporting problems, check http://wiki.x.org\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:         to make sure that you have the latest version.\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: Markers: (--) probed, (**) from config file, (==) default setting,\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:         (++) from command line, (!!) notice, (II) informational,\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (==) Log file: "/var/lib/gdm/.local/share/xorg/Xorg.0.log", Time: Wed Jun  9 19:38:05 2021\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (==) Using system config directory "/usr/share/X11/xorg.conf.d"\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (==) No Layout section.  Using the first Screen section.\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (==) No screen section available. Using defaults.\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (**) |-->Screen "Default Screen Section" (0)\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (**) |   |-->Monitor "<default monitor>"\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (==) No monitor specified for screen "Default Screen Section".\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:         Using a default monitor configuration.\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (==) Automatically adding devices\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (==) Automatically enabling devices\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (==) Automatically adding GPU devices\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (==) Automatically binding GPU devices\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (==) Max clients allowed: 256, resource mask: 0x1fffff\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (WW) The directory "/usr/share/fonts/misc" does not exist.\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:         Entry deleted from font path.\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (WW) The directory "/usr/share/fonts/TTF" does not exist.\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (WW) The directory "/usr/share/fonts/OTF" does not exist.\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (WW) The directory "/usr/share/fonts/Type1" does not exist.\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (==) FontPath set to:\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:         /usr/share/fonts/100dpi,\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:         /usr/share/fonts/75dpi\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (==) ModulePath set to "/usr/lib/xorg/modules"\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (II) The server relies on udev to provide the list of input devices.\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:         If no devices become available, reconfigure udev or disable AutoAddDevices.\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (II) Module ABI versions:\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:         X.Org ANSI C Emulation: 0.4\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:         X.Org Video Driver: 24.1\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:         X.Org XInput driver : 24.1\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:         X.Org Server Extension : 10.0\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (++) using VT number 1\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (EE) systemd-logind: TakeControl failed: Only owner of session may take control\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (--) PCI:*(45@0:0:0) 10de:1b81:3842:6178 rev 161, Mem @ 0xfb000000/16777216, 0xd0000000/268435456, 0xe0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (II) LoadModule: "glx"\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (II) Loading /usr/lib/xorg/modules/extensions/libglx.so\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (II) Module glx: vendor="X.Org Foundation"\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:         compiled for 1.20.11, module version = 1.0.0\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:         ABI class: X.Org Server Extension, version 10.0\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (==) Matched nouveau as autoconfigured driver 0\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (==) Matched nv as autoconfigured driver 1\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (==) Matched modesetting as autoconfigured driver 2\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (==) Matched fbdev as autoconfigured driver 3\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (==) Matched vesa as autoconfigured driver 4\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (==) Assigned the driver to the xf86ConfigLayout\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (II) LoadModule: "nouveau"\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (WW) Warning, couldn't open module nouveau\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (EE) Failed to load module "nouveau" (module does not exist, 0)\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (II) LoadModule: "nv"\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (WW) Warning, couldn't open module nv\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (EE) Failed to load module "nv" (module does not exist, 0)\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (II) LoadModule: "modesetting"\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (II) Module modesetting: vendor="X.Org Foundation"\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:         compiled for 1.20.11, module version = 1.20.11\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:         Module class: X.Org Video Driver\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:         ABI class: X.Org Video Driver, version 24.1\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (II) LoadModule: "fbdev"\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (WW) Warning, couldn't open module fbdev\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (EE) Failed to load module "fbdev" (module does not exist, 0)\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (II) LoadModule: "vesa"\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (II) Module vesa: vendor="X.Org Foundation"\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:         compiled for 1.20.9, module version = 2.5.0\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (II) modesetting: Driver for Modesetting Kernel Drivers: kms\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (II) VESA: driver for VESA chipsets: vesa\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (EE)\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: Fatal server error:\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (EE) xf86OpenConsole: Cannot open virtual console 1 (Permission denied)\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: Please consult the The X.Org Foundation support\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:          at http://wiki.x.org\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session:  for help.\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (EE) Please also check the log file at "/var/lib/gdm/.local/share/xorg/Xorg.0.log" for additional information.\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: (EE) Server terminated with error (1). Closing log file.\nJun 09 19:38:05 pitt-arch /usr/lib/gdm-x-session: Unable to run X server\nJun 09 19:38:05 pitt-arch audit: USER_END pid=19291 uid=0 auid=120 ses=3 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_succeed_if,pam_permit,pam_systemd,pam_env acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=pitt-arch addr=? terminal=/dev/tty1 res=success'\nJun 09 19:38:05 pitt-arch audit: CRED_DISP pid=19291 uid=0 auid=120 ses=3 msg='op=PAM:setcred grantors=pam_permit acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=pitt-arch addr=? terminal=/dev/tty1 res=success'\nJun 09 19:38:05 pitt-arch gdm: Gdm: Child process -19319 was already dead.\nJun 09 19:38:05 pitt-arch kernel: audit: type=1106 audit(1623263885.197:72): pid=19291 uid=0 auid=120 ses=3 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_succeed_if,pam_permit,pam_systemd,pam_env acct="gdm" exe="/usr/lib/gdm-session-worker" hostname=pitt-arch addr=? terminal=/dev/tty1 res=success'\nJun 09 19:40:21 pitt-arch systemd: man-db.service: Deactivated successfully.\nJun 09 19:40:21 pitt-arch audit: 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=success'\nJun 09 19:40:21 pitt-arch audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=man-db comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:40:21 pitt-arch systemd: Finished Daily man-db regeneration.\nJun 09 19:40:21 pitt-arch systemd: Startup finished in 15.213s (firmware) + 4.440s (loader) + 2.777s (kernel) + 2min 57.260s (userspace) = 3min 19.692s.\nJun 09 19:40:21 pitt-arch systemd: man-db.service: Consumed 3min 59.045s CPU time.\nJun 09 19:40:21 pitt-arch kernel: kauditd_printk_skb: 1 callbacks suppressed\nJun 09 19:40:21 pitt-arch kernel: audit: type=1130 audit(1623264021.103:74): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=man-db comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nJun 09 19:40:21 pitt-arch kernel: audit: type=1131 audit(1623264021.103:75): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=man-db comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'\nI can see a permission denied in there that I had not seen before, for virutal console 1\njust to explain I began this by loggin in as root and running\nLast edited by grimvoodoo (2021-06-09 19:03:14)\n#4 2021-06-09 19:40:49\nDoes "nvidia-smi" from the multi-user.target freeze the system as well?\nhttps://bbs.archlinux.org/viewtopic.php … 4#p1977104\n#5 2021-06-09 20:15:13\nYes, it locks up the same as running gdm\n#6 2021-06-09 20:16:44\nTry reverting to 460 as described in the thread linked in the linked thread.\n#7 2021-06-09 22:17:17\nYou are a hero Seth, I owe you a beer\nthis fixed it for me straight away\nI had the same problem, copy pasta to fix was:\nfor x in \_\ntest -f $x || \_\npacman -U *.zst\n#8 2021-06-09 22:19:29\nYou do not need to downgrade linux / linux-headers. Remove nvidia and let nvidia-dkms generate a module for the current kernel.