dmesg - osbench-resultss

Return To osbench-resultss System Information

Linux version 5.8.0-48-generic (buildd@lgw01-amd64-008) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #54~20.04.1-Ubuntu SMP Sat Mar 20 13:40:25 UTC 2021 (Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18)
KERNEL supported cpus:
  Intel GenuineIntel
  AMD AuthenticAMD
  Hygon HygonGenuine
  Centaur CentaurHauls
  zhaoxin   Shanghai  
x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
BIOS-provided physical RAM map:
BIOS-e820: [mem 0x0000000000000000-0x0000000000000fff] reserved
BIOS-e820: [mem 0x0000000000001000-0x0000000000001fff] usable
BIOS-e820: [mem 0x0000000000002000-0x000000000000bfff] reserved
BIOS-e820: [mem 0x000000000000c000-0x000000000005efff] usable
BIOS-e820: [mem 0x000000000005f000-0x0000000000086fff] reserved
BIOS-e820: [mem 0x0000000000087000-0x0000000000088fff] usable
BIOS-e820: [mem 0x0000000000089000-0x00000000000fffff] reserved
BIOS-e820: [mem 0x0000000000100000-0x000000007e4cffff] usable
BIOS-e820: [mem 0x000000007e4d0000-0x000000008ef9bfff] reserved
BIOS-e820: [mem 0x000000008ef9c000-0x000000008fb53fff] ACPI NVS
BIOS-e820: [mem 0x000000008fb54000-0x000000008fc4dfff] ACPI data
BIOS-e820: [mem 0x000000008fc4e000-0x000000008fc4efff] usable
BIOS-e820: [mem 0x000000008fc4f000-0x000000009b7fffff] reserved
BIOS-e820: [mem 0x0000000100000000-0x00000002627fffff] usable
NX (Execute Disable) protection: active
e820: update [mem 0x752ce018-0x752de057] usable ==> usable
e820: update [mem 0x752ce018-0x752de057] usable ==> usable
e820: update [mem 0x752bf018-0x752cd057] usable ==> usable
e820: update [mem 0x752bf018-0x752cd057] usable ==> usable
extended physical RAM map:
reserve setup_data: [mem 0x0000000000000000-0x0000000000000fff] reserved
reserve setup_data: [mem 0x0000000000001000-0x0000000000001fff] usable
reserve setup_data: [mem 0x0000000000002000-0x000000000000bfff] reserved
reserve setup_data: [mem 0x000000000000c000-0x000000000005efff] usable
reserve setup_data: [mem 0x000000000005f000-0x0000000000086fff] reserved
reserve setup_data: [mem 0x0000000000087000-0x0000000000088fff] usable
reserve setup_data: [mem 0x0000000000089000-0x00000000000fffff] reserved
reserve setup_data: [mem 0x0000000000100000-0x00000000752bf017] usable
reserve setup_data: [mem 0x00000000752bf018-0x00000000752cd057] usable
reserve setup_data: [mem 0x00000000752cd058-0x00000000752ce017] usable
reserve setup_data: [mem 0x00000000752ce018-0x00000000752de057] usable
reserve setup_data: [mem 0x00000000752de058-0x000000007e4cffff] usable
reserve setup_data: [mem 0x000000007e4d0000-0x000000008ef9bfff] reserved
reserve setup_data: [mem 0x000000008ef9c000-0x000000008fb53fff] ACPI NVS
reserve setup_data: [mem 0x000000008fb54000-0x000000008fc4dfff] ACPI data
reserve setup_data: [mem 0x000000008fc4e000-0x000000008fc4efff] usable
reserve setup_data: [mem 0x000000008fc4f000-0x000000009b7fffff] reserved
reserve setup_data: [mem 0x0000000100000000-0x00000002627fffff] usable
efi: EFI v2.70 by Phoenix Technologies Ltd.
efi: SMBIOS=0x80539000 SMBIOS 3.0=0x8052c000 TPMFinalLog=0x8fa1a000 ACPI=0x8fc4d000 ACPI 2.0=0x8fc4d014 ESRT=0x7e8be000 TPMEventLog=0x75ff7018 
secureboot: Secure boot disabled
SMBIOS 3.2.0 present.
DMI: LENOVO 20RV/LNVNB161216, BIOS CJCN33WW 12/09/2020
tsc: Detected 2100.000 MHz processor
tsc: Detected 2099.944 MHz TSC
e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
e820: remove [mem 0x000a0000-0x000fffff] usable
last_pfn = 0x262800 max_arch_pfn = 0x400000000
MTRR default type: write-back
MTRR fixed ranges enabled:
  00000-9FFFF write-back
  A0000-BFFFF uncachable
  C0000-FFFFF write-protect
MTRR variable ranges enabled:
  0 base 00C0000000 mask 7FC0000000 uncachable
  1 base 00A0000000 mask 7FE0000000 uncachable
  2 base 009C000000 mask 7FFC000000 uncachable
  3 base 009A000000 mask 7FFE000000 uncachable
  4 base 0099000000 mask 7FFF000000 uncachable
  5 base 2000000000 mask 6000000000 uncachable
  6 base 1000000000 mask 7000000000 uncachable
  7 base 0800000000 mask 7800000000 uncachable
  8 base 0400000000 mask 7C00000000 uncachable
  9 base 4000000000 mask 4000000000 uncachable
x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
last_pfn = 0x8fc4f max_arch_pfn = 0x400000000
esrt: Reserving ESRT space from 0x000000007e8be000 to 0x000000007e8be038.
check: Scanning 2 areas for low memory corruption
Using GB pages for direct mapping
secureboot: Secure boot disabled
RAMDISK: [mem 0x3cd8c000-0x3fffdfff]
ACPI: Early table checksum verification disabled
ACPI: RSDP 0x000000008FC4D014 000024 (v02 LENOVO)
ACPI: XSDT 0x000000008FC4B188 00010C (v01 LENOVO CB-01    20170001 PTEC 00000002)
ACPI: FACP 0x000000007FF00000 000114 (v06 LENOVO CB-01    20170001 PTEC 00000002)
ACPI: DSDT 0x000000007FEBA000 042D67 (v02 LENOVO CFL      20170001 INTL 20160422)
ACPI: FACS 0x000000008F9C3000 000040
ACPI: SSDT 0x000000008043D000 001B4A (v02 LENOVO CpuSsdt  00003000 INTL 20160527)
ACPI: SSDT 0x00000000803F2000 005E02 (v02 LENOVO DptfTabl 00001000 INTL 20160527)
ACPI: SSDT 0x000000007FF02000 003145 (v02 LENOVO SaSsdt   00003000 INTL 20160527)
ACPI: SSDT 0x000000007FF01000 000530 (v02 LENOVO PerfTune 00001000 INTL 20160527)
ACPI: HPET 0x000000007FEFF000 000038 (v01 LENOVO CB-01    20170001 PTEC 00000002)
ACPI: APIC 0x000000007FEFE000 000164 (v03 LENOVO CB-01    20170001 PTEC 00000002)
ACPI: MCFG 0x000000007FEFD000 00003C (v01 LENOVO CB-01    20170001 PTEC 00000002)
ACPI: SSDT 0x000000007FEB8000 00147B (v02 LENOVO Ther_Rvp 00001000 INTL 20160527)
ACPI: SSDT 0x000000007FEB4000 00326F (v02 LENOVO xh_cmud4 00000000 INTL 20160527)
ACPI: NHLT 0x000000007FEB3000 00002D (v00 LENOVO CB-01    20170001 PTEC 00000002)
ACPI: BOOT 0x000000007FEB2000 000028 (v01 LENOVO CB-01    00000002 PTEC 00000002)
ACPI: SSDT 0x000000007FEB1000 00045A (v02 LENOVO Tpm2Tabl 00001000 INTL 20160527)
ACPI: SSDT 0x000000007FEB0000 000046 (v02 LENOVO MeSsdt   00003000 INTL 20160527)
ACPI: TPM2 0x000000007FEAF000 000034 (v03 LENOVO CB-01    00000002 PTEC 00000002)
ACPI: SSDT 0x000000007FEAB000 001516 (v02 LENOVO UsbCTabl 00001000 INTL 20160527)
ACPI: LPIT 0x000000007FEAA000 000094 (v01 LENOVO CB-01    20170001 PTEC 00000002)
ACPI: WSMT 0x000000007FEA9000 000028 (v01 LENOVO CB-01    20170001 PTEC 00000002)
ACPI: SSDT 0x000000007FEA6000 002720 (v02 LENOVO PtidDevc 00001000 INTL 20160527)
ACPI: SSDT 0x000000007FEA4000 00149F (v02 LENOVO TbtTypeC 00000000 INTL 20160527)
ACPI: DBGP 0x000000007FEA3000 000034 (v01 LENOVO CB-01    20170001 PTEC 00000002)
ACPI: DBG2 0x000000007FEA2000 000054 (v00 LENOVO CB-01    20170001 PTEC 00000002)
ACPI: MSDM 0x000000007FEA1000 000055 (v03 LENOVO CB-01    00000000 PTEC 00000002)
ACPI: SLIC 0x000000007FEA0000 000176 (v01 LENOVO CB-01    00000002 PTEC 00000002)
ACPI: BATB 0x000000007FCC2000 00004A (v02 LENOVO CB-01    00000000 PTEC 00000002)
ACPI: DMAR 0x000000007E8C0000 0000A8 (v01 LENOVO CB-01    00000002 PTEC 00000002)
ACPI: BGRT 0x000000007E8BD000 000038 (v01 LENOVO CB-01    20170001 PTEC 00000002)
ACPI: UEFI 0x000000008F9B5000 00017A (v01 LENOVO CB-01    00000001 PTEC 00000002)
ACPI: FPDT 0x000000007E8BC000 000044 (v01 LENOVO CB-01    20170001 PTEC 00000002)
ACPI: Local APIC address 0xfee00000
No NUMA configuration found
Faking a node at [mem 0x0000000000000000-0x00000002627fffff]
NODE_DATA(0) allocated [mem 0x2627d6000-0x2627fffff]
Zone ranges:
  DMA      [mem 0x0000000000001000-0x0000000000ffffff]
  DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
  Normal   [mem 0x0000000100000000-0x00000002627fffff]
  Device   empty
Movable zone start for each node
Early memory node ranges
  node   0: [mem 0x0000000000001000-0x0000000000001fff]
  node   0: [mem 0x000000000000c000-0x000000000005efff]
  node   0: [mem 0x0000000000087000-0x0000000000088fff]
  node   0: [mem 0x0000000000100000-0x000000007e4cffff]
  node   0: [mem 0x000000008fc4e000-0x000000008fc4efff]
  node   0: [mem 0x0000000100000000-0x00000002627fffff]
Zeroed struct page in unavailable ranges: 62425 pages
Initmem setup node 0 [mem 0x0000000000001000-0x00000002627fffff]
On node 0 totalpages: 1969191
  DMA zone: 64 pages used for memmap
  DMA zone: 11 pages reserved
  DMA zone: 3926 pages, LIFO batch:0
  DMA32 zone: 8020 pages used for memmap
  DMA32 zone: 513233 pages, LIFO batch:63
  Normal zone: 22688 pages used for memmap
  Normal zone: 1452032 pages, LIFO batch:63
Reserving Intel graphics memory at [mem 0x99800000-0x9b7fffff]
ACPI: PM-Timer IO Port: 0x1808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x14] high edge lint[0x1])
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a201 base: 0xfed00000
e820: update [mem 0x79246000-0x79339fff] usable ==> reserved
TSC deadline timer available
smpboot: Allowing 8 CPUs, 0 hotplug CPUs
PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
PM: hibernation: Registered nosave memory: [mem 0x00002000-0x0000bfff]
PM: hibernation: Registered nosave memory: [mem 0x0005f000-0x00086fff]
PM: hibernation: Registered nosave memory: [mem 0x00089000-0x000fffff]
PM: hibernation: Registered nosave memory: [mem 0x752bf000-0x752bffff]
PM: hibernation: Registered nosave memory: [mem 0x752cd000-0x752cdfff]
PM: hibernation: Registered nosave memory: [mem 0x752ce000-0x752cefff]
PM: hibernation: Registered nosave memory: [mem 0x752de000-0x752defff]
PM: hibernation: Registered nosave memory: [mem 0x79246000-0x79339fff]
PM: hibernation: Registered nosave memory: [mem 0x7e4d0000-0x8ef9bfff]
PM: hibernation: Registered nosave memory: [mem 0x8ef9c000-0x8fb53fff]
PM: hibernation: Registered nosave memory: [mem 0x8fb54000-0x8fc4dfff]
PM: hibernation: Registered nosave memory: [mem 0x8fc4f000-0x9b7fffff]
PM: hibernation: Registered nosave memory: [mem 0x9b800000-0xffffffff]
[mem 0x9b800000-0xffffffff] available for PCI devices
Booting paravirtualized kernel on bare hardware
clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
setup_percpu: NR_CPUS:8192 nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1
percpu: Embedded 56 pages/cpu s192512 r8192 d28672 u262144
pcpu-alloc: s192512 r8192 d28672 u262144 alloc=1*2097152
pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
Built 1 zonelists, mobility grouping on.  Total pages: 1938408
Policy zone: Normal
Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
mem auto-init: stack:off, heap alloc:on, heap free:off
Memory: 7493872K/7876764K available (14339K kernel code, 2537K rwdata, 5436K rodata, 2644K init, 4916K bss, 382892K reserved, 0K cma-reserved)
random: get_random_u64 called from kmem_cache_open+0x2d/0x410 with crng_init=0
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
ftrace: allocating 46224 entries in 181 pages
ftrace: allocated 181 pages with 5 groups
rcu: Hierarchical RCU implementation.
rcu: 	RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=8.
	Trampoline variant of Tasks RCU enabled.
	Rude variant of Tasks RCU enabled.
	Tracing variant of Tasks RCU enabled.
rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
NR_IRQS: 524544, nr_irqs: 2048, preallocated irqs: 16
random: crng done (trusting CPU's manufacturer)
vt handoff: transparent VT on vt#7
Console: colour dummy device 80x25
printk: console [tty0] enabled
ACPI: Core revision 20200528
clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635855245 ns
APIC: Switch to symmetric I/O mode setup
DMAR: Host address width 39
DMAR: DRHD base: 0x000000fed90000 flags: 0x0
DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 19e2ff0505e
DMAR: DRHD base: 0x000000fed91000 flags: 0x1
DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da
DMAR: RMRR base: 0x0000008ef57000 end: 0x0000008ef76fff
DMAR: RMRR base: 0x00000099000000 end: 0x0000009b7fffff
DMAR-IR: IOAPIC id 2 under DRHD base  0xfed91000 IOMMU 1
DMAR-IR: HPET id 0 under DRHD base 0xfed91000
DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
DMAR-IR: Enabled IRQ remapping in x2apic mode
x2apic enabled
Switched APIC routing to cluster x2apic.
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x1e44fb6c2ab, max_idle_ns: 440795206594 ns
Calibrating delay loop (skipped), value calculated using timer frequency.. 4199.88 BogoMIPS (lpj=8399776)
pid_max: default: 32768 minimum: 301
LSM: Security Framework initializing
Yama: becoming mindful.
AppArmor: AppArmor initialized
Mount-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
mce: CPU0: Thermal monitoring enabled (TM1)
process: using mwait in idle threads
Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4
Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
Spectre V2 : Mitigation: Enhanced IBRS
Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
SRBDS: Mitigation: TSX disabled
Freeing SMP alternatives memory: 40K
smpboot: CPU0: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (family: 0x6, model: 0x8e, stepping: 0xc)
Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver.
... version:                4
... bit width:              48
... generic registers:      4
... value mask:             0000ffffffffffff
... max period:             00007fffffffffff
... fixed-purpose events:   3
... event mask:             000000070000000f
rcu: Hierarchical SRCU implementation.
NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
smp: Bringing up secondary CPUs ...
x86: Booting SMP configuration:
.... node  #0, CPUs:      #1 #2 #3 #4 #5 #6 #7
smp: Brought up 1 node, 8 CPUs
smpboot: Max logical packages: 1
smpboot: Total of 8 processors activated (33599.10 BogoMIPS)
devtmpfs: initialized
x86/mm: Memory block size: 128MB
PM: Registering ACPI NVS region [mem 0x8ef9c000-0x8fb53fff] (12288000 bytes)
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
futex hash table entries: 2048 (order: 5, 131072 bytes, linear)
pinctrl core: initialized pinctrl subsystem
PM: RTC time: 04:29:47, date: 2021-05-11
thermal_sys: Registered thermal governor 'fair_share'
thermal_sys: Registered thermal governor 'bang_bang'
thermal_sys: Registered thermal governor 'step_wise'
thermal_sys: Registered thermal governor 'user_space'
thermal_sys: Registered thermal governor 'power_allocator'
NET: Registered protocol family 16
DMA: preallocated 1024 KiB GFP_KERNEL pool for atomic allocations
DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
audit: initializing netlink subsys (disabled)
audit: type=2000 audit(1620707387.052:1): state=initialized audit_enabled=0 res=1
EISA bus registered
cpuidle: using governor ladder
cpuidle: using governor menu
Simple Boot Flag at 0x47 set to 0x1
ACPI: bus type PCI registered
acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
PCI: not using MMCONFIG
PCI: Using configuration type 1 for base access
ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
ACPI: Added _OSI(Module Device)
ACPI: Added _OSI(Processor Device)
ACPI: Added _OSI(3.0 _SCP Extensions)
ACPI: Added _OSI(Processor Aggregator Device)
ACPI: Added _OSI(Linux-Dell-Video)
ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.GUPC], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.TUPC], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS05._PLD], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS06._UPC], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS06._PLD], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS08._UPC], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS08._PLD], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS09._UPC], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS09._PLD], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS10._UPC], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS10._PLD], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS01._UPC], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS01._PLD], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS02._UPC], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS02._PLD], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS03._UPC], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS03._PLD], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS04._UPC], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS04._PLD], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS05._UPC], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS05._PLD], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS06._UPC], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS06._PLD], AE_ALREADY_EXISTS (20200528/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200528/psobject-220)
ACPI: Skipping parse of AML opcode: Method (0x0014)
ACPI: 12 ACPI AML tables successfully acquired and loaded
ACPI: Dynamic OEM Table Load:
ACPI: SSDT 0xFFFF936C58F79A00 0000F4 (v02 PmRef  Cpu0Psd  00003000 INTL 20160527)
ACPI: \_SB_.PR00: _OSC native thermal LVT Acked
ACPI: Dynamic OEM Table Load:
ACPI: SSDT 0xFFFF936C58B25000 000400 (v02 PmRef  Cpu0Cst  00003001 INTL 20160527)
ACPI: Dynamic OEM Table Load:
ACPI: SSDT 0xFFFF936C58A7C000 000560 (v02 PmRef  Cpu0Ist  00003000 INTL 20160527)
ACPI: Dynamic OEM Table Load:
ACPI: SSDT 0xFFFF936C58A79000 000778 (v02 PmRef  ApIst    00003000 INTL 20160527)
ACPI: Dynamic OEM Table Load:
ACPI: SSDT 0xFFFF936C58B73000 000D74 (v02 PmRef  ApPsd    00003000 INTL 20160527)
ACPI: Dynamic OEM Table Load:
ACPI: SSDT 0xFFFF936C58B23C00 0003CA (v02 PmRef  ApCst    00003000 INTL 20160527)
ACPI: EC: EC started
ACPI: EC: interrupt blocked
ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
ACPI: \_SB_.PCI0.LPCB.EC0_: Boot DSDT EC used to handle transactions
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
ACPI: Enabled 7 GPEs in block 00 to 7F
ACPI: Power Resource [USBC] (on)
ACPI: Power Resource [V0PR] (on)
ACPI: Power Resource [V1PR] (on)
ACPI: Power Resource [V2PR] (on)
ACPI: Power Resource [WRST] (off)
ACPI: Power Resource [FN00] (off)
ACPI: Power Resource [FN01] (off)
ACPI: Power Resource [FN02] (off)
ACPI: Power Resource [FN03] (off)
ACPI: Power Resource [FN04] (off)
ACPI: Power Resource [PIN] (off)
ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe])
acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug SHPCHotplug PME AER PCIeCapability LTR]
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
pci_bus 0000:00: root bus resource [mem 0x9b800000-0xdfffffff window]
pci_bus 0000:00: root bus resource [mem 0xfc800000-0xfe7fffff window]
pci_bus 0000:00: root bus resource [bus 00-fe]
pci 0000:00:00.0: [8086:9b61] type 00 class 0x060000
pci 0000:00:02.0: [8086:9b41] type 00 class 0x030000
pci 0000:00:02.0: reg 0x10: [mem 0xb0000000-0xb0ffffff 64bit]
pci 0000:00:02.0: reg 0x18: [mem 0xa0000000-0xafffffff 64bit pref]
pci 0000:00:02.0: reg 0x20: [io  0x3000-0x303f]
pci 0000:00:02.0: BAR 2: assigned to efifb
pci 0000:00:04.0: [8086:1903] type 00 class 0x118000
pci 0000:00:04.0: reg 0x10: [mem 0xb1410000-0xb1417fff 64bit]
pci 0000:00:08.0: [8086:1911] type 00 class 0x088000
pci 0000:00:08.0: reg 0x10: [mem 0xb1424000-0xb1424fff 64bit]
pci 0000:00:12.0: [8086:02f9] type 00 class 0x118000
pci 0000:00:12.0: reg 0x10: [mem 0xb1425000-0xb1425fff 64bit]
pci 0000:00:14.0: [8086:02ed] type 00 class 0x0c0330
pci 0000:00:14.0: reg 0x10: [mem 0xb1400000-0xb140ffff 64bit]
pci 0000:00:14.0: PME# supported from D3hot D3cold
pci 0000:00:14.2: [8086:02ef] type 00 class 0x050000
pci 0000:00:14.2: reg 0x10: [mem 0xb1420000-0xb1421fff 64bit]
pci 0000:00:14.2: reg 0x18: [mem 0xb1426000-0xb1426fff 64bit]
pci 0000:00:14.3: [8086:02f0] type 00 class 0x028000
pci 0000:00:14.3: reg 0x10: [mem 0xb1418000-0xb141bfff 64bit]
pci 0000:00:14.3: PME# supported from D0 D3hot D3cold
pci 0000:00:15.0: [8086:02e8] type 00 class 0x0c8000
pci 0000:00:15.0: reg 0x10: [mem 0xb1427000-0xb1427fff 64bit]
pci 0000:00:16.0: [8086:02e0] type 00 class 0x078000
pci 0000:00:16.0: reg 0x10: [mem 0xb1428000-0xb1428fff 64bit]
pci 0000:00:16.0: PME# supported from D3hot
pci 0000:00:17.0: [8086:02d3] type 00 class 0x010601
pci 0000:00:17.0: reg 0x10: [mem 0xb1422000-0xb1423fff]
pci 0000:00:17.0: reg 0x14: [mem 0xb142d000-0xb142d0ff]
pci 0000:00:17.0: reg 0x18: [io  0x3080-0x3087]
pci 0000:00:17.0: reg 0x1c: [io  0x3088-0x308b]
pci 0000:00:17.0: reg 0x20: [io  0x3060-0x307f]
pci 0000:00:17.0: reg 0x24: [mem 0xb142c000-0xb142c7ff]
pci 0000:00:17.0: PME# supported from D3hot
pci 0000:00:1d.0: [8086:02b0] type 01 class 0x060400
pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.0: PTM enabled (root), 4ns granularity
pci 0000:00:1d.2: [8086:02b2] type 01 class 0x060400
pci 0000:00:1d.2: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.2: PTM enabled (root), 4ns granularity
pci 0000:00:1d.4: [8086:02b4] type 01 class 0x060400
pci 0000:00:1d.4: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.4: PTM enabled (root), 4ns granularity
pci 0000:00:1e.0: [8086:02a8] type 00 class 0x078000
pci 0000:00:1e.0: reg 0x10: [mem 0xb1429000-0xb1429fff 64bit]
pci 0000:00:1f.0: [8086:0284] type 00 class 0x060100
pci 0000:00:1f.3: [8086:02c8] type 00 class 0x040300
pci 0000:00:1f.3: reg 0x10: [mem 0xb141c000-0xb141ffff 64bit]
pci 0000:00:1f.3: reg 0x20: [mem 0xb1000000-0xb10fffff 64bit]
pci 0000:00:1f.3: PME# supported from D3hot D3cold
pci 0000:00:1f.4: [8086:02a3] type 00 class 0x0c0500
pci 0000:00:1f.4: reg 0x10: [mem 0xb142a000-0xb142a0ff 64bit]
pci 0000:00:1f.4: reg 0x20: [io  0xefa0-0xefbf]
pci 0000:00:1f.5: [8086:02a4] type 00 class 0x0c8000
pci 0000:00:1f.5: reg 0x10: [mem 0xfe010000-0xfe010fff]
pci 0000:01:00.0: [10ec:8168] type 00 class 0x020000
pci 0000:01:00.0: reg 0x10: [io  0x2000-0x20ff]
pci 0000:01:00.0: reg 0x18: [mem 0xb1304000-0xb1304fff 64bit]
pci 0000:01:00.0: reg 0x20: [mem 0xb1300000-0xb1303fff 64bit]
pci 0000:01:00.0: supports D1 D2
pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:1d.0: PCI bridge to [bus 01]
pci 0000:00:1d.0:   bridge window [io  0x2000-0x2fff]
pci 0000:00:1d.0:   bridge window [mem 0xb1300000-0xb13fffff]
pci 0000:02:00.0: [10ec:522a] type 00 class 0xff0000
pci 0000:02:00.0: reg 0x10: [mem 0xb1200000-0xb1200fff]
pci 0000:02:00.0: supports D1 D2
pci 0000:02:00.0: PME# supported from D1 D2 D3hot D3cold
pci 0000:00:1d.2: PCI bridge to [bus 02]
pci 0000:00:1d.2:   bridge window [mem 0xb1200000-0xb12fffff]
pci 0000:03:00.0: [15b7:5006] type 00 class 0x010802
pci 0000:03:00.0: reg 0x10: [mem 0xb1100000-0xb1103fff 64bit]
pci 0000:03:00.0: reg 0x20: [mem 0xb1104000-0xb11040ff 64bit]
pci 0000:00:1d.4: PCI bridge to [bus 03]
pci 0000:00:1d.4:   bridge window [mem 0xb1100000-0xb11fffff]
ACPI: EC: interrupt unblocked
ACPI: EC: event unblocked
ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
ACPI: EC: GPE=0x6e
ACPI: \_SB_.PCI0.LPCB.EC0_: Boot DSDT EC initialization complete
ACPI: \_SB_.PCI0.LPCB.EC0_: EC: Used to handle transactions and events
iommu: Default domain type: Translated 
SCSI subsystem initialized
libata version 3.00 loaded.
pci 0000:00:02.0: vgaarb: setting as boot VGA device
pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
pci 0000:00:02.0: vgaarb: bridge control possible
vgaarb: loaded
ACPI: bus type USB registered
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti 
PTP clock support registered
EDAC MC: Ver: 3.0.0
Registered efivars operations
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
NetLabel:  unlabeled traffic allowed by default
PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
e820: reserve RAM buffer [mem 0x00002000-0x0000ffff]
e820: reserve RAM buffer [mem 0x0005f000-0x0005ffff]
e820: reserve RAM buffer [mem 0x00089000-0x0008ffff]
e820: reserve RAM buffer [mem 0x752bf018-0x77ffffff]
e820: reserve RAM buffer [mem 0x752ce018-0x77ffffff]
e820: reserve RAM buffer [mem 0x79246000-0x7bffffff]
e820: reserve RAM buffer [mem 0x7e4d0000-0x7fffffff]
e820: reserve RAM buffer [mem 0x8fc4f000-0x8fffffff]
e820: reserve RAM buffer [mem 0x262800000-0x263ffffff]
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
hpet0: 8 comparators, 64-bit 24.000000 MHz counter
clocksource: Switched to clocksource tsc-early
VFS: Disk quotas dquot_6.6.0
VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
AppArmor: AppArmor Filesystem Enabled
pnp: PnP ACPI init
system 00:00: [mem 0x40000000-0x403fffff] could not be reserved
system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:01: [io  0x1800-0x18fe] has been reserved
system 00:01: [mem 0xfd000000-0xfd69ffff] has been reserved
system 00:01: [mem 0xfd6b0000-0xfd6cffff] has been reserved
system 00:01: [mem 0xfd6f0000-0xfdffffff] has been reserved
system 00:01: [mem 0xfe000000-0xfe01ffff] could not be reserved
system 00:01: [mem 0xfe200000-0xfe7fffff] has been reserved
system 00:01: [mem 0xff000000-0xffffffff] has been reserved
system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:02: [io  0xff00-0xfffe] has been reserved
system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:03: [io  0x0680-0x069f] has been reserved
system 00:03: [io  0x164e-0x164f] has been reserved
system 00:03: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:04: [io  0x1854-0x1857] has been reserved
system 00:04: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
pnp 00:05: Plug and Play ACPI device, IDs PNP0303 (active)
system 00:06: [mem 0xfed10000-0xfed17fff] has been reserved
system 00:06: [mem 0xfed18000-0xfed18fff] has been reserved
system 00:06: [mem 0xfed19000-0xfed19fff] has been reserved
system 00:06: [mem 0xe0000000-0xefffffff] has been reserved
system 00:06: [mem 0xfed20000-0xfed3ffff] has been reserved
system 00:06: [mem 0xfed90000-0xfed93fff] could not be reserved
system 00:06: [mem 0xfed45000-0xfed8ffff] has been reserved
system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:07: [mem 0xfe038000-0xfe038fff] has been reserved
system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
pnp: PnP ACPI: found 8 devices
clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
NET: Registered protocol family 2
tcp_listen_portaddr_hash hash table entries: 4096 (order: 4, 65536 bytes, linear)
TCP established hash table entries: 65536 (order: 7, 524288 bytes, linear)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)
TCP: Hash tables configured (established 65536 bind 65536)
UDP hash table entries: 4096 (order: 5, 131072 bytes, linear)
UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes, linear)
NET: Registered protocol family 1
NET: Registered protocol family 44
pci 0000:00:1d.0: PCI bridge to [bus 01]
pci 0000:00:1d.0:   bridge window [io  0x2000-0x2fff]
pci 0000:00:1d.0:   bridge window [mem 0xb1300000-0xb13fffff]
pci 0000:00:1d.2: PCI bridge to [bus 02]
pci 0000:00:1d.2:   bridge window [mem 0xb1200000-0xb12fffff]
pci 0000:00:1d.4: PCI bridge to [bus 03]
pci 0000:00:1d.4:   bridge window [mem 0xb1100000-0xb11fffff]
pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
pci_bus 0000:00: resource 7 [mem 0x9b800000-0xdfffffff window]
pci_bus 0000:00: resource 8 [mem 0xfc800000-0xfe7fffff window]
pci_bus 0000:01: resource 0 [io  0x2000-0x2fff]
pci_bus 0000:01: resource 1 [mem 0xb1300000-0xb13fffff]
pci_bus 0000:02: resource 1 [mem 0xb1200000-0xb12fffff]
pci_bus 0000:03: resource 1 [mem 0xb1100000-0xb11fffff]
pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 51656K
PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
software IO TLB: mapped [mem 0x6e7f1000-0x727f1000] (64MB)
platform rtc_cmos: registered platform RTC device (no PNP device found)
check: Scanning for low memory corruption every 60 seconds
Initialise system trusted keyrings
Key type blacklist registered
workingset: timestamp_bits=36 max_order=21 bucket_order=0
zbud: loaded
squashfs: version 4.0 (2009/01/31) Phillip Lougher
fuse: init (API version 7.31)
integrity: Platform Keyring initialized
Key type asymmetric registered
Asymmetric key parser 'x509' registered
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
io scheduler mq-deadline registered
pcieport 0000:00:1d.0: PME: Signaling with IRQ 122
pcieport 0000:00:1d.0: AER: enabled with IRQ 122
pcieport 0000:00:1d.0: DPC: enabled with IRQ 122
pcieport 0000:00:1d.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
pcieport 0000:00:1d.2: PME: Signaling with IRQ 123
pcieport 0000:00:1d.2: AER: enabled with IRQ 123
pcieport 0000:00:1d.2: DPC: enabled with IRQ 123
pcieport 0000:00:1d.2: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
pcieport 0000:00:1d.4: PME: Signaling with IRQ 124
pcieport 0000:00:1d.4: AER: enabled with IRQ 124
pcieport 0000:00:1d.4: DPC: enabled with IRQ 124
pcieport 0000:00:1d.4: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
efifb: probing for efifb
efifb: showing boot graphics
efifb: framebuffer at 0xa0000000, using 8100k, total 8100k
efifb: mode is 1920x1080x32, linelength=7680, pages=1
efifb: scrolling: redraw
efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
fbcon: Deferring console take-over
fb0: EFI VGA frame buffer device
intel_idle: MWAIT substates: 0x11142120
intel_idle: v0.5.1 model 0x8E
intel_idle: Local APIC timer is reliable in all C-states
ACPI: AC Adapter [ACAD] (off-line)
input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
ACPI: Lid Switch [LID0]
input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
ACPI: Power Button [PWRB]
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
ACPI: Power Button [PWRF]
ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECRD], AE_NOT_FOUND (20200528/psargs-330)
No Local Variables are initialized for Method [_TMP]
No Arguments are initialized for method [_TMP]
ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
[Firmware Bug]: Invalid critical threshold (0)
ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.ECRD], AE_NOT_FOUND (20200528/psargs-330)
No Local Variables are initialized for Method [_TMP]
No Arguments are initialized for method [_TMP]
ACPI Error: Aborting method \_TZ.TZ00._TMP due to previous error (AE_NOT_FOUND) (20200528/psparse-529)
Linux agpgart interface v0.103
loop: module loaded
libphy: Fixed MDIO Bus: probed
tun: Universal TUN/TAP device driver, 1.6
PPP generic driver version 2.4.2
VFIO - User Level meta-driver version: 0.3
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ehci-platform: EHCI generic platform driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
ohci-platform: OHCI generic platform driver
uhci_hcd: USB Universal Host Controller Interface driver
i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
serio: i8042 KBD port at 0x60,0x64 irq 1
mousedev: PS/2 mouse device common for all mice
rtc_cmos rtc_cmos: RTC can wake from S4
rtc_cmos rtc_cmos: registered as rtc0
rtc_cmos rtc_cmos: setting system clock to 2021-05-11T04:29:48 UTC (1620707388)
rtc_cmos rtc_cmos: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
i2c /dev entries driver
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.42.0-ioctl (2020-02-27) initialised: dm-devel@redhat.com
platform eisa.0: Probing EISA bus 0
platform eisa.0: EISA: Cannot allocate resource for mainboard
platform eisa.0: Cannot allocate resource for EISA slot 1
platform eisa.0: Cannot allocate resource for EISA slot 2
platform eisa.0: Cannot allocate resource for EISA slot 3
platform eisa.0: Cannot allocate resource for EISA slot 4
platform eisa.0: Cannot allocate resource for EISA slot 5
platform eisa.0: Cannot allocate resource for EISA slot 6
platform eisa.0: Cannot allocate resource for EISA slot 7
platform eisa.0: Cannot allocate resource for EISA slot 8
platform eisa.0: EISA: Detected 0 cards
intel_pstate: Intel P-state driver initializing
intel_pstate: HWP enabled
ledtrig-cpu: registered to indicate activity on CPUs
EFI Variables Facility v0.08 2004-May-17
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
intel_pmc_core INT33A1:00:  initialized
drop_monitor: Initializing network drop monitor service
NET: Registered protocol family 10
Segment Routing with IPv6
NET: Registered protocol family 17
Key type dns_resolver registered
microcode: sig=0x806ec, pf=0x4, revision=0xde
microcode: Microcode Update Driver: v2.2.
IPI shorthand broadcast: enabled
sched_clock: Marking stable (917524071, 5499835)->(927108782, -4084876)
registered taskstats version 1
Loading compiled-in X.509 certificates
Loaded X.509 cert 'Build time autogenerated kernel key: 76eda9298d4765a62ac93bc1887b5735875ee8fe'
Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969'
Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19'
zswap: loaded using pool lzo/zbud
Key type ._fscrypt registered
Key type .fscrypt registered
Key type fscrypt-provisioning registered
Key type trusted registered
Key type encrypted registered
AppArmor: AppArmor sha1 policy hashing enabled
integrity: Loading X.509 certificate: UEFI:db
integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
integrity: Loading X.509 certificate: UEFI:db
integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
integrity: Loading X.509 certificate: UEFI:MokListRT
integrity: Loaded X.509 cert 'SomeOrg: shim: a01ee84e9b37ace407961cc468c5909447878469'
integrity: Loading X.509 certificate: UEFI:MokListRT
integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63'
ima: Allocated hash algorithm: sha1
ima: No architecture policies found
evm: Initialising EVM extended attributes:
evm: security.selinux
evm: security.SMACK64
evm: security.SMACK64EXEC
evm: security.SMACK64TRANSMUTE
evm: security.SMACK64MMAP
evm: security.apparmor
evm: security.ima
evm: security.capability
evm: HMAC attrs: 0x1
PM:   Magic number: 5:168:464
RAS: Correctable Errors collector initialized.
tsc: Refined TSC clocksource calibration: 2111.998 MHz
clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x1e71768ef8b, max_idle_ns: 440795218977 ns
clocksource: Switched to clocksource tsc
battery: ACPI: Battery Slot [BAT1] (battery present)
Freeing unused decrypted memory: 2040K
Freeing unused kernel image (initmem) memory: 2644K
Write protecting the kernel read-only data: 22528k
Freeing unused kernel image (text/rodata gap) memory: 2044K
Freeing unused kernel image (rodata/data gap) memory: 708K
x86/mm: Checked W+X mappings: passed, no W+X pages found.
Run /init as init process
  with arguments:
    /init
    splash
  with environment:
    HOME=/
    TERM=linux
    BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic
hid: raw HID events driver (C) Jiri Kosina
acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
acpi PNP0C14:04: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
acpi PNP0C14:05: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
xhci_hcd 0000:00:14.0: xHCI Host Controller
xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
ahci 0000:00:17.0: version 3.0
ahci 0000:00:17.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x2 impl SATA mode
ahci 0000:00:17.0: flags: 64bit ncq sntf pm clo only pio slum part deso sadm sds apst 
xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x110 quirks 0x0000000000009810
xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.08
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: xHCI Host Controller
usb usb1: Manufacturer: Linux 5.8.0-48-generic xhci-hcd
usb usb1: SerialNumber: 0000:00:14.0
scsi host0: ahci
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 12 ports detected
scsi host1: ahci
ata1: DUMMY
ata2: SATA max UDMA/133 abar m2048@0xb142c000 port 0xb142c180 irq 125
xhci_hcd 0000:00:14.0: xHCI Host Controller
xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
xhci_hcd 0000:00:14.0: Host supports USB 3.1 Enhanced SuperSpeed
usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.08
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: xHCI Host Controller
usb usb2: Manufacturer: Linux 5.8.0-48-generic xhci-hcd
usb usb2: SerialNumber: 0000:00:14.0
hub 2-0:1.0: USB hub found
rtsx_pci 0000:02:00.0: enabling device (0000 -> 0002)
hub 2-0:1.0: 6 ports detected
intel-lpss 0000:00:15.0: enabling device (0000 -> 0002)
idma64 idma64.0: Found Intel integrated DMA 64-bit
i801_smbus 0000:00:1f.4: enabling device (0000 -> 0003)
nvme nvme0: pci function 0000:03:00.0
i801_smbus 0000:00:1f.4: SPD Write Disable is set
i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
nvme nvme0: 8/0/0 default/read/poll queues
i2c i2c-0: 1/2 memory slots populated (from DMI)
 nvme0n1: p1 p2 p3 p4 p5 p6 p7 p8
i2c_hid i2c-ELAN0632:00: supply vdd not found, using dummy regulator
i2c_hid i2c-ELAN0632:00: supply vddl not found, using dummy regulator
libphy: r8169: probed
r8169 0000:01:00.0 eth0: RTL8168h/8111h, b4:a9:fc:d2:95:07, XID 541, IRQ 137
r8169 0000:01:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
intel-lpss 0000:00:1e.0: enabling device (0000 -> 0002)
idma64 idma64.1: Found Intel integrated DMA 64-bit
r8169 0000:01:00.0 enp1s0: renamed from eth0
ata2: SATA link down (SStatus 4 SControl 300)
usb 1-5: new full-speed USB device number 2 using xhci_hcd
usb 1-5: New USB device found, idVendor=04f3, idProduct=0c4b, bcdDevice= 1.74
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-5: Product: ELAN:Fingerprint
usb 1-5: Manufacturer: ELAN
fbcon: Taking over console
Console: switching to colour frame buffer device 240x67
EXT4-fs (nvme0n1p5): mounted filesystem with ordered data mode. Opts: (null)
usb 1-6: new high-speed USB device number 3 using xhci_hcd
systemd[1]: Inserted module 'autofs4'
systemd[1]: systemd 245.4-4ubuntu3.6 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)
systemd[1]: Detected architecture x86-64.
systemd[1]: Set hostname to .
usb 1-6: New USB device found, idVendor=04ca, idProduct=7070, bcdDevice= 0.24
usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-6: Product: Integrated Camera
usb 1-6: Manufacturer: 8SSC20F27068L1GZ077A7A6
systemd[1]: /etc/systemd/system/anydesk.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/anydesk.pid → /run/anydesk.pid; please update the unit file accordingly.
systemd[1]: Created slice system-modprobe.slice.
systemd[1]: Created slice system-systemd\x2dfsck.slice.
systemd[1]: Created slice User and Session Slice.
systemd[1]: Started Forward Password Requests to Wall Directory Watch.
systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
systemd[1]: Reached target User and Group Name Lookups.
systemd[1]: Reached target Remote File Systems.
systemd[1]: Reached target Slices.
systemd[1]: Listening on Syslog Socket.
systemd[1]: Listening on fsck to fsckd communication Socket.
systemd[1]: Listening on initctl Compatibility Named Pipe.
systemd[1]: Listening on Journal Audit Socket.
systemd[1]: Listening on Journal Socket (/dev/log).
systemd[1]: Listening on Journal Socket.
systemd[1]: Listening on udev Control Socket.
systemd[1]: Listening on udev Kernel Socket.
systemd[1]: Mounting Huge Pages File System...
systemd[1]: Mounting POSIX Message Queue File System...
systemd[1]: Mounting Kernel Debug File System...
systemd[1]: Mounting Kernel Trace File System...
systemd[1]: Starting Journal Service...
systemd[1]: Starting Set the console keyboard layout...
systemd[1]: Starting Create list of static device nodes for the current kernel...
systemd[1]: Starting Load Kernel Module drm...
systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
systemd[1]: Starting Load Kernel Modules...
systemd[1]: Starting Remount Root and Kernel File Systems...
systemd[1]: Starting udev Coldplug all Devices...
systemd[1]: Starting Uncomplicated firewall...
systemd[1]: Mounted Huge Pages File System.
systemd[1]: Mounted POSIX Message Queue File System.
systemd[1]: Mounted Kernel Debug File System.
systemd[1]: Mounted Kernel Trace File System.
systemd[1]: Finished Create list of static device nodes for the current kernel.
systemd[1]: Finished Uncomplicated firewall.
EXT4-fs (nvme0n1p5): re-mounted. Opts: errors=remount-ro
systemd[1]: modprobe@drm.service: Succeeded.
systemd[1]: Finished Load Kernel Module drm.
systemd[1]: Finished Remount Root and Kernel File Systems.
systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
lp: driver loaded but no devices found
systemd[1]: Starting Load/Save Random Seed...
systemd[1]: Starting Create System Users...
ppdev: user-space parallel port driver
systemd[1]: Finished Load Kernel Modules.
systemd[1]: Mounting FUSE Control File System...
systemd[1]: Mounting Kernel Configuration File System...
systemd[1]: Starting Apply Kernel Variables...
usb 1-10: new full-speed USB device number 4 using xhci_hcd
systemd[1]: Finished Load/Save Random Seed.
systemd[1]: Mounted FUSE Control File System.
systemd[1]: Mounted Kernel Configuration File System.
systemd[1]: Finished Create System Users.
systemd[1]: Starting Create Static Device Nodes in /dev...
systemd[1]: Finished Apply Kernel Variables.
systemd[1]: Finished Create Static Device Nodes in /dev.
systemd[1]: Starting udev Kernel Device Manager...
systemd[1]: Finished Set the console keyboard layout.
systemd[1]: Reached target Local File Systems (Pre).
systemd[1]: Mounting Mount unit for core18, revision 1988...
systemd[1]: Mounting Mount unit for core18, revision 1997...
systemd[1]: Mounting Mount unit for gnome-3-34-1804, revision 60...
systemd[1]: Mounting Mount unit for gnome-3-34-1804, revision 66...
systemd[1]: Mounting Mount unit for gtk-common-themes, revision 1514...
systemd[1]: Mounting Mount unit for gtk-common-themes, revision 1515...
systemd[1]: Mounting Mount unit for snap-store, revision 467...
systemd[1]: Mounting Mount unit for snap-store, revision 518...
systemd[1]: Mounting Mount unit for snapd, revision 11402...
systemd[1]: Mounting Mount unit for snapd, revision 11588...
systemd[1]: Mounting Mount unit for vlc, revision 2103...
systemd[1]: Started Journal Service.
systemd-journald[307]: Received client request to flush runtime journal.
usb 1-10: New USB device found, idVendor=8087, idProduct=0aaa, bcdDevice= 0.02
usb 1-10: New USB device strings: Mfr=0, Product=0, SerialNumber=0
elan_i2c i2c-ELAN0632:00: supply vcc not found, using dummy regulator
input: Ideapad extra buttons as /devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC2004:00/input/input4
proc_thermal 0000:00:04.0: enabling device (0000 -> 0002)
mei_me 0000:00:16.0: enabling device (0000 -> 0002)
intel_rapl_common: Found RAPL domain package
intel_rapl_common: Found RAPL domain dram
cfg80211: Loading compiled-in X.509 certificates for regulatory database
cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
proc_thermal 0000:00:04.0: Creating sysfs group for PROC_THERMAL_PCI
dw-apb-uart.1: ttyS4 at MMIO 0xb1429000 (irq = 20, base_baud = 7500000) is a 16550A
Intel(R) Wireless WiFi driver for Linux
iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
pstore: Using crash dump compression: deflate
pstore: Registered efi as persistent store backend
mc: Linux media interface: v0.10
videodev: Linux video capture interface: v2.00
iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-56.ucode failed with error -2
iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 65.3.35.22
iwlwifi 0000:00:14.3: loaded firmware version 55.d9698065.0 QuZ-a0-jf-b0-55.ucode op_mode iwlmvm
iwlwifi 0000:00:14.3: Direct firmware load for iwl-debug-yoyo.bin failed with error -2
uvcvideo: Found UVC 1.00 device Integrated Camera (04ca:7070)
input: Integrated Camera: Integrated C as /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/input/input5
usbcore: registered new interface driver uvcvideo
USB Video Class driver (1.1.1)
elan_i2c i2c-ELAN0632:00: Elan Touchpad: Module ID: 0x005b, Firmware: 0x0001, Sample: 0x0002, IAP: 0x000d
input: Elan Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN0632:00/input/input6
wl: loading out-of-tree module taints kernel.
wl: module license 'MIXED/Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
wl: module verification failed: signature and/or required key missing - tainting kernel
RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer
RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
RAPL PMU: hw unit of domain package 2^-14 Joules
RAPL PMU: hw unit of domain dram 2^-14 Joules
RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
RAPL PMU: hw unit of domain psys 2^-14 Joules
checking generic (a0000000 7e9000) vs hw (b0000000 1000000)
checking generic (a0000000 7e9000) vs hw (a0000000 10000000)
fb0: switching to inteldrmfb from EFI VGA
Console: switching to colour dummy device 80x25
i915 0000:00:02.0: vgaarb: deactivate vga console
cryptd: max_cpu_qlen set to 1000
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[drm] Initialized i915 1.6.0 20200515 for 0000:00:02.0 on minor 0
ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7
fbcon: i915drmfb (fb0) is primary device
Console: switching to colour frame buffer device 240x67
i915 0000:00:02.0: fb0: i915drmfb frame buffer device
AVX2 version of gcm_enc/dec engaged.
AES CTR mode by8 optimization enabled
iwlwifi 0000:00:14.3: Detected Intel(R) Wireless-AC 9560 160MHz, REV=0x354
intel_rapl_common: Found RAPL domain package
intel_rapl_common: Found RAPL domain core
intel_rapl_common: Found RAPL domain uncore
intel_rapl_common: Found RAPL domain dram
mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
Bluetooth: Core ver 2.22
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
usbcore: registered new interface driver btusb
Bluetooth: hci0: Bootloader revision 0.1 build 0 week 30 2018
Bluetooth: hci0: Device revision is 2
Bluetooth: hci0: Secure boot is enabled
Bluetooth: hci0: OTP lock is enabled
Bluetooth: hci0: API lock is enabled
Bluetooth: hci0: Debug lock is disabled
Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Bluetooth: hci0: Found device firmware: intel/ibt-19-0-1.sfi
iwlwifi 0000:00:14.3: base HW address: 9c:29:76:fa:e0:fb
snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC257: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
snd_hda_codec_realtek hdaudioC0D0:    inputs:
snd_hda_codec_realtek hdaudioC0D0:      Mic=0x19
snd_hda_codec_realtek hdaudioC0D0:      Internal Mic=0x12
thermal thermal_zone7: failed to read out thermal zone (-61)
iwlwifi 0000:00:14.3 wlp0s20f3: renamed from wlan0
input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input8
input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input9
input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input10
input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input11
input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input12
input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input13
input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input14
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
Adding 7812092k swap on /dev/nvme0n1p6.  Priority:-2 extents:1 across:7812092k SSFS
EXT4-fs (nvme0n1p8): mounted filesystem with ordered data mode. Opts: (null)
audit: type=1400 audit(1620707400.015:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="ippusbxd" pid=672 comm="apparmor_parser"
audit: type=1400 audit(1620707400.015:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" pid=670 comm="apparmor_parser"
audit: type=1400 audit(1620707400.015:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=674 comm="apparmor_parser"
audit: type=1400 audit(1620707400.015:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=674 comm="apparmor_parser"
audit: type=1400 audit(1620707400.015:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=674 comm="apparmor_parser"
audit: type=1400 audit(1620707400.019:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" pid=669 comm="apparmor_parser"
audit: type=1400 audit(1620707400.019:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-senddoc" pid=679 comm="apparmor_parser"
audit: type=1400 audit(1620707400.019:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=680 comm="apparmor_parser"
audit: type=1400 audit(1620707400.019:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=680 comm="apparmor_parser"
audit: type=1400 audit(1620707400.019:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=677 comm="apparmor_parser"
Bluetooth: hci0: Waiting for firmware download to complete
Bluetooth: hci0: Firmware loaded in 1560177 usecs
Bluetooth: hci0: Waiting for device to boot
Bluetooth: hci0: Device booted in 20102 usecs
Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-1.ddc
Bluetooth: hci0: Applying Intel DDC parameters completed
Bluetooth: hci0: Firmware revision 0.0 build 121 week 36 2020
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: BNEP socket layer initialized
NET: Registered protocol family 38
process '/usr/bin/anydesk' started with executable stack
aufs 5.x-rcN-20200622
Generic FE-GE Realtek PHY r8169-100:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-100:00, irq=IGNORE)
r8169 0000:01:00.0 enp1s0: Link is Down
rfkill: input handler disabled
wlp0s20f3: authenticate with 1c:3b:f3:1d:a3:c2
wlp0s20f3: send auth to 1c:3b:f3:1d:a3:c2 (try 1/3)
wlp0s20f3: authenticated
wlp0s20f3: associate with 1c:3b:f3:1d:a3:c2 (try 1/3)
wlp0s20f3: RX AssocResp from 1c:3b:f3:1d:a3:c2 (capab=0x411 status=0 aid=4)
wlp0s20f3: associated
IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready
kauditd_printk_skb: 28 callbacks suppressed
audit: type=1400 audit(1620707406.743:40): apparmor="STATUS" operation="profile_load" profile="unconfined" name="docker-default" pid=1603 comm="apparmor_parser"
bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
Bridge firewalling registered
bpfilter: Loaded bpfilter_umh pid 1656
Started bpfilter
Initializing XFRM netlink socket
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
ucsi_acpi USBC000:00: PPM init failed (-110)
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
rfkill: input handler enabled
rfkill: input handler disabled
audit: type=1400 audit(1620707501.760:41): apparmor="DENIED" operation="capable" profile="/snap/snapd/11588/usr/lib/snapd/snap-confine" pid=2467 comm="snap-confine" capability=4  capname="fsetid"
audit: type=1326 audit(1620707503.517:42): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.snap-store.ubuntu-software pid=2467 comm="snap-store" exe="/snap/snap-store/518/usr/bin/snap-store" sig=0 arch=c000003e syscall=314 compat=0 ip=0x7fc24fe6e639 code=0x50000
audit: type=1107 audit(1620707503.797:43): pid=718 uid=103 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.9" pid=2467 label="snap.snap-store.ubuntu-software" peer_pid=720 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?'
audit: type=1107 audit(1620707509.765:44): pid=718 uid=103 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/org/freedesktop/PolicyKit1/Authority" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.8" pid=2467 label="snap.snap-store.ubuntu-software" peer_pid=737 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?'
audit: type=1107 audit(1620707509.765:45): pid=718 uid=103 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/org/freedesktop/PolicyKit1/Authority" interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" mask="send" name=":1.8" pid=2467 label="snap.snap-store.ubuntu-software" peer_pid=737 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?'
audit: type=1107 audit(1620707509.777:46): pid=718 uid=103 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/org/freedesktop/PolicyKit1/Authority" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.8" pid=2467 label="snap.snap-store.ubuntu-software" peer_pid=737 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?'
audit: type=1107 audit(1620707509.781:47): pid=718 uid=103 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/org/freedesktop/PolicyKit1/Authority" interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" mask="send" name=":1.8" pid=2467 label="snap.snap-store.ubuntu-software" peer_pid=737 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?'
audit: type=1400 audit(1620707510.033:48): apparmor="DENIED" operation="open" profile="snap.snap-store.ubuntu-software" name="/etc/PackageKit/Vendor.conf" pid=2467 comm="snap-store" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
audit: type=1400 audit(1620707594.818:49): apparmor="DENIED" operation="open" profile="snap.snap-store.ubuntu-software" name="/var/lib/snapd/hostfs/usr/share/gdm/greeter/applications/gnome-initial-setup.desktop" pid=2467 comm="pool-org.gnome." requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
audit: type=1400 audit(1620707594.846:50): apparmor="DENIED" operation="open" profile="snap.snap-store.ubuntu-software" name="/var/lib/snapd/hostfs/usr/share/gdm/greeter/applications/gnome-initial-setup.desktop" pid=2467 comm="pool-org.gnome." requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
audit: type=1326 audit(1620707595.322:51): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.snap-store.ubuntu-software pid=2467 comm="pool-org.gnome." exe="/snap/snap-store/518/usr/bin/snap-store" sig=0 arch=c000003e syscall=93 compat=0 ip=0x7fc24fe644e7 code=0x50000
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
usb 1-1: new full-speed USB device number 5 using xhci_hcd
usb 1-1: New USB device found, idVendor=2a70, idProduct=1881, bcdDevice= 1.02
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: ED117
usb 1-1: Manufacturer: OnePlus Technology
usb 1-1: SerialNumber: 18835
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver snd-usb-audio
input: OnePlus Technology ED117 as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.3/0003:2A70:1881.0001/input/input15
hid-generic 0003:2A70:1881.0001: input,hidraw0: USB HID v1.11 Device [OnePlus Technology ED117] on usb-0000:00:14.0-1/input3
usb 1-1: USB disconnect, device number 5
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
usb 1-1: new full-speed USB device number 6 using xhci_hcd
usb 1-1: New USB device found, idVendor=2a70, idProduct=1881, bcdDevice= 1.02
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: ED117
usb 1-1: Manufacturer: OnePlus Technology
usb 1-1: SerialNumber: 18835
input: OnePlus Technology ED117 as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.3/0003:2A70:1881.0002/input/input16
hid-generic 0003:2A70:1881.0002: input,hidraw0: USB HID v1.11 Device [OnePlus Technology ED117] on usb-0000:00:14.0-1/input3
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
perf: interrupt took too long (2504 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
SGI XFS with ACLs, security attributes, realtime, quota, no debug enabled
JFS: nTxBlock = 8192, nTxLock = 65536
ntfs: driver 2.1.32 [Flags: R/O MODULE].
QNX4 filesystem 0.2.3 registered.
raid6: avx2x4   gen() 29945 MB/s
raid6: avx2x4   xor() 13058 MB/s
raid6: avx2x2   gen() 35881 MB/s
raid6: avx2x2   xor() 19930 MB/s
raid6: avx2x1   gen() 29286 MB/s
raid6: avx2x1   xor() 19371 MB/s
raid6: sse2x4   gen() 14185 MB/s
raid6: sse2x4   xor()  8953 MB/s
raid6: sse2x2   gen() 17018 MB/s
raid6: sse2x2   xor() 10226 MB/s
raid6: sse2x1   gen() 12529 MB/s
raid6: sse2x1   xor()  7162 MB/s
raid6: using algorithm avx2x2 gen() 35881 MB/s
raid6: .... xor() 19930 MB/s, rmw enabled
raid6: using avx2x2 recovery algorithm
xor: automatically using best checksumming function   avx       
Btrfs loaded, crc32c=crc32c-intel
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
usb 1-1: USB disconnect, device number 6
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
usb 1-1: new full-speed USB device number 7 using xhci_hcd
usb 1-1: New USB device found, idVendor=2a70, idProduct=1881, bcdDevice= 1.02
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: ED117
usb 1-1: Manufacturer: OnePlus Technology
usb 1-1: SerialNumber: 18835
input: OnePlus Technology ED117 as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.3/0003:2A70:1881.0003/input/input17
hid-generic 0003:2A70:1881.0003: input,hidraw0: USB HID v1.11 Device [OnePlus Technology ED117] on usb-0000:00:14.0-1/input3
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
usb 1-1: USB disconnect, device number 7
usb 1-1: new full-speed USB device number 8 using xhci_hcd
usb 1-1: New USB device found, idVendor=2a70, idProduct=1881, bcdDevice= 1.02
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: ED117
usb 1-1: Manufacturer: OnePlus Technology
usb 1-1: SerialNumber: 18835
input: OnePlus Technology ED117 as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.3/0003:2A70:1881.0004/input/input18
hid-generic 0003:2A70:1881.0004: input,hidraw0: USB HID v1.11 Device [OnePlus Technology ED117] on usb-0000:00:14.0-1/input3
usb 1-1: USB disconnect, device number 8
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
perf: interrupt took too long (3148 > 3130), lowering kernel.perf_event_max_sample_rate to 63500
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
perf: interrupt took too long (3972 > 3935), lowering kernel.perf_event_max_sample_rate to 50250
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
perf: interrupt took too long (4996 > 4965), lowering kernel.perf_event_max_sample_rate to 40000
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
audit: type=1400 audit(1620716392.753:52): apparmor="ALLOWED" operation="connect" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_354d4944f465b5e8aa5997ef5ee12" pid=28980 comm="oosplash" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
audit: type=1400 audit(1620716392.753:53): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_354d4944f465b5e8aa5997ef5ee12" pid=28980 comm="oosplash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
audit: type=1400 audit(1620716392.753:54): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_354d4944f465b5e8aa5997ef5ee12" pid=28980 comm="oosplash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
audit: type=1400 audit(1620716392.753:55): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_354d4944f465b5e8aa5997ef5ee12" pid=28980 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000
audit: type=1400 audit(1620716392.753:56): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_354d4944f465b5e8aa5997ef5ee12" pid=28980 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
audit: type=1400 audit(1620716659.911:57): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/usr/share/zoneinfo-icu/44/le/zoneinfo64.res" pid=4935 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
audit: type=1400 audit(1620716659.911:58): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/usr/share/zoneinfo-icu/44/le/timezoneTypes.res" pid=4935 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
audit: type=1400 audit(1620716910.306:59): apparmor="ALLOWED" operation="connect" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_354d4944f465b5e8aa5997ef5ee12" pid=29991 comm="oosplash" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
audit: type=1400 audit(1620716910.306:60): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_354d4944f465b5e8aa5997ef5ee12" pid=29991 comm="oosplash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
audit: type=1400 audit(1620716910.306:61): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_354d4944f465b5e8aa5997ef5ee12" pid=29991 comm="oosplash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
audit: type=1400 audit(1620716910.306:62): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_354d4944f465b5e8aa5997ef5ee12" pid=29991 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000
audit: type=1400 audit(1620716910.306:63): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_354d4944f465b5e8aa5997ef5ee12" pid=29991 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 
pcieport 0000:00:1d.4: AER: Corrected error received: 0000:03:00.0
nvme 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
nvme 0000:03:00.0: AER:   device [15b7:5006] error status/mask=00000001/0000e000
nvme 0000:03:00.0: AER:    [ 0] RxErr                 

Return To osbench-resultss System Information