You are not logged in.

#1 2020-04-26 08:51:38

stefan
Member
Registered: 2013-03-22
Posts: 104

Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

Hi,

I've also been hit by the recent trouble with `dhcpcd`, see [1, 2].
The effects I've observed were:

  * The laptop would not boot when no LAN cable was attached.  It
    would just hang at a black screen in text mode, with a blinking
    cursor.  There was no way to escape this, except to shut down with
    the power button.

  * The laptop would boot occasionally, say one out of five times,
    with with a cable attached.  Then the system was barely usable.
    `xterm` failed to start with an error along the lines “not enough
    ptys”, `firefox` failed with “access denied” to shared memory, as
    did semaphore creation.  Luckily `pacman` was functional and
    allowed me to downgrade `dhcpcd`.

As said in [2], downgrading `dhcpcd` fixes this.  I'd rather consider
this temporary, not a solution.

What surprises me is that a failure in DHCP can render the entire
system unusable.  If I had not been lucky with the occasional boot
with a LAN cable as described above, I would have gone to
boot-from-pendrive or even reinstallation.

Instead, I would have expected the box to boot up kinda nicely, to a
login, with a broken network subsystem.

Frankly, I do not understand `systemd`'s dependency mechanics.  I
assume that it should provide means to describe different subsystems
that should be brought up during boot, but failure of one should not
affect the other ones.  Am I wrong with that assumption?

If such independence can be expressed, I'd assume a mistake in the
`systemd` config, which leads to the described dependency on `dhcpcd`.
If so, who would be the right one to address about this issue?

Cheers,
Stefan


[1] Failed to boot after system update
    https://bbs.archlinux.org/viewtopic.php?id=254980
[2] DHCPCD 9.0.1-2 upgrade breaks IP configuration
    https://bbs.archlinux.org/viewtopic.php?id=254857

Offline

#2 2020-04-26 09:28:37

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,665

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

A lot of things on linux rely on a stable "network" environment for communication with each other even if that "network" is just the local computer. If you have a networking daemon that borks configuration here things will start to fail (I don't use dhcpcd so I wasn't affected but from looking at the threads that popped it seems that it accidentally broke at least the hostname resolution from what is initially configured on boot, that will reliably lead to break xorg and other utilities. There really isn't much systemd can do here.

You also have to differentiate between "failed to boot" and "my graphical environment didn't come up" I do suspect had you booted with systemd.unit=multi-user.target you should've been able to reliably get a system up.

Last edited by V1del (2020-04-26 10:00:19)

Offline

#3 2020-04-26 09:40:17

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,846
Website

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

Rather than vague wonderings, please post some actual logs.

Mod note: not an installation issue, moving to NC for now.


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#4 2020-04-26 09:59:09

stefan
Member
Registered: 2013-03-22
Posts: 104

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

V1del wrote:

If you have a networking daemon that borks configuration here things will start to fail

I see your point.  If a component wreaks havoc then there's probably
noting one can do in general. 


WorMzy wrote:

Rather than vague wonderings, please post some actual logs.

If the system does not boot, that's difficult.

Now that I've got it booting, yes, what log would you like to have?

Offline

#5 2020-04-26 10:03:16

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,665

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

If you know the time (or the logical boot number - like "my last (or second to last and so fort) boot failed") you can check relevant journal entries based on time frame or when that boot was.

https://wiki.archlinux.org/index.php/Sy … ing_output

Offline

#6 2020-04-26 10:29:00

Zod
Member
From: Hoosiertucky
Registered: 2019-03-10
Posts: 629

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

stefan wrote:

As said in [2], downgrading `dhcpcd` fixes this.  I'd rather consider
this temporary, not a solution.

It wasn't a solution.

I don't understand what the problem is, downgrading was a simple, fast way to get back into operation.

Upstream had it fixed, as far as I was concerned, early the next day.

I kinda thought, and that's how I operate Archlinux, that due to the nature of rolling release this sorta thing is to be expected from time to time.

Last edited by Zod (2020-04-26 10:43:26)

Offline

#7 2020-04-26 10:31:28

stefan
Member
Registered: 2013-03-22
Posts: 104

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

-- Logs begin at Sun 2019-12-01 11:10:48 CET, end at Sun 2020-04-26 12:35:12 CEST. --
Apr 26 12:10:08 verne kernel: Linux version 5.6.6-arch1-1 (linux@archlinux) (gcc version 9.3.0 (Arch Linux 9.3.0-1)) #1 SMP PREEMPT Tue, 21 Apr 2020 10:35:16 +0000
Apr 26 12:10:08 verne kernel: Command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/mapper/root cryptdevice=/dev/disk/by-uuid/b914c624-d81a-4081-9f1a-c3e4282ec8e5:root cryptkey=/dev/disk/by-label/key:ext2:verne rw initrd=../initramfs-linux.img
Apr 26 12:10:08 verne kernel: KERNEL supported cpus:
Apr 26 12:10:08 verne kernel:   Intel GenuineIntel
Apr 26 12:10:08 verne kernel:   AMD AuthenticAMD
Apr 26 12:10:08 verne kernel:   Hygon HygonGenuine
Apr 26 12:10:08 verne kernel:   Centaur CentaurHauls
Apr 26 12:10:08 verne kernel:   zhaoxin   Shanghai  
Apr 26 12:10:08 verne kernel: Disabled fast string operations
Apr 26 12:10:08 verne kernel: x86/fpu: x87 FPU will use FXSAVE
Apr 26 12:10:08 verne kernel: BIOS-provided physical RAM map:
Apr 26 12:10:08 verne kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
Apr 26 12:10:08 verne kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
Apr 26 12:10:08 verne kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Apr 26 12:10:08 verne kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003f493fff] usable
Apr 26 12:10:08 verne kernel: BIOS-e820: [mem 0x000000003f494000-0x000000003f4befff] reserved
Apr 26 12:10:08 verne kernel: BIOS-e820: [mem 0x000000003f4bf000-0x000000003f576fff] usable
Apr 26 12:10:08 verne kernel: BIOS-e820: [mem 0x000000003f577000-0x000000003f5befff] ACPI NVS
Apr 26 12:10:08 verne kernel: BIOS-e820: [mem 0x000000003f5bf000-0x000000003f5eafff] usable
Apr 26 12:10:08 verne kernel: BIOS-e820: [mem 0x000000003f5eb000-0x000000003f5fefff] ACPI data
Apr 26 12:10:08 verne kernel: BIOS-e820: [mem 0x000000003f5ff000-0x000000003f5fffff] usable
Apr 26 12:10:08 verne kernel: BIOS-e820: [mem 0x000000003f600000-0x000000003fffffff] reserved
Apr 26 12:10:08 verne kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Apr 26 12:10:08 verne kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Apr 26 12:10:08 verne kernel: BIOS-e820: [mem 0x00000000fed14000-0x00000000fed19fff] reserved
Apr 26 12:10:08 verne kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Apr 26 12:10:08 verne kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Apr 26 12:10:08 verne kernel: BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved
Apr 26 12:10:08 verne kernel: NX (Execute Disable) protection: active
Apr 26 12:10:08 verne kernel: SMBIOS 2.6 present.
Apr 26 12:10:08 verne kernel: DMI: eMachines eM355/HM02_PT, BIOS V3.16(DDR3) 04/22/2011
Apr 26 12:10:08 verne kernel: tsc: Fast TSC calibration using PIT
Apr 26 12:10:08 verne kernel: tsc: Detected 1662.397 MHz processor
Apr 26 12:10:08 verne kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Apr 26 12:10:08 verne kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Apr 26 12:10:08 verne kernel: last_pfn = 0x3f600 max_arch_pfn = 0x400000000
Apr 26 12:10:08 verne kernel: MTRR default type: uncachable
Apr 26 12:10:08 verne kernel: MTRR fixed ranges enabled:
Apr 26 12:10:08 verne kernel:   00000-9FFFF write-back
Apr 26 12:10:08 verne kernel:   A0000-BFFFF uncachable
Apr 26 12:10:08 verne kernel:   C0000-DFFFF write-through
Apr 26 12:10:08 verne kernel:   E0000-FFFFF write-protect
Apr 26 12:10:08 verne kernel: MTRR variable ranges enabled:
Apr 26 12:10:08 verne kernel:   0 base 0FFE00000 mask FFFE00000 write-protect
Apr 26 12:10:08 verne kernel:   1 base 000000000 mask FE0000000 write-back
Apr 26 12:10:08 verne kernel:   2 base 020000000 mask FE0000000 write-back
Apr 26 12:10:08 verne kernel:   3 base 03F800000 mask FFF800000 uncachable
Apr 26 12:10:08 verne kernel:   4 disabled
Apr 26 12:10:08 verne kernel:   5 disabled
Apr 26 12:10:08 verne kernel:   6 disabled
Apr 26 12:10:08 verne kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
Apr 26 12:10:08 verne kernel: check: Scanning 1 areas for low memory corruption
Apr 26 12:10:08 verne kernel: BRK [0x29c01000, 0x29c01fff] PGTABLE
Apr 26 12:10:08 verne kernel: BRK [0x29c02000, 0x29c02fff] PGTABLE
Apr 26 12:10:08 verne kernel: BRK [0x29c03000, 0x29c03fff] PGTABLE
Apr 26 12:10:08 verne kernel: BRK [0x29c04000, 0x29c04fff] PGTABLE
Apr 26 12:10:08 verne kernel: BRK [0x29c05000, 0x29c05fff] PGTABLE
Apr 26 12:10:08 verne kernel: RAMDISK: [mem 0x3e93e000-0x3f493fff]
Apr 26 12:10:08 verne kernel: ACPI: Early table checksum verification disabled
Apr 26 12:10:08 verne kernel: ACPI: RSDP 0x00000000000FE020 000024 (v02 ACRSYS)
Apr 26 12:10:08 verne kernel: ACPI: XSDT 0x000000003F5FE120 000064 (v01 ACRSYS ACRPRDCT 00000001      01000013)
Apr 26 12:10:08 verne kernel: ACPI: FACP 0x000000003F5FD000 0000F4 (v04 ACRSYS ACRPRDCT 00000001 1025 01000013)
Apr 26 12:10:08 verne kernel: ACPI: DSDT 0x000000003F5F0000 0096B6 (v01 ACRSYS ACRPRDCT 00000001 1025 01000013)
Apr 26 12:10:08 verne kernel: ACPI: FACS 0x000000003F584000 000040
Apr 26 12:10:08 verne kernel: ACPI: FACS 0x000000003F584000 000040
Apr 26 12:10:08 verne kernel: ACPI: HPET 0x000000003F5FC000 000038 (v01 ACRSYS ACRPRDCT 00000001 1025 01000013)
Apr 26 12:10:08 verne kernel: ACPI: APIC 0x000000003F5FB000 000078 (v02 ACRSYS ACRPRDCT 00000001 1025 01000013)
Apr 26 12:10:08 verne kernel: ACPI: MCFG 0x000000003F5FA000 00003C (v01 ACRSYS ACRPRDCT 00000001 1025 01000013)
Apr 26 12:10:08 verne kernel: ACPI: SLIC 0x000000003F5EF000 000176 (v01 ACRSYS ACRPRDCT 00000001 1025 01000013)
Apr 26 12:10:08 verne kernel: ACPI: BOOT 0x000000003F5EE000 000028 (v01 ACRSYS ACRPRDCT 00000001 1025 01000013)
Apr 26 12:10:08 verne kernel: ACPI: SSDT 0x000000003F5EC000 000655 (v01 PmRef  CpuPm    00003000 INTL 20051117)
Apr 26 12:10:08 verne kernel: ACPI: WDAT 0x000000003F5EB000 000194 (v01 INSYDE INSYDE   00000001 MSFT 01000013)
Apr 26 12:10:08 verne kernel: ACPI: Local APIC address 0xfee00000
Apr 26 12:10:08 verne kernel: No NUMA configuration found
Apr 26 12:10:08 verne kernel: Faking a node at [mem 0x0000000000000000-0x000000003f5fffff]
Apr 26 12:10:08 verne kernel: NODE_DATA(0) allocated [mem 0x3f5e7000-0x3f5eafff]
Apr 26 12:10:08 verne kernel: Zone ranges:
Apr 26 12:10:08 verne kernel:   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Apr 26 12:10:08 verne kernel:   DMA32    [mem 0x0000000001000000-0x000000003f5fffff]
Apr 26 12:10:08 verne kernel:   Normal   empty
Apr 26 12:10:08 verne kernel:   Device   empty
Apr 26 12:10:08 verne kernel: Movable zone start for each node
Apr 26 12:10:08 verne kernel: Early memory node ranges
Apr 26 12:10:08 verne kernel:   node   0: [mem 0x0000000000001000-0x000000000009efff]
Apr 26 12:10:08 verne kernel:   node   0: [mem 0x0000000000100000-0x000000003f493fff]
Apr 26 12:10:08 verne kernel:   node   0: [mem 0x000000003f4bf000-0x000000003f576fff]
Apr 26 12:10:08 verne kernel:   node   0: [mem 0x000000003f5bf000-0x000000003f5eafff]
Apr 26 12:10:08 verne kernel:   node   0: [mem 0x000000003f5ff000-0x000000003f5fffff]
Apr 26 12:10:08 verne kernel: Zeroed struct page in unavailable ranges: 2793 pages
Apr 26 12:10:08 verne kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000003f5fffff]
Apr 26 12:10:08 verne kernel: On node 0 totalpages: 259351
Apr 26 12:10:08 verne kernel:   DMA zone: 64 pages used for memmap
Apr 26 12:10:08 verne kernel:   DMA zone: 21 pages reserved
Apr 26 12:10:08 verne kernel:   DMA zone: 3998 pages, LIFO batch:0
Apr 26 12:10:08 verne kernel:   DMA32 zone: 3992 pages used for memmap
Apr 26 12:10:08 verne kernel:   DMA32 zone: 255353 pages, LIFO batch:63
Apr 26 12:10:08 verne kernel: Reserving Intel graphics memory at [mem 0x3f800000-0x3fffffff]
Apr 26 12:10:08 verne kernel: ACPI: PM-Timer IO Port: 0x408
Apr 26 12:10:08 verne kernel: ACPI: Local APIC address 0xfee00000
Apr 26 12:10:08 verne kernel: ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
Apr 26 12:10:08 verne kernel: ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
Apr 26 12:10:08 verne kernel: IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23
Apr 26 12:10:08 verne kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Apr 26 12:10:08 verne kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Apr 26 12:10:08 verne kernel: ACPI: IRQ0 used by override.
Apr 26 12:10:08 verne kernel: ACPI: IRQ9 used by override.
Apr 26 12:10:08 verne kernel: Using ACPI (MADT) for SMP configuration information
Apr 26 12:10:08 verne kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
Apr 26 12:10:08 verne kernel: smpboot: Allowing 4 CPUs, 0 hotplug CPUs
Apr 26 12:10:08 verne kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
Apr 26 12:10:08 verne kernel: PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Apr 26 12:10:08 verne kernel: PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Apr 26 12:10:08 verne kernel: PM: hibernation: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Apr 26 12:10:08 verne kernel: PM: hibernation: Registered nosave memory: [mem 0x3f494000-0x3f4befff]
Apr 26 12:10:08 verne kernel: PM: hibernation: Registered nosave memory: [mem 0x3f577000-0x3f5befff]
Apr 26 12:10:08 verne kernel: PM: hibernation: Registered nosave memory: [mem 0x3f5eb000-0x3f5fefff]
Apr 26 12:10:08 verne kernel: [mem 0x40000000-0xdfffffff] available for PCI devices
Apr 26 12:10:08 verne kernel: Booting paravirtualized kernel on bare hardware
Apr 26 12:10:08 verne kernel: clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370452778343963 ns
Apr 26 12:10:08 verne kernel: setup_percpu: NR_CPUS:320 nr_cpumask_bits:320 nr_cpu_ids:4 nr_node_ids:1
Apr 26 12:10:08 verne kernel: percpu: Embedded 57 pages/cpu s196608 r8192 d28672 u524288
Apr 26 12:10:08 verne kernel: pcpu-alloc: s196608 r8192 d28672 u524288 alloc=1*2097152
Apr 26 12:10:08 verne kernel: pcpu-alloc: [0] 0 1 2 3 
Apr 26 12:10:08 verne kernel: Built 1 zonelists, mobility grouping on.  Total pages: 255274
Apr 26 12:10:08 verne kernel: Policy zone: DMA32
Apr 26 12:10:08 verne kernel: Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/mapper/root cryptdevice=/dev/disk/by-uuid/b914c624-d81a-4081-9f1a-c3e4282ec8e5:root cryptkey=/dev/disk/by-label/key:ext2:verne rw initrd=../initramfs-linux.img
Apr 26 12:10:08 verne kernel: Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
Apr 26 12:10:08 verne kernel: Inode-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
Apr 26 12:10:08 verne kernel: mem auto-init: stack:byref_all, heap alloc:on, heap free:off
Apr 26 12:10:08 verne kernel: Memory: 976040K/1037404K available (12291K kernel code, 1463K rwdata, 4504K rodata, 1620K init, 3220K bss, 61364K reserved, 0K cma-reserved)
Apr 26 12:10:08 verne kernel: random: get_random_u64 called from __kmem_cache_create+0x3e/0x520 with crng_init=0
Apr 26 12:10:08 verne kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Apr 26 12:10:08 verne kernel: ftrace: allocating 40154 entries in 157 pages
Apr 26 12:10:08 verne kernel: ftrace: allocated 157 pages with 5 groups
Apr 26 12:10:08 verne kernel: rcu: Preemptible hierarchical RCU implementation.
Apr 26 12:10:08 verne kernel: rcu:         RCU dyntick-idle grace-period acceleration is enabled.
Apr 26 12:10:08 verne kernel: rcu:         RCU restricting CPUs from NR_CPUS=320 to nr_cpu_ids=4.
Apr 26 12:10:08 verne kernel: rcu:         RCU priority boosting: priority 1 delay 500 ms.
Apr 26 12:10:08 verne kernel:         Tasks RCU enabled.
Apr 26 12:10:08 verne kernel: rcu: RCU calculated value of scheduler-enlistment delay is 30 jiffies.
Apr 26 12:10:08 verne kernel: rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
Apr 26 12:10:08 verne kernel: NR_IRQS: 20736, nr_irqs: 456, preallocated irqs: 16
Apr 26 12:10:08 verne kernel: Console: colour VGA+ 80x25
Apr 26 12:10:08 verne kernel: printk: console [tty0] enabled
Apr 26 12:10:08 verne kernel: ACPI: Core revision 20200110
Apr 26 12:10:08 verne kernel: clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns
Apr 26 12:10:08 verne kernel: APIC: Switch to symmetric I/O mode setup
Apr 26 12:10:08 verne kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Apr 26 12:10:08 verne kernel: clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x17f66509abc, max_idle_ns: 440795223347 ns
Apr 26 12:10:08 verne kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 3326.32 BogoMIPS (lpj=5541323)
Apr 26 12:10:08 verne kernel: pid_max: default: 32768 minimum: 301
Apr 26 12:10:08 verne kernel: LSM: Security Framework initializing
Apr 26 12:10:08 verne kernel: Yama: becoming mindful.
Apr 26 12:10:08 verne kernel: Mount-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
Apr 26 12:10:08 verne kernel: Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
Apr 26 12:10:08 verne kernel: *** VALIDATE tmpfs ***
Apr 26 12:10:08 verne kernel: *** VALIDATE proc ***
Apr 26 12:10:08 verne kernel: *** VALIDATE cgroup ***
Apr 26 12:10:08 verne kernel: *** VALIDATE cgroup2 ***
Apr 26 12:10:08 verne kernel: Disabled fast string operations
Apr 26 12:10:08 verne kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
Apr 26 12:10:08 verne kernel: mce: CPU0: Thermal monitoring enabled (TM2)
Apr 26 12:10:08 verne kernel: process: using mwait in idle threads
Apr 26 12:10:08 verne kernel: Last level iTLB entries: 4KB 32, 2MB 0, 4MB 0
Apr 26 12:10:08 verne kernel: Last level dTLB entries: 4KB 64, 2MB 0, 4MB 8, 1GB 0
Apr 26 12:10:08 verne kernel: Freeing SMP alternatives memory: 32K
Apr 26 12:10:08 verne kernel: smpboot: CPU0: Intel(R) Atom(TM) CPU N570   @ 1.66GHz (family: 0x6, model: 0x1c, stepping: 0xa)
Apr 26 12:10:08 verne kernel: Performance Events: PEBS fmt0+, Atom events, 8-deep LBR, Intel PMU driver.
Apr 26 12:10:08 verne kernel: ... version:                3
Apr 26 12:10:08 verne kernel: ... bit width:              40
Apr 26 12:10:08 verne kernel: ... generic registers:      2
Apr 26 12:10:08 verne kernel: ... value mask:             000000ffffffffff
Apr 26 12:10:08 verne kernel: ... max period:             000000007fffffff
Apr 26 12:10:08 verne kernel: ... fixed-purpose events:   3
Apr 26 12:10:08 verne kernel: ... event mask:             0000000700000003
Apr 26 12:10:08 verne kernel: rcu: Hierarchical SRCU implementation.
Apr 26 12:10:08 verne kernel: NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
Apr 26 12:10:08 verne kernel: smp: Bringing up secondary CPUs ...
Apr 26 12:10:08 verne kernel: x86: Booting SMP configuration:
Apr 26 12:10:08 verne kernel: .... node  #0, CPUs:      #1
Apr 26 12:10:08 verne kernel: Disabled fast string operations
Apr 26 12:10:08 verne kernel:  #2
Apr 26 12:10:08 verne kernel: Disabled fast string operations
Apr 26 12:10:08 verne kernel: TSC synchronization [CPU#0 -> CPU#2]:
Apr 26 12:10:08 verne kernel: Measured 160 cycles TSC warp between CPUs, turning off TSC clock.
Apr 26 12:10:08 verne kernel: tsc: Marking TSC unstable due to check_tsc_sync_source failed
Apr 26 12:10:08 verne kernel:  #3
Apr 26 12:10:08 verne kernel: Disabled fast string operations
Apr 26 12:10:08 verne kernel: smp: Brought up 1 node, 4 CPUs
Apr 26 12:10:08 verne kernel: smpboot: Max logical packages: 1
Apr 26 12:10:08 verne kernel: smpboot: Total of 4 processors activated (13304.30 BogoMIPS)
Apr 26 12:10:08 verne kernel: devtmpfs: initialized
Apr 26 12:10:08 verne kernel: x86/mm: Memory block size: 128MB
Apr 26 12:10:08 verne kernel: PM: Registering ACPI NVS region [mem 0x3f577000-0x3f5befff] (294912 bytes)
Apr 26 12:10:08 verne kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370867519511994 ns
Apr 26 12:10:08 verne kernel: futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
Apr 26 12:10:08 verne kernel: pinctrl core: initialized pinctrl subsystem
Apr 26 12:10:08 verne kernel: PM: RTC time: 10:09:48, date: 2020-04-26
Apr 26 12:10:08 verne kernel: thermal_sys: Registered thermal governor 'fair_share'
Apr 26 12:10:08 verne kernel: thermal_sys: Registered thermal governor 'bang_bang'
Apr 26 12:10:08 verne kernel: thermal_sys: Registered thermal governor 'step_wise'
Apr 26 12:10:08 verne kernel: thermal_sys: Registered thermal governor 'user_space'
Apr 26 12:10:08 verne kernel: thermal_sys: Registered thermal governor 'power_allocator'
Apr 26 12:10:08 verne kernel: NET: Registered protocol family 16
Apr 26 12:10:08 verne kernel: audit: initializing netlink subsys (disabled)
Apr 26 12:10:08 verne kernel: audit: type=2000 audit(1587895788.309:1): state=initialized audit_enabled=0 res=1
Apr 26 12:10:08 verne kernel: cpuidle: using governor ladder
Apr 26 12:10:08 verne kernel: cpuidle: using governor menu
Apr 26 12:10:08 verne kernel: Simple Boot Flag at 0x44 set to 0x1
Apr 26 12:10:08 verne kernel: ACPI: bus type PCI registered
Apr 26 12:10:08 verne kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Apr 26 12:10:08 verne kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
Apr 26 12:10:08 verne kernel: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
Apr 26 12:10:08 verne kernel: PCI: Using configuration type 1 for base access
Apr 26 12:10:08 verne kernel: HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
Apr 26 12:10:08 verne kernel: ACPI: Added _OSI(Module Device)
Apr 26 12:10:08 verne kernel: ACPI: Added _OSI(Processor Device)
Apr 26 12:10:08 verne kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Apr 26 12:10:08 verne kernel: ACPI: Added _OSI(Processor Aggregator Device)
Apr 26 12:10:08 verne kernel: ACPI: Added _OSI(Linux-Dell-Video)
Apr 26 12:10:08 verne kernel: ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
Apr 26 12:10:08 verne kernel: ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
Apr 26 12:10:08 verne kernel: ACPI: 2 ACPI AML tables successfully acquired and loaded
Apr 26 12:10:08 verne kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
Apr 26 12:10:08 verne kernel: ACPI: Dynamic OEM Table Load:
Apr 26 12:10:08 verne kernel: ACPI: SSDT 0xFFFF956DFC9C2000 000708 (v01 PmRef  Cpu0Ist  00003000 INTL 20051117)
Apr 26 12:10:08 verne kernel: ACPI: Dynamic OEM Table Load:
Apr 26 12:10:08 verne kernel: ACPI: SSDT 0xFFFF956DFC9C0800 000646 (v01 PmRef  Cpu0Cst  00003001 INTL 20051117)
Apr 26 12:10:08 verne kernel: ACPI: Dynamic OEM Table Load:
Apr 26 12:10:08 verne kernel: ACPI: SSDT 0xFFFF956DFCA77A00 00015F (v01 PmRef  ApIst    00003000 INTL 20051117)
Apr 26 12:10:08 verne kernel: ACPI: Dynamic OEM Table Load:
Apr 26 12:10:08 verne kernel: ACPI: SSDT 0xFFFF956DFD381240 00008D (v01 PmRef  ApCst    00003000 INTL 20051117)
Apr 26 12:10:08 verne kernel: ACPI: EC: EC started
Apr 26 12:10:08 verne kernel: ACPI: EC: interrupt blocked
Apr 26 12:10:08 verne kernel: ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
Apr 26 12:10:08 verne kernel: ACPI: \_SB_.PCI0.LPC_.EC0_: Boot DSDT EC used to handle transactions
Apr 26 12:10:08 verne kernel: ACPI: Interpreter enabled
Apr 26 12:10:08 verne kernel: ACPI: (supports S0 S3 S4 S5)
Apr 26 12:10:08 verne kernel: ACPI: Using IOAPIC for interrupt routing
Apr 26 12:10:08 verne kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Apr 26 12:10:08 verne kernel: ACPI: Enabled 12 GPEs in block 00 to 1F
Apr 26 12:10:08 verne kernel: ACPI: Power Resource [FN00] (on)
Apr 26 12:10:08 verne kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
Apr 26 12:10:08 verne kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
Apr 26 12:10:08 verne kernel: acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug SHPCHotplug]
Apr 26 12:10:08 verne kernel: acpi PNP0A08:00: _OSC: OS now controls [PME AER PCIeCapability LTR]
Apr 26 12:10:08 verne kernel: PCI host bridge to bus 0000:00
Apr 26 12:10:08 verne kernel: pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
Apr 26 12:10:08 verne kernel: pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
Apr 26 12:10:08 verne kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
Apr 26 12:10:08 verne kernel: pci_bus 0000:00: root bus resource [mem 0x40000000-0xfebfffff window]
Apr 26 12:10:08 verne kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
Apr 26 12:10:08 verne kernel: pci 0000:00:00.0: [8086:a010] type 00 class 0x060000
Apr 26 12:10:08 verne kernel: pci 0000:00:02.0: [8086:a011] type 00 class 0x030000
Apr 26 12:10:08 verne kernel: pci 0000:00:02.0: reg 0x10: [mem 0x58180000-0x581fffff]
Apr 26 12:10:08 verne kernel: pci 0000:00:02.0: reg 0x14: [io  0x60c0-0x60c7]
Apr 26 12:10:08 verne kernel: pci 0000:00:02.0: reg 0x18: [mem 0x40000000-0x4fffffff pref]
Apr 26 12:10:08 verne kernel: pci 0000:00:02.0: reg 0x1c: [mem 0x58000000-0x580fffff]
Apr 26 12:10:08 verne kernel: pci 0000:00:02.1: [8086:a012] type 00 class 0x038000
Apr 26 12:10:08 verne kernel: pci 0000:00:02.1: reg 0x10: [mem 0x58100000-0x5817ffff]
Apr 26 12:10:08 verne kernel: pci 0000:00:1b.0: [8086:27d8] type 00 class 0x040300
Apr 26 12:10:08 verne kernel: pci 0000:00:1b.0: reg 0x10: [mem 0x58200000-0x58203fff 64bit]
Apr 26 12:10:08 verne kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
Apr 26 12:10:08 verne kernel: pci 0000:00:1c.0: [8086:27d0] type 01 class 0x060400
Apr 26 12:10:08 verne kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Apr 26 12:10:08 verne kernel: pci 0000:00:1c.1: [8086:27d2] type 01 class 0x060400
Apr 26 12:10:08 verne kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
Apr 26 12:10:08 verne kernel: pci 0000:00:1d.0: [8086:27c8] type 00 class 0x0c0300
Apr 26 12:10:08 verne kernel: pci 0000:00:1d.0: reg 0x20: [io  0x6080-0x609f]
Apr 26 12:10:08 verne kernel: pci 0000:00:1d.1: [8086:27c9] type 00 class 0x0c0300
Apr 26 12:10:08 verne kernel: pci 0000:00:1d.1: reg 0x20: [io  0x6060-0x607f]
Apr 26 12:10:08 verne kernel: pci 0000:00:1d.2: [8086:27ca] type 00 class 0x0c0300
Apr 26 12:10:08 verne kernel: pci 0000:00:1d.2: reg 0x20: [io  0x6040-0x605f]
Apr 26 12:10:08 verne kernel: pci 0000:00:1d.3: [8086:27cb] type 00 class 0x0c0300
Apr 26 12:10:08 verne kernel: pci 0000:00:1d.3: reg 0x20: [io  0x6020-0x603f]
Apr 26 12:10:08 verne kernel: pci 0000:00:1d.7: [8086:27cc] type 00 class 0x0c0320
Apr 26 12:10:08 verne kernel: pci 0000:00:1d.7: reg 0x10: [mem 0x58204400-0x582047ff]
Apr 26 12:10:08 verne kernel: pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
Apr 26 12:10:08 verne kernel: pci 0000:00:1e.0: [8086:2448] type 01 class 0x060401
Apr 26 12:10:08 verne kernel: pci 0000:00:1f.0: [8086:27bc] type 00 class 0x060100
Apr 26 12:10:08 verne kernel: pci 0000:00:1f.2: [8086:27c1] type 00 class 0x010601
Apr 26 12:10:08 verne kernel: pci 0000:00:1f.2: reg 0x10: [io  0x60b8-0x60bf]
Apr 26 12:10:08 verne kernel: pci 0000:00:1f.2: reg 0x14: [io  0x60cc-0x60cf]
Apr 26 12:10:08 verne kernel: pci 0000:00:1f.2: reg 0x18: [io  0x60b0-0x60b7]
Apr 26 12:10:08 verne kernel: pci 0000:00:1f.2: reg 0x1c: [io  0x60c8-0x60cb]
Apr 26 12:10:08 verne kernel: pci 0000:00:1f.2: reg 0x20: [io  0x60a0-0x60af]
Apr 26 12:10:08 verne kernel: pci 0000:00:1f.2: reg 0x24: [mem 0x58204000-0x582043ff]
Apr 26 12:10:08 verne kernel: pci 0000:00:1f.2: PME# supported from D3hot
Apr 26 12:10:08 verne kernel: pci 0000:00:1f.3: [8086:27da] type 00 class 0x0c0500
Apr 26 12:10:08 verne kernel: pci 0000:00:1f.3: reg 0x20: [io  0x6000-0x601f]
Apr 26 12:10:08 verne kernel: pci 0000:01:00.0: [1969:2062] type 00 class 0x020000
Apr 26 12:10:08 verne kernel: pci 0000:01:00.0: reg 0x10: [mem 0x57000000-0x5703ffff 64bit]
Apr 26 12:10:08 verne kernel: pci 0000:01:00.0: reg 0x18: [io  0x5000-0x507f]
Apr 26 12:10:08 verne kernel: pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
Apr 26 12:10:08 verne kernel: pci 0000:00:1c.0: PCI bridge to [bus 01]
Apr 26 12:10:08 verne kernel: pci 0000:00:1c.0:   bridge window [io  0x5000-0x5fff]
Apr 26 12:10:08 verne kernel: pci 0000:00:1c.0:   bridge window [mem 0x57000000-0x57ffffff]
Apr 26 12:10:08 verne kernel: pci 0000:00:1c.0:   bridge window [mem 0x50000000-0x50ffffff 64bit pref]
Apr 26 12:10:08 verne kernel: pci 0000:02:00.0: [168c:002b] type 00 class 0x028000
Apr 26 12:10:08 verne kernel: pci 0000:02:00.0: reg 0x10: [mem 0x56000000-0x5600ffff 64bit]
Apr 26 12:10:08 verne kernel: pci 0000:02:00.0: supports D1
Apr 26 12:10:08 verne kernel: pci 0000:02:00.0: PME# supported from D0 D1 D3hot
Apr 26 12:10:08 verne kernel: pci 0000:00:1c.1: PCI bridge to [bus 02]
Apr 26 12:10:08 verne kernel: pci 0000:00:1c.1:   bridge window [io  0x4000-0x4fff]
Apr 26 12:10:08 verne kernel: pci 0000:00:1c.1:   bridge window [mem 0x56000000-0x56ffffff]
Apr 26 12:10:08 verne kernel: pci 0000:00:1c.1:   bridge window [mem 0x51000000-0x51ffffff 64bit pref]
Apr 26 12:10:08 verne kernel: pci_bus 0000:05: extended config space not accessible
Apr 26 12:10:08 verne kernel: pci 0000:00:1e.0: PCI bridge to [bus 05] (subtractive decode)
Apr 26 12:10:08 verne kernel: pci 0000:00:1e.0:   bridge window [io  0x0000-0x0cf7 window] (subtractive decode)
Apr 26 12:10:08 verne kernel: pci 0000:00:1e.0:   bridge window [io  0x0d00-0xffff window] (subtractive decode)
Apr 26 12:10:08 verne kernel: pci 0000:00:1e.0:   bridge window [mem 0x000a0000-0x000bffff window] (subtractive decode)
Apr 26 12:10:08 verne kernel: pci 0000:00:1e.0:   bridge window [mem 0x40000000-0xfebfffff window] (subtractive decode)
Apr 26 12:10:08 verne kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 *11 12)
Apr 26 12:10:08 verne kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 *10 11 12)
Apr 26 12:10:08 verne kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 10 *11 12)
Apr 26 12:10:08 verne kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 *11 12)
Apr 26 12:10:08 verne kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
Apr 26 12:10:08 verne kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
Apr 26 12:10:08 verne kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
Apr 26 12:10:08 verne kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
Apr 26 12:10:08 verne kernel: ACPI: EC: interrupt unblocked
Apr 26 12:10:08 verne kernel: ACPI: EC: event unblocked
Apr 26 12:10:08 verne kernel: ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
Apr 26 12:10:08 verne kernel: ACPI: EC: GPE=0x19
Apr 26 12:10:08 verne kernel: ACPI: \_SB_.PCI0.LPC_.EC0_: Boot DSDT EC used to handle transactions and events
Apr 26 12:10:08 verne kernel: iommu: Default domain type: Translated 
Apr 26 12:10:08 verne kernel: pci 0000:00:02.0: vgaarb: setting as boot VGA device
Apr 26 12:10:08 verne kernel: pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
Apr 26 12:10:08 verne kernel: pci 0000:00:02.0: vgaarb: bridge control possible
Apr 26 12:10:08 verne kernel: vgaarb: loaded
Apr 26 12:10:08 verne kernel: SCSI subsystem initialized
Apr 26 12:10:08 verne kernel: libata version 3.00 loaded.
Apr 26 12:10:08 verne kernel: ACPI: bus type USB registered
Apr 26 12:10:08 verne kernel: usbcore: registered new interface driver usbfs
Apr 26 12:10:08 verne kernel: usbcore: registered new interface driver hub
Apr 26 12:10:08 verne kernel: usbcore: registered new device driver usb
Apr 26 12:10:08 verne kernel: pps_core: LinuxPPS API ver. 1 registered
Apr 26 12:10:08 verne kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Apr 26 12:10:08 verne kernel: PTP clock support registered
Apr 26 12:10:08 verne kernel: EDAC MC: Ver: 3.0.0
Apr 26 12:10:08 verne kernel: PCI: Using ACPI for IRQ routing
Apr 26 12:10:08 verne kernel: PCI: pci_cache_line_size set to 64 bytes
Apr 26 12:10:08 verne kernel: e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
Apr 26 12:10:08 verne kernel: e820: reserve RAM buffer [mem 0x3f494000-0x3fffffff]
Apr 26 12:10:08 verne kernel: e820: reserve RAM buffer [mem 0x3f577000-0x3fffffff]
Apr 26 12:10:08 verne kernel: e820: reserve RAM buffer [mem 0x3f5eb000-0x3fffffff]
Apr 26 12:10:08 verne kernel: e820: reserve RAM buffer [mem 0x3f600000-0x3fffffff]
Apr 26 12:10:08 verne kernel: NetLabel: Initializing
Apr 26 12:10:08 verne kernel: NetLabel:  domain hash size = 128
Apr 26 12:10:08 verne kernel: NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
Apr 26 12:10:08 verne kernel: NetLabel:  unlabeled traffic allowed by default
Apr 26 12:10:08 verne kernel: hpet: 3 channels of 0 reserved for per-cpu timers
Apr 26 12:10:08 verne kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
Apr 26 12:10:08 verne kernel: hpet0: 3 comparators, 64-bit 14.318180 MHz counter
Apr 26 12:10:08 verne kernel: clocksource: Switched to clocksource hpet
Apr 26 12:10:08 verne kernel: *** VALIDATE bpf ***
Apr 26 12:10:08 verne kernel: VFS: Disk quotas dquot_6.6.0
Apr 26 12:10:08 verne kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Apr 26 12:10:08 verne kernel: *** VALIDATE ramfs ***
Apr 26 12:10:08 verne kernel: *** VALIDATE hugetlbfs ***
Apr 26 12:10:08 verne kernel: pnp: PnP ACPI init
Apr 26 12:10:08 verne kernel: system 00:00: [io  0x164e-0x164f] has been reserved
Apr 26 12:10:08 verne kernel: system 00:00: [io  0x0600-0x060f] has been reserved
Apr 26 12:10:08 verne kernel: system 00:00: [io  0x0610] has been reserved
Apr 26 12:10:08 verne kernel: system 00:00: [io  0x0800-0x080f] has been reserved
Apr 26 12:10:08 verne kernel: system 00:00: [io  0x0810-0x0817] has been reserved
Apr 26 12:10:08 verne kernel: system 00:00: [io  0x0400-0x047f] has been reserved
Apr 26 12:10:08 verne kernel: system 00:00: [io  0x0500-0x053f] has been reserved
Apr 26 12:10:08 verne kernel: system 00:00: [io  0xff2c-0xff2f] has been reserved
Apr 26 12:10:08 verne kernel: system 00:00: [mem 0xe0000000-0xefffffff] has been reserved
Apr 26 12:10:08 verne kernel: system 00:00: [mem 0xfed1c000-0xfed1ffff] has been reserved
Apr 26 12:10:08 verne kernel: system 00:00: [mem 0xfed14000-0xfed17fff] has been reserved
Apr 26 12:10:08 verne kernel: system 00:00: [mem 0xfed18000-0xfed18fff] has been reserved
Apr 26 12:10:08 verne kernel: system 00:00: [mem 0xfed19000-0xfed19fff] has been reserved
Apr 26 12:10:08 verne kernel: system 00:00: [mem 0xfec00000-0xfec00fff] could not be reserved
Apr 26 12:10:08 verne kernel: system 00:00: [mem 0xfee00000-0xfee00fff] has been reserved
Apr 26 12:10:08 verne kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
Apr 26 12:10:08 verne kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
Apr 26 12:10:09 verne kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0303 (active)
Apr 26 12:10:09 verne kernel: pnp 00:03: Plug and Play ACPI device, IDs SYN1b1c SYN1b00 SYN0002 PNP0f13 (active)
Apr 26 12:10:09 verne kernel: pnp: PnP ACPI: found 4 devices
Apr 26 12:10:09 verne kernel: clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Apr 26 12:10:09 verne kernel: pci 0000:00:1c.0: PCI bridge to [bus 01]
Apr 26 12:10:09 verne kernel: pci 0000:00:1c.0:   bridge window [io  0x5000-0x5fff]
Apr 26 12:10:09 verne kernel: pci 0000:00:1c.0:   bridge window [mem 0x57000000-0x57ffffff]
Apr 26 12:10:09 verne kernel: pci 0000:00:1c.0:   bridge window [mem 0x50000000-0x50ffffff 64bit pref]
Apr 26 12:10:09 verne kernel: pci 0000:00:1c.1: PCI bridge to [bus 02]
Apr 26 12:10:09 verne kernel: pci 0000:00:1c.1:   bridge window [io  0x4000-0x4fff]
Apr 26 12:10:09 verne kernel: pci 0000:00:1c.1:   bridge window [mem 0x56000000-0x56ffffff]
Apr 26 12:10:09 verne kernel: pci 0000:00:1c.1:   bridge window [mem 0x51000000-0x51ffffff 64bit pref]
Apr 26 12:10:09 verne kernel: pci 0000:00:1e.0: PCI bridge to [bus 05]
Apr 26 12:10:09 verne kernel: pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
Apr 26 12:10:09 verne kernel: pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
Apr 26 12:10:09 verne kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
Apr 26 12:10:09 verne kernel: pci_bus 0000:00: resource 7 [mem 0x40000000-0xfebfffff window]
Apr 26 12:10:09 verne kernel: pci_bus 0000:01: resource 0 [io  0x5000-0x5fff]
Apr 26 12:10:09 verne kernel: pci_bus 0000:01: resource 1 [mem 0x57000000-0x57ffffff]
Apr 26 12:10:09 verne kernel: pci_bus 0000:01: resource 2 [mem 0x50000000-0x50ffffff 64bit pref]
Apr 26 12:10:09 verne kernel: pci_bus 0000:02: resource 0 [io  0x4000-0x4fff]
Apr 26 12:10:09 verne kernel: pci_bus 0000:02: resource 1 [mem 0x56000000-0x56ffffff]
Apr 26 12:10:09 verne kernel: pci_bus 0000:02: resource 2 [mem 0x51000000-0x51ffffff 64bit pref]
Apr 26 12:10:09 verne kernel: pci_bus 0000:05: resource 4 [io  0x0000-0x0cf7 window]
Apr 26 12:10:09 verne kernel: pci_bus 0000:05: resource 5 [io  0x0d00-0xffff window]
Apr 26 12:10:09 verne kernel: pci_bus 0000:05: resource 6 [mem 0x000a0000-0x000bffff window]
Apr 26 12:10:09 verne kernel: pci_bus 0000:05: resource 7 [mem 0x40000000-0xfebfffff window]
Apr 26 12:10:09 verne kernel: NET: Registered protocol family 2
Apr 26 12:10:09 verne kernel: tcp_listen_portaddr_hash hash table entries: 512 (order: 1, 8192 bytes, linear)
Apr 26 12:10:09 verne kernel: TCP established hash table entries: 8192 (order: 4, 65536 bytes, linear)
Apr 26 12:10:09 verne kernel: TCP bind hash table entries: 8192 (order: 5, 131072 bytes, linear)
Apr 26 12:10:09 verne kernel: TCP: Hash tables configured (established 8192 bind 8192)
Apr 26 12:10:09 verne kernel: UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
Apr 26 12:10:09 verne kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
Apr 26 12:10:09 verne kernel: NET: Registered protocol family 1
Apr 26 12:10:09 verne kernel: NET: Registered protocol family 44
Apr 26 12:10:09 verne kernel: pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Apr 26 12:10:09 verne kernel: pci 0000:01:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format)
Apr 26 12:10:09 verne kernel: PCI: CLS 64 bytes, default 64
Apr 26 12:10:09 verne kernel: Trying to unpack rootfs image as initramfs...
Apr 26 12:10:09 verne kernel: Freeing initrd memory: 11608K
Apr 26 12:10:09 verne kernel: check: Scanning for low memory corruption every 60 seconds
Apr 26 12:10:09 verne kernel: Initialise system trusted keyrings
Apr 26 12:10:09 verne kernel: Key type blacklist registered
Apr 26 12:10:09 verne kernel: workingset: timestamp_bits=41 max_order=18 bucket_order=0
Apr 26 12:10:09 verne kernel: zbud: loaded
Apr 26 12:10:09 verne kernel: Key type asymmetric registered
Apr 26 12:10:09 verne kernel: Asymmetric key parser 'x509' registered
Apr 26 12:10:09 verne kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
Apr 26 12:10:09 verne kernel: io scheduler mq-deadline registered
Apr 26 12:10:09 verne kernel: io scheduler kyber registered
Apr 26 12:10:09 verne kernel: io scheduler bfq registered
Apr 26 12:10:09 verne kernel: pcieport 0000:00:1c.0: PME: Signaling with IRQ 24
Apr 26 12:10:09 verne kernel: pcieport 0000:00:1c.1: PME: Signaling with IRQ 25
Apr 26 12:10:09 verne kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Apr 26 12:10:09 verne kernel: intel_idle: MWAIT substates: 0x20220
Apr 26 12:10:09 verne kernel: intel_idle: v0.4.1 model 0x1C
Apr 26 12:10:09 verne kernel: intel_idle: lapic_timer_reliable_states 0x2
Apr 26 12:10:09 verne kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
Apr 26 12:10:09 verne kernel: ACPI: Power Button [PWRB]
Apr 26 12:10:09 verne kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
Apr 26 12:10:09 verne kernel: ACPI: Sleep Button [SLPB]
Apr 26 12:10:09 verne kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
Apr 26 12:10:09 verne kernel: ACPI: Lid Switch [LID0]
Apr 26 12:10:09 verne kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
Apr 26 12:10:09 verne kernel: ACPI: Power Button [PWRF]
Apr 26 12:10:09 verne kernel: thermal LNXTHERM:00: registered as thermal_zone0
Apr 26 12:10:09 verne kernel: ACPI: Thermal Zone [THRM] (56 C)
Apr 26 12:10:09 verne kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
Apr 26 12:10:09 verne kernel: AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
Apr 26 12:10:09 verne kernel: AMD-Vi: AMD IOMMUv2 functionality not available on this system
Apr 26 12:10:09 verne kernel: ahci 0000:00:1f.2: version 3.0
Apr 26 12:10:09 verne kernel: ahci 0000:00:1f.2: SSS flag set, parallel bus scan disabled
Apr 26 12:10:09 verne kernel: ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0x3 impl SATA mode
Apr 26 12:10:09 verne kernel: ahci 0000:00:1f.2: flags: 64bit ncq ilck stag pm led clo pmp pio slum part 
Apr 26 12:10:09 verne kernel: scsi host0: ahci
Apr 26 12:10:09 verne kernel: scsi host1: ahci
Apr 26 12:10:09 verne kernel: scsi host2: ahci
Apr 26 12:10:09 verne kernel: scsi host3: ahci
Apr 26 12:10:09 verne kernel: ata1: SATA max UDMA/133 abar m1024@0x58204000 port 0x58204100 irq 26
Apr 26 12:10:09 verne kernel: ata2: SATA max UDMA/133 abar m1024@0x58204000 port 0x58204180 irq 26
Apr 26 12:10:09 verne kernel: ata3: DUMMY
Apr 26 12:10:09 verne kernel: ata4: DUMMY
Apr 26 12:10:09 verne kernel: usbcore: registered new interface driver usbserial_generic
Apr 26 12:10:09 verne kernel: usbserial: USB Serial support registered for generic
Apr 26 12:10:09 verne kernel: rtc_cmos 00:01: RTC can wake from S4
Apr 26 12:10:09 verne kernel: rtc_cmos 00:01: registered as rtc0
Apr 26 12:10:09 verne kernel: rtc_cmos 00:01: alarms up to one month, 242 bytes nvram, hpet irqs
Apr 26 12:10:09 verne kernel: intel_pstate: CPU model not supported
Apr 26 12:10:09 verne kernel: ledtrig-cpu: registered to indicate activity on CPUs
Apr 26 12:10:09 verne kernel: drop_monitor: Initializing network drop monitor service
Apr 26 12:10:09 verne kernel: NET: Registered protocol family 10
Apr 26 12:10:09 verne kernel: Segment Routing with IPv6
Apr 26 12:10:09 verne kernel: NET: Registered protocol family 17
Apr 26 12:10:09 verne kernel: RAS: Correctable Errors collector initialized.
Apr 26 12:10:09 verne kernel: microcode: sig=0x106ca, pf=0x10, revision=0x107
Apr 26 12:10:09 verne kernel: microcode: Microcode Update Driver: v2.2.
Apr 26 12:10:09 verne kernel: IPI shorthand broadcast: enabled
Apr 26 12:10:09 verne kernel: registered taskstats version 1
Apr 26 12:10:09 verne kernel: Loading compiled-in X.509 certificates
Apr 26 12:10:09 verne kernel: Loaded X.509 cert 'Build time autogenerated kernel key: 0c9628acc296c06ebd2a28dd1c6316e0b30b7d30'
Apr 26 12:10:09 verne kernel: zswap: loaded using pool lzo/zbud
Apr 26 12:10:09 verne kernel: Key type ._fscrypt registered
Apr 26 12:10:09 verne kernel: Key type .fscrypt registered
Apr 26 12:10:09 verne kernel: Key type fscrypt-provisioning registered
Apr 26 12:10:09 verne kernel: Key type big_key registered
Apr 26 12:10:09 verne kernel: PM:   Magic number: 0:617:174
Apr 26 12:10:09 verne kernel: acpi device:0a: hash matches
Apr 26 12:10:09 verne kernel: rtc_cmos 00:01: setting system clock to 2020-04-26T10:09:50 UTC (1587895790)
Apr 26 12:10:09 verne kernel: Unstable clock detected, switching default tracing clock to "global"
                              If you want to keep using the local clock, then add:
                                "trace_clock=local"
                              on the kernel command line
Apr 26 12:10:09 verne kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Apr 26 12:10:09 verne kernel: ata1.00: unexpected _GTF length (4)
Apr 26 12:10:09 verne kernel: ata1.00: ATA-8: TOSHIBA MK2559GSXP, GN003J, max UDMA/100
Apr 26 12:10:09 verne kernel: ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Apr 26 12:10:09 verne kernel: ata1.00: unexpected _GTF length (4)
Apr 26 12:10:09 verne kernel: ata1.00: configured for UDMA/100
Apr 26 12:10:09 verne kernel: scsi 0:0:0:0: Direct-Access     ATA      TOSHIBA MK2559GS 3J   PQ: 0 ANSI: 5
Apr 26 12:10:09 verne kernel: sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/233 GiB)
Apr 26 12:10:09 verne kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks
Apr 26 12:10:09 verne kernel: sd 0:0:0:0: [sda] Write Protect is off
Apr 26 12:10:09 verne kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Apr 26 12:10:09 verne kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 26 12:10:09 verne kernel:  sda: sda1 sda2
Apr 26 12:10:09 verne kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Apr 26 12:10:09 verne kernel: ata2: SATA link down (SStatus 0 SControl 300)
Apr 26 12:10:09 verne kernel: Freeing unused decrypted memory: 2040K
Apr 26 12:10:09 verne kernel: Freeing unused kernel image (initmem) memory: 1620K
Apr 26 12:10:09 verne kernel: Write protecting the kernel read-only data: 20480k
Apr 26 12:10:09 verne kernel: Freeing unused kernel image (text/rodata gap) memory: 2044K
Apr 26 12:10:09 verne kernel: Freeing unused kernel image (rodata/data gap) memory: 1640K
Apr 26 12:10:09 verne kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.
Apr 26 12:10:09 verne kernel: Run /init as init process
Apr 26 12:10:09 verne kernel:   with arguments:
Apr 26 12:10:09 verne kernel:     /init
Apr 26 12:10:09 verne kernel:   with environment:
Apr 26 12:10:09 verne kernel:     HOME=/
Apr 26 12:10:09 verne kernel:     TERM=linux
Apr 26 12:10:09 verne kernel:     BOOT_IMAGE=../vmlinuz-linux
Apr 26 12:10:09 verne kernel:     cryptdevice=/dev/disk/by-uuid/b914c624-d81a-4081-9f1a-c3e4282ec8e5:root
Apr 26 12:10:09 verne kernel:     cryptkey=/dev/disk/by-label/key:ext2:verne
Apr 26 12:10:09 verne kernel: usbcore: registered new interface driver usb-storage
Apr 26 12:10:09 verne kernel: usbcore: registered new interface driver uas
Apr 26 12:10:09 verne kernel: random: fast init done
Apr 26 12:10:09 verne kernel: i8042: PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSS0] at 0x60,0x64 irq 1,12
Apr 26 12:10:09 verne kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Apr 26 12:10:09 verne kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Apr 26 12:10:09 verne kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Apr 26 12:10:09 verne kernel: ehci-pci: EHCI PCI platform driver
Apr 26 12:10:09 verne kernel: ehci-pci 0000:00:1d.7: EHCI Host Controller
Apr 26 12:10:09 verne kernel: ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 1
Apr 26 12:10:09 verne kernel: ehci-pci 0000:00:1d.7: debug port 1
Apr 26 12:10:09 verne kernel: ehci-pci 0000:00:1d.7: cache line size of 64 is not supported
Apr 26 12:10:09 verne kernel: ehci-pci 0000:00:1d.7: irq 22, io mem 0x58204400
Apr 26 12:10:09 verne kernel: ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00
Apr 26 12:10:09 verne kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.06
Apr 26 12:10:09 verne kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Apr 26 12:10:09 verne kernel: usb usb1: Product: EHCI Host Controller
Apr 26 12:10:09 verne kernel: usb usb1: Manufacturer: Linux 5.6.6-arch1-1 ehci_hcd
Apr 26 12:10:09 verne kernel: usb usb1: SerialNumber: 0000:00:1d.7
Apr 26 12:10:09 verne kernel: hub 1-0:1.0: USB hub found
Apr 26 12:10:09 verne kernel: hub 1-0:1.0: 8 ports detected
Apr 26 12:10:09 verne kernel: uhci_hcd: USB Universal Host Controller Interface driver
Apr 26 12:10:09 verne kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
Apr 26 12:10:09 verne kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
Apr 26 12:10:09 verne kernel: uhci_hcd 0000:00:1d.0: detected 2 ports
Apr 26 12:10:09 verne kernel: uhci_hcd 0000:00:1d.0: irq 18, io base 0x00006080
Apr 26 12:10:09 verne kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.06
Apr 26 12:10:09 verne kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Apr 26 12:10:09 verne kernel: usb usb2: Product: UHCI Host Controller
Apr 26 12:10:09 verne kernel: usb usb2: Manufacturer: Linux 5.6.6-arch1-1 uhci_hcd
Apr 26 12:10:09 verne kernel: usb usb2: SerialNumber: 0000:00:1d.0
Apr 26 12:10:09 verne kernel: hub 2-0:1.0: USB hub found
Apr 26 12:10:09 verne kernel: hub 2-0:1.0: 2 ports detected
Apr 26 12:10:09 verne kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
Apr 26 12:10:09 verne kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
Apr 26 12:10:09 verne kernel: uhci_hcd 0000:00:1d.1: detected 2 ports
Apr 26 12:10:09 verne kernel: uhci_hcd 0000:00:1d.1: irq 20, io base 0x00006060
Apr 26 12:10:09 verne kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.06
Apr 26 12:10:09 verne kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Apr 26 12:10:09 verne kernel: usb usb3: Product: UHCI Host Controller
Apr 26 12:10:09 verne kernel: usb usb3: Manufacturer: Linux 5.6.6-arch1-1 uhci_hcd
Apr 26 12:10:09 verne kernel: usb usb3: SerialNumber: 0000:00:1d.1
Apr 26 12:10:09 verne kernel: hub 3-0:1.0: USB hub found
Apr 26 12:10:09 verne kernel: hub 3-0:1.0: 2 ports detected
Apr 26 12:10:09 verne kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
Apr 26 12:10:09 verne kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
Apr 26 12:10:09 verne kernel: uhci_hcd 0000:00:1d.2: detected 2 ports
Apr 26 12:10:09 verne kernel: uhci_hcd 0000:00:1d.2: irq 21, io base 0x00006040
Apr 26 12:10:09 verne kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.06
Apr 26 12:10:09 verne kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Apr 26 12:10:09 verne kernel: usb usb4: Product: UHCI Host Controller
Apr 26 12:10:09 verne kernel: usb usb4: Manufacturer: Linux 5.6.6-arch1-1 uhci_hcd
Apr 26 12:10:09 verne kernel: usb usb4: SerialNumber: 0000:00:1d.2
Apr 26 12:10:09 verne kernel: hub 4-0:1.0: USB hub found
Apr 26 12:10:09 verne kernel: hub 4-0:1.0: 2 ports detected
Apr 26 12:10:09 verne kernel: uhci_hcd 0000:00:1d.3: UHCI Host Controller
Apr 26 12:10:09 verne kernel: uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
Apr 26 12:10:09 verne kernel: uhci_hcd 0000:00:1d.3: detected 2 ports
Apr 26 12:10:09 verne kernel: uhci_hcd 0000:00:1d.3: irq 22, io base 0x00006020
Apr 26 12:10:09 verne kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.06
Apr 26 12:10:09 verne kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Apr 26 12:10:09 verne kernel: usb usb5: Product: UHCI Host Controller
Apr 26 12:10:09 verne kernel: usb usb5: Manufacturer: Linux 5.6.6-arch1-1 uhci_hcd
Apr 26 12:10:09 verne kernel: usb usb5: SerialNumber: 0000:00:1d.3
Apr 26 12:10:09 verne kernel: hub 5-0:1.0: USB hub found
Apr 26 12:10:09 verne kernel: hub 5-0:1.0: 2 ports detected
Apr 26 12:10:09 verne kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4
Apr 26 12:10:09 verne kernel: usb 1-3: new high-speed USB device number 2 using ehci-pci
Apr 26 12:10:09 verne kernel: usb 1-3: New USB device found, idVendor=090c, idProduct=1000, bcdDevice=11.00
Apr 26 12:10:09 verne kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 26 12:10:09 verne kernel: usb 1-3: Product: USB Flash Disk
Apr 26 12:10:09 verne kernel: usb 1-3: Manufacturer: General
Apr 26 12:10:09 verne kernel: usb 1-3: SerialNumber: 0414070000000275
Apr 26 12:10:09 verne kernel: usb-storage 1-3:1.0: USB Mass Storage device detected
Apr 26 12:10:09 verne kernel: usb-storage 1-3:1.0: Quirks match for vid 090c pid 1000: 400
Apr 26 12:10:09 verne kernel: scsi host4: usb-storage 1-3:1.0
Apr 26 12:10:09 verne kernel: device-mapper: uevent: version 1.0.3
Apr 26 12:10:09 verne kernel: device-mapper: ioctl: 4.42.0-ioctl (2020-02-27) initialised: dm-devel@redhat.com
Apr 26 12:10:09 verne kernel: usb 1-4: new high-speed USB device number 3 using ehci-pci
Apr 26 12:10:09 verne kernel: usb 1-4: New USB device found, idVendor=0402, idProduct=7675, bcdDevice= 0.04
Apr 26 12:10:09 verne kernel: usb 1-4: New USB device strings: Mfr=3, Product=1, SerialNumber=0
Apr 26 12:10:09 verne kernel: usb 1-4: Product: WebCam
Apr 26 12:10:09 verne kernel: usb 1-4: Manufacturer: Y2B7C04CN
Apr 26 12:10:09 verne kernel: scsi 4:0:0:0: Direct-Access     General  USB Flash Disk   1100 PQ: 0 ANSI: 4
Apr 26 12:10:09 verne kernel: sd 4:0:0:0: [sdb] 7864320 512-byte logical blocks: (4.03 GB/3.75 GiB)
Apr 26 12:10:09 verne kernel: sd 4:0:0:0: [sdb] Write Protect is off
Apr 26 12:10:09 verne kernel: sd 4:0:0:0: [sdb] Mode Sense: 43 00 00 00
Apr 26 12:10:09 verne kernel: sd 4:0:0:0: [sdb] No Caching mode page found
Apr 26 12:10:09 verne kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Apr 26 12:10:09 verne kernel:  sdb: sdb1 sdb2
Apr 26 12:10:09 verne kernel: sd 4:0:0:0: [sdb] Attached SCSI removable disk
Apr 26 12:10:09 verne kernel: EXT4-fs (sdb2): mounting ext2 file system using the ext4 subsystem
Apr 26 12:10:09 verne kernel: EXT4-fs (sdb2): mounted filesystem without journal. Opts: (null)
Apr 26 12:10:09 verne kernel: random: cryptsetup: uninitialized urandom read (4 bytes read)
Apr 26 12:10:09 verne kernel: random: cryptsetup: uninitialized urandom read (4 bytes read)
Apr 26 12:10:09 verne kernel: random: cryptsetup: uninitialized urandom read (2 bytes read)
Apr 26 12:10:09 verne kernel: cryptd: max_cpu_qlen set to 1000
Apr 26 12:10:09 verne kernel: raid6: sse2x4   gen()  1664 MB/s
Apr 26 12:10:09 verne kernel: raid6: sse2x4   xor()   639 MB/s
Apr 26 12:10:09 verne kernel: raid6: sse2x2   gen()   789 MB/s
Apr 26 12:10:09 verne kernel: raid6: sse2x2   xor()  1036 MB/s
Apr 26 12:10:09 verne kernel: raid6: sse2x1   gen()   720 MB/s
Apr 26 12:10:09 verne kernel: raid6: sse2x1   xor()   731 MB/s
Apr 26 12:10:09 verne kernel: raid6: using algorithm sse2x4 gen() 1664 MB/s
Apr 26 12:10:09 verne kernel: raid6: .... xor() 639 MB/s, rmw enabled
Apr 26 12:10:09 verne kernel: raid6: using ssse3x2 recovery algorithm
Apr 26 12:10:09 verne kernel: xor: measuring software checksum speed
Apr 26 12:10:09 verne kernel:    prefetch64-sse:  3738.000 MB/sec
Apr 26 12:10:09 verne kernel:    generic_sse:  3330.000 MB/sec
Apr 26 12:10:09 verne kernel: xor: using function: prefetch64-sse (3738.000 MB/sec)
Apr 26 12:10:09 verne kernel: Btrfs loaded, crc32c=crc32c-generic
Apr 26 12:10:09 verne kernel: BTRFS: device fsid 8a8ca44a-4df8-4790-b37c-a5bdcf4ee1ce devid 1 transid 23254 /dev/dm-0 scanned by systemd-udevd (207)
Apr 26 12:10:09 verne kernel: BTRFS info (device dm-0): disk space caching is enabled
Apr 26 12:10:09 verne kernel: BTRFS info (device dm-0): has skinny extents
Apr 26 12:10:09 verne kernel: random: crng init done
Apr 26 12:10:09 verne systemd[1]: systemd 245.5-2-arch running in system mode. (+PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
Apr 26 12:10:09 verne systemd[1]: Detected architecture x86-64.
Apr 26 12:10:09 verne systemd[1]: Set hostname to <verne>.
Apr 26 12:10:09 verne systemd[1]: Created slice system-dhcpcd.slice.
Apr 26 12:10:09 verne systemd[1]: Created slice system-getty.slice.
Apr 26 12:10:09 verne systemd[1]: Created slice system-modprobe.slice.
Apr 26 12:10:09 verne systemd[1]: Created slice system-systemd\x2dfsck.slice.
Apr 26 12:10:09 verne systemd[1]: Created slice system-wpa_supplicant.slice.
Apr 26 12:10:09 verne systemd[1]: Created slice User and Session Slice.
Apr 26 12:10:09 verne systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
Apr 26 12:10:09 verne systemd[1]: Started Forward Password Requests to Wall Directory Watch.
Apr 26 12:10:09 verne systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
Apr 26 12:10:09 verne systemd[1]: Reached target Local Encrypted Volumes.
Apr 26 12:10:09 verne systemd[1]: Reached target Paths.
Apr 26 12:10:09 verne systemd[1]: Reached target Remote File Systems.
Apr 26 12:10:09 verne systemd[1]: Reached target Slices.
Apr 26 12:10:09 verne systemd[1]: Reached target Swap.
Apr 26 12:10:09 verne systemd[1]: Listening on Device-mapper event daemon FIFOs.
Apr 26 12:10:09 verne systemd[1]: Listening on Process Core Dump Socket.
Apr 26 12:10:09 verne systemd[1]: Listening on initctl Compatibility Named Pipe.
Apr 26 12:10:09 verne systemd[1]: Listening on Journal Audit Socket.
Apr 26 12:10:09 verne systemd[1]: Listening on Journal Socket (/dev/log).
Apr 26 12:10:09 verne systemd[1]: Listening on Journal Socket.
Apr 26 12:10:09 verne systemd[1]: Listening on udev Control Socket.
Apr 26 12:10:09 verne systemd[1]: Listening on udev Kernel Socket.
Apr 26 12:10:09 verne systemd[1]: Mounting Huge Pages File System...
Apr 26 12:10:09 verne systemd[1]: Mounting POSIX Message Queue File System...
Apr 26 12:10:09 verne systemd[1]: Mounting Kernel Debug File System...
Apr 26 12:10:09 verne systemd[1]: Mounting Kernel Trace File System...
Apr 26 12:10:09 verne systemd[1]: Mounting Temporary Directory (/tmp)...
Apr 26 12:10:09 verne systemd[1]: Starting Create list of static device nodes for the current kernel...
Apr 26 12:10:09 verne systemd[1]: Starting Load Kernel Module drm...
Apr 26 12:10:09 verne systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
Apr 26 12:10:09 verne systemd[1]: Starting Journal Service...
Apr 26 12:10:09 verne systemd[1]: Condition check resulted in Load Kernel Modules being skipped.
Apr 26 12:10:09 verne systemd[1]: Condition check resulted in FUSE Control File System being skipped.
Apr 26 12:10:09 verne systemd[1]: Mounting Kernel Configuration File System...
Apr 26 12:10:09 verne systemd[1]: Starting Remount Root and Kernel File Systems...
Apr 26 12:10:09 verne systemd[1]: Starting Apply Kernel Variables...
Apr 26 12:10:09 verne systemd[1]: Starting udev Coldplug all Devices...
Apr 26 12:10:09 verne systemd[1]: Mounted Huge Pages File System.
Apr 26 12:10:09 verne systemd[1]: Mounted Kernel Debug File System.
Apr 26 12:10:09 verne systemd[1]: Mounted Kernel Trace File System.
Apr 26 12:10:09 verne systemd[1]: Mounted Temporary Directory (/tmp).
Apr 26 12:10:09 verne systemd[1]: Finished Create list of static device nodes for the current kernel.
Apr 26 12:10:09 verne systemd[1]: Mounted POSIX Message Queue File System.
Apr 26 12:10:09 verne systemd[1]: Mounted Kernel Configuration File System.
Apr 26 12:10:09 verne kernel: Linux agpgart interface v0.103
Apr 26 12:10:09 verne systemd[1]: Finished Apply Kernel Variables.
Apr 26 12:10:09 verne kernel: BTRFS info (device dm-0): enabling ssd optimizations
Apr 26 12:10:09 verne kernel: BTRFS info (device dm-0): disk space caching is enabled
Apr 26 12:10:09 verne systemd[1]: Finished Remount Root and Kernel File Systems.
Apr 26 12:10:09 verne systemd[1]: modprobe@drm.service: Succeeded.
Apr 26 12:10:09 verne systemd[1]: Finished Load Kernel Module drm.
Apr 26 12:10:09 verne systemd[1]: Condition check resulted in First Boot Wizard being skipped.
Apr 26 12:10:09 verne systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Apr 26 12:10:09 verne systemd[1]: Starting Load/Save Random Seed...
Apr 26 12:10:09 verne systemd[1]: Starting Create System Users...
Apr 26 12:10:09 verne systemd[1]: Finished udev Coldplug all Devices.
Apr 26 12:10:09 verne systemd[1]: Finished Load/Save Random Seed.
Apr 26 12:10:09 verne systemd[1]: Finished Create System Users.
Apr 26 12:10:09 verne systemd[1]: Starting Create Static Device Nodes in /dev...
Apr 26 12:10:09 verne systemd[1]: Finished Create Static Device Nodes in /dev.
Apr 26 12:10:09 verne systemd[1]: Reached target Local File Systems (Pre).
Apr 26 12:10:09 verne systemd[1]: Condition check resulted in Virtual Machine and Container Storage (Compatibility) being skipped.
Apr 26 12:10:09 verne systemd[1]: Starting udev Kernel Device Manager...
Apr 26 12:10:09 verne systemd-journald[394]: Journal started
Apr 26 12:10:09 verne systemd-journald[394]: Runtime Journal (/run/log/journal/9eb23238dbfb4bb3941fef0a37ead5d1) is 6.0M, max 48.5M, 42.5M free.
Apr 26 12:10:09 verne systemd-sysctl[397]: Not setting net/ipv4/conf/all/rp_filter (explicit setting exists).
Apr 26 12:10:09 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:09 verne systemd[1]: Started Journal Service.
Apr 26 12:10:09 verne kernel: audit: type=1130 audit(1587895809.196:2): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:09 verne systemd-sysctl[397]: Not setting net/ipv4/conf/default/rp_filter (explicit setting exists).
Apr 26 12:10:09 verne systemd-sysctl[397]: Not setting net/ipv4/conf/all/accept_source_route (explicit setting exists).
Apr 26 12:10:09 verne systemd-sysctl[397]: Not setting net/ipv4/conf/default/accept_source_route (explicit setting exists).
Apr 26 12:10:09 verne systemd-sysctl[397]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists).
Apr 26 12:10:09 verne systemd-sysctl[397]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists).
Apr 26 12:10:09 verne systemd[1]: Starting Flush Journal to Persistent Storage...
Apr 26 12:10:09 verne systemd-journald[394]: Time spent on flushing to /var/log/journal/9eb23238dbfb4bb3941fef0a37ead5d1 is 1.133684s for 711 entries.
Apr 26 12:10:09 verne systemd-journald[394]: System Journal (/var/log/journal/9eb23238dbfb4bb3941fef0a37ead5d1) is 472.0M, max 4.0G, 3.5G free.
Apr 26 12:10:13 verne kernel: audit: type=1130 audit(1587895809.666:3): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:13 verne kernel: ACPI: AC Adapter [AC] (on-line)
Apr 26 12:10:13 verne kernel: pci 0000:00:1e.0: PCI bridge to [bus 05]
Apr 26 12:10:13 verne kernel: pci 0000:00:1e.0: PCI bridge to [bus 05]
Apr 26 12:10:13 verne kernel: pci 0000:00:1e.0: PCI bridge to [bus 05]
Apr 26 12:10:13 verne kernel: pci 0000:00:1e.0: PCI bridge to [bus 05]
Apr 26 12:10:13 verne kernel: pci 0000:00:1e.0: PCI bridge to [bus 05]
Apr 26 12:10:13 verne kernel: pci 0000:00:1e.0: PCI bridge to [bus 05]
Apr 26 12:10:13 verne kernel: battery: ACPI: Battery Slot [BAT0] (battery present)
Apr 26 12:10:13 verne kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMBA) (20200110/utaddress-204)
Apr 26 12:10:13 verne kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Apr 26 12:10:13 verne kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000053E (\GPIO) (20200110/utaddress-204)
Apr 26 12:10:13 verne kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Apr 26 12:10:13 verne kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000053E (\GPIO) (20200110/utaddress-204)
Apr 26 12:10:13 verne kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Apr 26 12:10:13 verne kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Apr 26 12:10:13 verne kernel: lpc_ich 0000:00:1f.0: No MFD cells added
Apr 26 12:10:13 verne kernel: atl1c 0000:01:00.0: version 1.0.1.1-NAPI
Apr 26 12:10:13 verne kernel: mc: Linux media interface: v0.10
Apr 26 12:10:13 verne kernel: i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
Apr 26 12:10:13 verne kernel: videodev: Linux video capture interface: v2.00
Apr 26 12:10:13 verne kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC272X: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
Apr 26 12:10:13 verne kernel: snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Apr 26 12:10:13 verne kernel: snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
Apr 26 12:10:13 verne kernel: snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
Apr 26 12:10:13 verne kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
Apr 26 12:10:13 verne kernel: snd_hda_codec_realtek hdaudioC0D0:      Mic=0x18
Apr 26 12:10:13 verne kernel: snd_hda_codec_realtek hdaudioC0D0:      Internal Mic=0x12
Apr 26 12:10:13 verne kernel: input: PC Speaker as /devices/platform/pcspkr/input/input6
Apr 26 12:10:13 verne kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
Apr 26 12:10:13 verne kernel: input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
Apr 26 12:10:13 verne kernel: input: HDA Intel Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
Apr 26 12:10:13 verne kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
Apr 26 12:10:13 verne kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Apr 26 12:10:13 verne kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Apr 26 12:10:13 verne kernel: cfg80211: failed to load regulatory.db
Apr 26 12:10:13 verne kernel: pci 0000:00:00.0: Intel GMA3150 Chipset
Apr 26 12:10:13 verne kernel: pci 0000:00:00.0: detected gtt size: 524288K total, 262144K mappable
Apr 26 12:10:13 verne kernel: pci 0000:00:00.0: detected 8192K stolen memory
Apr 26 12:10:13 verne kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Apr 26 12:10:13 verne kernel: Console: switching to colour dummy device 80x25
Apr 26 12:10:13 verne kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Apr 26 12:10:13 verne kernel: [drm] Driver supports precise vblank timestamp query.
Apr 26 12:10:13 verne kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Apr 26 12:10:13 verne kernel: [drm] Initialized overlay support.
Apr 26 12:10:13 verne kernel: [drm] Initialized i915 1.6.0 20200114 for 0000:00:02.0 on minor 0
Apr 26 12:10:13 verne kernel: ACPI: Video Device [OVGA] (multi-head: yes  rom: no  post: no)
Apr 26 12:10:13 verne kernel: intel_powerclamp: No package C-state available
Apr 26 12:10:13 verne kernel: intel_powerclamp: No package C-state available
Apr 26 12:10:13 verne kernel: uvcvideo: Found UVC 1.00 device WebCam (0402:7675)
Apr 26 12:10:13 verne kernel: intel_powerclamp: No package C-state available
Apr 26 12:10:13 verne kernel: uvcvideo 1-4:1.0: Entity type for entity Extension 6 was not initialized!
Apr 26 12:10:13 verne kernel: uvcvideo 1-4:1.0: Entity type for entity Processing 5 was not initialized!
Apr 26 12:10:13 verne kernel: uvcvideo 1-4:1.0: Entity type for entity Selector 4 was not initialized!
Apr 26 12:10:13 verne kernel: uvcvideo 1-4:1.0: Entity type for entity Camera 1 was not initialized!
Apr 26 12:10:13 verne kernel: input: WebCam: WebCam as /devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4:1.0/input/input11
Apr 26 12:10:13 verne kernel: usbcore: registered new interface driver uvcvideo
Apr 26 12:10:13 verne kernel: USB Video Class driver (1.1.1)
Apr 26 12:10:13 verne kernel: intel_powerclamp: No package C-state available
Apr 26 12:10:13 verne kernel: acpi device:27: registered as cooling_device5
Apr 26 12:10:13 verne kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12
Apr 26 12:10:13 verne kernel: fbcon: i915drmfb (fb0) is primary device
Apr 26 12:10:09 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:13 verne kernel: acer_wmi: Acer Laptop ACPI-WMI Extras
Apr 26 12:10:13 verne kernel: acer_wmi: Function bitmap for Communication Button: 0x1
Apr 26 12:10:09 verne systemd[1]: Started udev Kernel Device Manager.
Apr 26 12:10:12 verne systemd[1]: Found device TOSHIBA_MK2559GSXP 1.
Apr 26 12:10:12 verne systemd[1]: Starting File System Check on /dev/disk/by-uuid/6ff1edd4-f8be-4656-856f-d9ad361edd8a...
Apr 26 12:10:12 verne systemd-udevd[407]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 26 12:10:13 verne systemd[1]: Finished Flush Journal to Persistent Storage.
Apr 26 12:10:13 verne kernel: input: Acer WMI hotkeys as /devices/virtual/input/input13
Apr 26 12:10:13 verne kernel: psmouse serio1: synaptics: queried max coordinates: x [..5612], y [..4618]
Apr 26 12:10:13 verne kernel: psmouse serio1: synaptics: Touchpad model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd04731/0xa40000/0xa0000/0x0, board id: 0, fw id: 528321
Apr 26 12:10:13 verne kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input10
Apr 26 12:10:13 verne kernel: ath: phy0: Enable LNA combining
Apr 26 12:10:13 verne kernel: ath: phy0: ASPM enabled: 0x42
Apr 26 12:10:13 verne kernel: ath: EEPROM regdomain: 0x65
Apr 26 12:10:13 verne kernel: ath: EEPROM indicates we should expect a direct regpair map
Apr 26 12:10:13 verne kernel: ath: Country alpha2 being used: 00
Apr 26 12:10:13 verne kernel: ath: Regpair used: 0x65
Apr 26 12:10:13 verne kernel: ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Apr 26 12:10:13 verne kernel: ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xffffb2e300550000, irq=17
Apr 26 12:10:13 verne systemd-udevd[409]: Using default interface naming scheme 'v245'.
Apr 26 12:10:13 verne systemd-udevd[409]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 26 12:10:13 verne kernel: atl1c 0000:01:00.0 enp1s0: renamed from eth0
Apr 26 12:10:13 verne kernel: Console: switching to colour frame buffer device 128x37
Apr 26 12:10:13 verne kernel: i915 0000:00:02.0: fb0: i915drmfb frame buffer device
Apr 26 12:10:13 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-flush comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:13 verne kernel: audit: type=1130 audit(1587895813.866:4): 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'
Apr 26 12:10:13 verne systemd[1]: Reached target Sound Card.
Apr 26 12:10:13 verne systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Apr 26 12:10:13 verne systemd[1]: Starting Load/Save RF Kill Switch Status...
Apr 26 12:10:13 verne systemd-fsck[436]: /dev/sda1: clean, 79/16384 files, 55748/65536 blocks
Apr 26 12:10:13 verne systemd[1]: Created slice system-systemd\x2dbacklight.slice.
Apr 26 12:10:13 verne systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:acpi_video0...
Apr 26 12:10:13 verne kernel: BTRFS info (device dm-0): device fsid 8a8ca44a-4df8-4790-b37c-a5bdcf4ee1ce devid 1 moved old:/dev/mapper/root new:/dev/dm-0
Apr 26 12:10:13 verne kernel: BTRFS info (device dm-0): device fsid 8a8ca44a-4df8-4790-b37c-a5bdcf4ee1ce devid 1 moved old:/dev/dm-0 new:/dev/mapper/root
Apr 26 12:10:14 verne systemd-udevd[412]: Using default interface naming scheme 'v245'.
Apr 26 12:10:14 verne systemd-udevd[412]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 26 12:10:14 verne kernel: ath9k 0000:02:00.0 wlp2s0: renamed from wlan0
Apr 26 12:10:14 verne systemd-udevd[416]: Using default interface naming scheme 'v245'.
Apr 26 12:10:14 verne systemd[1]: Finished File System Check on /dev/disk/by-uuid/6ff1edd4-f8be-4656-856f-d9ad361edd8a.
Apr 26 12:10:14 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-6ff1edd4\x2df8be\x2d4656\x2d856f\x2dd9ad361edd8a comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:14 verne kernel: audit: type=1130 audit(1587895814.049:5): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-6ff1edd4\x2df8be\x2d4656\x2d856f\x2dd9ad361edd8a comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:14 verne systemd[1]: Mounting /boot...
Apr 26 12:10:14 verne systemd[1]: Started Load/Save RF Kill Switch Status.
Apr 26 12:10:14 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:14 verne kernel: audit: type=1130 audit(1587895814.069:6): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:14 verne kernel: EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem
Apr 26 12:10:14 verne kernel: mousedev: PS/2 mouse device common for all mice
Apr 26 12:10:14 verne systemd[1]: Finished Load/Save Screen Backlight Brightness of backlight:acpi_video0.
Apr 26 12:10:14 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-backlight@backlight:acpi_video0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:14 verne kernel: audit: type=1130 audit(1587895814.119:7): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-backlight@backlight:acpi_video0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:14 verne systemd-udevd[413]: Using default interface naming scheme 'v245'.
Apr 26 12:10:14 verne systemd[1]: Found device AR9285 Wireless Network Adapter (PCI-Express).
Apr 26 12:10:14 verne kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: stripe=4
Apr 26 12:10:14 verne kernel: ext3 filesystem being mounted at /boot supports timestamps until 2038 (0x7fffffff)
Apr 26 12:10:14 verne systemd[1]: Mounted /boot.
Apr 26 12:10:14 verne systemd[1]: Reached target Local File Systems.
Apr 26 12:10:14 verne systemd[1]: Starting Rebuild Dynamic Linker Cache...
Apr 26 12:10:14 verne systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
Apr 26 12:10:14 verne systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
Apr 26 12:10:14 verne systemd[1]: Starting Create Volatile Files and Directories...
Apr 26 12:10:14 verne systemd[1]: Finished Create Volatile Files and Directories.
Apr 26 12:10:14 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:14 verne kernel: audit: type=1130 audit(1587895814.489:8): 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'
Apr 26 12:10:14 verne systemd[1]: Starting Rebuild Journal Catalog...
Apr 26 12:10:14 verne systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Apr 26 12:10:14 verne audit[464]: SYSTEM_BOOT pid=464 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:14 verne kernel: audit: type=1127 audit(1587895814.566:9): pid=464 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:14 verne systemd[1]: Finished Update UTMP about System Boot/Shutdown.
Apr 26 12:10:14 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:14 verne kernel: audit: type=1130 audit(1587895814.603:10): 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'
Apr 26 12:10:14 verne systemd[1]: Finished Rebuild Journal Catalog.
Apr 26 12:10:14 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-catalog-update comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:14 verne kernel: audit: type=1130 audit(1587895814.756:11): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-catalog-update comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:17 verne systemd[1]: Finished Rebuild Dynamic Linker Cache.
Apr 26 12:10:17 verne kernel: audit: type=1130 audit(1587895817.213:12): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ldconfig comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:17 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ldconfig comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:17 verne systemd[1]: Starting Update is Completed...
Apr 26 12:10:17 verne systemd[1]: Finished Update is Completed.
Apr 26 12:10:17 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-done comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:17 verne systemd[1]: Reached target System Initialization.
Apr 26 12:10:17 verne kernel: audit: type=1130 audit(1587895817.286:13): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-done comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:17 verne systemd[1]: Started Daily man-db regeneration.
Apr 26 12:10:17 verne systemd[1]: Started Daily verification of password and group files.
Apr 26 12:10:17 verne systemd[1]: Started Daily Cleanup of Temporary Directories.
Apr 26 12:10:17 verne systemd[1]: Started Daily locate database update.
Apr 26 12:10:17 verne systemd[1]: Reached target Timers.
Apr 26 12:10:17 verne systemd[1]: Listening on D-Bus System Message Bus Socket.
Apr 26 12:10:17 verne systemd[1]: Reached target Sockets.
Apr 26 12:10:17 verne systemd[1]: Reached target Basic System.
Apr 26 12:10:17 verne systemd[1]: Started D-Bus System Message Bus.
Apr 26 12:10:17 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:17 verne kernel: audit: type=1130 audit(1587895817.393:14): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:17 verne systemd[1]: Starting dhcpcd on all interfaces...
Apr 26 12:10:17 verne systemd[1]: Starting dhcpcd on wlp2s0...
Apr 26 12:10:17 verne systemd[1]: Condition check resulted in SSH Key Generation being skipped.
Apr 26 12:10:17 verne audit: AUDIT1334 prog-id=7 op=LOAD
Apr 26 12:10:17 verne kernel: audit: type=1334 audit(1587895817.433:15): prog-id=7 op=LOAD
Apr 26 12:10:17 verne audit: AUDIT1334 prog-id=8 op=LOAD
Apr 26 12:10:17 verne systemd[1]: Starting Login Service...
Apr 26 12:10:17 verne kernel: audit: type=1334 audit(1587895817.433:16): prog-id=8 op=LOAD
Apr 26 12:10:17 verne dhcpcd[468]: dhcpcd-9.0.2 starting
Apr 26 12:10:17 verne systemd[1]: Started WPA supplicant daemon (interface-specific version).
Apr 26 12:10:17 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=wpa_supplicant@wlp2s0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:17 verne kernel: audit: type=1130 audit(1587895817.466:17): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=wpa_supplicant@wlp2s0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:17 verne dhcpcd[467]: dhcpcd-9.0.2 starting
Apr 26 12:10:17 verne wpa_supplicant[470]: Successfully initialized wpa_supplicant
Apr 26 12:10:18 verne dhcpcd[508]: dev: loaded udev
Apr 26 12:10:18 verne kernel: 8021q: 802.1Q VLAN Support v1.8
Apr 26 12:10:18 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:18 verne systemd[1]: Started dhcpcd on all interfaces.
Apr 26 12:10:18 verne dhcpcd[507]: wlp2s0: waiting for carrier
Apr 26 12:10:18 verne dhcpcd[508]: enp1s0: waiting for carrier
Apr 26 12:10:18 verne dhcpcd[508]: wlp2s0: waiting for carrier
Apr 26 12:10:18 verne dhcpcd[508]: enp1s0: carrier acquired
Apr 26 12:10:18 verne dhcpcd[508]: DUID 00:01:00:01:26:31:67:d2:d0:df:9a:80:bd:06
Apr 26 12:10:18 verne dhcpcd[508]: enp1s0: IAID f4:b2:ba:00
Apr 26 12:10:18 verne dhcpcd[508]: enp1s0: adding address fe80::dbab:d645:576f:ff38
Apr 26 12:10:18 verne dhcpcd[508]: enp1s0: soliciting a DHCP lease
Apr 26 12:10:18 verne dhcpcd[508]: enp1s0: carrier lost
Apr 26 12:10:19 verne dhcpcd[508]: enp1s0: deleting address fe80::dbab:d645:576f:ff38
Apr 26 12:10:19 verne kernel: wlp2s0: authenticate with 88:71:b1:a7:93:61
Apr 26 12:10:19 verne wpa_supplicant[470]: wlp2s0: SME: Trying to authenticate with 88:71:b1:a7:93:61 (SSID='soad' freq=2437 MHz)
Apr 26 12:10:19 verne wpa_supplicant[470]: wlp2s0: Trying to associate with 88:71:b1:a7:93:61 (SSID='soad' freq=2437 MHz)
Apr 26 12:10:19 verne kernel: wlp2s0: send auth to 88:71:b1:a7:93:61 (try 1/3)
Apr 26 12:10:19 verne kernel: wlp2s0: authenticated
Apr 26 12:10:19 verne kernel: wlp2s0: associate with 88:71:b1:a7:93:61 (try 1/3)
Apr 26 12:10:19 verne systemd[1]: systemd-rfkill.service: Succeeded.
Apr 26 12:10:19 verne audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:19 verne kernel: wlp2s0: RX AssocResp from 88:71:b1:a7:93:61 (capab=0x431 status=0 aid=1)
Apr 26 12:10:19 verne kernel: wlp2s0: associated
Apr 26 12:10:19 verne wpa_supplicant[470]: wlp2s0: Associated with 88:71:b1:a7:93:61
Apr 26 12:10:19 verne wpa_supplicant[470]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 26 12:10:19 verne wpa_supplicant[470]: wlp2s0: WPA: Key negotiation completed with 88:71:b1:a7:93:61 [PTK=CCMP GTK=CCMP]
Apr 26 12:10:19 verne wpa_supplicant[470]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 88:71:b1:a7:93:61 completed [id=0 id_str=]
Apr 26 12:10:19 verne kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
Apr 26 12:10:19 verne dhcpcd[507]: wlp2s0: carrier acquired
Apr 26 12:10:19 verne dhcpcd[508]: wlp2s0: carrier acquired
Apr 26 12:10:19 verne dhcpcd[508]: wlp2s0: connected to Access Point `soad'
Apr 26 12:10:19 verne dhcpcd[507]: wlp2s0: connected to Access Point `soad'
Apr 26 12:10:19 verne dhcpcd[508]: wlp2s0: IAID 9a:80:bd:06
Apr 26 12:10:19 verne dhcpcd[508]: wlp2s0: adding address fe80::9163:6bf2:9dd2:557
Apr 26 12:10:19 verne dhcpcd[507]: DUID 00:01:00:01:26:31:67:d2:d0:df:9a:80:bd:06
Apr 26 12:10:19 verne dhcpcd[507]: wlp2s0: IAID 9a:80:bd:06
Apr 26 12:10:19 verne dhcpcd[507]: wlp2s0: adding address fe80::9163:6bf2:9dd2:557
Apr 26 12:10:19 verne dhcpcd[508]: wlp2s0: soliciting an IPv6 router
Apr 26 12:10:19 verne dhcpcd[508]: wlp2s0: rebinding lease of 192.168.0.193
Apr 26 12:10:19 verne systemd-logind[469]: New seat seat0.
Apr 26 12:10:19 verne dhcpcd[508]: wlp2s0: probing address 192.168.0.193/24
Apr 26 12:10:19 verne systemd-logind[469]: Watching system buttons on /dev/input/event3 (Power Button)
Apr 26 12:10:19 verne systemd-logind[469]: Watching system buttons on /dev/input/event0 (Power Button)
Apr 26 12:10:19 verne systemd-logind[469]: Watching system buttons on /dev/input/event2 (Lid Switch)
Apr 26 12:10:19 verne systemd-logind[469]: Watching system buttons on /dev/input/event1 (Sleep Button)
Apr 26 12:10:19 verne systemd-logind[469]: Watching system buttons on /dev/input/event4 (AT Translated Set 2 keyboard)
Apr 26 12:10:19 verne systemd-logind[469]: Watching system buttons on /dev/input/event11 (Acer WMI hotkeys)
Apr 26 12:10:19 verne systemd[1]: Started Login Service.
Apr 26 12:10:19 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:19 verne kernel: kauditd_printk_skb: 2 callbacks suppressed
Apr 26 12:10:19 verne kernel: audit: type=1130 audit(1587895819.796:20): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:19 verne dhcpcd[507]: wlp2s0: rebinding lease of 192.168.0.193
Apr 26 12:10:19 verne dhcpcd[507]: wlp2s0: probing address 192.168.0.193/24
Apr 26 12:10:19 verne dhcpcd[507]: wlp2s0: soliciting an IPv6 router
Apr 26 12:10:21 verne dhcpcd[560]: dhcp6_openudp: Address already in use
Apr 26 12:10:21 verne dhcpcd[560]: ps_inet_listenin6: Address already in use
Apr 26 12:10:21 verne dhcpcd[560]: ps_root_recvmsg: Address already in use
Apr 26 12:10:21 verne dhcpcd[508]: wlp2s0: Router Advertisement from fe80::8a71:b1ff:fea7:9363
Apr 26 12:10:21 verne dhcpcd[507]: wlp2s0: Router Advertisement from fe80::8a71:b1ff:fea7:9363
Apr 26 12:10:21 verne dhcpcd[508]: wlp2s0: adding address 2a02:810d:41bf:ecc8:5790:dcd9:907d:105c/64
Apr 26 12:10:21 verne dhcpcd[507]: if_route (ADD): File exists
Apr 26 12:10:21 verne dhcpcd[507]: wlp2s0: adding address 2a02:810d:41bf:ecc8:5790:dcd9:907d:105c/64
Apr 26 12:10:21 verne dhcpcd[508]: wlp2s0: adding route to 2a02:810d:41bf:ecc8::/64
Apr 26 12:10:21 verne dhcpcd[507]: wlp2s0: adding route to 2a02:810d:41bf:ecc8::/64
Apr 26 12:10:21 verne dhcpcd[508]: wlp2s0: confirming prior DHCPv6 lease
Apr 26 12:10:21 verne dhcpcd[507]: if_route (ADD): File exists
Apr 26 12:10:21 verne dhcpcd[507]: wlp2s0: confirming prior DHCPv6 lease
Apr 26 12:10:21 verne dhcpcd[507]: wlp2s0: adding route to 2a02:810d:41bf:ecc8::/64
Apr 26 12:10:21 verne dhcpcd[507]: wlp2s0: adding default route via fe80::8a71:b1ff:fea7:9363
Apr 26 12:10:21 verne dhcpcd[508]: wlp2s0: adding default route via fe80::8a71:b1ff:fea7:9363
Apr 26 12:10:22 verne dhcpcd[509]: ps_root_recvmsg: Connection refused
Apr 26 12:10:22 verne dhcpcd[508]: wlp2s0: REPLY6 received from fe80::8a71:b1ff:fea7:9363
Apr 26 12:10:22 verne dhcpcd[508]: wlp2s0: adding address 2a02:810d:41bf:ecc8::8564/128
Apr 26 12:10:22 verne dhcpcd[508]: wlp2s0: renew in 0, rebind in 236, expire in 776 seconds
Apr 26 12:10:23 verne dhcpcd[507]: script_runreason: Connection refused
Apr 26 12:10:23 verne dhcpcd[507]: script_runreason: Connection refused
Apr 26 12:10:23 verne dhcpcd[507]: dhcp6_handleifa: Transport endpoint is not connected
Apr 26 12:10:23 verne systemd[1]: Started dhcpcd on wlp2s0.
Apr 26 12:10:23 verne kernel: audit: type=1130 audit(1587895823.029:21): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd@wlp2s0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:23 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd@wlp2s0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:23 verne systemd[1]: Reached target Network.
Apr 26 12:10:23 verne systemd[1]: Reached target Network is Online.
Apr 26 12:10:23 verne systemd[1]: Started proxy name server.
Apr 26 12:10:23 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=pdnsd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:23 verne kernel: audit: type=1130 audit(1587895823.073:22): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=pdnsd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:23 verne systemd[1]: Started OpenSSH Daemon.
Apr 26 12:10:23 verne kernel: audit: type=1130 audit(1587895823.089:23): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sshd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:23 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sshd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:23 verne systemd[1]: Starting Permit User Sessions...
Apr 26 12:10:23 verne systemd[1]: Finished Permit User Sessions.
Apr 26 12:10:23 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-user-sessions comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:23 verne kernel: audit: type=1130 audit(1587895823.166:24): 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'
Apr 26 12:10:23 verne systemd[1]: Started Getty on tty1.
Apr 26 12:10:23 verne audit[1]: 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'
Apr 26 12:10:23 verne systemd[1]: Reached target Login Prompts.
Apr 26 12:10:23 verne kernel: audit: type=1130 audit(1587895823.186:25): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:23 verne systemd[1]: Reached target Multi-User System.
Apr 26 12:10:23 verne systemd[1]: Reached target Graphical Interface.
Apr 26 12:10:23 verne systemd[1]: Startup finished in 14.528s (kernel) + 20.185s (userspace) = 34.713s.
Apr 26 12:10:23 verne pdnsd[565]: * 04/26 12:10:23| pdnsd: info: pdnsd-1.2.9a-par starting.
Apr 26 12:10:23 verne dhcpcd[507]: dhcp6_sendmessage: Transport endpoint is not connected
Apr 26 12:10:23 verne sshd[566]: Server listening on 0.0.0.0 port 22.
Apr 26 12:10:23 verne sshd[566]: Server listening on :: port 22.
Apr 26 12:10:23 verne dhcpcd[507]: arp_probe1: Transport endpoint is not connected
Apr 26 12:10:23 verne dhcpcd[507]: ipv6nd_applyra: Transport endpoint is not connected
Apr 26 12:10:23 verne dhcpcd[507]: ipv6_addaddr1: Transport endpoint is not connected
Apr 26 12:10:23 verne dhcpcd[507]: script_runreason: Transport endpoint is not connected
Apr 26 12:10:23 verne dhcpcd[507]: dhcp6_handleifa: Transport endpoint is not connected
Apr 26 12:10:23 verne dhcpcd[507]: dhcp6_handleifa: Transport endpoint is not connected
Apr 26 12:10:24 verne dhcpcd[508]: wlp2s0: leased 192.168.0.193 for 3600 seconds
Apr 26 12:10:24 verne dhcpcd[508]: wlp2s0: adding route to 192.168.0.0/24
Apr 26 12:10:24 verne dhcpcd[508]: wlp2s0: adding default route via 192.168.0.1
Apr 26 12:10:25 verne kernel: usb 1-3: USB disconnect, device number 2
Apr 26 12:10:25 verne dhcpcd[507]: dhcp6_sendmessage: Transport endpoint is not connected
Apr 26 12:10:25 verne dhcpcd[507]: wlp2s0: leased 192.168.0.193 for 3600 seconds
Apr 26 12:10:25 verne dhcpcd[507]: ipv4_addaddr: if_addaddress: Transport endpoint is not connected
Apr 26 12:10:25 verne audit[507]: ANOM_ABEND auid=4294967295 uid=973 gid=973 ses=4294967295 pid=507 comm="dhcpcd" exe="/usr/bin/dhcpcd" sig=11 res=1
Apr 26 12:10:25 verne kernel: dhcpcd[507]: segfault at 10 ip 00005612182da9eb sp 00007ffd37987a40 error 4 in dhcpcd[5612182a9000+38000]
Apr 26 12:10:25 verne kernel: Code: ff 90 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 d6 8b 7f 3c 31 d2 ff 25 ea b1 01 00 66 90 48 83 ec 58 66 0f ef c0 48 89 d1 <8b> 57 10 64 48 8b 04 25 28 00 00 00 48 89 44 24 48 31 c0 48 8b 47
Apr 26 12:10:25 verne kernel: audit: type=1701 audit(1587895825.583:26): auid=4294967295 uid=973 gid=973 ses=4294967295 pid=507 comm="dhcpcd" exe="/usr/bin/dhcpcd" sig=11 res=1
Apr 26 12:10:25 verne systemd[1]: dhcpcd@wlp2s0.service: Main process exited, code=killed, status=11/SEGV
Apr 26 12:10:25 verne systemd[1]: dhcpcd@wlp2s0.service: Failed with result 'signal'.
Apr 26 12:10:25 verne audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd@wlp2s0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 26 12:10:25 verne kernel: audit: type=1131 audit(1587895825.603:27): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd@wlp2s0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 26 12:10:28 verne audit[570]: USER_AUTH pid=570 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty1 res=success'
Apr 26 12:10:28 verne kernel: audit: type=1100 audit(1587895828.989:28): pid=570 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty1 res=success'
Apr 26 12:10:29 verne kernel: audit: type=1101 audit(1587895829.059:29): pid=570 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty1 res=success'
Apr 26 12:10:29 verne audit[570]: USER_ACCT pid=570 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty1 res=success'
Apr 26 12:10:29 verne audit[570]: CRED_ACQ pid=570 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty1 res=success'
Apr 26 12:10:29 verne kernel: audit: type=1103 audit(1587895829.066:30): pid=570 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty1 res=success'
Apr 26 12:10:29 verne kernel: audit: type=1006 audit(1587895829.066:31): pid=570 uid=0 old-auid=4294967295 auid=1000 tty=tty1 old-ses=4294967295 ses=1 res=1
Apr 26 12:10:29 verne login[570]: pam_unix(login:session): session opened for user sk by LOGIN(uid=0)
Apr 26 12:10:29 verne systemd-logind[469]: New session 1 of user sk.
Apr 26 12:10:29 verne systemd[1]: Created slice User Slice of UID 1000.
Apr 26 12:10:29 verne systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
Apr 26 12:10:29 verne systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
Apr 26 12:10:29 verne systemd[1]: Condition check resulted in First Boot Wizard being skipped.
Apr 26 12:10:29 verne systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Apr 26 12:10:29 verne systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
Apr 26 12:10:29 verne systemd[1]: Condition check resulted in Load Kernel Modules being skipped.
Apr 26 12:10:29 verne systemd[1]: Condition check resulted in FUSE Control File System being skipped.
Apr 26 12:10:29 verne systemd[1]: Starting User Runtime Directory /run/user/1000...
Apr 26 12:10:29 verne systemd[1]: Finished User Runtime Directory /run/user/1000.
Apr 26 12:10:29 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:29 verne kernel: audit: type=1130 audit(1587895829.193:32): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:29 verne systemd[1]: Starting User Manager for UID 1000...
Apr 26 12:10:29 verne audit[743]: USER_ACCT pid=743 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="sk" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:29 verne systemd[743]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[sk] ruser=[<unknown>] rhost=[<unknown>]
Apr 26 12:10:29 verne kernel: audit: type=1101 audit(1587895829.236:33): pid=743 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="sk" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:29 verne kernel: audit: type=1103 audit(1587895829.236:34): pid=743 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="sk" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 26 12:10:29 verne audit[743]: CRED_ACQ pid=743 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="sk" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 26 12:10:29 verne systemd[743]: pam_unix(systemd-user:session): session opened for user sk by (uid=0)
Apr 26 12:10:29 verne audit[743]: USER_START pid=743 uid=0 auid=1000 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="sk" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:29 verne audit: AUDIT1334 prog-id=9 op=LOAD
Apr 26 12:10:29 verne audit: AUDIT1334 prog-id=9 op=UNLOAD
Apr 26 12:10:29 verne systemd[743]: Reached target Paths.
Apr 26 12:10:29 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:10:29 verne audit[570]: USER_START pid=570 uid=0 auid=1000 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="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty1 res=success'
Apr 26 12:10:29 verne audit[570]: CRED_REFR pid=570 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty1 res=success'
Apr 26 12:10:29 verne systemd[743]: Reached target Timers.
Apr 26 12:10:29 verne login[570]: LOGIN ON tty1 BY sk
Apr 26 12:10:29 verne systemd[743]: Starting D-Bus User Message Bus Socket.
Apr 26 12:10:29 verne systemd[743]: dirmngr.socket: Socket service dirmngr.service not loaded, refusing.
Apr 26 12:10:30 verne ssh-agent[760]: SSH_AUTH_SOCK=/run/user/1000/ssh-agent.socket; export SSH_AUTH_SOCK;
Apr 26 12:10:30 verne ssh-agent[760]: echo Agent pid 760;
Apr 26 12:10:29 verne systemd[743]: Failed to listen on GnuPG network certificate management daemon.
Apr 26 12:10:29 verne systemd[743]: gpg-agent-browser.socket: Socket service gpg-agent.service not loaded, refusing.
Apr 26 12:10:29 verne systemd[743]: Failed to listen on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 26 12:10:29 verne systemd[743]: gpg-agent-extra.socket: Socket service gpg-agent.service not loaded, refusing.
Apr 26 12:10:29 verne systemd[743]: Failed to listen on GnuPG cryptographic agent and passphrase cache (restricted).
Apr 26 12:10:29 verne systemd[743]: gpg-agent-ssh.socket: Socket service gpg-agent.service not loaded, refusing.
Apr 26 12:10:29 verne systemd[743]: Failed to listen on GnuPG cryptographic agent (ssh-agent emulation).
Apr 26 12:10:29 verne systemd[743]: gpg-agent.socket: Socket service gpg-agent.service not loaded, refusing.
Apr 26 12:10:29 verne systemd[743]: Failed to listen on GnuPG cryptographic agent and passphrase cache.
Apr 26 12:10:29 verne systemd[743]: Listening on p11-kit server.
Apr 26 12:10:29 verne systemd[743]: Listening on Sound System.
Apr 26 12:10:29 verne systemd[743]: Listening on D-Bus User Message Bus Socket.
Apr 26 12:10:29 verne systemd[743]: Reached target Sockets.
Apr 26 12:10:29 verne systemd[743]: Reached target Basic System.
Apr 26 12:10:29 verne systemd[1]: Started User Manager for UID 1000.
Apr 26 12:10:29 verne systemd[1]: Started Session 1 of user sk.
Apr 26 12:10:29 verne systemd[743]: Starting Delete old files under ~/grabber...
Apr 26 12:10:29 verne systemd[743]: Started SSH agent.
Apr 26 12:10:29 verne systemd[743]: cleanup-downloads.service: Succeeded.
Apr 26 12:10:29 verne systemd[743]: Finished Delete old files under ~/grabber.
Apr 26 12:10:29 verne systemd[743]: Reached target Main User Target.
Apr 26 12:10:29 verne systemd[743]: Startup finished in 719ms.
Apr 26 12:10:36 verne systemd[743]: Started D-Bus User Message Bus.
Apr 26 12:11:08 verne systemd[1]: Started Getty on tty2.
Apr 26 12:11:08 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:11:08 verne kernel: kauditd_printk_skb: 7 callbacks suppressed
Apr 26 12:11:08 verne kernel: audit: type=1130 audit(1587895868.296:42): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:11:12 verne audit[959]: USER_AUTH pid=959 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty2 res=success'
Apr 26 12:11:12 verne kernel: audit: type=1100 audit(1587895872.756:43): pid=959 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty2 res=success'
Apr 26 12:11:12 verne audit[959]: USER_ACCT pid=959 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty2 res=success'
Apr 26 12:11:12 verne kernel: audit: type=1101 audit(1587895872.816:44): pid=959 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty2 res=success'
Apr 26 12:11:12 verne audit[959]: CRED_ACQ pid=959 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty2 res=success'
Apr 26 12:11:12 verne kernel: audit: type=1103 audit(1587895872.822:45): pid=959 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty2 res=success'
Apr 26 12:11:12 verne kernel: audit: type=1006 audit(1587895872.822:46): pid=959 uid=0 old-auid=4294967295 auid=1000 tty=tty2 old-ses=4294967295 ses=3 res=1
Apr 26 12:11:12 verne login[959]: pam_unix(login:session): session opened for user sk by LOGIN(uid=0)
Apr 26 12:11:12 verne systemd-logind[469]: New session 3 of user sk.
Apr 26 12:11:12 verne systemd[1]: Started Session 3 of user sk.
Apr 26 12:11:12 verne audit[959]: USER_START pid=959 uid=0 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty2 res=success'
Apr 26 12:11:12 verne audit[959]: CRED_REFR pid=959 uid=0 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty2 res=success'
Apr 26 12:11:12 verne kernel: audit: type=1105 audit(1587895872.889:47): pid=959 uid=0 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty2 res=success'
Apr 26 12:11:12 verne kernel: audit: type=1110 audit(1587895872.889:48): pid=959 uid=0 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty2 res=success'
Apr 26 12:11:12 verne login[959]: LOGIN ON tty2 BY sk
Apr 26 12:12:25 verne kernel: perf: interrupt took too long (2517 > 2500), lowering kernel.perf_event_max_sample_rate to 79200
Apr 26 12:13:17 verne kernel: perf: interrupt took too long (3163 > 3146), lowering kernel.perf_event_max_sample_rate to 63000
Apr 26 12:13:17 verne systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
Apr 26 12:13:17 verne systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
Apr 26 12:13:17 verne systemd[1]: Condition check resulted in First Boot Wizard being skipped.
Apr 26 12:13:17 verne systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Apr 26 12:13:17 verne systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
Apr 26 12:13:17 verne systemd[1]: Condition check resulted in Load Kernel Modules being skipped.
Apr 26 12:13:17 verne systemd[1]: Condition check resulted in FUSE Control File System being skipped.
Apr 26 12:13:17 verne systemd[1]: Started Getty on tty3.
Apr 26 12:13:17 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty3 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:13:17 verne kernel: audit: type=1130 audit(1587895997.708:49): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty3 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:13:22 verne audit[1477]: USER_AUTH pid=1477 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:13:22 verne kernel: audit: type=1100 audit(1587896002.078:50): pid=1477 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:13:22 verne audit[1477]: USER_ACCT pid=1477 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:13:22 verne kernel: audit: type=1101 audit(1587896002.138:51): pid=1477 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:13:22 verne audit[1477]: CRED_ACQ pid=1477 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:13:22 verne kernel: audit: type=1103 audit(1587896002.145:52): pid=1477 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:13:22 verne kernel: audit: type=1006 audit(1587896002.145:53): pid=1477 uid=0 old-auid=4294967295 auid=1000 tty=tty3 old-ses=4294967295 ses=4 res=1
Apr 26 12:13:22 verne login[1477]: pam_unix(login:session): session opened for user sk by LOGIN(uid=0)
Apr 26 12:13:22 verne systemd-logind[469]: New session 4 of user sk.
Apr 26 12:13:22 verne systemd[1]: Started Session 4 of user sk.
Apr 26 12:13:22 verne audit[1477]: USER_START pid=1477 uid=0 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:13:22 verne kernel: audit: type=1105 audit(1587896002.208:54): pid=1477 uid=0 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:13:22 verne kernel: audit: type=1110 audit(1587896002.212:55): pid=1477 uid=0 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:13:22 verne audit[1477]: CRED_REFR pid=1477 uid=0 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:13:22 verne login[1477]: LOGIN ON tty3 BY sk
Apr 26 12:13:39 verne audit[1518]: USER_AUTH pid=1518 uid=1000 auid=1000 ses=4 msg='op=PAM:authentication grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:13:39 verne kernel: audit: type=1100 audit(1587896019.458:56): pid=1518 uid=1000 auid=1000 ses=4 msg='op=PAM:authentication grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:13:39 verne audit[1518]: USER_ACCT pid=1518 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:13:39 verne su[1518]: (to root) sk on tty3
Apr 26 12:13:39 verne kernel: audit: type=1101 audit(1587896019.462:57): pid=1518 uid=1000 auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:13:39 verne kernel: audit: type=1103 audit(1587896019.465:58): pid=1518 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:13:39 verne kernel: audit: type=1105 audit(1587896019.465:59): pid=1518 uid=1000 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:13:39 verne audit[1518]: CRED_ACQ pid=1518 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:13:39 verne audit[1518]: USER_START pid=1518 uid=1000 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:13:39 verne su[1518]: pam_unix(su:session): session opened for user root by sk(uid=1000)
Apr 26 12:14:18 verne dhcpcd[508]: wlp2s0: rebinding prior DHCPv6 lease
Apr 26 12:14:36 verne kernel: perf: interrupt took too long (3975 > 3953), lowering kernel.perf_event_max_sample_rate to 50100
Apr 26 12:16:24 verne kernel: perf: interrupt took too long (4980 > 4968), lowering kernel.perf_event_max_sample_rate to 39900
Apr 26 12:16:24 verne sshd[2127]: Connection closed by ::1 port 35900 [preauth]
Apr 26 12:17:30 verne audit[2360]: USER_ACCT pid=2360 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="sk" exe="/usr/bin/sshd" hostname=192.168.0.51 addr=192.168.0.51 terminal=ssh res=success'
Apr 26 12:17:30 verne kernel: audit: type=1101 audit(1587896250.974:60): pid=2360 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="sk" exe="/usr/bin/sshd" hostname=192.168.0.51 addr=192.168.0.51 terminal=ssh res=success'
Apr 26 12:17:30 verne sshd[2360]: Accepted publickey for sk from 192.168.0.51 port 53810 ssh2: RSA SHA256:Rfkn+jb0T5z3zlCsyJ8MwVr6hP5M3G0BWHyi4KPdy5Q
Apr 26 12:17:30 verne kernel: audit: type=1103 audit(1587896250.980:61): pid=2360 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_env acct="sk" exe="/usr/bin/sshd" hostname=192.168.0.51 addr=192.168.0.51 terminal=ssh res=success'
Apr 26 12:17:30 verne kernel: audit: type=1006 audit(1587896250.984:62): pid=2360 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=5 res=1
Apr 26 12:17:30 verne audit[2360]: CRED_ACQ pid=2360 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_env acct="sk" exe="/usr/bin/sshd" hostname=192.168.0.51 addr=192.168.0.51 terminal=ssh res=success'
Apr 26 12:17:30 verne sshd[2360]: pam_unix(sshd:session): session opened for user sk by (uid=0)
Apr 26 12:17:31 verne systemd-logind[469]: New session 5 of user sk.
Apr 26 12:17:31 verne systemd[1]: Started Session 5 of user sk.
Apr 26 12:17:31 verne audit[2360]: USER_START pid=2360 uid=0 auid=1000 ses=5 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="sk" exe="/usr/bin/sshd" hostname=192.168.0.51 addr=192.168.0.51 terminal=ssh res=success'
Apr 26 12:17:31 verne kernel: audit: type=1105 audit(1587896251.044:63): pid=2360 uid=0 auid=1000 ses=5 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="sk" exe="/usr/bin/sshd" hostname=192.168.0.51 addr=192.168.0.51 terminal=ssh res=success'
Apr 26 12:17:31 verne audit[2362]: CRED_ACQ pid=2362 uid=0 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_env acct="sk" exe="/usr/bin/sshd" hostname=192.168.0.51 addr=192.168.0.51 terminal=ssh res=success'
Apr 26 12:17:31 verne kernel: audit: type=1103 audit(1587896251.054:64): pid=2362 uid=0 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_env acct="sk" exe="/usr/bin/sshd" hostname=192.168.0.51 addr=192.168.0.51 terminal=ssh res=success'
Apr 26 12:17:31 verne sshd[2360]: error: openpty: No such file or directory
Apr 26 12:17:31 verne sshd[2362]: error: session_pty_req: session 0 alloc failed
Apr 26 12:18:30 verne systemd[1]: Reloading.
Apr 26 12:18:30 verne audit: AUDIT1334 prog-id=8 op=UNLOAD
Apr 26 12:18:30 verne kernel: audit: type=1334 audit(1587896310.960:65): prog-id=8 op=UNLOAD
Apr 26 12:18:30 verne kernel: audit: type=1334 audit(1587896310.960:66): prog-id=7 op=UNLOAD
Apr 26 12:18:30 verne audit: AUDIT1334 prog-id=7 op=UNLOAD
Apr 26 12:18:30 verne audit: AUDIT1334 prog-id=6 op=UNLOAD
Apr 26 12:18:30 verne kernel: audit: type=1334 audit(1587896310.990:67): prog-id=6 op=UNLOAD
Apr 26 12:18:30 verne kernel: audit: type=1334 audit(1587896310.990:68): prog-id=5 op=UNLOAD
Apr 26 12:18:30 verne audit: AUDIT1334 prog-id=5 op=UNLOAD
Apr 26 12:18:31 verne audit: AUDIT1334 prog-id=4 op=UNLOAD
Apr 26 12:18:31 verne kernel: audit: type=1334 audit(1587896311.020:69): prog-id=4 op=UNLOAD
Apr 26 12:18:31 verne kernel: audit: type=1334 audit(1587896311.023:70): prog-id=3 op=UNLOAD
Apr 26 12:18:31 verne audit: AUDIT1334 prog-id=3 op=UNLOAD
Apr 26 12:18:31 verne audit: AUDIT1334 prog-id=10 op=LOAD
Apr 26 12:18:31 verne kernel: audit: type=1334 audit(1587896311.583:71): prog-id=10 op=LOAD
Apr 26 12:18:31 verne kernel: audit: type=1334 audit(1587896311.587:72): prog-id=11 op=LOAD
Apr 26 12:18:31 verne audit: AUDIT1334 prog-id=11 op=LOAD
Apr 26 12:18:31 verne audit: AUDIT1334 prog-id=12 op=LOAD
Apr 26 12:18:31 verne kernel: audit: type=1334 audit(1587896311.637:73): prog-id=12 op=LOAD
Apr 26 12:18:31 verne kernel: audit: type=1334 audit(1587896311.637:74): prog-id=13 op=LOAD
Apr 26 12:18:31 verne audit: AUDIT1334 prog-id=13 op=LOAD
Apr 26 12:18:31 verne audit: AUDIT1334 prog-id=14 op=LOAD
Apr 26 12:18:31 verne audit: AUDIT1334 prog-id=15 op=LOAD
Apr 26 12:18:47 verne systemd[1]: Stopping Session 1 of user sk.
Apr 26 12:18:47 verne systemd[1]: Stopping Session 3 of user sk.
Apr 26 12:18:48 verne kernel: kauditd_printk_skb: 2 callbacks suppressed
Apr 26 12:18:48 verne kernel: audit: type=1106 audit(1587896327.797:77): pid=1518 uid=1000 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:18:48 verne kernel: audit: type=1104 audit(1587896327.797:78): pid=1518 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:18:48 verne kernel: audit: type=1106 audit(1587896327.830:79): pid=2360 uid=0 auid=1000 ses=5 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="sk" exe="/usr/bin/sshd" hostname=192.168.0.51 addr=192.168.0.51 terminal=ssh res=success'
Apr 26 12:18:48 verne kernel: audit: type=1104 audit(1587896327.833:80): pid=2360 uid=0 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_env acct="sk" exe="/usr/bin/sshd" hostname=192.168.0.51 addr=192.168.0.51 terminal=ssh res=success'
Apr 26 12:18:48 verne kernel: audit: type=1131 audit(1587896327.953:81): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sshd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:18:47 verne audit[1518]: USER_END pid=1518 uid=1000 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:18:48 verne kernel: audit: type=1104 audit(1587896328.400:82): pid=959 uid=0 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty2 res=success'
Apr 26 12:18:48 verne kernel: audit: type=1104 audit(1587896328.407:83): pid=1477 uid=0 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:18:48 verne kernel: audit: type=1106 audit(1587896328.410:84): pid=959 uid=0 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty2 res=success'
Apr 26 12:18:47 verne audit[1518]: CRED_DISP pid=1518 uid=1000 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:18:47 verne audit[2360]: USER_END pid=2360 uid=0 auid=1000 ses=5 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="sk" exe="/usr/bin/sshd" hostname=192.168.0.51 addr=192.168.0.51 terminal=ssh res=success'
Apr 26 12:18:47 verne audit[2360]: CRED_DISP pid=2360 uid=0 auid=1000 ses=5 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_env acct="sk" exe="/usr/bin/sshd" hostname=192.168.0.51 addr=192.168.0.51 terminal=ssh res=success'
Apr 26 12:18:47 verne audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sshd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:18:48 verne audit[959]: CRED_DISP pid=959 uid=0 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty2 res=success'
Apr 26 12:18:48 verne audit[1477]: CRED_DISP pid=1477 uid=0 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:18:48 verne audit[959]: USER_END pid=959 uid=0 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty2 res=success'
Apr 26 12:18:47 verne systemd[1]: Stopping Session 4 of user sk.
Apr 26 12:18:47 verne su[1518]: pam_unix(su:session): session closed for user root
Apr 26 12:18:48 verne pdnsd[565]: * 04/26 12:18:48| pdnsd: warning: Caught signal 15. Exiting.
Apr 26 12:18:48 verne audit[1477]: USER_END pid=1477 uid=0 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:18:47 verne systemd[1]: Stopping Session 5 of user sk.
Apr 26 12:18:48 verne kernel: audit: type=1106 audit(1587896328.433:85): pid=1477 uid=0 auid=1000 ses=4 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty3 res=success'
Apr 26 12:18:47 verne sshd[2360]: pam_unix(sshd:session): session closed for user sk
Apr 26 12:18:47 verne systemd[1]: Removed slice system-dhcpcd.slice.
Apr 26 12:18:47 verne sshd[566]: Received signal 15; terminating.
Apr 26 12:18:47 verne systemd[1]: Removed slice system-modprobe.slice.
Apr 26 12:18:48 verne login[959]: pam_unix(login:session): session closed for user sk
Apr 26 12:18:47 verne systemd[1]: Stopped target Graphical Interface.
Apr 26 12:18:48 verne login[1477]: pam_unix(login:session): session closed for user sk
Apr 26 12:18:48 verne kernel: audit: type=1131 audit(1587896328.443:86): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:18:48 verne audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:18:47 verne systemd[1]: Stopped target Multi-User System.
Apr 26 12:18:47 verne systemd[1]: Stopped target Login Prompts.
Apr 26 12:18:47 verne systemd[1]: Stopped target Sound Card.
Apr 26 12:18:47 verne systemd[1]: Stopped target Timers.
Apr 26 12:18:47 verne systemd[1]: man-db.timer: Succeeded.
Apr 26 12:18:47 verne systemd[1]: Stopped Daily man-db regeneration.
Apr 26 12:18:47 verne systemd[1]: shadow.timer: Succeeded.
Apr 26 12:18:47 verne systemd[1]: Stopped Daily verification of password and group files.
Apr 26 12:18:47 verne systemd[1]: systemd-tmpfiles-clean.timer: Succeeded.
Apr 26 12:18:47 verne systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Apr 26 12:18:47 verne systemd[1]: updatedb.timer: Succeeded.
Apr 26 12:18:47 verne systemd[1]: Stopped Daily locate database update.
Apr 26 12:18:47 verne systemd[1]: systemd-rfkill.socket: Succeeded.
Apr 26 12:18:47 verne systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Apr 26 12:18:47 verne systemd[1]: Stopping Getty on tty1...
Apr 26 12:18:47 verne systemd[1]: Stopping Getty on tty2...
Apr 26 12:18:47 verne systemd[1]: Stopping Getty on tty3...
Apr 26 12:18:47 verne systemd[1]: Starting Generate shutdown-ramfs...
Apr 26 12:18:47 verne systemd[1]: Stopping proxy name server...
Apr 26 12:18:47 verne systemd[1]: Stopping OpenSSH Daemon...
Apr 26 12:18:47 verne systemd[1]: Stopping Load/Save Random Seed...
Apr 26 12:18:47 verne systemd[1]: sshd.service: Succeeded.
Apr 26 12:18:47 verne systemd[1]: Stopped OpenSSH Daemon.
Apr 26 12:18:47 verne systemd[1]: session-5.scope: Succeeded.
Apr 26 12:18:47 verne systemd[1]: Stopped Session 5 of user sk.
Apr 26 12:18:47 verne systemd-logind[469]: Session 5 logged out. Waiting for processes to exit.
Apr 26 12:18:48 verne systemd-logind[469]: Removed session 5.
Apr 26 12:18:48 verne systemd[1]: getty@tty2.service: Succeeded.
Apr 26 12:18:48 verne systemd[1]: Stopped Getty on tty2.
Apr 26 12:18:48 verne systemd[1]: pdnsd.service: Succeeded.
Apr 26 12:18:48 verne systemd[1]: Stopped proxy name server.
Apr 26 12:18:48 verne audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=pdnsd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:18:48 verne systemd[1]: getty@tty3.service: Succeeded.
Apr 26 12:18:48 verne systemd[1]: Stopped Getty on tty3.
Apr 26 12:18:48 verne audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty3 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:18:48 verne systemd[1]: session-3.scope: Succeeded.
Apr 26 12:18:48 verne systemd[1]: Stopped Session 3 of user sk.
Apr 26 12:18:48 verne systemd-logind[469]: Session 3 logged out. Waiting for processes to exit.
Apr 26 12:18:48 verne systemd[1]: Stopped target Network is Online.
Apr 26 12:18:48 verne systemd-logind[469]: Session 4 logged out. Waiting for processes to exit.
Apr 26 12:18:48 verne systemd-logind[469]: Removed session 3.
Apr 26 12:18:48 verne systemd[1]: systemd-random-seed.service: Succeeded.
Apr 26 12:18:48 verne systemd[1]: Stopped Load/Save Random Seed.
Apr 26 12:18:48 verne audit[1]: SERVICE_STOP 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'
Apr 26 12:18:48 verne mkinitcpio[2649]: ==> Starting build: none
Apr 26 12:18:48 verne mkinitcpio[2649]:   -> Running build hook: [sd-shutdown]
Apr 26 12:18:48 verne audit[570]: CRED_DISP pid=570 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty1 res=success'
Apr 26 12:18:48 verne login[570]: pam_unix(login:session): session closed for user sk
Apr 26 12:18:48 verne audit[570]: USER_END pid=570 uid=0 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="sk" exe="/usr/bin/login" hostname=verne addr=? terminal=tty1 res=success'
Apr 26 12:18:48 verne systemd[1]: session-1.scope: Succeeded.
Apr 26 12:18:48 verne systemd-logind[469]: Session 1 logged out. Waiting for processes to exit.
Apr 26 12:18:48 verne systemd[1]: Stopped Session 1 of user sk.
Apr 26 12:18:48 verne systemd[1]: getty@tty1.service: Succeeded.
Apr 26 12:18:48 verne systemd[1]: Stopped Getty on tty1.
Apr 26 12:18:48 verne audit[1]: 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'
Apr 26 12:18:48 verne systemd[1]: Removed slice system-getty.slice.
Apr 26 12:18:48 verne systemd-logind[469]: Removed session 1.
Apr 26 12:18:49 verne mkinitcpio[2649]: ==> Build complete.
Apr 26 12:18:49 verne systemd[1]: mkinitcpio-generate-shutdown-ramfs.service: Succeeded.
Apr 26 12:18:49 verne systemd[1]: Finished Generate shutdown-ramfs.
Apr 26 12:18:49 verne audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=mkinitcpio-generate-shutdown-ramfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:18:49 verne audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=mkinitcpio-generate-shutdown-ramfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:18:49 verne systemd[1]: session-4.scope: Succeeded.
Apr 26 12:18:49 verne systemd[1]: Stopped Session 4 of user sk.
Apr 26 12:18:49 verne systemd[1]: Stopping Login Service...
Apr 26 12:18:49 verne systemd[1]: Stopping User Manager for UID 1000...
Apr 26 12:18:49 verne systemd[743]: Stopped target Main User Target.
Apr 26 12:18:49 verne systemd-logind[469]: Removed session 4.
Apr 26 12:18:49 verne systemd[743]: Stopping D-Bus User Message Bus...
Apr 26 12:18:49 verne systemd[743]: Stopping SSH agent...
Apr 26 12:18:49 verne systemd[743]: ssh-agent.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 26 12:18:49 verne systemd[743]: ssh-agent.service: Failed with result 'exit-code'.
Apr 26 12:18:49 verne systemd[743]: Stopped SSH agent.
Apr 26 12:18:49 verne systemd[743]: dbus.service: Succeeded.
Apr 26 12:18:49 verne systemd[743]: Stopped D-Bus User Message Bus.
Apr 26 12:18:49 verne systemd[743]: Stopped target Basic System.
Apr 26 12:18:49 verne systemd[743]: Stopped target Paths.
Apr 26 12:18:49 verne systemd[743]: Stopped target Sockets.
Apr 26 12:18:49 verne systemd[743]: Stopped target Timers.
Apr 26 12:18:49 verne systemd[743]: dbus.socket: Succeeded.
Apr 26 12:18:49 verne systemd[743]: Closed D-Bus User Message Bus Socket.
Apr 26 12:18:49 verne systemd[743]: p11-kit-server.socket: Succeeded.
Apr 26 12:18:49 verne systemd[743]: Closed p11-kit server.
Apr 26 12:18:49 verne systemd[743]: pulseaudio.socket: Succeeded.
Apr 26 12:18:49 verne systemd[743]: Closed Sound System.
Apr 26 12:18:49 verne systemd[743]: Reached target Shutdown.
Apr 26 12:18:49 verne systemd[743]: systemd-exit.service: Succeeded.
Apr 26 12:18:49 verne systemd[743]: Finished Exit the Session.
Apr 26 12:18:49 verne systemd[743]: Reached target Exit the Session.
Apr 26 12:18:49 verne systemd[744]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[sk] ruser=[<unknown>] rhost=[<unknown>]
Apr 26 12:18:49 verne systemd[1]: user@1000.service: Succeeded.
Apr 26 12:18:49 verne audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:18:49 verne systemd[1]: Stopped User Manager for UID 1000.
Apr 26 12:18:49 verne systemd[1]: Stopping User Runtime Directory /run/user/1000...
Apr 26 12:18:49 verne systemd[1]: run-user-1000.mount: Succeeded.
Apr 26 12:18:49 verne systemd[1]: Unmounted /run/user/1000.
Apr 26 12:18:49 verne systemd[1]: user-runtime-dir@1000.service: Succeeded.
Apr 26 12:18:49 verne systemd[1]: Stopped User Runtime Directory /run/user/1000.
Apr 26 12:18:49 verne audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:18:49 verne systemd[1]: Removed slice User Slice of UID 1000.
Apr 26 12:18:49 verne systemd[1]: Stopping D-Bus System Message Bus...
Apr 26 12:18:49 verne systemd[1]: Stopping Permit User Sessions...
Apr 26 12:18:49 verne systemd[1]: dbus.service: Succeeded.
Apr 26 12:18:49 verne systemd[1]: Stopped D-Bus System Message Bus.
Apr 26 12:18:49 verne audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:18:49 verne systemd[1]: systemd-user-sessions.service: Succeeded.
Apr 26 12:18:50 verne systemd[1]: Stopped Permit User Sessions.
Apr 26 12:18:50 verne audit[1]: SERVICE_STOP 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'
Apr 26 12:18:50 verne systemd[1]: Stopped target Network.
Apr 26 12:18:50 verne systemd[1]: Stopped target Remote File Systems.
Apr 26 12:18:50 verne systemd[1]: Stopping dhcpcd on all interfaces...
Apr 26 12:18:50 verne systemd[1]: Stopping WPA supplicant daemon (interface-specific version)...
Apr 26 12:18:50 verne kernel: wlp2s0: deauthenticating from 88:71:b1:a7:93:61 by local choice (Reason: 3=DEAUTH_LEAVING)
Apr 26 12:18:50 verne wpa_supplicant[470]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=88:71:b1:a7:93:61 reason=3 locally_generated=1
Apr 26 12:18:50 verne dhcpcd[508]: wlp2s0: carrier lost
Apr 26 12:18:50 verne dhcpcd[2776]: dhcpcd not running
Apr 26 12:18:50 verne systemd[1]: dhcpcd.service: Control process exited, code=exited, status=1/FAILURE
Apr 26 12:18:50 verne dhcpcd[2776]: dhcpcd not running
Apr 26 12:18:50 verne dhcpcd[508]: wlp2s0: deleting address 2a02:810d:41bf:ecc8::8564/128
Apr 26 12:18:50 verne dhcpcd[511]: process 511 unexpectedly terminating on signal 15
Apr 26 12:18:50 verne wpa_supplicant[470]: nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
Apr 26 12:18:50 verne systemd[1]: systemd-logind.service: Succeeded.
Apr 26 12:18:50 verne systemd[1]: Stopped Login Service.
Apr 26 12:18:50 verne audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:18:50 verne audit: AUDIT1334 prog-id=15 op=UNLOAD
Apr 26 12:18:50 verne audit: AUDIT1334 prog-id=14 op=UNLOAD
Apr 26 12:18:50 verne wpa_supplicant[470]: wlp2s0: CTRL-EVENT-TERMINATING
Apr 26 12:18:50 verne systemd[1]: wpa_supplicant@wlp2s0.service: Succeeded.
Apr 26 12:18:50 verne systemd[1]: Stopped WPA supplicant daemon (interface-specific version).
Apr 26 12:18:50 verne audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=wpa_supplicant@wlp2s0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 12:18:50 verne systemd[1]: Removed slice system-wpa_supplicant.slice.
Apr 26 12:18:50 verne kernel: usb 1-3: new high-speed USB device number 4 using ehci-pci
Apr 26 12:18:51 verne kernel: usb 1-3: New USB device found, idVendor=090c, idProduct=1000, bcdDevice=11.00
Apr 26 12:18:51 verne kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 26 12:18:51 verne kernel: usb 1-3: Product: USB Flash Disk
Apr 26 12:18:51 verne kernel: usb 1-3: Manufacturer: General
Apr 26 12:18:51 verne kernel: usb 1-3: SerialNumber: 0414070000000275
Apr 26 12:18:51 verne kernel: usb-storage 1-3:1.0: USB Mass Storage device detected
Apr 26 12:18:51 verne kernel: usb-storage 1-3:1.0: Quirks match for vid 090c pid 1000: 400
Apr 26 12:18:51 verne kernel: scsi host4: usb-storage 1-3:1.0
Apr 26 12:18:52 verne kernel: scsi 4:0:0:0: Direct-Access     General  USB Flash Disk   1100 PQ: 0 ANSI: 4
Apr 26 12:18:52 verne kernel: sd 4:0:0:0: [sdb] 7864320 512-byte logical blocks: (4.03 GB/3.75 GiB)
Apr 26 12:18:52 verne kernel: sd 4:0:0:0: [sdb] Write Protect is off
Apr 26 12:18:52 verne kernel: sd 4:0:0:0: [sdb] Mode Sense: 43 00 00 00
Apr 26 12:18:52 verne kernel: sd 4:0:0:0: [sdb] No Caching mode page found
Apr 26 12:18:52 verne kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Apr 26 12:18:52 verne kernel:  sdb: sdb1 sdb2
Apr 26 12:18:52 verne kernel: sd 4:0:0:0: [sdb] Attached SCSI removable disk
Apr 26 12:19:19 verne kernel: perf: interrupt took too long (6238 > 6225), lowering kernel.perf_event_max_sample_rate to 31800
Apr 26 12:19:48 verne systemd[1]: Received SIGINT.
Apr 26 12:19:48 verne systemd[1]: Condition check resulted in Generate shutdown-ramfs being skipped.
Apr 26 12:19:48 verne systemd[1]: Received SIGINT.
Apr 26 12:19:48 verne systemd[1]: Condition check resulted in Generate shutdown-ramfs being skipped.
Apr 26 12:19:48 verne kernel: kauditd_printk_skb: 16 callbacks suppressed
Apr 26 12:19:48 verne kernel: audit: type=1334 audit(1587896388.793:103): prog-id=13 op=UNLOAD
Apr 26 12:19:48 verne kernel: audit: type=1334 audit(1587896388.793:104): prog-id=12 op=UNLOAD
Apr 26 12:19:48 verne kernel: audit: type=1334 audit(1587896388.800:105): prog-id=11 op=UNLOAD
Apr 26 12:19:48 verne kernel: audit: type=1334 audit(1587896388.803:106): prog-id=10 op=UNLOAD
Apr 26 12:19:48 verne systemd-shutdown[1]: Syncing filesystems and block devices.
Apr 26 12:19:48 verne audit: AUDIT1334 prog-id=13 op=UNLOAD
Apr 26 12:19:48 verne audit: AUDIT1334 prog-id=12 op=UNLOAD
Apr 26 12:19:48 verne audit: AUDIT1334 prog-id=11 op=UNLOAD
Apr 26 12:19:48 verne audit: AUDIT1334 prog-id=10 op=UNLOAD
Apr 26 12:19:48 verne systemd[1]: Received SIGINT.
Apr 26 12:19:48 verne systemd[1]: Condition check resulted in Generate shutdown-ramfs being skipped.
Apr 26 12:19:48 verne systemd[1]: Received SIGINT.
Apr 26 12:19:48 verne systemd[1]: Condition check resulted in Generate shutdown-ramfs being skipped.
Apr 26 12:19:48 verne systemd[1]: Received SIGINT.
Apr 26 12:19:48 verne systemd[1]: Condition check resulted in Generate shutdown-ramfs being skipped.
Apr 26 12:19:48 verne systemd[1]: Received SIGINT.
Apr 26 12:19:48 verne systemd[1]: Condition check resulted in Generate shutdown-ramfs being skipped.
Apr 26 12:19:48 verne systemd[1]: Received SIGINT.
Apr 26 12:19:48 verne systemd[1]: Condition check resulted in Generate shutdown-ramfs being skipped.
Apr 26 12:19:48 verne systemd[1]: Received SIGINT.
Apr 26 12:19:48 verne systemd[1]: Forcibly rebooting: Ctrl-Alt-Del was pressed more than 7 times within 2s
Apr 26 12:19:48 verne systemd[1]: Shutting down.
Apr 26 12:19:49 verne systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Apr 26 12:19:49 verne systemd-journald[394]: Journal stopped

Offline

#8 2020-04-26 13:00:40

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,523
Website

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

stefan wrote:

Am I wrong with that assumption?

Nope, you're absolutely right about what should happen and about where the problem lies.

stefan wrote:

If such independence can be expressed, I'd assume a mistake in the `systemd` config, which leads to the described dependency on `dhcpcd`.

Agreed.  This can certainly be well managed with systemd.  The default service files, however, are often rather ridiculous.  So much so that our wiki is loaded with recommended changes, like one for an unrelated issue with the default dhcpcd service file here.

stefan wrote:

who would be the right one to address about this issue?

You.  It's your system tongue

I say that only half facetiously.  You are expected to configure your arch system the way you want it.  Very little comes configured "out of the box".  That said, I'd argue there is a difference between having something ship from the repos unconfigured and coming configured in a way that is prone to breakage.  When a compelling case can be made that the latter is happening, that should be addressed to the packager of the arch package.

---

stefan wrote:
V1del wrote:

If you have a networking daemon that borks configuration here things will start to fail

I see your point.

Do you, really?  I certainly don't - I completely disagree on this point, and I think it's an important disagreement.  A modular system that becomes completely unstable or unusable because a single component has failed is a sign of a very bad design.  Linux (the OS ecosystem not just the kernel) is not so badly designed.  Do not accept components* that make such fragile and horrible design choices to become normalized and acceptable.  This is not a necessary limitation of the software or technology, but it is the result of a monopolistic system that results in people saying "that's just the way it is now."  Expect better.

*note: for clarity dhcpcd is not a fragile component.  Quite the opposite.  I find it to be a great example of solid reliable software engineering.  Systemd is also not the fragile component here ... while I'm not so much of a fan of it, there is no blame to cast it's way right now (except perhaps to the degree that it's workings facilitate poorly designed configurations).  But poorly written service files, units, and targets are absolutely to blame.

Last edited by Trilby (2020-04-26 13:09:05)


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#9 2020-04-26 13:54:35

seth
Member
Registered: 2012-09-03
Posts: 51,046

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

Apr 26 12:10:17 verne systemd[1]: Starting dhcpcd on all interfaces...
Apr 26 12:10:17 verne systemd[1]: Starting dhcpcd on wlp2s0...
…
Apr 26 12:10:17 verne dhcpcd[468]: dhcpcd-9.0.2 starting
…
Apr 26 12:10:17 verne dhcpcd[467]: dhcpcd-9.0.2 starting
…
… dhcpcd@wlp2s0.service…

It very much looks like you've two dhcpcd services enabled, one on the wifi NIC and one general one for all interfaces.
They'll probably trip overeach other and multiple network controlling services per NIC isn't supported at all (see the networking wiki)

=> Remove that condition and see whether you still have issues with an up-to-date dhcpcd.

Offline

#10 2020-04-28 09:13:15

stefan
Member
Registered: 2013-03-22
Posts: 104

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

seth wrote:

It very much looks like you've two dhcpcd services enabled, one on the wifi NIC and one general one for all interfaces.

Well spotted, removing the `dhcpcd` for `wlp2s0` resolved the issue. Thank you very much for pointing this out.

V1del wrote:

You also have to differentiate between "failed to boot" and "my graphical environment didn't come up" I do suspect had you booted with systemd.unit=multi-user.target you should've been able to reliably get a system up.

Yes, I'm very well aware of that.  I always boot into text mode.  I'm still surprised about the adverse effects my misconfiguration of `dhcpcd` had.  Unfortunately, while I was able to reproducibly trigger them with up- and downgrading of `dhcpcd`, I cannot, now, reproduce them with enabling/disabling of `dhcpcd@wlp2s0`.

Lastly, my intention was to talk rather about unit isolation in `systemd`, than about `dhcpcd`.  I'm sorry that I have failed to make this clear in the first post (but happy that it led to seth point out a solution).

Which brings me to my original intention: First

Trilby wrote:
stefan wrote:
V1del wrote:

If you have a networking daemon that borks configuration here things will start to fail

I see your point.

[...]  A modular system that becomes completely unstable or unusable because a single component has failed is a sign of a very bad design.

Yes, I do.  What do we want a unit to be able to do in startup?  If components were completely isolated, than it would not be possible that one could set up the network for the others to use.  I do not believe that there is any means to cleanly separate all good from all bad behaviours, the Halting Problem demonstrates that.

As outlined above, I do not know what the issue with `dhcpcd` was.  Maybe it was something that could have been mitigated by `systemd`, maybe not.  Thats why I was trying to find someone who would know about `systemd`'s setup

Trilby wrote:
stefan wrote:

who would be the right one to address about this issue?

You.  It's your system tongue

I wanted to know how the dependencies between units came to be.  I've got them when installing ArchLinux, and I did not review them all (I'd bet nobody reviews all config files you get when installing ArchLinux).  So how did the dependencies get there?  I would assume someone very smart wrote them, and that was the guy I was looking for.

Offline

#11 2020-04-28 10:45:44

seth
Member
Registered: 2012-09-03
Posts: 51,046

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

Splendid.

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Offline

#12 2020-04-28 10:46:48

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,911

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

you can try systemd-analyze plot > systemd1.svg or systemd-analyze dot | dot -Tsvg > systemd2.svg .

For individual services systemctl list-dependencies some-service can give an idea.


So how did the dependencies get there?  I would assume someone very smart wrote them, and that was the guy I was looking for.

It's more like many smart people that know & understand the rules all design their own thing using those rules.
Those things are then combined into one big thing without further communication between the designers.

Last edited by Lone_Wolf (2020-04-28 10:47:19)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Online

#13 2020-04-28 11:38:41

stefan
Member
Registered: 2013-03-22
Posts: 104

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

seth wrote:

Please always remember to mark resolved threads by editing your initial posts subject

I'd love to.  Being a split topic about `systemd` and `dhcpcd`, what would you suggest?  Just "solved" would ignore the `systemd` configuration question (it is rather a question or discussion than an issue or a bug) I was initally aiming at.  Or should I give up on that?

Offline

#14 2020-04-28 12:01:21

seth
Member
Registered: 2012-09-03
Posts: 51,046

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

Ah, completely missed that there's a second issue.
(Though it only arose because of the dhcpcd/network situation, did it?

That's btw. the reason for the one-topic-per-thread rule ;-)

Edit: the provided journal however does not cover the missing ethernet carrier and for the /dev/pts mess I'd
a) expect the dhcpcd situation to be the cause (race conditions can get you out of resources easily)
b) we would require the answer to https://bbs.archlinux.org/viewtopic.php … 8#p1901018 (though I understand it is indeed no longer reproducible)

As for "can a systemd service stall the boot forever" in general? The answer is "yes of course".
If I make a target depending on the success of the service and then the service execute "sleep 5h" you'll have a very slow boot process.
When facing a problem you'll have to isolate the impeding service and look at the stupidity inside smile

Last edited by seth (2020-04-28 12:09:47)

Offline

#15 2020-04-28 12:28:21

stefan
Member
Registered: 2013-03-22
Posts: 104

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

seth wrote:

Edit: the provided journal however does not cover the missing ethernet carrier and for the /dev/pts mess I'd
a) expect the dhcpcd situation to be the cause (race conditions can get you out of resources easily)

That was the complete journal of the previous boot, copied with `ssh root@verne journalctl -b-1 | xclip -i`.

seth wrote:

b) we would require the answer to https://bbs.archlinux.org/viewtopic.php … 8#p1901018 (though I understand it is indeed no longer reproducible)

Now this is from a system that runs fine, with the "bad" second `dhcpcd` disabled.  I'll try to reproduce the problem again, and post the results as a followup.

# systemctl status dhcpcd
● dhcpcd.service - dhcpcd on all interfaces
     Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; enabled; vendor preset: disabled)
     Active: active (running) since Tue 2020-04-28 14:18:48 CEST; 7min ago
    Process: 464 ExecStart=/usr/bin/dhcpcd -q -b (code=exited, status=0/SUCCESS)
   Main PID: 468 (dhcpcd)
      Tasks: 1 (limit: 1143)
     Memory: 4.2M
     CGroup: /system.slice/dhcpcd.service
             └─468 dhcpcd: [master] [ip4] [ip6]

# systemctl status dhcpcd@wlp2s0
● dhcpcd@wlp2s0.service - dhcpcd on wlp2s0
     Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; disabled; vendor preset: disabled)
     Active: inactive (dead)

As requested:

# cat /proc/sys/kernel/pty/max /proc/sys/kernel/pty/nr
4096
1
# lsof -n | grep pts
systemd      1              root  mem       REG               0,23              448654 /usr/lib/libcryptsetup.so.12.6.0 (path dev=0,25)
systemd-j  394              root  mem       REG               0,23              448654 /usr/lib/libcryptsetup.so.12.6.0 (path dev=0,25)
systemd-u  406              root  mem       REG               0,23              448654 /usr/lib/libcryptsetup.so.12.6.0 (path dev=0,25)
systemd-l  465              root  mem       REG               0,23              448654 /usr/lib/libcryptsetup.so.12.6.0 (path dev=0,25)
systemd    838                sk  mem       REG               0,23              448654 /usr/lib/libcryptsetup.so.12.6.0 (path dev=0,25)
(sd-pam)   839                sk  mem       REG               0,23              448654 /usr/lib/libcryptsetup.so.12.6.0 (path dev=0,25)
bash       848                sk    0u      CHR              136,0      0t0          3 /dev/pts/0
bash       848                sk    1u      CHR              136,0      0t0          3 /dev/pts/0
bash       848                sk    2u      CHR              136,0      0t0          3 /dev/pts/0
bash       848                sk  255u      CHR              136,0      0t0          3 /dev/pts/0
su         889              root    0u      CHR              136,0      0t0          3 /dev/pts/0
su         889              root    1u      CHR              136,0      0t0          3 /dev/pts/0
su         889              root    2u      CHR              136,0      0t0          3 /dev/pts/0
bash       890              root    0u      CHR              136,0      0t0          3 /dev/pts/0
bash       890              root    1u      CHR              136,0      0t0          3 /dev/pts/0
bash       890              root    2u      CHR              136,0      0t0          3 /dev/pts/0
bash       890              root  255u      CHR              136,0      0t0          3 /dev/pts/0
lsof      1045              root    0u      CHR              136,0      0t0          3 /dev/pts/0
lsof      1045              root    2u      CHR              136,0      0t0          3 /dev/pts/0
grep      1046              root    1u      CHR              136,0      0t0          3 /dev/pts/0
grep      1046              root    2u      CHR              136,0      0t0          3 /dev/pts/0
# ls -l /dev/pts 
total 0
crw--w---- 1 sk   tty  136, 0 Apr 28  2020 0
c--------- 1 root root   5, 2 Apr 28 14:18 ptmx

Offline

#16 2020-04-28 12:47:11

stefan
Member
Registered: 2013-03-22
Posts: 104

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

And yes: No, it's not reproducible.  Sorry.

# systemctl status dhcpcd
● dhcpcd.service - dhcpcd on all interfaces
     Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; enabled; vendor preset: disabled)
     Active: active (running) since Tue 2020-04-28 14:35:42 CEST; 3min 16s ago
    Process: 469 ExecStart=/usr/bin/dhcpcd -q -b (code=exited, status=0/SUCCESS)
   Main PID: 474 (dhcpcd)
      Tasks: 1 (limit: 1143)
     Memory: 3.4M
     CGroup: /system.slice/dhcpcd.service
             └─474 dhcpcd: [master] [ip4] [ip6]

# systemctl status dhcpcd@wlp2s0
● dhcpcd@wlp2s0.service - dhcpcd on wlp2s0
     Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; enabled; vendor preset: disabled)
     Active: failed (Result: protocol) since Tue 2020-04-28 14:35:42 CEST; 7min ago
    Process: 470 ExecStart=/usr/bin/dhcpcd -q -w wlp2s0 (code=exited, status=0/SUCCESS)

Apr 28 14:35:42 verne systemd[1]: Starting dhcpcd on wlp2s0...
Apr 28 14:35:42 verne dhcpcd[470]: sending commands to master dhcpcd process
Apr 28 14:35:42 verne systemd[1]: dhcpcd@wlp2s0.service: Can't open PID file /run/dhcpcd-wlp2s0.pid (yet?) after start: Operation not permitted
Apr 28 14:35:42 verne systemd[1]: dhcpcd@wlp2s0.service: Failed with result 'protocol'.
Apr 28 14:35:42 verne systemd[1]: Failed to start dhcpcd on wlp2s0.

As requested:

# cat /proc/sys/kernel/pty/max /proc/sys/kernel/pty/nr
4096
2
# lsof -n | grep pts
systemd      1               root  mem       REG               0,23              448654 /usr/lib/libcryptsetup.so.12.6.0 (path dev=0,25)
systemd-j  394               root  mem       REG               0,23              448654 /usr/lib/libcryptsetup.so.12.6.0 (path dev=0,25)
systemd-u  407               root  mem       REG               0,23              448654 /usr/lib/libcryptsetup.so.12.6.0 (path dev=0,25)
systemd-l  471               root  mem       REG               0,23              448654 /usr/lib/libcryptsetup.so.12.6.0 (path dev=0,25)
systemd    691                 sk  mem       REG               0,23              448654 /usr/lib/libcryptsetup.so.12.6.0 (path dev=0,25)
(sd-pam)   692                 sk  mem       REG               0,23              448654 /usr/lib/libcryptsetup.so.12.6.0 (path dev=0,25)
bash       701                 sk    0u      CHR              136,0      0t0          3 /dev/pts/0
bash       701                 sk    1u      CHR              136,0      0t0          3 /dev/pts/0
bash       701                 sk    2u      CHR              136,0      0t0          3 /dev/pts/0
bash       701                 sk  255u      CHR              136,0      0t0          3 /dev/pts/0
su        1051               root    0u      CHR              136,0      0t0          3 /dev/pts/0
su        1051               root    1u      CHR              136,0      0t0          3 /dev/pts/0
su        1051               root    2u      CHR              136,0      0t0          3 /dev/pts/0
bash      1118               root    0u      CHR              136,0      0t0          3 /dev/pts/0
bash      1118               root    1u      CHR              136,0      0t0          3 /dev/pts/0
bash      1118               root    2u      CHR              136,0      0t0          3 /dev/pts/0
bash      1118               root  255u      CHR              136,0      0t0          3 /dev/pts/0
bash      2405                 sk    0u      CHR              136,1      0t0          4 /dev/pts/1
bash      2405                 sk    1u      CHR              136,1      0t0          4 /dev/pts/1
bash      2405                 sk    2u      CHR              136,1      0t0          4 /dev/pts/1
bash      2405                 sk  255u      CHR              136,1      0t0          4 /dev/pts/1
lsof      2591               root    0u      CHR              136,0      0t0          3 /dev/pts/0
lsof      2591               root    2u      CHR              136,0      0t0          3 /dev/pts/0
grep      2592               root    1u      CHR              136,0      0t0          3 /dev/pts/0
grep      2592               root    2u      CHR              136,0      0t0          3 /dev/pts/0
# ls -l /dev/pts 
total 0
crw--w---- 1 sk   tty  136, 0 Apr 28 14:43 0
crw--w---- 1 sk   tty  136, 1 Apr 28 14:43 1
c--------- 1 root root   5, 2 Apr 28 14:35 ptmx

Offline

#17 2020-04-28 12:59:47

seth
Member
Registered: 2012-09-03
Posts: 51,046

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

The journal still does not reflect a boot w/o a carrier (no ethernet cable plugged) - though I assume even then the two services just got in a bigger mess w/ each other (because now both are only configuring the WiFi NIC)

The PTS situation looks normal. Is this when you get the “not enough ptys” error?

Offline

#18 2020-04-28 13:36:36

stefan
Member
Registered: 2013-03-22
Posts: 104

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

seth wrote:

The PTS situation looks normal. Is this when you get the “not enough ptys” error?

No, sorry, I cannot reproduce the “not enough ptys” problem.  And if it was a race condition indeed, I may never be.

I really don't want to waste your time on this.  Maybe we should close this.  Although the systemd-config-stuff is not cleared, I'm sure another occasion will arise...

Offline

#19 2020-04-28 14:17:28

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,523
Website

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

stefan wrote:

What do we want a unit to be able to do in startup?

That's a complete strawman argument.  Modular doesn't mean completely isolated.  And there is a wide span of all the real world between completely isolated and completely interdependent.  Some things may depend on networking and when networking fails those dependent items would not start.  But there's no reason your login prompt, WM/DE, text editor, word processors, etc, etc, all need to have a strong dependency on networking.

Hell even packages have optional dependencies.  If another package is installed, new features in the target software can be used.  But the target software need not fail completely because an optional accessory is not present.

But it's your thread, and your system.

EDIT:

stefan wrote:

Just "solved" would ignore the `systemd` configuration question (it is rather a question or discussion than an issue or a bug) I was initally aiming at.  Or should I give up on that?

What's this then?  If you're ok boot up depending on networking then what is your question?  If you are not ok with this, why did you react to my suggestion so dismissively?

FYI:

stefan wrote:

I'd bet nobody reviews all config files you get when installing ArchLinux.

You'd lose that bet.  But I'd not suggest everyone should review every config file.  But when you have a problem with a systemd service, you absolutely should review that service's config file.

Last edited by Trilby (2020-04-28 14:23:19)


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#20 2020-04-28 16:01:32

mitchell4136
Member
Registered: 2020-04-21
Posts: 10

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

I think seth, along with the other mods entirely missed the point of stefan's OP question. He does not have an unsolved issue. He recognized in his original OP that his boot problem was solved by downgrading or pugrading dhcpcd, and even links to the thread where he is provided the solution.

Stefan's goal with his original post was to start a conversation about why multiple seemingly unrelated systemd services would fail with a single unit's bad configuration  and hang up the boot process to begin with. This week on multiple threads it was a dhcpcd issue due to an update, but what if down the road say Gnome Display Manager got an update and the systemd service broke multiple things to the point where something unrelated like getty tty would fail? What stefan was alluding to is that in theory, if dhcpcd had failed, the pc should still be able to boot and get into console with no networking enabled, not have multiple unrelated services fail outright.

stefan's question was one about the design of systemd overall and questions posed by this week's broken (now fixed as of a few days ago) dhcpcd update.
He says so himself "(it is rather a question or discussion than an issue or a bug)".

The one question per thread rule was broken when WorMzy asked for logs on a question that did not need logs. This wasn't the typical "help me, system broke" post but rather "Why would failure of one modular item cause failure of multiple unrelated units". I think its absolutely a question that merits further inquiry. The closest thing we have to an answer so far is post #2 where Videl states that network goes much beyond just "the internet" and in fact things like user accounts requires a working "local" network in the machine itself, and so a broken dhcpcd would absolutely mess with those other systemd units.

Just my two cents.

Offline

#21 2020-04-28 16:14:26

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,523
Website

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

Mitchell, that's how I read the OPs post too.  But it would seem this reading is wrong as that's exactly what I responded to in post #8.  The problem is poor service files.  Every problem that has popped up this last week or so related to this could be solved by using more thoughtfully designed service files or often just by adding a single flag to the exec line of the default service file.  Oddly, such changes are even recommended in our wiki ... which is most baffling when it is a arch wiki recommended change to an arch linux provided (not upstream) service file.


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#22 2020-04-28 17:17:18

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,665

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

Now I do think you are  simplifying the problem. Quite a few people had issues even after the "unit file" fix for 9.0.1-4 and looking at the actual upstream source there were a few code changes in 9.0.2, see https://bbs.archlinux.org/viewtopic.php?id=254906 as well.

But yeah the underlying issue of "completely unbootable" and the like are likely related to multiple daemons, which is emphatically recommended against in the wiki. Where one might be able to play around with the service file

Last edited by V1del (2020-04-28 17:20:54)

Offline

#23 2020-04-28 17:19:42

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,523
Website

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

Ah ... what?  I didn't suggest the only problem in the known universe was poor service files.

If there was only a one-off problem with a bit of software (e.g., dhcpcd) this thread wouldn't exist.  This thread (seems to) exists because there have been a large number of problems over the past week or two related to dhcpcd.  The fact that you can point out the one that may not be due to problematic service file configurations does not change the fact that the pattern of breakage has been from problematic service files.

As for the edit - there's a warning on my vehicle by the gas cap that instructs operators to ensure the gas cap is securely closed before starting the car back up.  This is sound advice.  But even with this advice, if cars relibaly and consistently exploded every time the ignition turned with an open gas cap, I don't think anyone would argue, "well, you were warned'.  No, that'd be evidence of unsafe engineering.  A well engineered system may fail to work optimally when rules aren't followed, but a well engineered system must also be at least somewhat robust to small perturbations ... otherwise it is just crap engineering.

Last edited by Trilby (2020-04-28 17:26:53)


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#24 2020-04-28 18:32:33

stefan
Member
Registered: 2013-03-22
Posts: 104

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

mitchell4136 wrote:

Stefan's goal with his original post was to start a conversation about why multiple seemingly unrelated systemd services would fail with a single unit's bad configuration  and hang up the boot process to begin with.

Yep, you've got that exactly right, `dhcpcd` was just the trigger.

And also you, Trilby, got me right in the very first part of post #8.  And no, I did not react dismissively to your suggestion.  I just think your absolute standpoint is not valid, and I've incorporated in my reply what I've learned from V1del.

I totally agree with Tribly that getting a login prompt should not depend on networking, and my initial assumption was that such a dependency might be the problem.  But I do accept (#4, #10) what V1del pointed out in #2, that any unit may compromise a system if it tries hard enough.  I think that's obvious, a unit could just intentionally trigger a kernel panic.

Without being able to reproduce the `dhcpcd` mess, it's hard to tell whether better dependencies between units would have helped.  If it was two daemons racing for a resource and on the way depleting PTYs (I'm completely making this up), then this is something more akin to messing badly with the system.

So the remaining question/discussion is whether there is room for improvement on the dependencies between `systemd` units.  But by now I also have learned that there is no one single guy carefully hand-crafting the unit files for ArchLinux.

Offline

#25 2020-04-28 18:44:05

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,523
Website

Re: Maybe the `dhcpcd` trouble hints at a `systemd` config problem?

stefan wrote:

And no, I did not react dismissively to your suggestion.  I just think your absolute standpoint is not valid

Thanks for clarifying, and sorry if I misread the response.  I'm curious which part of my view your found to be an absolute.

stefan wrote:

... any unit may compromise a system if it tries hard enough

Certainly true.  But a well written service file (or collection of service files / targets) should be deliberately written to try very hard for the opposite result.  That's my standpoint.  I don't think any service files are written with intent to break, but I think many of the defaults are not well engineered to create a robust system.

stefan wrote:

... there is no one single guy carefully hand-crafting the unit files for ArchLinux.

This is true, but I'm not sure the implications go very far.  The same can be said about all software in the linux ecosystem.  There is no one person crafting each bit to work in harmony with the others.  But every software developer should be putting forth some effort to ensure their tool plays well with others.  Generally, and historically, any developer who creates software that is mindless/oblivious to the environment it will work in first gets sent feature requests and bug reports.  If these are ignored, so to would be their software and it would die, rightly, of neglect.  We vote with our feet to use software that is well designed and well engineered.

We should apply the same standard to service files as we do to (other) software.

Last edited by Trilby (2020-04-28 18:45:02)


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

Board footer

Powered by FluxBB