Mar 04 20:31:09 volumiow kernel: Linux version 6.12.57-volumio (gkkpch@UbuntuVM24.04) (gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #2 SMP PREEMPT_DYNAMIC Thu Nov 13 17:08:37 CET 2025 Mar 04 20:31:09 volumiow kernel: Command line: BOOT_IMAGE=vmlinuz initramfs.clear splash plymouth.ignore-serial-consoles quiet loglevel=0 bootdelay=5 biosdevname=0 imgpart=UUID=b0a058e9-0951-4405-9f54-2004a4130548 bootpart=UUID=5F54-6886 datapart=UUID=a75a63ef-7a01-4f5e-b572-6ddd34d5e25f hwdevice=x86 uuidconfig=syslinux.cfg,efi/BOOT/grub.cfg imgfile=/volumio_current.sqsh logo.nologo vt.global_cursor_default=0 acpi_backlight=native net.ifnames=0 use_kmsg=no initrd=volumio.initrd Mar 04 20:31:09 volumiow kernel: KERNEL supported cpus: Mar 04 20:31:09 volumiow kernel: Intel GenuineIntel Mar 04 20:31:09 volumiow kernel: AMD AuthenticAMD Mar 04 20:31:09 volumiow kernel: Hygon HygonGenuine Mar 04 20:31:09 volumiow kernel: Centaur CentaurHauls Mar 04 20:31:09 volumiow kernel: zhaoxin Shanghai Mar 04 20:31:09 volumiow kernel: BIOS-provided physical RAM map: Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009c3ff] usable Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x000000000009c400-0x000000000009ffff] reserved Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000085638fff] usable Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x0000000085639000-0x0000000085639fff] ACPI NVS Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x000000008563a000-0x000000008563afff] reserved Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x000000008563b000-0x000000008b2d4fff] usable Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x000000008b2d5000-0x000000008c798fff] reserved Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x000000008c799000-0x000000008c8d4fff] usable Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x000000008c8d5000-0x000000008cfddfff] ACPI NVS Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x000000008cfde000-0x000000008d3fefff] reserved Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x000000008d3ff000-0x000000008d3fffff] usable Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x000000008d400000-0x000000008fffffff] reserved Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved Mar 04 20:31:09 volumiow kernel: BIOS-e820: [mem 0x0000000100000000-0x000000046effffff] usable Mar 04 20:31:09 volumiow kernel: NX (Execute Disable) protection: active Mar 04 20:31:09 volumiow kernel: APIC: Static calls initialized Mar 04 20:31:09 volumiow kernel: SMBIOS 3.0.0 present. Mar 04 20:31:09 volumiow kernel: DMI: Intel Corp NUC7i5BNF/NUC7i5BNF, BIOS 5.12 08/31/2017 Mar 04 20:31:09 volumiow kernel: DMI: Memory slots populated: 2/2 Mar 04 20:31:09 volumiow kernel: tsc: Detected 2700.000 MHz processor Mar 04 20:31:09 volumiow kernel: tsc: Detected 2699.909 MHz TSC Mar 04 20:31:09 volumiow kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved Mar 04 20:31:09 volumiow kernel: e820: remove [mem 0x000a0000-0x000fffff] usable Mar 04 20:31:09 volumiow kernel: last_pfn = 0x46f000 max_arch_pfn = 0x400000000 Mar 04 20:31:09 volumiow kernel: MTRR map: 4 entries (3 fixed + 1 variable; max 23), built from 10 variable MTRRs Mar 04 20:31:09 volumiow kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT Mar 04 20:31:09 volumiow kernel: last_pfn = 0x8d400 max_arch_pfn = 0x400000000 Mar 04 20:31:09 volumiow kernel: found SMP MP-table at [mem 0x000fcbf0-0x000fcbff] Mar 04 20:31:09 volumiow kernel: Using GB pages for direct mapping Mar 04 20:31:09 volumiow kernel: RAMDISK: [mem 0x7b128000-0x7fffffff] Mar 04 20:31:09 volumiow kernel: ACPI: Early table checksum verification disabled Mar 04 20:31:09 volumiow kernel: ACPI: RSDP 0x00000000000F05B0 000024 (v02 ALASKA) Mar 04 20:31:09 volumiow kernel: ACPI: XSDT 0x000000008C8D50A8 0000D4 (v01 ALASKA A M I 01072009 AMI 00010013) Mar 04 20:31:09 volumiow kernel: ACPI: FACP 0x000000008C8FCEF8 000114 (v06 ALASKA A M I 01072009 AMI 00010013) Mar 04 20:31:09 volumiow kernel: ACPI: DSDT 0x000000008C8D5218 027CDE (v02 ALASKA A M I 01072009 INTL 20160422) Mar 04 20:31:09 volumiow kernel: ACPI: FACS 0x000000008CFDDC40 000040 Mar 04 20:31:09 volumiow kernel: ACPI: APIC 0x000000008C8FD010 000084 (v03 ALASKA A M I 01072009 AMI 00010013) Mar 04 20:31:09 volumiow kernel: ACPI: FPDT 0x000000008C8FD098 000044 (v01 ALASKA A M I 01072009 AMI 00010013) Mar 04 20:31:09 volumiow kernel: ACPI: MCFG 0x000000008C8FD0E0 00003C (v01 ALASKA A M I 01072009 MSFT 00000097) Mar 04 20:31:09 volumiow kernel: ACPI: SSDT 0x000000008C8FD120 000322 (v01 SataRe SataTabl 00001000 INTL 20160422) Mar 04 20:31:09 volumiow kernel: ACPI: FIDT 0x000000008C8FD448 00009C (v01 ALASKA A M I 01072009 AMI 00010013) Mar 04 20:31:09 volumiow kernel: ACPI: SSDT 0x000000008C8FD4E8 003154 (v02 SaSsdt SaSsdt 00003000 INTL 20160422) Mar 04 20:31:09 volumiow kernel: ACPI: HPET 0x000000008C900640 000038 (v01 INTEL KBL-ULT 00000001 MSFT 0000005F) Mar 04 20:31:09 volumiow kernel: ACPI: SSDT 0x000000008C900678 00485C (v02 INTEL RVP7Rtd3 00001000 INTL 20160422) Mar 04 20:31:09 volumiow kernel: ACPI: SSDT 0x000000008C904ED8 000DE5 (v02 INTEL Ther_Rvp 00001000 INTL 20160422) Mar 04 20:31:09 volumiow kernel: ACPI: SSDT 0x000000008C905CC0 00065F (v02 INTEL xh_rvp07 00000000 INTL 20160422) Mar 04 20:31:09 volumiow kernel: ACPI: UEFI 0x000000008C906320 000042 (v01 INTEL EDK2 00000002 01000013) Mar 04 20:31:09 volumiow kernel: ACPI: SSDT 0x000000008C906368 000EDE (v02 CpuRef CpuSsdt 00003000 INTL 20160422) Mar 04 20:31:09 volumiow kernel: ACPI: LPIT 0x000000008C907248 000094 (v01 INTEL KBL-ULT 00000000 MSFT 0000005F) Mar 04 20:31:09 volumiow kernel: ACPI: WSMT 0x000000008C9072E0 000028 (v01 INTEL KBL-ULT 00000000 MSFT 0000005F) Mar 04 20:31:09 volumiow kernel: ACPI: SSDT 0x000000008C907308 00029F (v02 INTEL sensrhub 00000000 INTL 20160422) Mar 04 20:31:09 volumiow kernel: ACPI: SSDT 0x000000008C9075A8 003002 (v02 INTEL PtidDevc 00001000 INTL 20160422) Mar 04 20:31:09 volumiow kernel: ACPI: DBGP 0x000000008C90A5B0 000034 (v01 INTEL 00000002 MSFT 0000005F) Mar 04 20:31:09 volumiow kernel: ACPI: DBG2 0x000000008C90A5E8 000054 (v00 INTEL 00000002 MSFT 0000005F) Mar 04 20:31:09 volumiow kernel: ACPI: DMAR 0x000000008C90A640 0000CC (v01 INTEL KBL 00000001 INTL 00000001) Mar 04 20:31:09 volumiow kernel: ACPI: ASF! 0x000000008C90A710 0000A0 (v32 INTEL HCG 00000001 TFSM 000F4240) Mar 04 20:31:09 volumiow kernel: ACPI: Reserving FACP table memory at [mem 0x8c8fcef8-0x8c8fd00b] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving DSDT table memory at [mem 0x8c8d5218-0x8c8fcef5] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving FACS table memory at [mem 0x8cfddc40-0x8cfddc7f] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving APIC table memory at [mem 0x8c8fd010-0x8c8fd093] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving FPDT table memory at [mem 0x8c8fd098-0x8c8fd0db] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving MCFG table memory at [mem 0x8c8fd0e0-0x8c8fd11b] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving SSDT table memory at [mem 0x8c8fd120-0x8c8fd441] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving FIDT table memory at [mem 0x8c8fd448-0x8c8fd4e3] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving SSDT table memory at [mem 0x8c8fd4e8-0x8c90063b] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving HPET table memory at [mem 0x8c900640-0x8c900677] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving SSDT table memory at [mem 0x8c900678-0x8c904ed3] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving SSDT table memory at [mem 0x8c904ed8-0x8c905cbc] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving SSDT table memory at [mem 0x8c905cc0-0x8c90631e] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving UEFI table memory at [mem 0x8c906320-0x8c906361] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving SSDT table memory at [mem 0x8c906368-0x8c907245] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving LPIT table memory at [mem 0x8c907248-0x8c9072db] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving WSMT table memory at [mem 0x8c9072e0-0x8c907307] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving SSDT table memory at [mem 0x8c907308-0x8c9075a6] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving SSDT table memory at [mem 0x8c9075a8-0x8c90a5a9] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving DBGP table memory at [mem 0x8c90a5b0-0x8c90a5e3] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving DBG2 table memory at [mem 0x8c90a5e8-0x8c90a63b] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving DMAR table memory at [mem 0x8c90a640-0x8c90a70b] Mar 04 20:31:09 volumiow kernel: ACPI: Reserving ASF! table memory at [mem 0x8c90a710-0x8c90a7af] Mar 04 20:31:09 volumiow kernel: Zone ranges: Mar 04 20:31:09 volumiow kernel: DMA [mem 0x0000000000001000-0x0000000000ffffff] Mar 04 20:31:09 volumiow kernel: DMA32 [mem 0x0000000001000000-0x00000000ffffffff] Mar 04 20:31:09 volumiow kernel: Normal [mem 0x0000000100000000-0x000000046effffff] Mar 04 20:31:09 volumiow kernel: Movable zone start for each node Mar 04 20:31:09 volumiow kernel: Early memory node ranges Mar 04 20:31:09 volumiow kernel: node 0: [mem 0x0000000000001000-0x000000000009bfff] Mar 04 20:31:09 volumiow kernel: node 0: [mem 0x0000000000100000-0x0000000085638fff] Mar 04 20:31:09 volumiow kernel: node 0: [mem 0x000000008563b000-0x000000008b2d4fff] Mar 04 20:31:09 volumiow kernel: node 0: [mem 0x000000008c799000-0x000000008c8d4fff] Mar 04 20:31:09 volumiow kernel: node 0: [mem 0x000000008d3ff000-0x000000008d3fffff] Mar 04 20:31:09 volumiow kernel: node 0: [mem 0x0000000100000000-0x000000046effffff] Mar 04 20:31:09 volumiow kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000046effffff] Mar 04 20:31:09 volumiow kernel: On node 0, zone DMA: 1 pages in unavailable ranges Mar 04 20:31:09 volumiow kernel: On node 0, zone DMA: 100 pages in unavailable ranges Mar 04 20:31:09 volumiow kernel: On node 0, zone DMA32: 2 pages in unavailable ranges Mar 04 20:31:09 volumiow kernel: On node 0, zone DMA32: 5316 pages in unavailable ranges Mar 04 20:31:09 volumiow kernel: On node 0, zone DMA32: 2858 pages in unavailable ranges Mar 04 20:31:09 volumiow kernel: On node 0, zone Normal: 11264 pages in unavailable ranges Mar 04 20:31:09 volumiow kernel: On node 0, zone Normal: 4096 pages in unavailable ranges Mar 04 20:31:09 volumiow kernel: Reserving Intel graphics memory at [mem 0x8e000000-0x8fffffff] Mar 04 20:31:09 volumiow kernel: ACPI: PM-Timer IO Port: 0x1808 Mar 04 20:31:09 volumiow kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) Mar 04 20:31:09 volumiow kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) Mar 04 20:31:09 volumiow kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) Mar 04 20:31:09 volumiow kernel: ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) Mar 04 20:31:09 volumiow kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119 Mar 04 20:31:09 volumiow kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) Mar 04 20:31:09 volumiow kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Mar 04 20:31:09 volumiow kernel: ACPI: Using ACPI (MADT) for SMP configuration information Mar 04 20:31:09 volumiow kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000 Mar 04 20:31:09 volumiow kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x52 (or later) Mar 04 20:31:09 volumiow kernel: CPU topo: Max. logical packages: 1 Mar 04 20:31:09 volumiow kernel: CPU topo: Max. logical dies: 1 Mar 04 20:31:09 volumiow kernel: CPU topo: Max. dies per package: 1 Mar 04 20:31:09 volumiow kernel: CPU topo: Max. threads per core: 2 Mar 04 20:31:09 volumiow kernel: CPU topo: Num. cores per package: 2 Mar 04 20:31:09 volumiow kernel: CPU topo: Num. threads per package: 4 Mar 04 20:31:09 volumiow kernel: CPU topo: Allowing 4 present CPUs plus 0 hotplug CPUs Mar 04 20:31:09 volumiow kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff] Mar 04 20:31:09 volumiow kernel: PM: hibernation: Registered nosave memory: [mem 0x0009c000-0x000fffff] Mar 04 20:31:09 volumiow kernel: PM: hibernation: Registered nosave memory: [mem 0x85639000-0x8563afff] Mar 04 20:31:09 volumiow kernel: PM: hibernation: Registered nosave memory: [mem 0x8b2d5000-0x8c798fff] Mar 04 20:31:09 volumiow kernel: PM: hibernation: Registered nosave memory: [mem 0x8c8d5000-0x8d3fefff] Mar 04 20:31:09 volumiow kernel: PM: hibernation: Registered nosave memory: [mem 0x8d400000-0xffffffff] Mar 04 20:31:09 volumiow kernel: [mem 0x90000000-0xdfffffff] available for PCI devices Mar 04 20:31:09 volumiow kernel: Booting paravirtualized kernel on bare hardware Mar 04 20:31:09 volumiow kernel: clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns Mar 04 20:31:09 volumiow kernel: setup_percpu: NR_CPUS:64 nr_cpumask_bits:4 nr_cpu_ids:4 nr_node_ids:1 Mar 04 20:31:09 volumiow kernel: percpu: Embedded 59 pages/cpu s201368 r8192 d32104 u524288 Mar 04 20:31:09 volumiow kernel: pcpu-alloc: s201368 r8192 d32104 u524288 alloc=1*2097152 Mar 04 20:31:09 volumiow kernel: pcpu-alloc: [0] 0 1 2 3 Mar 04 20:31:09 volumiow kernel: Kernel command line: BOOT_IMAGE=vmlinuz initramfs.clear splash plymouth.ignore-serial-consoles quiet loglevel=0 bootdelay=5 biosdevname=0 imgpart=UUID=b0a058e9-0951-4405-9f54-2004a4130548 bootpart=UUID=5F54-6886 datapart=UUID=a75a63ef-7a01-4f5e-b572-6ddd34d5e25f hwdevice=x86 uuidconfig=syslinux.cfg,efi/BOOT/grub.cfg imgfile=/volumio_current.sqsh logo.nologo vt.global_cursor_default=0 acpi_backlight=native net.ifnames=0 use_kmsg=no initrd=volumio.initrd Mar 04 20:31:09 volumiow kernel: Unknown kernel command line parameters "splash bootdelay=5 biosdevname=0 imgpart=UUID=b0a058e9-0951-4405-9f54-2004a4130548 bootpart=UUID=5F54-6886 datapart=UUID=a75a63ef-7a01-4f5e-b572-6ddd34d5e25f hwdevice=x86 uuidconfig=syslinux.cfg,efi/BOOT/grub.cfg imgfile=/volumio_current.sqsh use_kmsg=no", will be passed to user space. Mar 04 20:31:09 volumiow kernel: random: crng init done Mar 04 20:31:09 volumiow kernel: Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) Mar 04 20:31:09 volumiow kernel: Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) Mar 04 20:31:09 volumiow kernel: Built 1 zonelists, mobility grouping on. Total pages: 4170667 Mar 04 20:31:09 volumiow kernel: mem auto-init: stack:all(pattern), heap alloc:off, heap free:off Mar 04 20:31:09 volumiow kernel: software IO TLB: area num 4. Mar 04 20:31:09 volumiow kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 Mar 04 20:31:09 volumiow kernel: Kernel/User page tables isolation: enabled Mar 04 20:31:09 volumiow kernel: ftrace: allocating 43851 entries in 172 pages Mar 04 20:31:09 volumiow kernel: ftrace: allocated 172 pages with 4 groups Mar 04 20:31:09 volumiow kernel: Dynamic Preempt: voluntary Mar 04 20:31:09 volumiow kernel: rcu: Preemptible hierarchical RCU implementation. Mar 04 20:31:09 volumiow kernel: rcu: RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4. Mar 04 20:31:09 volumiow kernel: Trampoline variant of Tasks RCU enabled. Mar 04 20:31:09 volumiow kernel: Rude variant of Tasks RCU enabled. Mar 04 20:31:09 volumiow kernel: Tracing variant of Tasks RCU enabled. Mar 04 20:31:09 volumiow kernel: rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. Mar 04 20:31:09 volumiow kernel: rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 Mar 04 20:31:09 volumiow kernel: RCU Tasks: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=4. Mar 04 20:31:09 volumiow kernel: RCU Tasks Rude: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=4. Mar 04 20:31:09 volumiow kernel: RCU Tasks Trace: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=4. Mar 04 20:31:09 volumiow kernel: NR_IRQS: 4352, nr_irqs: 1024, preallocated irqs: 16 Mar 04 20:31:09 volumiow kernel: rcu: srcu_init: Setting srcu_struct sizes based on contention. Mar 04 20:31:09 volumiow kernel: Console: colour VGA+ 80x25 Mar 04 20:31:09 volumiow kernel: printk: legacy console [tty0] enabled Mar 04 20:31:09 volumiow kernel: ACPI: Core revision 20240827 Mar 04 20:31:09 volumiow kernel: hpet: HPET dysfunctional in PC10. Force disabled. Mar 04 20:31:09 volumiow kernel: APIC: Switch to symmetric I/O mode setup Mar 04 20:31:09 volumiow kernel: x2apic: IRQ remapping doesn't support X2APIC mode Mar 04 20:31:09 volumiow kernel: clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x26eae8729ef, max_idle_ns: 440795235156 ns Mar 04 20:31:09 volumiow kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 5399.81 BogoMIPS (lpj=10799636) Mar 04 20:31:09 volumiow kernel: CPU0: Thermal monitoring enabled (TM1) Mar 04 20:31:09 volumiow kernel: Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8 Mar 04 20:31:09 volumiow kernel: Last level dTLB entries: 4KB 64, 2MB 32, 4MB 32, 1GB 4 Mar 04 20:31:09 volumiow kernel: process: using mwait in idle threads Mar 04 20:31:09 volumiow kernel: Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization Mar 04 20:31:09 volumiow kernel: Spectre V2 : Mitigation: Retpolines Mar 04 20:31:09 volumiow kernel: Spectre V2 : Spectre v2 / SpectreRSB: Filling RSB on context switch and VMEXIT Mar 04 20:31:09 volumiow kernel: RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible! Mar 04 20:31:09 volumiow kernel: RETBleed: Vulnerable Mar 04 20:31:09 volumiow kernel: Speculative Store Bypass: Vulnerable Mar 04 20:31:09 volumiow kernel: MDS: Vulnerable: Clear CPU buffers attempted, no microcode Mar 04 20:31:09 volumiow kernel: MMIO Stale Data: Vulnerable: Clear CPU buffers attempted, no microcode Mar 04 20:31:09 volumiow kernel: SRBDS: Vulnerable: No microcode Mar 04 20:31:09 volumiow kernel: GDS: Vulnerable: No microcode Mar 04 20:31:09 volumiow kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Mar 04 20:31:09 volumiow kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Mar 04 20:31:09 volumiow kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Mar 04 20:31:09 volumiow kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' Mar 04 20:31:09 volumiow kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' Mar 04 20:31:09 volumiow kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Mar 04 20:31:09 volumiow kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 Mar 04 20:31:09 volumiow kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 Mar 04 20:31:09 volumiow kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. Mar 04 20:31:09 volumiow kernel: Freeing SMP alternatives memory: 36K Mar 04 20:31:09 volumiow kernel: pid_max: default: 32768 minimum: 301 Mar 04 20:31:09 volumiow kernel: LSM: initializing lsm=capability,yama Mar 04 20:31:09 volumiow kernel: Yama: becoming mindful. Mar 04 20:31:09 volumiow kernel: Mount-cache hash table entries: 32768 (order: 6, 262144 bytes, linear) Mar 04 20:31:09 volumiow kernel: Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes, linear) Mar 04 20:31:09 volumiow kernel: smpboot: CPU0: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (family: 0x6, model: 0x8e, stepping: 0x9) Mar 04 20:31:09 volumiow kernel: Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver. Mar 04 20:31:09 volumiow kernel: ... version: 4 Mar 04 20:31:09 volumiow kernel: ... bit width: 48 Mar 04 20:31:09 volumiow kernel: ... generic registers: 4 Mar 04 20:31:09 volumiow kernel: ... value mask: 0000ffffffffffff Mar 04 20:31:09 volumiow kernel: ... max period: 00007fffffffffff Mar 04 20:31:09 volumiow kernel: ... fixed-purpose events: 3 Mar 04 20:31:09 volumiow kernel: ... event mask: 000000070000000f Mar 04 20:31:09 volumiow kernel: signal: max sigframe size: 2032 Mar 04 20:31:09 volumiow kernel: Estimated ratio of average max frequency by base frequency (times 1024): 1175 Mar 04 20:31:09 volumiow kernel: rcu: Hierarchical SRCU implementation. Mar 04 20:31:09 volumiow kernel: rcu: Max phase no-delay instances is 1000. Mar 04 20:31:09 volumiow kernel: Timer migration: 1 hierarchy levels; 8 children per group; 1 crossnode level Mar 04 20:31:09 volumiow kernel: NMI watchdog: Enabled. Permanently consumes one hw-PMU counter. Mar 04 20:31:09 volumiow kernel: smp: Bringing up secondary CPUs ... Mar 04 20:31:09 volumiow kernel: smpboot: x86: Booting SMP configuration: Mar 04 20:31:09 volumiow kernel: .... node #0, CPUs: #1 #2 #3 Mar 04 20:31:09 volumiow kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details. Mar 04 20:31:09 volumiow kernel: MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_stale_data.html for more details. Mar 04 20:31:09 volumiow kernel: smp: Brought up 1 node, 4 CPUs Mar 04 20:31:09 volumiow kernel: smpboot: Total of 4 processors activated (21599.27 BogoMIPS) Mar 04 20:31:09 volumiow kernel: Memory: 16210780K/16682668K available (16384K kernel code, 2032K rwdata, 5320K rodata, 3128K init, 840K bss, 464064K reserved, 0K cma-reserved) Mar 04 20:31:09 volumiow kernel: devtmpfs: initialized Mar 04 20:31:09 volumiow kernel: x86/mm: Memory block size: 128MB Mar 04 20:31:09 volumiow kernel: ACPI: PM: Registering ACPI NVS region [mem 0x85639000-0x85639fff] (4096 bytes) Mar 04 20:31:09 volumiow kernel: ACPI: PM: Registering ACPI NVS region [mem 0x8c8d5000-0x8cfddfff] (7376896 bytes) Mar 04 20:31:09 volumiow kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns Mar 04 20:31:09 volumiow kernel: futex hash table entries: 1024 (order: 4, 65536 bytes, linear) Mar 04 20:31:09 volumiow kernel: pinctrl core: initialized pinctrl subsystem Mar 04 20:31:09 volumiow kernel: NET: Registered PF_NETLINK/PF_ROUTE protocol family Mar 04 20:31:09 volumiow kernel: audit: initializing netlink subsys (disabled) Mar 04 20:31:09 volumiow kernel: audit: type=2000 audit(1772652657.000:1): state=initialized audit_enabled=0 res=1 Mar 04 20:31:09 volumiow kernel: thermal_sys: Registered thermal governor 'fair_share' Mar 04 20:31:09 volumiow kernel: thermal_sys: Registered thermal governor 'bang_bang' Mar 04 20:31:09 volumiow kernel: thermal_sys: Registered thermal governor 'step_wise' Mar 04 20:31:09 volumiow kernel: thermal_sys: Registered thermal governor 'user_space' Mar 04 20:31:09 volumiow kernel: cpuidle: using governor ladder Mar 04 20:31:09 volumiow kernel: cpuidle: using governor menu Mar 04 20:31:09 volumiow kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 Mar 04 20:31:09 volumiow kernel: PCI: ECAM [mem 0xe0000000-0xefffffff] (base 0xe0000000) for domain 0000 [bus 00-ff] Mar 04 20:31:09 volumiow kernel: PCI: Using configuration type 1 for base access Mar 04 20:31:09 volumiow kernel: kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible. Mar 04 20:31:09 volumiow kernel: HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages Mar 04 20:31:09 volumiow kernel: HugeTLB: 16380 KiB vmemmap can be freed for a 1.00 GiB page Mar 04 20:31:09 volumiow kernel: HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages Mar 04 20:31:09 volumiow kernel: HugeTLB: 28 KiB vmemmap can be freed for a 2.00 MiB page Mar 04 20:31:09 volumiow kernel: ACPI: Added _OSI(Module Device) Mar 04 20:31:09 volumiow kernel: ACPI: Added _OSI(Processor Device) Mar 04 20:31:09 volumiow kernel: ACPI: Added _OSI(Processor Aggregator Device) Mar 04 20:31:09 volumiow kernel: ACPI: 9 ACPI AML tables successfully acquired and loaded Mar 04 20:31:09 volumiow kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored Mar 04 20:31:09 volumiow kernel: ACPI: Dynamic OEM Table Load: Mar 04 20:31:09 volumiow kernel: ACPI: SSDT 0xFFFF888100DA8000 0003FF (v02 PmRef Cpu0Cst 00003001 INTL 20160422) Mar 04 20:31:09 volumiow kernel: ACPI: Dynamic OEM Table Load: Mar 04 20:31:09 volumiow kernel: ACPI: SSDT 0xFFFF888100959000 0006B4 (v02 PmRef Cpu0Ist 00003000 INTL 20160422) Mar 04 20:31:09 volumiow kernel: ACPI: Dynamic OEM Table Load: Mar 04 20:31:09 volumiow kernel: ACPI: SSDT 0xFFFF888100AA8000 000115 (v02 PmRef Cpu0Hwp 00003000 INTL 20160422) Mar 04 20:31:09 volumiow kernel: ACPI: Dynamic OEM Table Load: Mar 04 20:31:09 volumiow kernel: ACPI: SSDT 0xFFFF888100AA8200 0001A4 (v02 PmRef HwpLvt 00003000 INTL 20160422) Mar 04 20:31:09 volumiow kernel: ACPI: Dynamic OEM Table Load: Mar 04 20:31:09 volumiow kernel: ACPI: SSDT 0xFFFF88810095A000 00065C (v02 PmRef ApIst 00003000 INTL 20160422) Mar 04 20:31:09 volumiow kernel: ACPI: Dynamic OEM Table Load: Mar 04 20:31:09 volumiow kernel: ACPI: SSDT 0xFFFF888100AA8400 000197 (v02 PmRef ApHwp 00003000 INTL 20160422) Mar 04 20:31:09 volumiow kernel: ACPI: Dynamic OEM Table Load: Mar 04 20:31:09 volumiow kernel: ACPI: SSDT 0xFFFF888100AA8600 00018A (v02 PmRef ApCst 00003000 INTL 20160422) Mar 04 20:31:09 volumiow kernel: ACPI: Interpreter enabled Mar 04 20:31:09 volumiow kernel: ACPI: PM: (supports S0 S3 S4 S5) Mar 04 20:31:09 volumiow kernel: ACPI: Using IOAPIC for interrupt routing Mar 04 20:31:09 volumiow kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug Mar 04 20:31:09 volumiow kernel: PCI: Using E820 reservations for host bridge windows Mar 04 20:31:09 volumiow kernel: ACPI: Enabled 6 GPEs in block 00 to 7F Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP09.PXP_: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP09.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP10.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP11.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP12.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP13.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP01.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP02.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP03.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP04.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP05.PXP_: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP05.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP06.PXP_: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP06.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP07.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP08.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP17.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP18.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP19.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP20.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP14.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP15.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.RP16.PXSX.WRST: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.XHC_.RHUB.HS06.PX06: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.USBC: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.PAUD: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.SAT0.VOL0.V0PR: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.SAT0.VOL1.V1PR: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.SAT0.VOL2.V2PR: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_SB_.PCI0.I2C1.PXTC: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_TZ_.FN00: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_TZ_.FN01: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_TZ_.FN02: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_TZ_.FN03: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: \_TZ_.FN04: New power resource Mar 04 20:31:09 volumiow kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe]) Mar 04 20:31:09 volumiow kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3] Mar 04 20:31:09 volumiow kernel: acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug SHPCHotplug PME AER PCIeCapability LTR] Mar 04 20:31:09 volumiow kernel: PCI host bridge to bus 0000:00 Mar 04 20:31:09 volumiow kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window] Mar 04 20:31:09 volumiow kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window] Mar 04 20:31:09 volumiow kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window] Mar 04 20:31:09 volumiow kernel: pci_bus 0000:00: root bus resource [mem 0x90000000-0xdfffffff window] Mar 04 20:31:09 volumiow kernel: pci_bus 0000:00: root bus resource [mem 0xfd000000-0xfe7fffff window] Mar 04 20:31:09 volumiow kernel: pci_bus 0000:00: root bus resource [bus 00-fe] Mar 04 20:31:09 volumiow kernel: pci 0000:00:00.0: [8086:5904] type 00 class 0x060000 conventional PCI endpoint Mar 04 20:31:09 volumiow kernel: pci 0000:00:02.0: [8086:5916] type 00 class 0x030000 PCIe Root Complex Integrated Endpoint Mar 04 20:31:09 volumiow kernel: pci 0000:00:02.0: BAR 0 [mem 0xde000000-0xdeffffff 64bit] Mar 04 20:31:09 volumiow kernel: pci 0000:00:02.0: BAR 2 [mem 0xc0000000-0xcfffffff 64bit pref] Mar 04 20:31:09 volumiow kernel: pci 0000:00:02.0: BAR 4 [io 0xf000-0xf03f] Mar 04 20:31:09 volumiow kernel: pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff] Mar 04 20:31:09 volumiow kernel: pci 0000:00:08.0: [8086:1911] type 00 class 0x088000 conventional PCI endpoint Mar 04 20:31:09 volumiow kernel: pci 0000:00:08.0: BAR 0 [mem 0xdf131000-0xdf131fff 64bit] Mar 04 20:31:09 volumiow kernel: pci 0000:00:14.0: [8086:9d2f] type 00 class 0x0c0330 conventional PCI endpoint Mar 04 20:31:09 volumiow kernel: pci 0000:00:14.0: BAR 0 [mem 0xdf110000-0xdf11ffff 64bit] Mar 04 20:31:09 volumiow kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold Mar 04 20:31:09 volumiow kernel: pci 0000:00:14.2: [8086:9d31] type 00 class 0x118000 conventional PCI endpoint Mar 04 20:31:09 volumiow kernel: pci 0000:00:14.2: BAR 0 [mem 0xdf130000-0xdf130fff 64bit] Mar 04 20:31:09 volumiow kernel: pci 0000:00:17.0: [8086:9d03] type 00 class 0x010601 conventional PCI endpoint Mar 04 20:31:09 volumiow kernel: pci 0000:00:17.0: BAR 0 [mem 0xdf128000-0xdf129fff] Mar 04 20:31:09 volumiow kernel: pci 0000:00:17.0: BAR 1 [mem 0xdf12f000-0xdf12f0ff] Mar 04 20:31:09 volumiow kernel: pci 0000:00:17.0: BAR 2 [io 0xf090-0xf097] Mar 04 20:31:09 volumiow kernel: pci 0000:00:17.0: BAR 3 [io 0xf080-0xf083] Mar 04 20:31:09 volumiow kernel: pci 0000:00:17.0: BAR 4 [io 0xf060-0xf07f] Mar 04 20:31:09 volumiow kernel: pci 0000:00:17.0: BAR 5 [mem 0xdf12e000-0xdf12e7ff] Mar 04 20:31:09 volumiow kernel: pci 0000:00:17.0: PME# supported from D3hot Mar 04 20:31:09 volumiow kernel: pci 0000:00:1c.0: [8086:9d12] type 01 class 0x060400 PCIe Root Port Mar 04 20:31:09 volumiow kernel: pci 0000:00:1c.0: PCI bridge to [bus 01] Mar 04 20:31:09 volumiow kernel: pci 0000:00:1c.0: bridge window [io 0xe000-0xefff] Mar 04 20:31:09 volumiow kernel: pci 0000:00:1c.0: bridge window [mem 0xd0000000-0xd00fffff 64bit pref] Mar 04 20:31:09 volumiow kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold Mar 04 20:31:09 volumiow kernel: pci 0000:00:1c.3: [8086:9d13] type 01 class 0x060400 PCIe Root Port Mar 04 20:31:09 volumiow kernel: pci 0000:00:1c.3: PCI bridge to [bus 02] Mar 04 20:31:09 volumiow kernel: pci 0000:00:1c.3: bridge window [mem 0xdf000000-0xdf0fffff] Mar 04 20:31:09 volumiow kernel: pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold Mar 04 20:31:09 volumiow kernel: pci 0000:00:1e.0: [8086:9d27] type 00 class 0x118000 conventional PCI endpoint Mar 04 20:31:09 volumiow kernel: pci 0000:00:1e.0: BAR 0 [mem 0xdf12d000-0xdf12dfff 64bit] Mar 04 20:31:09 volumiow kernel: pci 0000:00:1e.4: [8086:9d2b] type 00 class 0x080501 conventional PCI endpoint Mar 04 20:31:09 volumiow kernel: pci 0000:00:1e.4: BAR 0 [mem 0xdf12c000-0xdf12cfff 64bit] Mar 04 20:31:09 volumiow kernel: pci 0000:00:1e.6: [8086:9d2d] type 00 class 0x080501 conventional PCI endpoint Mar 04 20:31:09 volumiow kernel: pci 0000:00:1e.6: BAR 0 [mem 0xdf12b000-0xdf12bfff 64bit] Mar 04 20:31:09 volumiow kernel: pci 0000:00:1f.0: [8086:9d58] type 00 class 0x060100 conventional PCI endpoint Mar 04 20:31:09 volumiow kernel: pci 0000:00:1f.2: [8086:9d21] type 00 class 0x058000 conventional PCI endpoint Mar 04 20:31:09 volumiow kernel: pci 0000:00:1f.2: BAR 0 [mem 0xdf124000-0xdf127fff] Mar 04 20:31:09 volumiow kernel: pci 0000:00:1f.3: [8086:9d71] type 00 class 0x040300 conventional PCI endpoint Mar 04 20:31:09 volumiow kernel: pci 0000:00:1f.3: BAR 0 [mem 0xdf120000-0xdf123fff 64bit] Mar 04 20:31:09 volumiow kernel: pci 0000:00:1f.3: BAR 4 [mem 0xdf100000-0xdf10ffff 64bit] Mar 04 20:31:09 volumiow kernel: pci 0000:00:1f.3: PME# supported from D3hot D3cold Mar 04 20:31:09 volumiow kernel: pci 0000:00:1f.4: [8086:9d23] type 00 class 0x0c0500 conventional PCI endpoint Mar 04 20:31:09 volumiow kernel: pci 0000:00:1f.4: BAR 0 [mem 0xdf12a000-0xdf12a0ff 64bit] Mar 04 20:31:09 volumiow kernel: pci 0000:00:1f.4: BAR 4 [io 0xf040-0xf05f] Mar 04 20:31:09 volumiow kernel: pci 0000:01:00.0: [10ec:8168] type 00 class 0x020000 PCIe Endpoint Mar 04 20:31:09 volumiow kernel: pci 0000:01:00.0: BAR 0 [io 0xe000-0xe0ff] Mar 04 20:31:09 volumiow kernel: pci 0000:01:00.0: BAR 2 [mem 0xd0004000-0xd0004fff 64bit pref] Mar 04 20:31:09 volumiow kernel: pci 0000:01:00.0: BAR 4 [mem 0xd0000000-0xd0003fff 64bit pref] Mar 04 20:31:09 volumiow kernel: pci 0000:01:00.0: supports D1 D2 Mar 04 20:31:09 volumiow kernel: pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold Mar 04 20:31:09 volumiow kernel: pci 0000:00:1c.0: PCI bridge to [bus 01] Mar 04 20:31:09 volumiow kernel: pci 0000:02:00.0: [168c:0030] type 00 class 0x028000 PCIe Endpoint Mar 04 20:31:09 volumiow kernel: pci 0000:02:00.0: BAR 0 [mem 0xdf000000-0xdf01ffff 64bit] Mar 04 20:31:09 volumiow kernel: pci 0000:02:00.0: ROM [mem 0xdf020000-0xdf02ffff pref] Mar 04 20:31:09 volumiow kernel: pci 0000:02:00.0: supports D1 Mar 04 20:31:09 volumiow kernel: pci 0000:02:00.0: PME# supported from D0 D1 D3hot Mar 04 20:31:09 volumiow kernel: pci 0000:00:1c.3: PCI bridge to [bus 02] Mar 04 20:31:09 volumiow kernel: pci_bus 0000:00: on NUMA node 0 Mar 04 20:31:09 volumiow kernel: ACPI: PCI: Interrupt link LNKA configured for IRQ 11 Mar 04 20:31:09 volumiow kernel: ACPI: PCI: Interrupt link LNKB configured for IRQ 10 Mar 04 20:31:09 volumiow kernel: ACPI: PCI: Interrupt link LNKC configured for IRQ 11 Mar 04 20:31:09 volumiow kernel: ACPI: PCI: Interrupt link LNKD configured for IRQ 11 Mar 04 20:31:09 volumiow kernel: ACPI: PCI: Interrupt link LNKE configured for IRQ 11 Mar 04 20:31:09 volumiow kernel: ACPI: PCI: Interrupt link LNKF configured for IRQ 11 Mar 04 20:31:09 volumiow kernel: ACPI: PCI: Interrupt link LNKG configured for IRQ 11 Mar 04 20:31:09 volumiow kernel: ACPI: PCI: Interrupt link LNKH configured for IRQ 11 Mar 04 20:31:09 volumiow kernel: iommu: Default domain type: Translated Mar 04 20:31:09 volumiow kernel: iommu: DMA domain TLB invalidation policy: lazy mode Mar 04 20:31:09 volumiow kernel: SCSI subsystem initialized Mar 04 20:31:09 volumiow kernel: libata version 3.00 loaded. Mar 04 20:31:09 volumiow kernel: ACPI: bus type USB registered Mar 04 20:31:09 volumiow kernel: usbcore: registered new interface driver usbfs Mar 04 20:31:09 volumiow kernel: usbcore: registered new interface driver hub Mar 04 20:31:09 volumiow kernel: usbcore: registered new device driver usb Mar 04 20:31:09 volumiow kernel: PCI: Using ACPI for IRQ routing Mar 04 20:31:09 volumiow kernel: PCI: pci_cache_line_size set to 64 bytes Mar 04 20:31:09 volumiow kernel: e820: reserve RAM buffer [mem 0x0009c400-0x0009ffff] Mar 04 20:31:09 volumiow kernel: e820: reserve RAM buffer [mem 0x85639000-0x87ffffff] Mar 04 20:31:09 volumiow kernel: e820: reserve RAM buffer [mem 0x8b2d5000-0x8bffffff] Mar 04 20:31:09 volumiow kernel: e820: reserve RAM buffer [mem 0x8c8d5000-0x8fffffff] Mar 04 20:31:09 volumiow kernel: e820: reserve RAM buffer [mem 0x8d400000-0x8fffffff] Mar 04 20:31:09 volumiow kernel: e820: reserve RAM buffer [mem 0x46f000000-0x46fffffff] Mar 04 20:31:09 volumiow kernel: pci 0000:00:02.0: vgaarb: setting as boot VGA device Mar 04 20:31:09 volumiow kernel: pci 0000:00:02.0: vgaarb: bridge control possible Mar 04 20:31:09 volumiow kernel: pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none Mar 04 20:31:09 volumiow kernel: vgaarb: loaded Mar 04 20:31:09 volumiow kernel: clocksource: Switched to clocksource tsc-early Mar 04 20:31:09 volumiow kernel: VFS: Disk quotas dquot_6.6.0 Mar 04 20:31:09 volumiow kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Mar 04 20:31:09 volumiow kernel: pnp: PnP ACPI init Mar 04 20:31:09 volumiow kernel: system 00:00: [io 0x0a00-0x0a2f] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:00: [io 0x0a30-0x0a3f] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:00: [io 0x0a40-0x0a4f] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:01: [io 0x0680-0x069f] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:01: [io 0xffff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:01: [io 0xffff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:01: [io 0xffff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:01: [io 0x1800-0x18fe] could not be reserved Mar 04 20:31:09 volumiow kernel: system 00:01: [io 0x164e-0x164f] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:03: [mem 0xfed10000-0xfed17fff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:03: [mem 0xfed18000-0xfed18fff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:03: [mem 0xfed19000-0xfed19fff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:03: [mem 0xe0000000-0xefffffff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:03: [mem 0xfed20000-0xfed3ffff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:03: [mem 0xfed90000-0xfed93fff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:03: [mem 0xfed45000-0xfed8ffff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:03: [mem 0xff000000-0xffffffff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:03: [mem 0xfee00000-0xfeefffff] could not be reserved Mar 04 20:31:09 volumiow kernel: system 00:03: [mem 0xdffe0000-0xdfffffff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:04: [mem 0xfd000000-0xfdabffff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:04: [mem 0xfdad0000-0xfdadffff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:04: [mem 0xfdb00000-0xfdffffff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:04: [mem 0xfe000000-0xfe01ffff] could not be reserved Mar 04 20:31:09 volumiow kernel: system 00:04: [mem 0xfe036000-0xfe03bfff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:04: [mem 0xfe03d000-0xfe3fffff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:04: [mem 0xfe410000-0xfe7fffff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:05: [io 0xff00-0xfffe] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:06: [mem 0xfe029000-0xfe029fff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:06: [mem 0xfe028000-0xfe028fff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:06: [mem 0xfdaf0000-0xfdafffff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:06: [mem 0xfdae0000-0xfdaeffff] has been reserved Mar 04 20:31:09 volumiow kernel: system 00:06: [mem 0xfdac0000-0xfdacffff] has been reserved Mar 04 20:31:09 volumiow kernel: pnp: PnP ACPI: found 7 devices Mar 04 20:31:09 volumiow kernel: clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns Mar 04 20:31:09 volumiow kernel: NET: Registered PF_INET protocol family Mar 04 20:31:09 volumiow kernel: IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear) Mar 04 20:31:09 volumiow kernel: tcp_listen_portaddr_hash hash table entries: 8192 (order: 5, 131072 bytes, linear) Mar 04 20:31:09 volumiow kernel: Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) Mar 04 20:31:09 volumiow kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes, linear) Mar 04 20:31:09 volumiow kernel: TCP bind hash table entries: 65536 (order: 9, 2097152 bytes, linear) Mar 04 20:31:09 volumiow kernel: TCP: Hash tables configured (established 131072 bind 65536) Mar 04 20:31:09 volumiow kernel: UDP hash table entries: 8192 (order: 6, 262144 bytes, linear) Mar 04 20:31:09 volumiow kernel: UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes, linear) Mar 04 20:31:09 volumiow kernel: NET: Registered PF_UNIX/PF_LOCAL protocol family Mar 04 20:31:09 volumiow kernel: pci 0000:00:1c.0: PCI bridge to [bus 01] Mar 04 20:31:09 volumiow kernel: pci 0000:00:1c.0: bridge window [io 0xe000-0xefff] Mar 04 20:31:09 volumiow kernel: pci 0000:00:1c.0: bridge window [mem 0xd0000000-0xd00fffff 64bit pref] Mar 04 20:31:09 volumiow kernel: pci 0000:00:1c.3: PCI bridge to [bus 02] Mar 04 20:31:09 volumiow kernel: pci 0000:00:1c.3: bridge window [mem 0xdf000000-0xdf0fffff] Mar 04 20:31:09 volumiow kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window] Mar 04 20:31:09 volumiow kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window] Mar 04 20:31:09 volumiow kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window] Mar 04 20:31:09 volumiow kernel: pci_bus 0000:00: resource 7 [mem 0x90000000-0xdfffffff window] Mar 04 20:31:09 volumiow kernel: pci_bus 0000:00: resource 8 [mem 0xfd000000-0xfe7fffff window] Mar 04 20:31:09 volumiow kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff] Mar 04 20:31:09 volumiow kernel: pci_bus 0000:01: resource 2 [mem 0xd0000000-0xd00fffff 64bit pref] Mar 04 20:31:09 volumiow kernel: pci_bus 0000:02: resource 1 [mem 0xdf000000-0xdf0fffff] Mar 04 20:31:09 volumiow kernel: PCI: CLS 64 bytes, default 64 Mar 04 20:31:09 volumiow kernel: pci 0000:00:1f.1: [8086:9d20] type 00 class 0x058000 conventional PCI endpoint Mar 04 20:31:09 volumiow kernel: pci 0000:00:1f.1: BAR 0 [mem 0xfd000000-0xfdffffff 64bit] Mar 04 20:31:09 volumiow kernel: DMAR: Host address width 39 Mar 04 20:31:09 volumiow kernel: DMAR: DRHD base: 0x000000fed90000 flags: 0x0 Mar 04 20:31:09 volumiow kernel: DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 19e2ff0505e Mar 04 20:31:09 volumiow kernel: DMAR: DRHD base: 0x000000fed91000 flags: 0x1 Mar 04 20:31:09 volumiow kernel: DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da Mar 04 20:31:09 volumiow kernel: DMAR: RMRR base: 0x0000008b915000 end: 0x0000008b934fff Mar 04 20:31:09 volumiow kernel: DMAR: RMRR base: 0x0000008d800000 end: 0x0000008fffffff Mar 04 20:31:09 volumiow kernel: DMAR: ANDD device: 9 name: \_SB.PCI0.UA00 Mar 04 20:31:09 volumiow kernel: DMAR: ACPI device "device:76" under DMAR at fed91000 as 00:1e.0 Mar 04 20:31:09 volumiow kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Mar 04 20:31:09 volumiow kernel: software IO TLB: mapped [mem 0x00000000872d5000-0x000000008b2d5000] (64MB) Mar 04 20:31:09 volumiow kernel: Trying to unpack rootfs image as initramfs... Mar 04 20:31:09 volumiow kernel: RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer Mar 04 20:31:09 volumiow kernel: RAPL PMU: hw unit of domain pp0-core 2^-14 Joules Mar 04 20:31:09 volumiow kernel: RAPL PMU: hw unit of domain package 2^-14 Joules Mar 04 20:31:09 volumiow kernel: RAPL PMU: hw unit of domain dram 2^-14 Joules Mar 04 20:31:09 volumiow kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules Mar 04 20:31:09 volumiow kernel: RAPL PMU: hw unit of domain psys 2^-14 Joules Mar 04 20:31:09 volumiow kernel: Initialise system trusted keyrings Mar 04 20:31:09 volumiow kernel: workingset: timestamp_bits=46 max_order=22 bucket_order=0 Mar 04 20:31:09 volumiow kernel: Key type asymmetric registered Mar 04 20:31:09 volumiow kernel: Asymmetric key parser 'x509' registered Mar 04 20:31:09 volumiow kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250) Mar 04 20:31:09 volumiow kernel: io scheduler mq-deadline registered Mar 04 20:31:09 volumiow kernel: io scheduler kyber registered Mar 04 20:31:09 volumiow kernel: ledtrig-cpu: registered to indicate activity on CPUs Mar 04 20:31:09 volumiow kernel: pcieport 0000:00:1c.0: PME: Signaling with IRQ 120 Mar 04 20:31:09 volumiow kernel: pcieport 0000:00:1c.0: AER: enabled with IRQ 120 Mar 04 20:31:09 volumiow kernel: pcieport 0000:00:1c.3: PME: Signaling with IRQ 121 Mar 04 20:31:09 volumiow kernel: pcieport 0000:00:1c.3: AER: enabled with IRQ 121 Mar 04 20:31:09 volumiow kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Mar 04 20:31:09 volumiow kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 Mar 04 20:31:09 volumiow kernel: ACPI: button: Sleep Button [SLPB] Mar 04 20:31:09 volumiow kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 Mar 04 20:31:09 volumiow kernel: ACPI: button: Power Button [PWRB] Mar 04 20:31:09 volumiow kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 Mar 04 20:31:09 volumiow kernel: ACPI: button: Power Button [PWRF] Mar 04 20:31:09 volumiow kernel: thermal LNXTHERM:00: registered as thermal_zone0 Mar 04 20:31:09 volumiow kernel: ACPI: thermal: Thermal Zone [TZ00] (28 C) Mar 04 20:31:09 volumiow kernel: thermal LNXTHERM:01: registered as thermal_zone1 Mar 04 20:31:09 volumiow kernel: ACPI: thermal: Thermal Zone [TZ01] (30 C) Mar 04 20:31:09 volumiow kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled Mar 04 20:31:09 volumiow kernel: hpet_acpi_add: no address or irqs in _CRS Mar 04 20:31:09 volumiow kernel: Linux agpgart interface v0.103 Mar 04 20:31:09 volumiow kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller Mar 04 20:31:09 volumiow kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1 Mar 04 20:31:09 volumiow kernel: xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0000000081109810 Mar 04 20:31:09 volumiow kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller Mar 04 20:31:09 volumiow kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2 Mar 04 20:31:09 volumiow kernel: xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed Mar 04 20:31:09 volumiow kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.12 Mar 04 20:31:09 volumiow kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Mar 04 20:31:09 volumiow kernel: usb usb1: Product: xHCI Host Controller Mar 04 20:31:09 volumiow kernel: usb usb1: Manufacturer: Linux 6.12.57-volumio xhci-hcd Mar 04 20:31:09 volumiow kernel: usb usb1: SerialNumber: 0000:00:14.0 Mar 04 20:31:09 volumiow kernel: hub 1-0:1.0: USB hub found Mar 04 20:31:09 volumiow kernel: hub 1-0:1.0: 12 ports detected Mar 04 20:31:09 volumiow kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.12 Mar 04 20:31:09 volumiow kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Mar 04 20:31:09 volumiow kernel: usb usb2: Product: xHCI Host Controller Mar 04 20:31:09 volumiow kernel: usb usb2: Manufacturer: Linux 6.12.57-volumio xhci-hcd Mar 04 20:31:09 volumiow kernel: usb usb2: SerialNumber: 0000:00:14.0 Mar 04 20:31:09 volumiow kernel: hub 2-0:1.0: USB hub found Mar 04 20:31:09 volumiow kernel: hub 2-0:1.0: 6 ports detected Mar 04 20:31:09 volumiow kernel: usbcore: registered new interface driver usb-storage Mar 04 20:31:09 volumiow kernel: i8042: PNP: No PS/2 controller found. Mar 04 20:31:09 volumiow kernel: mousedev: PS/2 mouse device common for all mice Mar 04 20:31:09 volumiow kernel: rtc_cmos 00:02: RTC can wake from S4 Mar 04 20:31:09 volumiow kernel: rtc_cmos 00:02: registered as rtc0 Mar 04 20:31:09 volumiow kernel: rtc_cmos 00:02: setting system clock to 2026-03-04T19:30:57 UTC (1772652657) Mar 04 20:31:09 volumiow kernel: rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram Mar 04 20:31:09 volumiow kernel: i2c_dev: i2c /dev entries driver Mar 04 20:31:09 volumiow kernel: intel_pstate: Intel P-state driver initializing Mar 04 20:31:09 volumiow kernel: intel_pstate: HWP enabled Mar 04 20:31:09 volumiow kernel: hid: raw HID events driver (C) Jiri Kosina Mar 04 20:31:09 volumiow kernel: NET: Registered PF_INET6 protocol family Mar 04 20:31:09 volumiow kernel: Segment Routing with IPv6 Mar 04 20:31:09 volumiow kernel: In-situ OAM (IOAM) with IPv6 Mar 04 20:31:09 volumiow kernel: mip6: Mobile IPv6 Mar 04 20:31:09 volumiow kernel: NET: Registered PF_PACKET protocol family Mar 04 20:31:09 volumiow kernel: mpls_gso: MPLS GSO support Mar 04 20:31:09 volumiow kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance' Mar 04 20:31:09 volumiow kernel: microcode: Current revision: 0x0000003c Mar 04 20:31:09 volumiow kernel: IPI shorthand broadcast: enabled Mar 04 20:31:09 volumiow kernel: sched_clock: Marking stable (256003037, 8260356)->(297419480, -33156087) Mar 04 20:31:09 volumiow kernel: Loading compiled-in X.509 certificates Mar 04 20:31:09 volumiow kernel: clk: Disabling unused clocks Mar 04 20:31:09 volumiow kernel: PM: genpd: Disabling unused power domains Mar 04 20:31:09 volumiow kernel: usb 1-4: new high-speed USB device number 2 using xhci_hcd Mar 04 20:31:09 volumiow kernel: usb 1-4: New USB device found, idVendor=152a, idProduct=8750, bcdDevice= 1.39 Mar 04 20:31:09 volumiow kernel: usb 1-4: New USB device strings: Mfr=1, Product=3, SerialNumber=0 Mar 04 20:31:09 volumiow kernel: usb 1-4: Product: D50 III Mar 04 20:31:09 volumiow kernel: usb 1-4: Manufacturer: Topping Mar 04 20:31:09 volumiow kernel: Freeing initrd memory: 80736K Mar 04 20:31:09 volumiow kernel: Freeing unused kernel image (initmem) memory: 3128K Mar 04 20:31:09 volumiow kernel: Write protecting the kernel read-only data: 22528k Mar 04 20:31:09 volumiow kernel: Freeing unused kernel image (rodata/data gap) memory: 824K Mar 04 20:31:09 volumiow kernel: Run /init as init process Mar 04 20:31:09 volumiow kernel: with arguments: Mar 04 20:31:09 volumiow kernel: /init Mar 04 20:31:09 volumiow kernel: splash Mar 04 20:31:09 volumiow kernel: with environment: Mar 04 20:31:09 volumiow kernel: HOME=/ Mar 04 20:31:09 volumiow kernel: TERM=linux Mar 04 20:31:09 volumiow kernel: bootdelay=5 Mar 04 20:31:09 volumiow kernel: biosdevname=0 Mar 04 20:31:09 volumiow kernel: imgpart=UUID=b0a058e9-0951-4405-9f54-2004a4130548 Mar 04 20:31:09 volumiow kernel: bootpart=UUID=5F54-6886 Mar 04 20:31:09 volumiow kernel: datapart=UUID=a75a63ef-7a01-4f5e-b572-6ddd34d5e25f Mar 04 20:31:09 volumiow kernel: hwdevice=x86 Mar 04 20:31:09 volumiow kernel: uuidconfig=syslinux.cfg,efi/BOOT/grub.cfg Mar 04 20:31:09 volumiow kernel: imgfile=/volumio_current.sqsh Mar 04 20:31:09 volumiow kernel: use_kmsg=no Mar 04 20:31:09 volumiow kernel: intel-lpss 0000:00:1e.0: enabling device (0000 -> 0002) Mar 04 20:31:09 volumiow kernel: idma64 idma64.0: Found Intel integrated DMA 64-bit Mar 04 20:31:09 volumiow kernel: ahci 0000:00:17.0: version 3.0 Mar 04 20:31:09 volumiow kernel: i801_smbus 0000:00:1f.4: SPD Write Disable is set Mar 04 20:31:09 volumiow kernel: i801_smbus 0000:00:1f.4: SMBus using PCI interrupt Mar 04 20:31:09 volumiow kernel: i2c i2c-0: Successfully instantiated SPD at 0x50 Mar 04 20:31:09 volumiow kernel: ahci 0000:00:17.0: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode Mar 04 20:31:09 volumiow kernel: ahci 0000:00:17.0: 3/3 ports implemented (port mask 0x7) Mar 04 20:31:09 volumiow kernel: ahci 0000:00:17.0: flags: 64bit ncq pm led clo only pio slum part deso sadm sds apst Mar 04 20:31:09 volumiow kernel: usb 2-3: new SuperSpeed USB device number 2 using xhci_hcd Mar 04 20:31:09 volumiow kernel: scsi host0: ahci Mar 04 20:31:09 volumiow kernel: scsi host1: ahci Mar 04 20:31:09 volumiow kernel: usbcore: registered new interface driver usbhid Mar 04 20:31:09 volumiow kernel: usbhid: USB HID core driver Mar 04 20:31:09 volumiow kernel: scsi host2: ahci Mar 04 20:31:09 volumiow kernel: ata1: SATA max UDMA/133 abar m2048@0xdf12e000 port 0xdf12e100 irq 123 lpm-pol 3 Mar 04 20:31:09 volumiow kernel: ata2: SATA max UDMA/133 abar m2048@0xdf12e000 port 0xdf12e180 irq 123 lpm-pol 3 Mar 04 20:31:09 volumiow kernel: ata3: SATA max UDMA/133 abar m2048@0xdf12e000 port 0xdf12e200 irq 123 lpm-pol 3 Mar 04 20:31:09 volumiow kernel: ACPI: bus type drm_connector registered Mar 04 20:31:09 volumiow kernel: sdhci: Secure Digital Host Controller Interface driver Mar 04 20:31:09 volumiow kernel: sdhci: Copyright(c) Pierre Ossman Mar 04 20:31:09 volumiow kernel: usb 2-3: New USB device found, idVendor=0bda, idProduct=9201, bcdDevice=f2.00 Mar 04 20:31:09 volumiow kernel: usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 04 20:31:09 volumiow kernel: usb 2-3: Product: RTL9201 Mar 04 20:31:09 volumiow kernel: usb 2-3: Manufacturer: Realtek Mar 04 20:31:09 volumiow kernel: usb 2-3: SerialNumber: 012345678999 Mar 04 20:31:09 volumiow kernel: input: Topping D50 III as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.3/0003:152A:8750.0001/input/input3 Mar 04 20:31:09 volumiow kernel: hid-generic 0003:152A:8750.0001: input,hidraw0: USB HID v1.10 Device [Topping D50 III] on usb-0000:00:14.0-4/input3 Mar 04 20:31:09 volumiow kernel: usb 2-3: Enable of device-initiated U1 failed. Mar 04 20:31:09 volumiow kernel: usb 2-3: Enable of device-initiated U2 failed. Mar 04 20:31:09 volumiow kernel: usb 2-3: Enable of device-initiated U1 failed. Mar 04 20:31:09 volumiow kernel: usb 2-3: Enable of device-initiated U2 failed. Mar 04 20:31:09 volumiow kernel: scsi host3: uas Mar 04 20:31:09 volumiow kernel: usbcore: registered new interface driver uas Mar 04 20:31:09 volumiow kernel: scsi 3:0:0:0: Direct-Access Emtec X1 50 960GB 1.02 PQ: 0 ANSI: 6 Mar 04 20:31:09 volumiow kernel: sd 3:0:0:0: [sda] 1875385008 512-byte logical blocks: (960 GB/894 GiB) Mar 04 20:31:09 volumiow kernel: sd 3:0:0:0: [sda] Write Protect is off Mar 04 20:31:09 volumiow kernel: sd 3:0:0:0: [sda] Mode Sense: 37 00 00 08 Mar 04 20:31:09 volumiow kernel: sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 04 20:31:09 volumiow kernel: sd 3:0:0:0: [sda] Preferred minimum I/O size 512 bytes Mar 04 20:31:09 volumiow kernel: sd 3:0:0:0: [sda] Optimal transfer size 33553920 bytes Mar 04 20:31:09 volumiow kernel: ata2: SATA link down (SStatus 4 SControl 300) Mar 04 20:31:09 volumiow kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 04 20:31:09 volumiow kernel: ata3: SATA link down (SStatus 4 SControl 300) Mar 04 20:31:09 volumiow kernel: ata1.00: Model 'Samsung SSD 860 EVO mSATA 250GB', rev 'RVT41B6Q', applying quirks: noncqtrim zeroaftertrim noncqonati nolpmonati Mar 04 20:31:09 volumiow kernel: ata1.00: supports DRM functions and may not be fully accessible Mar 04 20:31:09 volumiow kernel: ata1.00: ATA-11: Samsung SSD 860 EVO mSATA 250GB, RVT41B6Q, max UDMA/133 Mar 04 20:31:09 volumiow kernel: ata1.00: 488397168 sectors, multi 1: LBA48 NCQ (depth 32), AA Mar 04 20:31:09 volumiow kernel: ata1.00: Features: Trust Dev-Sleep NCQ-sndrcv Mar 04 20:31:09 volumiow kernel: ata1.00: supports DRM functions and may not be fully accessible Mar 04 20:31:09 volumiow kernel: sda: sda1 Mar 04 20:31:09 volumiow kernel: sd 3:0:0:0: [sda] Attached SCSI disk Mar 04 20:31:09 volumiow kernel: ata1.00: configured for UDMA/133 Mar 04 20:31:09 volumiow kernel: ahci 0000:00:17.0: port does not support device sleep Mar 04 20:31:09 volumiow kernel: scsi 0:0:0:0: Direct-Access ATA Samsung SSD 860 1B6Q PQ: 0 ANSI: 5 Mar 04 20:31:09 volumiow kernel: ata1.00: Enabling discard_zeroes_data Mar 04 20:31:09 volumiow kernel: sd 0:0:0:0: [sdb] 488397168 512-byte logical blocks: (250 GB/233 GiB) Mar 04 20:31:09 volumiow kernel: sd 0:0:0:0: [sdb] Write Protect is off Mar 04 20:31:09 volumiow kernel: sd 0:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Mar 04 20:31:09 volumiow kernel: sd 0:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 04 20:31:09 volumiow kernel: sd 0:0:0:0: [sdb] Preferred minimum I/O size 512 bytes Mar 04 20:31:09 volumiow kernel: ata1.00: Enabling discard_zeroes_data Mar 04 20:31:09 volumiow kernel: sdb: sdb1 sdb2 sdb3 Mar 04 20:31:09 volumiow kernel: sd 0:0:0:0: [sdb] Attached SCSI disk Mar 04 20:31:09 volumiow kernel: sdhci-pci 0000:00:1e.4: SDHCI controller found [8086:9d2b] (rev 21) Mar 04 20:31:09 volumiow kernel: mmc0: SDHCI controller on PCI [0000:00:1e.4] using ADMA 64-bit Mar 04 20:31:09 volumiow kernel: sdhci-pci 0000:00:1e.6: SDHCI controller found [8086:9d2d] (rev 21) Mar 04 20:31:09 volumiow kernel: sdhci-pci 0000:00:1e.6: failed to setup card detect gpio Mar 04 20:31:09 volumiow kernel: mmc1: SDHCI controller on PCI [0000:00:1e.6] using ADMA 64-bit Mar 04 20:31:09 volumiow kernel: r8169 0000:01:00.0 eth0: RTL8168evl/8111evl, 00:e0:4c:68:5e:ad, XID 2c9, IRQ 124 Mar 04 20:31:09 volumiow kernel: r8169 0000:01:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko] Mar 04 20:31:09 volumiow kernel: tsc: Refined TSC clocksource calibration: 2711.999 MHz Mar 04 20:31:09 volumiow kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x271785701be, max_idle_ns: 440795203568 ns Mar 04 20:31:09 volumiow kernel: clocksource: Switched to clocksource tsc Mar 04 20:31:09 volumiow kernel: i915 0000:00:02.0: [drm] Found KABYLAKE/ULT (device ID 5916) display version 9.00 stepping B0 Mar 04 20:31:09 volumiow kernel: i915 0000:00:02.0: vgaarb: deactivate vga console Mar 04 20:31:09 volumiow kernel: Console: switching to colour dummy device 80x25 Mar 04 20:31:09 volumiow kernel: i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=io+mem Mar 04 20:31:09 volumiow kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Mar 04 20:31:09 volumiow kernel: [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 0 Mar 04 20:31:09 volumiow kernel: ACPI: video: Video Device [GFX0] (multi-head: yes rom: no post: no) Mar 04 20:31:09 volumiow kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input4 Mar 04 20:31:09 volumiow kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Mar 04 20:31:09 volumiow kernel: i915 0000:00:02.0: [drm] Cannot find any crtc or sizes Mar 04 20:31:09 volumiow kernel: i915 0000:00:02.0: [drm] Cannot find any crtc or sizes Mar 04 20:31:09 volumiow kernel: snd_hda_codec_generic hdaudioC0D0: autoconfig for Generic: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line Mar 04 20:31:09 volumiow kernel: snd_hda_codec_generic hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) Mar 04 20:31:09 volumiow kernel: snd_hda_codec_generic hdaudioC0D0: hp_outs=0 (0x0/0x0/0x0/0x0/0x0) Mar 04 20:31:09 volumiow kernel: snd_hda_codec_generic hdaudioC0D0: mono: mono_out=0x0 Mar 04 20:31:09 volumiow kernel: snd_hda_codec_generic hdaudioC0D0: inputs: Mar 04 20:31:09 volumiow kernel: snd_hda_codec_generic hdaudioC0D0: Mic=0x18 Mar 04 20:31:09 volumiow kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher Mar 04 20:31:09 volumiow kernel: fuse: init (API version 7.41) Mar 04 20:31:09 volumiow kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input5 Mar 04 20:31:09 volumiow kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input6 Mar 04 20:31:09 volumiow kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input7 Mar 04 20:31:09 volumiow kernel: [drm] radeon kernel modesetting enabled. Mar 04 20:31:09 volumiow kernel: mmc0: Failed to initialize a non-removable card Mar 04 20:31:09 volumiow kernel: [drm] amdgpu kernel modesetting enabled. Mar 04 20:31:09 volumiow kernel: scsi host4: pata_legacy Mar 04 20:31:09 volumiow kernel: ata4: PATA max PIO4 cmd 0x1f0 ctl 0x3f6 irq 14 lpm-pol 0 Mar 04 20:31:09 volumiow kernel: scsi host4: pata_legacy Mar 04 20:31:09 volumiow kernel: ata4: PATA max PIO4 cmd 0x170 ctl 0x376 irq 15 lpm-pol 0 Mar 04 20:31:09 volumiow kernel: FAT-fs (sdb1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! Mar 04 20:31:09 volumiow kernel: EXT4-fs (sdb2): recovery complete Mar 04 20:31:09 volumiow kernel: EXT4-fs (sdb2): mounted filesystem b0a058e9-0951-4405-9f54-2004a4130548 r/w with ordered data mode. Quota mode: none. Mar 04 20:31:09 volumiow kernel: FAT-fs (sda1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! Mar 04 20:31:09 volumiow kernel: FAT-fs (sda1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! Mar 04 20:31:09 volumiow kernel: loop: module loaded Mar 04 20:31:09 volumiow kernel: block device autoloading is deprecated and will be removed. Mar 04 20:31:09 volumiow kernel: loop0: detected capacity change from 0 to 2331400 Mar 04 20:31:09 volumiow kernel: EXT4-fs (sdb3): recovery complete Mar 04 20:31:09 volumiow kernel: EXT4-fs (sdb3): mounted filesystem a75a63ef-7a01-4f5e-b572-6ddd34d5e25f r/w with ordered data mode. Quota mode: none. Mar 04 20:31:09 volumiow systemd[1]: Inserted module 'autofs4' Mar 04 20:31:09 volumiow systemd[1]: systemd 252.39-1~deb12u1 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified) Mar 04 20:31:09 volumiow systemd[1]: Detected architecture x86-64. Mar 04 20:31:09 volumiow systemd[1]: Hostname set to . Mar 04 20:31:09 volumiow systemd[1]: Queued start job for default target graphical.target. Mar 04 20:31:09 volumiow systemd[1]: Created slice system-getty.slice - Slice /system/getty. Mar 04 20:31:09 volumiow systemd[1]: Created slice system-modprobe.slice - Slice /system/modprobe. Mar 04 20:31:09 volumiow systemd[1]: Created slice system-systemd\x2dfsck.slice - Slice /system/systemd-fsck. Mar 04 20:31:09 volumiow systemd[1]: Created slice user.slice - User and Session Slice. Mar 04 20:31:09 volumiow systemd[1]: Started systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch. Mar 04 20:31:09 volumiow systemd[1]: Set up automount proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point. Mar 04 20:31:09 volumiow systemd[1]: Expecting device dev-disk-by\x2duuid-5F54\x2d6886.device - /dev/disk/by-uuid/5F54-6886... Mar 04 20:31:09 volumiow systemd[1]: Reached target integritysetup.target - Local Integrity Protected Volumes. Mar 04 20:31:09 volumiow systemd[1]: Reached target slices.target - Slice Units. Mar 04 20:31:09 volumiow systemd[1]: Reached target veritysetup.target - Local Verity Protected Volumes. Mar 04 20:31:09 volumiow systemd[1]: Listening on rpcbind.socket - RPCbind Server Activation Socket. Mar 04 20:31:09 volumiow systemd[1]: Listening on systemd-fsckd.socket - fsck to fsckd communication Socket. Mar 04 20:31:09 volumiow systemd[1]: Listening on systemd-initctl.socket - initctl Compatibility Named Pipe. Mar 04 20:31:09 volumiow systemd[1]: Listening on systemd-journald-audit.socket - Journal Audit Socket. Mar 04 20:31:09 volumiow systemd[1]: Listening on systemd-journald-dev-log.socket - Journal Socket (/dev/log). Mar 04 20:31:09 volumiow systemd[1]: Listening on systemd-journald.socket - Journal Socket. Mar 04 20:31:09 volumiow systemd[1]: Listening on systemd-udevd-control.socket - udev Control Socket. Mar 04 20:31:09 volumiow systemd[1]: Listening on systemd-udevd-kernel.socket - udev Kernel Socket. Mar 04 20:31:09 volumiow systemd[1]: Mounting dev-hugepages.mount - Huge Pages File System... Mar 04 20:31:09 volumiow systemd[1]: Mounting dev-mqueue.mount - POSIX Message Queue File System... Mar 04 20:31:09 volumiow systemd[1]: Mounting sys-kernel-debug.mount - Kernel Debug File System... Mar 04 20:31:09 volumiow systemd[1]: Mounting sys-kernel-tracing.mount - Kernel Trace File System... Mar 04 20:31:09 volumiow systemd[1]: auth-rpcgss-module.service - Kernel Module supporting RPCSEC_GSS was skipped because of an unmet condition check (ConditionPathExists=/etc/krb5.keytab). Mar 04 20:31:09 volumiow systemd[1]: Started dynamicswap.service - dynamicswap service. Mar 04 20:31:09 volumiow systemd[1]: Reached target swap.target - Swaps. Mar 04 20:31:09 volumiow systemd[1]: Starting fake-hwclock.service - Restore / save the current clock... Mar 04 20:31:09 volumiow systemd[1]: Starting kmod-static-nodes.service - Create List of Static Device Nodes... Mar 04 20:31:09 volumiow systemd[1]: Starting modprobe@configfs.service - Load Kernel Module configfs... Mar 04 20:31:09 volumiow systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod... Mar 04 20:31:09 volumiow systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm... Mar 04 20:31:09 volumiow systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore... Mar 04 20:31:09 volumiow systemd[1]: Starting modprobe@fuse.service - Load Kernel Module fuse... Mar 04 20:31:09 volumiow systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop... Mar 04 20:31:09 volumiow systemd[1]: Starting systemd-journald.service - Journal Service... Mar 04 20:31:09 volumiow systemd[1]: Starting systemd-modules-load.service - Load Kernel Modules... Mar 04 20:31:09 volumiow systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Mar 04 20:31:09 volumiow systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Mar 04 20:31:09 volumiow systemd[1]: Mounted dev-hugepages.mount - Huge Pages File System. Mar 04 20:31:09 volumiow systemd[1]: Mounted dev-mqueue.mount - POSIX Message Queue File System. Mar 04 20:31:09 volumiow systemd[1]: Mounted sys-kernel-debug.mount - Kernel Debug File System. Mar 04 20:31:09 volumiow systemd[1]: Mounted sys-kernel-tracing.mount - Kernel Trace File System. Mar 04 20:31:09 volumiow systemd[1]: Finished fake-hwclock.service - Restore / save the current clock. Mar 04 20:31:09 volumiow systemd[1]: Finished kmod-static-nodes.service - Create List of Static Device Nodes. Mar 04 20:31:09 volumiow systemd[1]: modprobe@configfs.service: Deactivated successfully. Mar 04 20:31:09 volumiow systemd[1]: Finished modprobe@configfs.service - Load Kernel Module configfs. Mar 04 20:31:09 volumiow systemd[1]: modprobe@dm_mod.service: Deactivated successfully. Mar 04 20:31:09 volumiow systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod. Mar 04 20:31:09 volumiow systemd[1]: modprobe@drm.service: Deactivated successfully. Mar 04 20:31:09 volumiow systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm. Mar 04 20:31:09 volumiow systemd[1]: modprobe@efi_pstore.service: Deactivated successfully. Mar 04 20:31:09 volumiow systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore. Mar 04 20:31:09 volumiow systemd[1]: modprobe@fuse.service: Deactivated successfully. Mar 04 20:31:09 volumiow systemd[1]: Finished modprobe@fuse.service - Load Kernel Module fuse. Mar 04 20:31:09 volumiow systemd[1]: modprobe@loop.service: Deactivated successfully. Mar 04 20:31:09 volumiow systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop. Mar 04 20:31:09 volumiow systemd[1]: Mounting sys-fs-fuse-connections.mount - FUSE Control File System... Mar 04 20:31:09 volumiow systemd[1]: Mounting sys-kernel-config.mount - Kernel Configuration File System... Mar 04 20:31:09 volumiow systemd[1]: systemd-repart.service - Repartition Root Disk was skipped because no trigger condition checks were met. Mar 04 20:31:09 volumiow systemd[1]: Finished systemd-remount-fs.service - Remount Root and Kernel File Systems. Mar 04 20:31:09 volumiow systemd[1]: Mounted sys-fs-fuse-connections.mount - FUSE Control File System. Mar 04 20:31:09 volumiow systemd[1]: Mounted sys-kernel-config.mount - Kernel Configuration File System. Mar 04 20:31:09 volumiow systemd[1]: systemd-firstboot.service - First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes). Mar 04 20:31:09 volumiow systemd[1]: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore). Mar 04 20:31:09 volumiow systemd[1]: Starting systemd-random-seed.service - Load/Save Random Seed... Mar 04 20:31:09 volumiow systemd[1]: Starting systemd-sysusers.service - Create System Users... Mar 04 20:31:09 volumiow systemd[1]: Finished systemd-modules-load.service - Load Kernel Modules. Mar 04 20:31:09 volumiow systemd[1]: Starting systemd-sysctl.service - Apply Kernel Variables... Mar 04 20:31:09 volumiow systemd[1]: Finished systemd-random-seed.service - Load/Save Random Seed. Mar 04 20:31:09 volumiow systemd[1]: first-boot-complete.target - First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes). Mar 04 20:31:09 volumiow systemd[1]: Finished systemd-sysctl.service - Apply Kernel Variables. Mar 04 20:31:09 volumiow systemd[1]: dynamicswap.service: Deactivated successfully. Mar 04 20:31:09 volumiow systemd[1]: Finished systemd-sysusers.service - Create System Users. Mar 04 20:31:09 volumiow systemd[1]: Starting systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev... Mar 04 20:31:09 volumiow systemd-journald[559]: Journal started Mar 04 20:31:09 volumiow systemd-journald[559]: Runtime Journal (/run/log/journal/0f11d747902988a222300c786984a9ae) is 3.7M, max 30.0M, 26.2M free. Mar 04 20:31:09 volumiow fake-hwclock[549]: Current system time: 2026-03-04 19:31:09 Mar 04 20:31:09 volumiow fake-hwclock[549]: fake-hwclock saved clock information is in the past: 2026-03-03 14:23:26 Mar 04 20:31:09 volumiow fake-hwclock[549]: To set system time to this saved clock anyway, use "force" Mar 04 20:31:09 volumiow systemd[1]: Started systemd-journald.service - Journal Service. Mar 04 20:31:09 volumiow systemd[1]: Finished systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev. Mar 04 20:31:09 volumiow systemd[1]: Reached target local-fs-pre.target - Preparation for Local File Systems. Mar 04 20:31:09 volumiow systemd[1]: Starting systemd-udevd.service - Rule-based Manager for Device Events and Files... Mar 04 20:31:09 volumiow systemd-udevd[581]: Using default interface naming scheme 'v252'. Mar 04 20:31:09 volumiow systemd[1]: Finished systemd-udev-trigger.service - Coldplug All udev Devices. Mar 04 20:31:09 volumiow systemd[1]: Starting ifupdown-pre.service - Helper to synchronize boot up for ifupdown... Mar 04 20:31:09 volumiow systemd[1]: Finished ifupdown-pre.service - Helper to synchronize boot up for ifupdown. Mar 04 20:31:09 volumiow systemd[1]: Started systemd-udevd.service - Rule-based Manager for Device Events and Files. Mar 04 20:31:09 volumiow kernel: sd 3:0:0:0: Attached scsi generic sg0 type 0 Mar 04 20:31:09 volumiow kernel: sd 0:0:0:0: Attached scsi generic sg1 type 0 Mar 04 20:31:09 volumiow (udev-worker)[592]: Network interface NamePolicy= disabled on kernel command line. Mar 04 20:31:09 volumiow systemd[1]: Found device dev-disk-by\x2duuid-5F54\x2d6886.device - Samsung_SSD_860_EVO_mSATA_250GB boot. Mar 04 20:31:09 volumiow systemd[1]: Starting systemd-fsck@dev-disk-by\x2duuid-5F54\x2d6886.service - File System Check on /dev/disk/by-uuid/5F54-6886... Mar 04 20:31:09 volumiow systemd[1]: Expecting device sys-subsystem-net-devices-eth0.device - /sys/subsystem/net/devices/eth0... Mar 04 20:31:09 volumiow systemd[1]: Started systemd-fsckd.service - File System Check Daemon to report status. Mar 04 20:31:10 volumiow kernel: intel_pmc_core INT33A1:00: initialized Mar 04 20:31:10 volumiow systemd-fsck[632]: fsck.fat 4.2 (2021-01-31) Mar 04 20:31:10 volumiow systemd-fsck[632]: /dev/sdb1: 18 files, 23295/93500 clusters Mar 04 20:31:10 volumiow systemd[1]: Finished systemd-fsck@dev-disk-by\x2duuid-5F54\x2d6886.service - File System Check on /dev/disk/by-uuid/5F54-6886. Mar 04 20:31:10 volumiow systemd[1]: Found device sys-subsystem-net-devices-eth0.device - RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller. Mar 04 20:31:10 volumiow kernel: dw-apb-uart.0: ttyS4 at MMIO 0xdf12d000 (irq = 20, base_baud = 115200) is a 16550A Mar 04 20:31:10 volumiow kernel: cryptd: max_cpu_qlen set to 1000 Mar 04 20:31:10 volumiow kernel: at24 0-0050: supply vcc not found, using dummy regulator Mar 04 20:31:10 volumiow kernel: at24 0-0050: 256 byte spd EEPROM, read-only Mar 04 20:31:10 volumiow systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod... Mar 04 20:31:10 volumiow systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore... Mar 04 20:31:10 volumiow systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop... Mar 04 20:31:10 volumiow systemd[1]: systemd-firstboot.service - First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes). Mar 04 20:31:10 volumiow kernel: AES CTR mode by8 optimization enabled Mar 04 20:31:10 volumiow systemd[1]: first-boot-complete.target - First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes). Mar 04 20:31:10 volumiow systemd[1]: modprobe@dm_mod.service: Deactivated successfully. Mar 04 20:31:10 volumiow systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod. Mar 04 20:31:10 volumiow systemd[1]: modprobe@efi_pstore.service: Deactivated successfully. Mar 04 20:31:10 volumiow systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore. Mar 04 20:31:10 volumiow systemd[1]: modprobe@loop.service: Deactivated successfully. Mar 04 20:31:10 volumiow systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop. Mar 04 20:31:10 volumiow systemd[1]: Listening on systemd-rfkill.socket - Load/Save RF Kill Switch Status /dev/rfkill Watch. Mar 04 20:31:10 volumiow systemd[1]: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore). Mar 04 20:31:10 volumiow systemd[1]: systemd-repart.service - Repartition Root Disk was skipped because no trigger condition checks were met. Mar 04 20:31:10 volumiow kernel: usb 1-4: Warning! Unlikely big volume range (=2032), cval->res is probably wrong. Mar 04 20:31:10 volumiow kernel: usb 1-4: [10] FU [D50 III Playback Volume] ch = 1, val = -32512/0/16 Mar 04 20:31:10 volumiow kernel: usbcore: registered new interface driver snd-usb-audio Mar 04 20:31:10 volumiow kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database Mar 04 20:31:10 volumiow kernel: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Mar 04 20:31:10 volumiow kernel: Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600' Mar 04 20:31:10 volumiow systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod... Mar 04 20:31:10 volumiow systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore... Mar 04 20:31:10 volumiow systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop... Mar 04 20:31:10 volumiow systemd[1]: systemd-firstboot.service - First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes). Mar 04 20:31:10 volumiow systemd[1]: first-boot-complete.target - First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes). Mar 04 20:31:10 volumiow systemd[1]: modprobe@dm_mod.service: Deactivated successfully. Mar 04 20:31:10 volumiow systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod. Mar 04 20:31:10 volumiow systemd[1]: modprobe@loop.service: Deactivated successfully. Mar 04 20:31:10 volumiow systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop. Mar 04 20:31:10 volumiow systemd[1]: systemd-repart.service - Repartition Root Disk was skipped because no trigger condition checks were met. Mar 04 20:31:10 volumiow systemd[1]: modprobe@efi_pstore.service: Deactivated successfully. Mar 04 20:31:10 volumiow systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore. Mar 04 20:31:10 volumiow systemd[1]: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore). Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: ath: phy0: ASPM enabled: 0x43 Mar 04 20:31:10 volumiow kernel: ath: EEPROM regdomain: 0x6a Mar 04 20:31:10 volumiow kernel: ath: EEPROM indicates we should expect a direct regpair map Mar 04 20:31:10 volumiow kernel: ath: Country alpha2 being used: 00 Mar 04 20:31:10 volumiow kernel: ath: Regpair used: 0x6a Mar 04 20:31:10 volumiow kernel: ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' Mar 04 20:31:10 volumiow (udev-worker)[600]: pcmC5D0p: Process '/bin/bash -c '/usr/local/bin/volumio usbattach'' failed with exit code 7. Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: ieee80211 phy0: Atheros AR9300 Rev:3 mem=0x00000000080a590f, irq=19 Mar 04 20:31:10 volumiow systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill Switch Status... Mar 04 20:31:10 volumiow (udev-worker)[588]: Network interface NamePolicy= disabled on kernel command line. Mar 04 20:31:10 volumiow systemd[1]: Started systemd-rfkill.service - Load/Save RF Kill Switch Status. Mar 04 20:31:10 volumiow systemd[1]: Expecting device sys-subsystem-net-devices-wlan0.device - /sys/subsystem/net/devices/wlan0... Mar 04 20:31:10 volumiow systemd[1]: Found device sys-subsystem-net-devices-wlan0.device - AR93xx Wireless Network Adapter. Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow systemd[1]: Mounting boot.mount - /boot... Mar 04 20:31:10 volumiow systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway. Mar 04 20:31:10 volumiow systemd[1]: Mounting tmp.mount - /tmp... Mar 04 20:31:10 volumiow systemd[1]: var-log.mount: Directory /var/log to mount over is not empty, mounting anyway. Mar 04 20:31:10 volumiow systemd[1]: Mounting var-log.mount - /var/log... Mar 04 20:31:10 volumiow kernel: FAT-fs (sdb1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow systemd[1]: Mounting var-spool-cups.mount - /var/spool/cups... Mar 04 20:31:10 volumiow systemd[1]: Mounted boot.mount - /boot. Mar 04 20:31:10 volumiow systemd[1]: Mounted tmp.mount - /tmp. Mar 04 20:31:10 volumiow systemd[1]: Mounted var-log.mount - /var/log. Mar 04 20:31:10 volumiow systemd[1]: Mounted var-spool-cups.mount - /var/spool/cups. Mar 04 20:31:10 volumiow systemd[1]: Mounting var-spool-cups-tmp.mount - /var/spool/cups/tmp... Mar 04 20:31:10 volumiow systemd[1]: Starting systemd-journal-flush.service - Flush Journal to Persistent Storage... Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow systemd[1]: Mounted var-spool-cups-tmp.mount - /var/spool/cups/tmp. Mar 04 20:31:10 volumiow systemd[1]: Reached target local-fs.target - Local File Systems. Mar 04 20:31:10 volumiow systemd[1]: Started ifup@eth0.service - ifup for eth0. Mar 04 20:31:10 volumiow systemd[1]: Started ifup@wlan0.service - ifup for wlan0. Mar 04 20:31:10 volumiow systemd[1]: Starting networking.service - Raise network interfaces... Mar 04 20:31:10 volumiow systemd[1]: Starting plymouth-read-write.service - Tell Plymouth To Write Out Runtime Data... Mar 04 20:31:10 volumiow systemd-journald[559]: Runtime Journal (/run/log/journal/0f11d747902988a222300c786984a9ae) is 3.7M, max 30.0M, 26.2M free. Mar 04 20:31:10 volumiow systemd-journald[559]: Received client request to flush runtime journal. Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow systemd[1]: Starting plymouth-rotation.service - Plymouth rotation detection for shutdown/reboot... Mar 04 20:31:10 volumiow systemd[1]: Starting systemd-binfmt.service - Set Up Additional Binary Formats... Mar 04 20:31:10 volumiow systemd[1]: systemd-machine-id-commit.service - Commit a transient machine-id on disk was skipped because of an unmet condition check (ConditionPathIsMountPoint=/etc/machine-id). Mar 04 20:31:10 volumiow systemd[1]: Finished systemd-journal-flush.service - Flush Journal to Persistent Storage. Mar 04 20:31:10 volumiow systemd[1]: Finished plymouth-read-write.service - Tell Plymouth To Write Out Runtime Data. Mar 04 20:31:10 volumiow systemd[1]: Received SIGRTMIN+20 from PID 407 (plymouthd). Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow systemd[1]: Starting systemd-tmpfiles-setup.service - Create System Files and Directories... Mar 04 20:31:10 volumiow systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 752 (systemd-binfmt) Mar 04 20:31:10 volumiow kernel: warning: `iwconfig' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211 Mar 04 20:31:10 volumiow systemd[1]: Finished plymouth-rotation.service - Plymouth rotation detection for shutdown/reboot. Mar 04 20:31:10 volumiow systemd[1]: Starting plymouth-start.service - Show Plymouth Boot Screen... Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow systemd[1]: Finished systemd-tmpfiles-setup.service - Create System Files and Directories. Mar 04 20:31:10 volumiow systemd[1]: Started haveged.service - Entropy Daemon based on the HAVEGE algorithm. Mar 04 20:31:10 volumiow systemd[1]: Starting rpcbind.service - RPC bind portmap service... Mar 04 20:31:10 volumiow systemd[1]: Starting systemd-update-utmp.service - Record System Boot/Shutdown in UTMP... Mar 04 20:31:10 volumiow sh[790]: dhcpcd-9.4.1 starting Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow dhcpcd[790]: dhcpcd-9.4.1 starting Mar 04 20:31:10 volumiow systemd[1]: Started plymouth-start.service - Show Plymouth Boot Screen. Mar 04 20:31:10 volumiow sh[790]: DUID 00:04:03:00:02:00:04:00:05:00:00:06:00:07:00:08:00:09 Mar 04 20:31:10 volumiow dhcpcd[806]: DUID 00:04:03:00:02:00:04:00:05:00:00:06:00:07:00:08:00:09 Mar 04 20:31:10 volumiow systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid). Mar 04 20:31:10 volumiow systemd[1]: Started systemd-ask-password-plymouth.path - Forward Password Requests to Plymouth Directory Watch. Mar 04 20:31:10 volumiow systemd[1]: Reached target cryptsetup.target - Local Encrypted Volumes. Mar 04 20:31:10 volumiow systemd[1]: Finished systemd-update-utmp.service - Record System Boot/Shutdown in UTMP. Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:10 volumiow kernel: 8021q: 802.1Q VLAN Support v1.8 Mar 04 20:31:10 volumiow haveged[795]: haveged: command socket is listening at fd 3 Mar 04 20:31:10 volumiow systemd[1]: Started rpcbind.service - RPC bind portmap service. Mar 04 20:31:10 volumiow systemd[1]: Reached target rpcbind.target - RPC Port Mapper. Mar 04 20:31:11 volumiow kernel: RTL8211E Gigabit Ethernet r8169-0-100:00: attached PHY driver (mii_bus:phy_addr=r8169-0-100:00, irq=MAC) Mar 04 20:31:11 volumiow sh[876]: wlan0=wlan0 Mar 04 20:31:11 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:11 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:11 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:11 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:11 volumiow systemd[1]: Finished networking.service - Raise network interfaces. Mar 04 20:31:11 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:11 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:11 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:11 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:11 volumiow haveged[795]: haveged: ver: 1.9.14; arch: x86; vend: GenuineIntel; build: (gcc 12.2.0 ITV); collect: 128K Mar 04 20:31:11 volumiow haveged[795]: haveged: cpu: (L4 VC); data: 32K (L4 V); inst: 32K (L4 V); idx: 24/40; sz: 32010/53875 Mar 04 20:31:11 volumiow haveged[795]: haveged: tot tests(BA8): A:1/1 B:1/1 continuous tests(B): last entropy estimate 8.00189 Mar 04 20:31:11 volumiow haveged[795]: haveged: fills: 0, generated: 0 Mar 04 20:31:11 volumiow sh[790]: eth0: waiting for carrier Mar 04 20:31:11 volumiow sh[790]: eth0: carrier acquired Mar 04 20:31:11 volumiow dhcpcd[806]: eth0: waiting for carrier Mar 04 20:31:11 volumiow dhcpcd[806]: eth0: carrier acquired Mar 04 20:31:11 volumiow kernel: r8169 0000:01:00.0 eth0: Link is Down Mar 04 20:31:11 volumiow dhcpcd[806]: eth0: IAID 4c:68:5e:ad Mar 04 20:31:11 volumiow sh[790]: eth0: IAID 4c:68:5e:ad Mar 04 20:31:11 volumiow dhcpcd[806]: eth0: adding address fe80::2f04:4d5:a0d7:fcbe Mar 04 20:31:11 volumiow dhcpcd[806]: ipv6_addaddr1: Permission denied Mar 04 20:31:11 volumiow sh[790]: eth0: adding address fe80::2f04:4d5:a0d7:fcbe Mar 04 20:31:11 volumiow sh[790]: ipv6_addaddr1: Permission denied Mar 04 20:31:11 volumiow systemd[1]: Mounting proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System... Mar 04 20:31:11 volumiow systemd[1]: Mounting run-rpc_pipefs.mount - RPC Pipe File System... Mar 04 20:31:11 volumiow systemd[1]: Mounted proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System. Mar 04 20:31:11 volumiow systemd[1]: Finished systemd-binfmt.service - Set Up Additional Binary Formats. Mar 04 20:31:11 volumiow systemd[1]: Reached target sysinit.target - System Initialization. Mar 04 20:31:11 volumiow systemd[1]: Started acpid.path - ACPI Events Check. Mar 04 20:31:11 volumiow systemd[1]: Started apt-daily.timer - Daily apt download activities. Mar 04 20:31:11 volumiow systemd[1]: Started apt-daily-upgrade.timer - Daily apt upgrade and clean activities. Mar 04 20:31:11 volumiow systemd[1]: Started dpkg-db-backup.timer - Daily dpkg database backup timer. Mar 04 20:31:11 volumiow systemd[1]: Started e2scrub_all.timer - Periodic ext4 Online Metadata Check for All Filesystems. Mar 04 20:31:11 volumiow systemd[1]: Started fstrim.timer - Discard unused blocks once a week. Mar 04 20:31:11 volumiow systemd[1]: Started man-db.timer - Daily man-db regeneration. Mar 04 20:31:11 volumiow systemd[1]: Started ntpsec-rotate-stats.timer - Rotate ntpd stats daily. Mar 04 20:31:11 volumiow systemd[1]: Started setdatetime-helper.timer - Volumio Time Sync Watchdog Timer. Mar 04 20:31:11 volumiow systemd[1]: Started systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories. Mar 04 20:31:11 volumiow systemd[1]: Reached target paths.target - Path Units. Mar 04 20:31:11 volumiow systemd[1]: Reached target timers.target - Timer Units. Mar 04 20:31:11 volumiow systemd[1]: Listening on acpid.socket - ACPID Listen Socket. Mar 04 20:31:11 volumiow systemd[1]: Listening on avahi-daemon.socket - Avahi mDNS/DNS-SD Stack Activation Socket. Mar 04 20:31:11 volumiow systemd[1]: Listening on dbus.socket - D-Bus System Message Bus Socket. Mar 04 20:31:11 volumiow systemd[1]: Reached target sockets.target - Socket Units. Mar 04 20:31:11 volumiow systemd[1]: systemd-pcrphase-sysinit.service - TPM2 PCR Barrier (Initialization) was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f). Mar 04 20:31:11 volumiow systemd[1]: Reached target basic.target - Basic System. Mar 04 20:31:11 volumiow systemd[1]: Started acpid.service - ACPI event daemon. Mar 04 20:31:11 volumiow systemd[1]: alsa-state.service - Manage Sound Card State (restore and store) was skipped because of an unmet condition check (ConditionPathExists=/etc/alsa/state-daemon.conf). Mar 04 20:31:11 volumiow systemd[1]: Starting alsa-restore.service - Save/Restore Sound Card State... Mar 04 20:31:11 volumiow systemd[1]: Starting avahi-daemon.service - Avahi mDNS/DNS-SD Stack... Mar 04 20:31:11 volumiow systemd[1]: Starting dbus.service - D-Bus System Message Bus... Mar 04 20:31:11 volumiow systemd[1]: Starting e2scrub_reap.service - Remove Stale Online ext4 Metadata Check Snapshots... Mar 04 20:31:11 volumiow systemd[1]: getty-static.service - getty on tty2-tty6 if dbus and logind are not available was skipped because of an unmet condition check (ConditionPathExists=!/usr/bin/dbus-daemon). Mar 04 20:31:11 volumiow systemd[1]: headless_wireless.service - Copy user wpa_supplicant.conf was skipped because of an unmet condition check (ConditionPathExists=/boot/wpa_supplicant.conf). Mar 04 20:31:11 volumiow systemd[1]: Started iptables.service - Volumio Iptables Module. Mar 04 20:31:11 volumiow systemd[1]: Starting systemd-logind.service - User Login Management... Mar 04 20:31:11 volumiow systemd[1]: Starting triggerhappy.service - triggerhappy global hotkey daemon... Mar 04 20:31:11 volumiow systemd[1]: Started upmpdcli.service - UPnP Renderer front-end to MPD. Mar 04 20:31:11 volumiow systemd[1]: Started volumio-remote-updater.service - Volumio Remote OTA Updater. Mar 04 20:31:11 volumiow systemd[1]: Starting volumio_rfkill_unblock.service - Manage nl80211 modules blocking state... Mar 04 20:31:11 volumiow systemd[1]: volumiossh.service - Volumio SSH enabler was skipped because of an unmet condition check (ConditionPathExistsGlob=/boot/ssh{,.txt}). Mar 04 20:31:11 volumiow systemd[1]: Starting wireless.service - Wireless Services... Mar 04 20:31:11 volumiow systemd[1]: Started ntpsec-rotate-stats.service - Rotate ntpd stats. Mar 04 20:31:11 volumiow thd[897]: Unable to parse trigger line: Mar 04 20:31:11 volumiow thd[897]: Unable to parse trigger line: Mar 04 20:31:11 volumiow volumio_rfkill_unblock.sh[900]: Volumio WiFi Soft Blocked check script Mar 04 20:31:11 volumiow volumio_rfkill_unblock.sh[900]: Check if rfkill is available Mar 04 20:31:11 volumiow volumio_rfkill_unblock.sh[900]: Check if rfkill listed devices are already unblocked Mar 04 20:31:11 volumiow kernel: RPC: Registered named UNIX socket transport module. Mar 04 20:31:11 volumiow kernel: RPC: Registered udp transport module. Mar 04 20:31:11 volumiow kernel: RPC: Registered tcp transport module. Mar 04 20:31:11 volumiow kernel: RPC: Registered tcp-with-tls transport module. Mar 04 20:31:11 volumiow kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Mar 04 20:31:11 volumiow avahi-daemon[892]: Found user 'avahi' (UID 103) and group 'avahi' (GID 109). Mar 04 20:31:11 volumiow avahi-daemon[892]: Successfully dropped root privileges. Mar 04 20:31:11 volumiow avahi-daemon[892]: avahi-daemon 0.8 starting up. Mar 04 20:31:11 volumiow systemd[1]: Mounted run-rpc_pipefs.mount - RPC Pipe File System. Mar 04 20:31:11 volumiow systemd[1]: Finished alsa-restore.service - Save/Restore Sound Card State. Mar 04 20:31:11 volumiow systemd[1]: Reached target rpc_pipefs.target. Mar 04 20:31:11 volumiow systemd[1]: Reached target sound.target - Sound Card. Mar 04 20:31:11 volumiow systemd[1]: rpc-gssd.service - RPC security service for NFS client and server was skipped because of an unmet condition check (ConditionPathExists=/etc/krb5.keytab). Mar 04 20:31:11 volumiow systemd[1]: Reached target nfs-client.target - NFS client services. Mar 04 20:31:11 volumiow systemd[1]: Reached target remote-fs-pre.target - Preparation for Remote File Systems. Mar 04 20:31:11 volumiow systemd[1]: Reached target remote-fs.target - Remote File Systems. Mar 04 20:31:11 volumiow thd[897]: Device /dev/input/event3 not suitable. Mar 04 20:31:11 volumiow systemd[1]: Starting loadcpufreq.service - LSB: Load kernel modules needed to enable cpufreq scaling... Mar 04 20:31:11 volumiow systemd[1]: systemd-pcrphase.service - TPM2 PCR Barrier (User) was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f). Mar 04 20:31:11 volumiow systemd[1]: ntpsec-rotate-stats.service: Deactivated successfully. Mar 04 20:31:11 volumiow acpid[890]: starting up with netlink and the input layer Mar 04 20:31:11 volumiow volumio_rfkill_unblock.sh[900]: Wi-Fi is already unblocked. Mar 04 20:31:11 volumiow systemd[1]: Finished volumio_rfkill_unblock.service - Manage nl80211 modules blocking state. Mar 04 20:31:11 volumiow systemd[1]: Starting dhcpcd.service - DHCP Client Daemon on all interfaces... Mar 04 20:31:11 volumiow systemd[1]: e2scrub_reap.service: Deactivated successfully. Mar 04 20:31:11 volumiow systemd[1]: Finished e2scrub_reap.service - Remove Stale Online ext4 Metadata Check Snapshots. Mar 04 20:31:11 volumiow acpid[890]: 3 rules loaded Mar 04 20:31:11 volumiow acpid[890]: waiting for events: event logging is off Mar 04 20:31:11 volumiow dhcpcd[918]: dhcpcd-9.4.1 starting Mar 04 20:31:11 volumiow systemd-logind[896]: New seat seat0. Mar 04 20:31:11 volumiow systemd-logind[896]: Watching system buttons on /dev/input/event2 (Power Button) Mar 04 20:31:11 volumiow systemd-logind[896]: Watching system buttons on /dev/input/event1 (Power Button) Mar 04 20:31:11 volumiow systemd-logind[896]: Watching system buttons on /dev/input/event0 (Sleep Button) Mar 04 20:31:11 volumiow dhcpcd[806]: eth0: soliciting an IPv6 router Mar 04 20:31:11 volumiow sh[790]: eth0: soliciting an IPv6 router Mar 04 20:31:11 volumiow systemd[1]: Started triggerhappy.service - triggerhappy global hotkey daemon. Mar 04 20:31:11 volumiow volumio-remote-updater[899]: Volumio OTA Client: 1.7.0 Mar 04 20:31:11 volumiow volumio-remote-updater[899]: Error: No active session Mar 04 20:31:11 volumiow volumio-remote-updater[899]: [2026-03-04 20:31:11] [info] asio async_connect error: asio.system:111 (Connection refused) Mar 04 20:31:11 volumiow volumio-remote-updater[899]: [2026-03-04 20:31:11] [info] Error getting remote endpoint: asio.system:107 (Transport endpoint is not connected) Mar 04 20:31:11 volumiow volumio-remote-updater[899]: [2026-03-04 20:31:11] [error] handle_connect error: Connection refused Mar 04 20:31:11 volumiow dhcpcd[926]: dev: loaded udev Mar 04 20:31:11 volumiow dhcpcd[926]: DUID 00:04:03:00:02:00:04:00:05:00:00:06:00:07:00:08:00:09 Mar 04 20:31:11 volumiow systemd[1]: Starting th-udev-rebind.service - Late rebind of input devices to triggerhappy... Mar 04 20:31:11 volumiow systemd[1]: Started dhcpcd.service - DHCP Client Daemon on all interfaces. Mar 04 20:31:11 volumiow systemd[1]: Started dbus.service - D-Bus System Message Bus. Mar 04 20:31:11 volumiow avahi-daemon[892]: Successfully called chroot(). Mar 04 20:31:11 volumiow avahi-daemon[892]: Successfully dropped remaining capabilities. Mar 04 20:31:11 volumiow th-udev-rebind.sh[933]: Rebinding /dev/input/event0 to thd using --add... Mar 04 20:31:11 volumiow dbus-daemon[893]: [system] Successfully activated service 'org.freedesktop.systemd1' Mar 04 20:31:11 volumiow systemd[1]: Starting wpa_supplicant.service - WPA supplicant... Mar 04 20:31:11 volumiow systemd[1]: Started systemd-logind.service - User Login Management. Mar 04 20:31:11 volumiow systemd[1]: Started avahi-daemon.service - Avahi mDNS/DNS-SD Stack. Mar 04 20:31:11 volumiow avahi-daemon[892]: Loading service file /services/volumio.service. Mar 04 20:31:11 volumiow avahi-daemon[892]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1. Mar 04 20:31:11 volumiow avahi-daemon[892]: New relevant interface lo.IPv4 for mDNS. Mar 04 20:31:11 volumiow avahi-daemon[892]: Network interface enumeration completed. Mar 04 20:31:11 volumiow avahi-daemon[892]: Registering new address record for 127.0.0.1 on lo.IPv4. Mar 04 20:31:11 volumiow th-udev-rebind.sh[933]: Rebinding /dev/input/event1 to thd using --add... Mar 04 20:31:11 volumiow th-udev-rebind.sh[933]: Rebinding /dev/input/event2 to thd using --add... Mar 04 20:31:11 volumiow dhcpcd[926]: eth0: IAID 4c:68:5e:ad Mar 04 20:31:11 volumiow dhcpcd[926]: eth0: adding address fe80::2f04:4d5:a0d7:fcbe Mar 04 20:31:11 volumiow dhcpcd[926]: ipv6_addaddr1: Permission denied Mar 04 20:31:11 volumiow dhcpcd[926]: wlan0: waiting for carrier Mar 04 20:31:11 volumiow th-udev-rebind.sh[933]: Rebinding /dev/input/event3 to thd using --add... Mar 04 20:31:11 volumiow upmpdcli[898]: Could not open config: /tmp/upmpdcli.conf Mar 04 20:31:12 volumiow dhcpcd[806]: eth0: carrier lost Mar 04 20:31:12 volumiow dhcpcd[926]: eth0: carrier lost Mar 04 20:31:12 volumiow sh[790]: eth0: carrier lost Mar 04 20:31:12 volumiow thd[897]: Device /dev/input/event3 not suitable. Mar 04 20:31:12 volumiow wpa_supplicant[942]: Successfully initialized wpa_supplicant Mar 04 20:31:12 volumiow loadcpufreq[916]: Loading cpufreq kernel modules...done (acpi-cpufreq). Mar 04 20:31:12 volumiow systemd[1]: upmpdcli.service: Main process exited, code=exited, status=1/FAILURE Mar 04 20:31:12 volumiow systemd[1]: upmpdcli.service: Failed with result 'exit-code'. Mar 04 20:31:12 volumiow systemd[1]: Started loadcpufreq.service - LSB: Load kernel modules needed to enable cpufreq scaling. Mar 04 20:31:12 volumiow systemd[1]: Started wpa_supplicant.service - WPA supplicant. Mar 04 20:31:12 volumiow systemd[1]: iptables.service: Deactivated successfully. Mar 04 20:31:12 volumiow systemd[1]: Reached target network.target - Network. Mar 04 20:31:12 volumiow systemd[1]: Reached target network-online.target - Network is Online. Mar 04 20:31:12 volumiow systemd[1]: Starting cpufrequtils.service - LSB: set CPUFreq kernel parameters... Mar 04 20:31:12 volumiow systemd[1]: Starting ifplugd.service - LSB: Brings up/down network automatically... Mar 04 20:31:12 volumiow systemd[1]: Starting nmbd.service - Samba NMB Daemon... Mar 04 20:31:12 volumiow systemd[1]: Starting ntpsec.service - Network Time Service... Mar 04 20:31:12 volumiow systemd[1]: Starting rc-local.service - /etc/rc.local Compatibility... Mar 04 20:31:12 volumiow systemd[1]: Starting rpc-statd-notify.service - Notify NFS peers of a restart... Mar 04 20:31:12 volumiow systemd[1]: Starting samba-ad-dc.service - Samba AD Daemon... Mar 04 20:31:12 volumiow sm-notify[1013]: Version 2.6.2 starting Mar 04 20:31:12 volumiow systemd[1]: Starting setdatetime-helper.service - Time Synchronization Helper Service... Mar 04 20:31:12 volumiow systemd[1]: Started shairport-sync.service - Shairport Sync - AirPlay Audio Receiver. Mar 04 20:31:12 volumiow th-udev-rebind.sh[933]: Rebinding /dev/input/event4 to thd using --add... Mar 04 20:31:12 volumiow systemd[1]: Starting systemd-user-sessions.service - Permit User Sessions... Mar 04 20:31:12 volumiow th-udev-rebind.sh[933]: Rebinding /dev/input/event5 to thd using --add... Mar 04 20:31:12 volumiow systemd[1]: Started volumio-ipchange.service - Volumio IP Change Monitor. Mar 04 20:31:12 volumiow th-udev-rebind.sh[933]: Rebinding /dev/input/event6 to thd using --add... Mar 04 20:31:12 volumiow th-udev-rebind.sh[933]: Rebinding /dev/input/event7 to thd using --add... Mar 04 20:31:12 volumiow systemd[1]: Starting welcome.service - Show a welcome message on console... Mar 04 20:31:12 volumiow systemd[1]: Started rc-local.service - /etc/rc.local Compatibility. Mar 04 20:31:12 volumiow systemd[1]: Started rpc-statd-notify.service - Notify NFS peers of a restart. Mar 04 20:31:12 volumiow systemd[1]: th-udev-rebind.service: Deactivated successfully. Mar 04 20:31:12 volumiow systemd[1]: Finished th-udev-rebind.service - Late rebind of input devices to triggerhappy. Mar 04 20:31:12 volumiow systemd[1]: Finished systemd-user-sessions.service - Permit User Sessions. Mar 04 20:31:12 volumiow welcome[1033]: Resolved ip:[0] Mar 04 20:31:12 volumiow ntpd[1024]: INIT: ntpd ntpsec-1.2.2: Starting Mar 04 20:31:12 volumiow ntpd[1024]: INIT: Command line: /usr/sbin/ntpd -p /run/ntpd.pid -c /etc/ntpsec/ntp.conf -g -N -u ntpsec:ntpsec Mar 04 20:31:12 volumiow ntp-systemd-wrapper[1024]: 2026-03-04T20:31:12 ntpd[1024]: INIT: ntpd ntpsec-1.2.2: Starting Mar 04 20:31:12 volumiow ntp-systemd-wrapper[1024]: 2026-03-04T20:31:12 ntpd[1024]: INIT: Command line: /usr/sbin/ntpd -p /run/ntpd.pid -c /etc/ntpsec/ntp.conf -g -N -u ntpsec:ntpsec Mar 04 20:31:12 volumiow systemd[1]: Starting plymouth-quit-wait.service - Hold until boot process finishes up... Mar 04 20:31:12 volumiow systemd[1]: Starting plymouth-quit.service - Terminate Plymouth Boot Screen... Mar 04 20:31:12 volumiow systemd[1]: Started ntpsec.service - Network Time Service. Mar 04 20:31:12 volumiow ntpd[1041]: INIT: precision = 0.079 usec (-24) Mar 04 20:31:12 volumiow systemd[1]: Received SIGRTMIN+21 from PID 407 (plymouthd). Mar 04 20:31:12 volumiow cpufrequtils[1005]: CPUFreq Utilities: Setting ondemand CPUFreq governor...disabled, governor not available...done. Mar 04 20:31:12 volumiow ntpd[1041]: INIT: successfully locked into RAM Mar 04 20:31:12 volumiow ntpd[1041]: CONFIG: readconfig: parsing file: /etc/ntpsec/ntp.conf Mar 04 20:31:12 volumiow systemd[1]: Started cpufrequtils.service - LSB: set CPUFreq kernel parameters. Mar 04 20:31:12 volumiow ntpd[1041]: CONFIG: restrict nopeer ignored Mar 04 20:31:12 volumiow ifplugd(eth0)[1062]: ifplugd 0.28 initializing. Mar 04 20:31:12 volumiow ifplugd(eth0)[1062]: Using interface eth0/00:E0:4C:68:5E:AD with driver (version: 6.12.57-volumio) Mar 04 20:31:12 volumiow ifplugd(eth0)[1062]: Using detection mode: SIOCETHTOOL Mar 04 20:31:12 volumiow ifplugd(eth0)[1062]: Initialization complete, link beat not detected. Mar 04 20:31:12 volumiow systemd[1]: Received SIGRTMIN+21 from PID 407 (plymouthd). Mar 04 20:31:12 volumiow ntpd[1041]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature Mar 04 20:31:12 volumiow ntpd[1041]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): loaded, expire=2026-06-28T00:00Z last=2017-01-01T00:00Z ofs=37 Mar 04 20:31:12 volumiow ntpd[1041]: INIT: Using SO_TIMESTAMPNS(ns) Mar 04 20:31:12 volumiow ntpd[1041]: IO: Listen and drop on 0 v6wildcard [::]:123 Mar 04 20:31:12 volumiow ntpd[1041]: IO: Listen and drop on 1 v4wildcard 0.0.0.0:123 Mar 04 20:31:12 volumiow ntpd[1041]: IO: Listen normally on 2 lo 127.0.0.1:123 Mar 04 20:31:12 volumiow systemd[1]: Finished plymouth-quit-wait.service - Hold until boot process finishes up. Mar 04 20:31:12 volumiow ntpd[1041]: IO: Listening on routing socket on fd #19 for interface updates Mar 04 20:31:12 volumiow systemd[1]: Finished plymouth-quit.service - Terminate Plymouth Boot Screen. Mar 04 20:31:12 volumiow ntpd[1041]: INIT: MRU 10922 entries, 13 hash bits, 65536 bytes Mar 04 20:31:12 volumiow ntpd[1041]: INIT: Built with OpenSSL 3.0.9 30 May 2023, 30000090 Mar 04 20:31:12 volumiow ntpd[1041]: INIT: Running with OpenSSL 3.0.18 30 Sep 2025, 30000120 Mar 04 20:31:12 volumiow ntpd[1041]: NTSc: Using system default root certificates. Mar 04 20:31:12 volumiow systemd[1]: Started getty@tty1.service - Getty on tty1. Mar 04 20:31:12 volumiow systemd[1]: Reached target getty.target - Login Prompts. Mar 04 20:31:12 volumiow systemd[1]: Finished welcome.service - Show a welcome message on console. Mar 04 20:31:12 volumiow ntpd[1041]: statistics directory /var/log/ntpsec/ does not exist or is unwriteable, error No such file or directory Mar 04 20:31:12 volumiow ifplugd[1006]: Network Interface Plugging Daemon...start eth0...done. Mar 04 20:31:12 volumiow systemd[1]: Started ifplugd.service - LSB: Brings up/down network automatically. Mar 04 20:31:12 volumiow systemd[1]: samba-ad-dc.service: Skipped due to 'exec-condition'. Mar 04 20:31:12 volumiow systemd[1]: Condition check resulted in samba-ad-dc.service - Samba AD Daemon being skipped. Mar 04 20:31:12 volumiow wireless.js[901]: WIRELESS.JS - INFO: Single Network Mode enabled (default) - only one network device can be active at a time between ethernet and wireless Mar 04 20:31:12 volumiow wireless.js[901]: WIRELESS.JS - INFO: Wireless.js initializing wireless flow Mar 04 20:31:12 volumiow nmbd[1100]: [2026/03/04 20:31:12.753240, 0] ../../source3/nmbd/nmbd.c:901(main) Mar 04 20:31:12 volumiow nmbd[1100]: nmbd version 4.17.12-Debian started. Mar 04 20:31:12 volumiow nmbd[1100]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Mar 04 20:31:12 volumiow nmbd[1100]: [2026/03/04 20:31:12.758159, 0] ../../source3/nmbd/asyncdns.c:158(start_async_dns) Mar 04 20:31:12 volumiow nmbd[1100]: started asyncdns process 1117 Mar 04 20:31:12 volumiow nmbd[1100]: [2026/03/04 20:31:12.758938, 0] ../../lib/util/become_daemon.c:150(daemon_status) Mar 04 20:31:12 volumiow nmbd[1100]: daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ... Mar 04 20:31:12 volumiow nmbd[1100]: [2026/03/04 20:31:12.759088, 0] ../../source3/nmbd/nmbd_subnetdb.c:252(create_subnets) Mar 04 20:31:12 volumiow nmbd[1100]: NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6). Mar 04 20:31:12 volumiow sudo[1122]: root : unable to resolve host volumiow: System error Mar 04 20:31:12 volumiow sudo[1122]: root : PWD=/ ; USER=root ; COMMAND=/sbin/ip addr flush dev wlan0 Mar 04 20:31:12 volumiow sudo[1122]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Mar 04 20:31:12 volumiow sudo[1122]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:12 volumiow sudo[1124]: root : unable to resolve host volumiow: System error Mar 04 20:31:12 volumiow sudo[1124]: root : PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 down Mar 04 20:31:12 volumiow sudo[1124]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Mar 04 20:31:12 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:12 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:12 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:12 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:12 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:12 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:12 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:12 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:12 volumiow sudo[1124]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:12 volumiow wireless.js[901]: WIRELESS.JS - INFO: Cleaning previous... Mar 04 20:31:12 volumiow sudo[1127]: root : unable to resolve host volumiow: System error Mar 04 20:31:12 volumiow sudo[1127]: root : PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 up Mar 04 20:31:12 volumiow sudo[1127]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Mar 04 20:31:12 volumiow sudo[1127]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:12 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:12 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:12 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:12 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:12 volumiow wireless.js[901]: WIRELESS.JS - INFO: InterfaceValidator: READY - wlan0 is ready for operations Mar 04 20:31:12 volumiow wireless.js[901]: WIRELESS.JS - INFO: InterfaceValidator: wlan0 became ready after 1ms Mar 04 20:31:12 volumiow wireless.js[901]: WIRELESS.JS - INFO: ensureInterfaceReady: Interface ready (MAC: 44:6d:57:c4:89:37) Mar 04 20:31:12 volumiow sudo[1135]: volumio : unable to resolve host volumiow: System error Mar 04 20:31:12 volumiow sudo[1135]: volumio : PWD=/ ; USER=root ; COMMAND=/sbin/iw reg get Mar 04 20:31:12 volumiow sudo[1135]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:12 volumiow sudo[1135]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:12 volumiow wireless.js[901]: sudo: unable to resolve host volumiow: System error Mar 04 20:31:12 volumiow sudo[1143]: volumio : unable to resolve host volumiow: System error Mar 04 20:31:12 volumiow sudo[1143]: volumio : PWD=/ ; USER=root ; COMMAND=/sbin/iw wlan0 scan Mar 04 20:31:12 volumiow sudo[1143]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:12 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:12 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:12 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:12 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:12 volumiow avahi-daemon[892]: Server startup complete. Host name is volumiow.local. Local service cookie is 2585079866. Mar 04 20:31:12 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:12 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:12 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:12 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow ntpd[1041]: DNS: dns_probe: 0.debian.pool.ntp.org, cast_flags:8, flags:101 Mar 04 20:31:13 volumiow ntpd[1041]: DNS: dns_check: processing 0.debian.pool.ntp.org, 8, 101 Mar 04 20:31:13 volumiow ntpd[1041]: DNS: dns_check: DNS error: -11, System error Mar 04 20:31:13 volumiow ntpd[1041]: DNS: dns_take_status: 0.debian.pool.ntp.org=>error, 12 Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow dhcpcd[926]: eth0: carrier acquired Mar 04 20:31:13 volumiow dhcpcd[806]: eth0: carrier acquired Mar 04 20:31:13 volumiow sh[790]: eth0: carrier acquired Mar 04 20:31:13 volumiow kernel: r8169 0000:01:00.0 eth0: Link is Up - 1Gbps/Full - flow control off Mar 04 20:31:13 volumiow sh[790]: eth0: IAID 4c:68:5e:ad Mar 04 20:31:13 volumiow dhcpcd[806]: eth0: IAID 4c:68:5e:ad Mar 04 20:31:13 volumiow dhcpcd[926]: eth0: IAID 4c:68:5e:ad Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow dhcpcd[926]: eth0: soliciting a DHCP lease Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow avahi-daemon[892]: Service "Volumio_W" (/services/volumio.service) successfully established. Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:13 volumiow dhcpcd[806]: eth0: soliciting an IPv6 router Mar 04 20:31:13 volumiow sh[790]: eth0: soliciting an IPv6 router Mar 04 20:31:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow dhcpcd[926]: eth0: soliciting an IPv6 router Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow ntpd[1041]: DNS: dns_probe: 1.debian.pool.ntp.org, cast_flags:8, flags:101 Mar 04 20:31:14 volumiow ntpd[1041]: DNS: dns_check: processing 1.debian.pool.ntp.org, 8, 101 Mar 04 20:31:14 volumiow ntpd[1041]: DNS: dns_check: DNS error: -11, System error Mar 04 20:31:14 volumiow ntpd[1041]: DNS: dns_take_status: 1.debian.pool.ntp.org=>error, 12 Mar 04 20:31:14 volumiow ifplugd(eth0)[1062]: Link beat detected. Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow ifplugd(eth0)[1062]: Executing '/etc/ifplugd/ifplugd.action eth0 up'. Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow ifplugd(eth0)[1062]: client: ifup: waiting for lock on /run/network/ifstate.eth0 Mar 04 20:31:14 volumiow dhcpcd[806]: eth0: soliciting a DHCP lease Mar 04 20:31:14 volumiow sh[790]: eth0: soliciting a DHCP lease Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow ntpd[1041]: DNS: dns_probe: 2.debian.pool.ntp.org, cast_flags:8, flags:101 Mar 04 20:31:15 volumiow ntpd[1041]: DNS: dns_check: processing 2.debian.pool.ntp.org, 8, 101 Mar 04 20:31:15 volumiow ntpd[1041]: DNS: dns_check: DNS error: -11, System error Mar 04 20:31:15 volumiow ntpd[1041]: DNS: dns_take_status: 2.debian.pool.ntp.org=>error, 12 Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow systemd[1]: systemd-rfkill.service: Deactivated successfully. Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow ntpd[1041]: DNS: dns_probe: 3.debian.pool.ntp.org, cast_flags:8, flags:101 Mar 04 20:31:16 volumiow ntpd[1041]: DNS: dns_check: processing 3.debian.pool.ntp.org, 8, 101 Mar 04 20:31:16 volumiow ntpd[1041]: DNS: dns_check: DNS error: -11, System error Mar 04 20:31:16 volumiow ntpd[1041]: DNS: dns_take_status: 3.debian.pool.ntp.org=>error, 12 Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow sh[790]: eth0: offered 192.168.1.43 from 192.168.1.1 Mar 04 20:31:16 volumiow dhcpcd[806]: eth0: offered 192.168.1.43 from 192.168.1.1 Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow sudo[1143]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:16 volumiow wireless.js[901]: sudo: unable to resolve host volumiow: System error Mar 04 20:31:16 volumiow wireless.js[901]: WIRELESS.JS - INFO: SETTING APPROPRIATE REG DOMAIN: IT Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow sudo[1182]: volumio : unable to resolve host volumiow: System error Mar 04 20:31:16 volumiow sudo[1182]: volumio : PWD=/ ; USER=root ; COMMAND=/sbin/iw reg set IT Mar 04 20:31:16 volumiow sudo[1182]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:16 volumiow sudo[1182]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:16 volumiow wireless.js[901]: sudo: unable to resolve host volumiow: System error Mar 04 20:31:16 volumiow wireless.js[901]: WIRELESS.JS - INFO: SUCCESSFULLY SET NEW REGDOMAIN: IT Mar 04 20:31:16 volumiow wireless.js[901]: WIRELESS.JS - INFO: refreshEthernetState: Corrected ethernet state: connected Mar 04 20:31:16 volumiow wireless.js[901]: WIRELESS.JS - INFO: netconfigured file not found, starting hotspot Mar 04 20:31:16 volumiow wireless.js[901]: WIRELESS.JS - INFO: Single Network Mode: Ethernet active, maintaining WiFi scan capability Mar 04 20:31:16 volumiow wireless.js[901]: WIRELESS.JS - INFO: SNM: Maintaining wlan0 UP without IP (scan mode) Mar 04 20:31:16 volumiow wireless.js[901]: WIRELESS.JS - INFO: SNM: Users can configure WiFi via WebUI while ethernet is active Mar 04 20:31:16 volumiow sudo[1191]: root : unable to resolve host volumiow: System error Mar 04 20:31:16 volumiow sudo[1191]: root : PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 up Mar 04 20:31:16 volumiow sudo[1191]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Mar 04 20:31:16 volumiow sudo[1191]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:16 volumiow sudo[1194]: root : unable to resolve host volumiow: System error Mar 04 20:31:16 volumiow sudo[1194]: root : PWD=/ ; USER=root ; COMMAND=/sbin/ip addr flush dev wlan0 Mar 04 20:31:16 volumiow sudo[1194]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Mar 04 20:31:16 volumiow sudo[1194]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:16 volumiow wpa_supplicant[1197]: Successfully initialized wpa_supplicant Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow dhcpcd[806]: eth0: probing address 192.168.1.43/24 Mar 04 20:31:16 volumiow sh[790]: eth0: probing address 192.168.1.43/24 Mar 04 20:31:16 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:16 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:16 volumiow wireless.js[901]: WIRELESS.JS - INFO: SNM: wlan0 is UP without IP, scan capable Mar 04 20:31:16 volumiow wireless.js[901]: Failed to connect to non-global ctrl_ifname: wlan0 error: No such file or directory Mar 04 20:31:16 volumiow wireless.js[901]: WIRELESS.JS - INFO: Notified systemd about wireless ready Mar 04 20:31:16 volumiow iwconfig[1215]: Error for wireless request "Set Power Management" (8B2C) : Mar 04 20:31:16 volumiow iwconfig[1215]: SET failed on device wlan0 ; Operation not supported. Mar 04 20:31:16 volumiow systemd[1]: Started wireless.service - Wireless Services. Mar 04 20:31:16 volumiow systemd[1]: Started volumio.service - Volumio Backend Module. Mar 04 20:31:16 volumiow systemd[1]: Started screenshot.service - Process screenshots triggered by PrtSc-button. Mar 04 20:31:16 volumiow systemd[1]: Started soundcard-init.service - Intel SST and HDA soundcard init service. Mar 04 20:31:16 volumiow systemd[1]: Started volumio-kiosk.service - Start Volumio Kiosk. Mar 04 20:31:16 volumiow systemd[1]: Started volumio_cpu_tweak.service - Volumio Cpu Tweaker. Mar 04 20:31:16 volumiow startx[1253]: hostname: System error Mar 04 20:31:16 volumiow volumio-cpu-tweak[1231]: Setting RT Priority for mpd Mar 04 20:31:16 volumiow volumio-cpu-tweak[1255]: pid 35's current scheduling policy: SCHED_OTHER Mar 04 20:31:16 volumiow volumio-cpu-tweak[1255]: pid 35's current scheduling priority: 0 Mar 04 20:31:16 volumiow volumio-cpu-tweak[1231]: Setting MPD Affinity Mar 04 20:31:16 volumiow volumio-cpu-tweak[1260]: pid 3's current affinity mask: f Mar 04 20:31:16 volumiow volumio-cpu-tweak[1231]: VOLUMIO CPU TWEAK: Setting CPU Governor: performance Mar 04 20:31:16 volumiow systemd[1]: volumio_cpu_tweak.service: Deactivated successfully. Mar 04 20:31:16 volumiow startx[1286]: xauth: (stdin):1: bad display name "volumiow:0" in "add" command Mar 04 20:31:16 volumiow soundcard-init.sh[1300]: Card 0 Chip Realtek Generic Name HDA Intel PCH Mar 04 20:31:16 volumiow soundcard-init.sh[1313]: Simple mixer control 'Master',0 Mar 04 20:31:16 volumiow soundcard-init.sh[1313]: Capabilities: pvolume pswitch Mar 04 20:31:16 volumiow soundcard-init.sh[1313]: Playback channels: Front Left - Front Right Mar 04 20:31:16 volumiow soundcard-init.sh[1313]: Limits: Playback 0 - 64 Mar 04 20:31:16 volumiow soundcard-init.sh[1313]: Mono: Mar 04 20:31:16 volumiow soundcard-init.sh[1313]: Front Left: Playback 48 [75%] [-16.00dB] [on] Mar 04 20:31:16 volumiow soundcard-init.sh[1313]: Front Right: Playback 48 [75%] [-16.00dB] [on] Mar 04 20:31:16 volumiow soundcard-init.sh[1300]: Card 5 Chip USB Mixer Name D50 III Mar 04 20:31:16 volumiow systemd[1]: soundcard-init.service: Deactivated successfully. Mar 04 20:31:16 volumiow startx[1292]: X.Org X Server 1.21.1.7 Mar 04 20:31:16 volumiow startx[1292]: X Protocol Version 11, Revision 0 Mar 04 20:31:16 volumiow startx[1292]: Current Operating System: Linux volumiow 6.12.57-volumio #2 SMP PREEMPT_DYNAMIC Thu Nov 13 17:08:37 CET 2025 x86_64 Mar 04 20:31:16 volumiow startx[1292]: Kernel command line: BOOT_IMAGE=vmlinuz initramfs.clear splash plymouth.ignore-serial-consoles quiet loglevel=0 bootdelay=5 biosdevname=0 imgpart=UUID=b0a058e9-0951-4405-9f54-2004a4130548 bootpart=UUID=5F54-6886 datapart=UUID=a75a63ef-7a01-4f5e-b572-6ddd34d5e25f hwdevice=x86 uuidconfig=syslinux.cfg,efi/BOOT/grub.cfg imgfile=/volumio_current.sqsh logo.nologo vt.global_cursor_default=0 acpi_backlight=native net.ifnames=0 use_kmsg=no initrd=volumio.initrd Mar 04 20:31:16 volumiow startx[1292]: xorg-server 2:21.1.7-3+deb12u11 (https://www.debian.org/support) Mar 04 20:31:16 volumiow startx[1292]: Current version of pixman: 0.42.2 Mar 04 20:31:16 volumiow startx[1292]: Before reporting problems, check http://wiki.x.org Mar 04 20:31:16 volumiow startx[1292]: to make sure that you have the latest version. Mar 04 20:31:16 volumiow startx[1292]: Markers: (--) probed, (**) from config file, (==) default setting, Mar 04 20:31:16 volumiow startx[1292]: (++) from command line, (!!) notice, (II) informational, Mar 04 20:31:16 volumiow startx[1292]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown. Mar 04 20:31:16 volumiow startx[1292]: (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 4 20:31:16 2026 Mar 04 20:31:16 volumiow startx[1292]: (==) Using system config directory "/usr/share/X11/xorg.conf.d" Mar 04 20:31:16 volumiow volumio-remote-updater[899]: [2026-03-04 20:31:16] [info] asio async_connect error: asio.system:111 (Connection refused) Mar 04 20:31:16 volumiow volumio-remote-updater[899]: [2026-03-04 20:31:16] [info] Error getting remote endpoint: asio.system:107 (Transport endpoint is not connected) Mar 04 20:31:16 volumiow volumio-remote-updater[899]: [2026-03-04 20:31:16] [error] handle_connect error: Connection refused Mar 04 20:31:17 volumiow wireless.js[901]: WIRELESS.JS - INFO: === SNM TRANSITION === Mar 04 20:31:17 volumiow wireless.js[901]: WIRELESS.JS - INFO: Previous ethernet state: disconnected Mar 04 20:31:17 volumiow wireless.js[901]: WIRELESS.JS - INFO: New ethernet state: connected Mar 04 20:31:17 volumiow wireless.js[901]: WIRELESS.JS - INFO: Single Network Mode: enabled Mar 04 20:31:17 volumiow wireless.js[901]: WIRELESS.JS - INFO: First start: no Mar 04 20:31:17 volumiow wireless.js[901]: WIRELESS.JS - INFO: Action: Switch to ethernet (WiFi scan mode) Mar 04 20:31:17 volumiow wireless.js[901]: WIRELESS.JS - INFO: === END TRANSITION === Mar 04 20:31:17 volumiow wireless.js[901]: WIRELESS.JS - INFO: SNM: Ethernet connected, switching to ethernet (WiFi scan mode) Mar 04 20:31:17 volumiow sudo[1338]: root : unable to resolve host volumiow: System error Mar 04 20:31:17 volumiow sudo[1338]: root : PWD=/ ; USER=root ; COMMAND=/sbin/dhcpcd -k wlan0 Mar 04 20:31:17 volumiow sudo[1338]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Mar 04 20:31:17 volumiow dhcpcd[1339]: dhcpcd not running Mar 04 20:31:17 volumiow sudo[1338]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:17 volumiow wireless.js[901]: sudo: unable to resolve host volumiow: System error Mar 04 20:31:17 volumiow wireless.js[901]: dhcpcd not running Mar 04 20:31:17 volumiow wireless.js[901]: WIRELESS.JS - INFO: Wireless.js initializing wireless flow Mar 04 20:31:17 volumiow volumio[1216]: info: ------------------------------------------- Mar 04 20:31:17 volumiow volumio[1216]: info: ----- Volumio3 ---- Mar 04 20:31:17 volumiow volumio[1216]: info: ------------------------------------------- Mar 04 20:31:17 volumiow volumio[1216]: info: ----- System startup ---- Mar 04 20:31:17 volumiow volumio[1216]: info: ------------------------------------------- Mar 04 20:31:17 volumiow wpa_supplicant[1199]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all Mar 04 20:31:17 volumiow sudo[1347]: root : unable to resolve host volumiow: System error Mar 04 20:31:17 volumiow sudo[1347]: root : PWD=/ ; USER=root ; COMMAND=/sbin/ip addr flush dev wlan0 Mar 04 20:31:17 volumiow sudo[1347]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Mar 04 20:31:17 volumiow sudo[1347]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:17 volumiow sudo[1349]: root : unable to resolve host volumiow: System error Mar 04 20:31:17 volumiow sudo[1349]: root : PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 down Mar 04 20:31:17 volumiow sudo[1349]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Mar 04 20:31:17 volumiow sudo[1349]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:17 volumiow wireless.js[901]: WIRELESS.JS - INFO: Cleaning previous... Mar 04 20:31:17 volumiow wpa_supplicant[1199]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all Mar 04 20:31:17 volumiow wpa_supplicant[1199]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0 Mar 04 20:31:17 volumiow wpa_supplicant[1199]: wlan0: CTRL-EVENT-TERMINATING Mar 04 20:31:17 volumiow sudo[1356]: root : unable to resolve host volumiow: System error Mar 04 20:31:17 volumiow sudo[1356]: root : PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 up Mar 04 20:31:17 volumiow sudo[1356]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Mar 04 20:31:17 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:17 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:17 volumiow sudo[1356]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:17 volumiow wireless.js[901]: WIRELESS.JS - INFO: InterfaceValidator: READY - wlan0 is ready for operations Mar 04 20:31:17 volumiow wireless.js[901]: WIRELESS.JS - INFO: InterfaceValidator: wlan0 became ready after 1ms Mar 04 20:31:17 volumiow wireless.js[901]: WIRELESS.JS - INFO: ensureInterfaceReady: Interface ready (MAC: 44:6d:57:c4:89:37) Mar 04 20:31:17 volumiow sudo[1366]: volumio : unable to resolve host volumiow: System error Mar 04 20:31:17 volumiow sudo[1366]: volumio : PWD=/ ; USER=root ; COMMAND=/sbin/iw reg get Mar 04 20:31:17 volumiow sudo[1366]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:17 volumiow sudo[1366]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:17 volumiow wireless.js[901]: sudo: unable to resolve host volumiow: System error Mar 04 20:31:17 volumiow sudo[1374]: volumio : unable to resolve host volumiow: System error Mar 04 20:31:17 volumiow sudo[1374]: volumio : PWD=/ ; USER=root ; COMMAND=/sbin/iw wlan0 scan Mar 04 20:31:17 volumiow sudo[1374]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:17 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:17 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:17 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:17 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:17 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:17 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:17 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:17 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:17 volumiow bash[1023]: setdatetime-helper: all HTTPS Date fallbacks failed Mar 04 20:31:17 volumiow systemd[1]: setdatetime-helper.service: Deactivated successfully. Mar 04 20:31:17 volumiow systemd[1]: Finished setdatetime-helper.service - Time Synchronization Helper Service. Mar 04 20:31:17 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:17 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:17 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:17 volumiow volumio[1216]: info: MYVOLUMIO Environment detected Mar 04 20:31:17 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:17 volumiow volumio[1216]: info: Plugin folders cleanup Mar 04 20:31:17 volumiow volumio[1216]: info: Scanning into folder /volumio/app/plugins/ Mar 04 20:31:17 volumiow volumio[1216]: info: Scanning category audio_interface Mar 04 20:31:17 volumiow volumio[1216]: info: Scanning category miscellanea Mar 04 20:31:17 volumiow volumio[1216]: info: Scanning category music_service Mar 04 20:31:17 volumiow volumio[1216]: info: Scanning category plugins.json Mar 04 20:31:17 volumiow volumio[1216]: info: Scanning category system_controller Mar 04 20:31:17 volumiow volumio[1216]: info: Scanning category user_interface Mar 04 20:31:17 volumiow volumio[1216]: info: Scanning into folder /data/plugins/ Mar 04 20:31:17 volumiow volumio[1216]: info: Plugin folders cleanup completed Mar 04 20:31:17 volumiow volumio[1216]: info: ------------------------------------------- Mar 04 20:31:17 volumiow volumio[1216]: info: ----- Core plugins startup ---- Mar 04 20:31:17 volumiow volumio[1216]: info: ------------------------------------------- Mar 04 20:31:17 volumiow volumio[1216]: info: Loading plugins from folder /volumio/app/plugins/ Mar 04 20:31:17 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:17 volumiow volumio[1216]: info: Adding plugin upnp to MyMusic Plugins Mar 04 20:31:17 volumiow volumio[1216]: info: Adding plugin airplay_emulation to MyMusic Plugins Mar 04 20:31:17 volumiow volumio[1216]: info: Adding plugin upnp_browser to MyMusic Plugins Mar 04 20:31:17 volumiow volumio[1216]: info: Loading plugins from folder /data/plugins/ Mar 04 20:31:17 volumiow volumio[1216]: info: Loading plugin "system"... Mar 04 20:31:17 volumiow volumio[1216]: info: Loading plugin "appearance"... Mar 04 20:31:17 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:17 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:17 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow volumio[1216]: info: Loading plugin "network"... Mar 04 20:31:18 volumiow volumio[1216]: info: Refreshing Cached IP Addresses Mar 04 20:31:18 volumiow sudo[1470]: volumio : unable to resolve host volumiow: System error Mar 04 20:31:18 volumiow sudo[1473]: volumio : unable to resolve host volumiow: System error Mar 04 20:31:18 volumiow volumio[1216]: info: Loading plugin "services"... Mar 04 20:31:18 volumiow sudo[1470]: volumio : PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig eth0 Mar 04 20:31:18 volumiow volumio[1216]: info: Loading plugin "volumio5onboarding"... Mar 04 20:31:18 volumiow sudo[1473]: volumio : PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 Mar 04 20:31:18 volumiow sudo[1473]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:18 volumiow sudo[1470]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:18 volumiow sudo[1481]: volumio : unable to resolve host volumiow: System error Mar 04 20:31:18 volumiow sudo[1473]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:18 volumiow sudo[1481]: volumio : PWD=/ ; USER=root ; COMMAND=/sbin/iwlist wlan0 scan Mar 04 20:31:18 volumiow sudo[1481]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:18 volumiow sudo[1470]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:18 volumiow volumio[1216]: info: Loading plugin "alsa_controller"... Mar 04 20:31:18 volumiow sudo[1481]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getSystemVersion Mar 04 20:31:18 volumiow volumio[1216]: info: Loading plugin "wizard"... Mar 04 20:31:18 volumiow volumio[1216]: info: Loading plugin "networkfs"... Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow volumio[1216]: info: Starting Udev Watcher for removable devices Mar 04 20:31:18 volumiow volumio[1216]: info: Mounting Device 01DA612410BFC090 Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow sudo[1517]: volumio : unable to resolve host volumiow: System error Mar 04 20:31:18 volumiow sudo[1517]: volumio : PWD=/ ; USER=root ; COMMAND=/bin/mount /dev/sda1 /mnt/USB/01DA612410BFC090 -o noatime,dmask=0000,fmask=0000,iocharset=utf8 Mar 04 20:31:18 volumiow sudo[1517]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:18 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:18 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow ntfs-3g[1520]: Version 2022.10.3 integrated FUSE 28 Mar 04 20:31:19 volumiow ntfs-3g[1520]: Mounted /dev/sda1 (Read-Write, label "", NTFS 3.1) Mar 04 20:31:19 volumiow ntfs-3g[1520]: Cmdline options: rw,noatime,dmask=0000,fmask=0000,iocharset=utf8 Mar 04 20:31:19 volumiow ntfs-3g[1520]: Mount options: iocharset=utf8,allow_other,nonempty,noatime,rw,default_permissions,fsname=/dev/sda1,blkdev,blksize=4096 Mar 04 20:31:19 volumiow ntfs-3g[1520]: Global ownership and permissions enforced, configuration type 7 Mar 04 20:31:19 volumiow sudo[1517]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:19 volumiow volumio[1216]: sudo: unable to resolve host volumiow: System error Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow volumio[1216]: info: Ignoring mount for partition: boot Mar 04 20:31:19 volumiow volumio[1216]: info: Ignoring mount for partition: volumio Mar 04 20:31:19 volumiow volumio[1216]: info: Ignoring mount for partition: volumio_data Mar 04 20:31:19 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , registerCallback Mar 04 20:31:19 volumiow volumio[1216]: info: Loading plugin "volumio_command_line_client"... Mar 04 20:31:19 volumiow volumio[1216]: info: Loading plugin "upnp"... Mar 04 20:31:19 volumiow volumio[1216]: info: [1772652679104] Starting Upmpd Daemon Mar 04 20:31:19 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , registerCallback Mar 04 20:31:19 volumiow volumio[1216]: info: Loading plugin "my_music"... Mar 04 20:31:19 volumiow volumio[1216]: info: Loading plugin "mpd"... Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow volumio[1216]: info: Loading plugin "upnp_browser"... Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow dbus-daemon[893]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.7' (uid=0 pid=1432 comm="/usr/lib/chromium/chromium --show-component-extens") Mar 04 20:31:19 volumiow systemd[1]: Starting bluetooth.service - Bluetooth service... Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow volumio[1216]: info: Starting UPNP Browser Mar 04 20:31:19 volumiow volumio[1216]: info: Loading plugin "alarm-clock"... Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: Bluetooth: Core ver 2.22 Mar 04 20:31:19 volumiow kernel: NET: Registered PF_BLUETOOTH protocol family Mar 04 20:31:19 volumiow kernel: Bluetooth: HCI device and connection manager initialized Mar 04 20:31:19 volumiow kernel: Bluetooth: HCI socket layer initialized Mar 04 20:31:19 volumiow kernel: Bluetooth: L2CAP socket layer initialized Mar 04 20:31:19 volumiow kernel: Bluetooth: SCO socket layer initialized Mar 04 20:31:19 volumiow bluetoothd[1543]: Bluetooth daemon 5.83 Mar 04 20:31:19 volumiow dbus-daemon[893]: [system] Successfully activated service 'org.bluez' Mar 04 20:31:19 volumiow systemd[1]: Started bluetooth.service - Bluetooth service. Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow bluetoothd[1543]: Starting SDP server Mar 04 20:31:19 volumiow bluetoothd[1543]: Excluding (cli) sap Mar 04 20:31:19 volumiow bluetoothd[1543]: Excluding (cli) midi Mar 04 20:31:19 volumiow bluetoothd[1543]: Excluding (cli) battery Mar 04 20:31:19 volumiow kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Mar 04 20:31:19 volumiow kernel: Bluetooth: BNEP filters: protocol multicast Mar 04 20:31:19 volumiow kernel: Bluetooth: BNEP socket layer initialized Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow dbus-daemon[893]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.8' (uid=0 pid=1543 comm="/usr/libexec/bluetooth/bluetoothd --noplugin=sap,b") Mar 04 20:31:19 volumiow bluetoothd[1543]: Bluetooth management interface 1.23 initialized Mar 04 20:31:19 volumiow volumio[1216]: info: Loading plugin "airplay_emulation"... Mar 04 20:31:19 volumiow volumio[1216]: info: Starting Shairport Sync Mar 04 20:31:19 volumiow volumio[1216]: info: Loading plugin "last_100"... Mar 04 20:31:19 volumiow volumio[1216]: info: Loading plugin "webradio"... Mar 04 20:31:19 volumiow systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Mar 04 20:31:19 volumiow volumio[1216]: info: Loading plugin "i2s_dacs"... Mar 04 20:31:19 volumiow dbus-daemon[893]: [system] Successfully activated service 'org.freedesktop.hostname1' Mar 04 20:31:19 volumiow volumio[1216]: info: I2S DAC not set, start Auto-detection Mar 04 20:31:19 volumiow systemd[1]: Started systemd-hostnamed.service - Hostname Service. Mar 04 20:31:19 volumiow volumio[1216]: info: Loading plugin "volumiodiscovery"... Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:19 volumiow node[1216]: *** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi. Mar 04 20:31:19 volumiow volumio[1216]: *** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi. Mar 04 20:31:19 volumiow volumio[1216]: *** WARNING *** Please fix your application to use the native API of Avahi! Mar 04 20:31:19 volumiow volumio[1216]: *** WARNING *** For more information see Mar 04 20:31:19 volumiow volumio[1216]: *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi. Mar 04 20:31:19 volumiow volumio[1216]: *** WARNING *** Please fix your application to use the native API of Avahi! Mar 04 20:31:19 volumiow volumio[1216]: *** WARNING *** For more information see Mar 04 20:31:19 volumiow node[1216]: *** WARNING *** Please fix your application to use the native API of Avahi! Mar 04 20:31:19 volumiow node[1216]: *** WARNING *** For more information see Mar 04 20:31:19 volumiow node[1216]: *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi. Mar 04 20:31:19 volumiow node[1216]: *** WARNING *** Please fix your application to use the native API of Avahi! Mar 04 20:31:19 volumiow node[1216]: *** WARNING *** For more information see Mar 04 20:31:19 volumiow volumio[1216]: info: Applying required configuration parameters for plugin volumiodiscovery Mar 04 20:31:19 volumiow volumio[1216]: info: Discovery: Started advertising with name: Volumio_W Mar 04 20:31:19 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , registerCallback Mar 04 20:31:19 volumiow volumio[1216]: info: Loading plugin "outputs"... Mar 04 20:31:19 volumiow volumio[1216]: info: Loading plugin "albumart"... Mar 04 20:31:19 volumiow volumio[1216]: info: Plugin example_plugin is not enabled Mar 04 20:31:19 volumiow volumio[1216]: info: Loading plugin "inputs"... Mar 04 20:31:19 volumiow volumio[1216]: info: Loading plugin "updater_comm"... Mar 04 20:31:20 volumiow volumio[1616]: Forking 3 albumart workers Mar 04 20:31:20 volumiow volumio[1216]: info: Plugin mpdemulation is not enabled Mar 04 20:31:20 volumiow volumio[1216]: info: Loading plugin "rest_api"... Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow volumio[1216]: info: Loading plugin "websocket"... Mar 04 20:31:20 volumiow volumio[1216]: info: Starting Socket.io Server version 1.7.4 Mar 04 20:31:20 volumiow volumio[1216]: info: Loading i18n strings for locale it Mar 04 20:31:20 volumiow volumio[1216]: Updating browse sources language Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow volumio[1633]: Starting albumart workers Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow volumio[1635]: Starting albumart workers Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow volumio[1636]: Starting albumart workers Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: mpd , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::initPlayerControls Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: mpd , getConfigParam Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow volumio[1216]: Express server listening on port 3000 Mar 04 20:31:20 volumiow volumio[1216]: [Metrics] WebUI: 2s 985.43ms Mar 04 20:31:20 volumiow volumio[1216]: info: Setting Device type: x86 Mar 04 20:31:20 volumiow volumio[1216]: info: CoreStateMachine::resetVolumioState Mar 04 20:31:20 volumiow volumio[1216]: info: CoreStateMachine::getcurrentVolume Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::volumioRetrievevolume Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: error: Cannot read config.txt file: Error: ENOENT: no such file or directory, open '/boot/config.txt' Mar 04 20:31:20 volumiow volumio[1216]: info: Completed loading Core Plugins Mar 04 20:31:20 volumiow volumio[1216]: info: Preparing to generate the ALSA configuration file Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow volumio[1216]: info: Volumio Network Manager: Network status updated: 0 Mar 04 20:31:20 volumiow volumio[1216]: error: An error occurred while scanning: Error: Command failed: sudo /sbin/iwlist wlan0 scan Mar 04 20:31:20 volumiow volumio[1216]: sudo: unable to resolve host volumiow: System error Mar 04 20:31:20 volumiow volumio[1216]: wlan0 Interface doesn't support scanning : Device or resource busy Mar 04 20:31:20 volumiow volumio[1216]: info: Cannot use regular scanning, forcing with ap-force Mar 04 20:31:20 volumiow sudo[1698]: volumio : unable to resolve host volumiow: System error Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow sudo[1698]: volumio : PWD=/ ; USER=root ; COMMAND=/sbin/iw dev wlan0 scan ap-force Mar 04 20:31:20 volumiow sudo[1698]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:20 volumiow sudo[1698]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:20 volumiow volumio[1216]: sudo: unable to resolve host volumiow: System error Mar 04 20:31:20 volumiow volumio[1216]: command failed: Device or resource busy (-16) Mar 04 20:31:20 volumiow volumio[1216]: error: Cannot use fallback scanning method: Error: Command failed: /usr/bin/sudo /sbin/iw dev wlan0 scan ap-force Mar 04 20:31:20 volumiow volumio[1216]: sudo: unable to resolve host volumiow: System error Mar 04 20:31:20 volumiow volumio[1216]: command failed: Device or resource busy (-16) Mar 04 20:31:20 volumiow volumio[1216]: info: Cannot read proc/cpuinfo: Error: Command failed: cat /proc/cpuinfo | grep Revision Mar 04 20:31:20 volumiow dhcpcd[926]: eth0: offered 192.168.1.43 from 192.168.1.1 Mar 04 20:31:20 volumiow volumio[1216]: info: Reloading queue from file Mar 04 20:31:20 volumiow volumio[1216]: info: Asound.conf file unchanged, so no further update is needed Mar 04 20:31:20 volumiow volumio[1216]: info: Output device has changed, restarting MPD Mar 04 20:31:20 volumiow volumio[1216]: info: Output device has changed, restarting Shairport Sync Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Mar 04 20:31:20 volumiow sudo[1733]: volumio : unable to resolve host volumiow: System error Mar 04 20:31:20 volumiow sudo[1731]: volumio : unable to resolve host volumiow: System error Mar 04 20:31:20 volumiow sudo[1733]: volumio : PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart mpd.service Mar 04 20:31:20 volumiow sudo[1733]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:20 volumiow sudo[1731]: volumio : PWD=/ ; USER=root ; COMMAND=/bin/chmod 777 /etc/mpd.conf Mar 04 20:31:20 volumiow sudo[1731]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:20 volumiow sudo[1731]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:20 volumiow volumio[1216]: info: Could not detect Primo: Error: Command failed: aplay -l | grep es90x8q2m-dac-dai-0 Mar 04 20:31:20 volumiow volumio[1216]: info: ___________ START PLUGINS ___________ Mar 04 20:31:20 volumiow volumio[1216]: info: ControllerMpd::onStart: Initializing MPD Mar 04 20:31:20 volumiow volumio[1216]: info: Creating MPD Configuration file Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: mpd , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::volumioAddToBrowseSources[object Object] Mar 04 20:31:20 volumiow volumio[1216]: info: [1772652680549] CoreMusicLibrary::Adding element Server multimediali Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources Mar 04 20:31:20 volumiow sudo[1743]: volumio : unable to resolve host volumiow: System error Mar 04 20:31:20 volumiow sudo[1743]: volumio : PWD=/ ; USER=root ; COMMAND=/bin/chmod 777 /etc/mpd.conf Mar 04 20:31:20 volumiow sudo[1743]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:20 volumiow volumio[1216]: info: UPNP Browser: Client initialized successfully Mar 04 20:31:20 volumiow sudo[1743]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Mar 04 20:31:20 volumiow sudo[1745]: volumio : unable to resolve host volumiow: System error Mar 04 20:31:20 volumiow sudo[1741]: volumio : unable to resolve host volumiow: System error Mar 04 20:31:20 volumiow sudo[1745]: volumio : PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart mpd.service Mar 04 20:31:20 volumiow sudo[1745]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow sudo[1741]: volumio : PWD=/ ; USER=root ; COMMAND=/bin/systemctl start volumio5-onboarding.service Mar 04 20:31:20 volumiow sudo[1741]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:20 volumiow systemd[1]: Listening on mpd.socket - Music Player Daemon Socket. Mar 04 20:31:20 volumiow systemd[1]: Starting mpd.service - Music Player Daemon... Mar 04 20:31:20 volumiow volumio[1216]: info: Could not detect Primo: Error: Command failed: aplay -l | grep es90x8q2m-dac-dai-0 Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Mar 04 20:31:20 volumiow systemd[1]: Started volumio5-onboarding.service - Volumio5 Onboarding Server. Mar 04 20:31:20 volumiow systemd[1]: mpd.service: Deactivated successfully. Mar 04 20:31:20 volumiow systemd[1]: Stopped mpd.service - Music Player Daemon. Mar 04 20:31:20 volumiow sudo[1741]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:20 volumiow systemd[1]: mpd.socket: Deactivated successfully. Mar 04 20:31:20 volumiow systemd[1]: Closed mpd.socket - Music Player Daemon Socket. Mar 04 20:31:20 volumiow systemd[1]: Stopping mpd.socket - Music Player Daemon Socket... Mar 04 20:31:20 volumiow systemd[1]: Listening on mpd.socket - Music Player Daemon Socket. Mar 04 20:31:20 volumiow volumio[1216]: info: Could not detect Primo: Error: Command failed: aplay -l | grep es90x8q2m-dac-dai-0 Mar 04 20:31:20 volumiow systemd[1]: Starting mpd.service - Music Player Daemon... Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::volumioAddToBrowseSources[object Object] Mar 04 20:31:20 volumiow volumio[1216]: info: [1772652680593] CoreMusicLibrary::Adding element Last_100 Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::volumioAddToBrowseSources[object Object] Mar 04 20:31:20 volumiow volumio[1216]: info: [1772652680598] CoreMusicLibrary::Adding element Webradio Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getSystemVersion Mar 04 20:31:20 volumiow volumio[1216]: info: Initializing BBC Radios Mar 04 20:31:20 volumiow sudo[1761]: root : unable to resolve host volumiow: System error Mar 04 20:31:20 volumiow sudo[1761]: sudo: unable to resolve host volumiow: System error Mar 04 20:31:20 volumiow dhcpcd[926]: eth0: probing address 192.168.1.43/24 Mar 04 20:31:20 volumiow sudo[1761]: root : PWD=/ ; USER=root ; COMMAND=/bin/chown mpd:audio /var/log/mpd.log Mar 04 20:31:20 volumiow sudo[1761]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow sudo[1774]: /bin/chown: cannot access '/var/log/mpd.log': No such file or directory Mar 04 20:31:20 volumiow sudo[1761]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getSystemVersion Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: Volumio Calling Home Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow volumio[1216]: info: CoreStateMachine::setRepeat null single undefined Mar 04 20:31:20 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:31:20 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:31:20 volumiow volumio[1216]: info: CoreStateMachine::setRandom null Mar 04 20:31:20 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:31:20 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:31:20 volumiow volumio[1216]: info: VolumeController:: Volume=100 Mute =false Mar 04 20:31:20 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:31:20 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:31:20 volumiow volumio[1216]: info: CoreStateMachine::updateTrackBlock Mar 04 20:31:20 volumiow volumio[1216]: info: CorePlayQueue::getTrackBlock Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::volumioRetrievevolume Mar 04 20:31:20 volumiow volumio[1216]: Unhandled rejection Error: No sockets available, cannot start. Mar 04 20:31:20 volumiow volumio[1216]: at SSDP._createSockets (/volumio/node_modules/node-ssdp/lib/index.js:186:11) Mar 04 20:31:20 volumiow volumio[1216]: at SSDP._start (/volumio/node_modules/node-ssdp/lib/index.js:229:10) Mar 04 20:31:20 volumiow volumio[1216]: at /volumio/node_modules/node-ssdp/lib/client.js:60:10 Mar 04 20:31:20 volumiow volumio[1216]: at Promise._execute (/volumio/node_modules/bluebird/js/release/debuggability.js:384:9) Mar 04 20:31:20 volumiow volumio[1216]: at Promise._resolveFromExecutor (/volumio/node_modules/bluebird/js/release/promise.js:518:18) Mar 04 20:31:20 volumiow volumio[1216]: at new Promise (/volumio/node_modules/bluebird/js/release/promise.js:103:10) Mar 04 20:31:20 volumiow volumio[1216]: at SsdpClient.start (/volumio/node_modules/node-ssdp/lib/client.js:54:10) Mar 04 20:31:20 volumiow volumio[1216]: at SsdpClient.search (/volumio/node_modules/node-ssdp/lib/client.js:82:17) Mar 04 20:31:20 volumiow volumio[1216]: at ControllerUPNPBrowser.onStart (/volumio/app/plugins/music_service/upnp_browser/index.js:156:14) Mar 04 20:31:20 volumiow volumio[1216]: at PluginManager.startCorePlugin (/volumio/app/pluginmanager.js:398:24) Mar 04 20:31:20 volumiow volumio[1216]: at HashMap. (/volumio/app/pluginmanager.js:496:31) Mar 04 20:31:20 volumiow volumio[1216]: at HashMap.forEach (/volumio/node_modules/hashmap/hashmap.js:171:10) Mar 04 20:31:20 volumiow volumio[1216]: at proto. [as forEach] (/volumio/node_modules/hashmap/hashmap.js:201:7) Mar 04 20:31:20 volumiow volumio[1216]: at PluginManager.startCorePlugins (/volumio/app/pluginmanager.js:495:20) Mar 04 20:31:20 volumiow volumio[1216]: at Promise._successFn (/volumio/app/pluginmanager.js:142:29) Mar 04 20:31:20 volumiow volumio[1216]: at nextTickCallback (/volumio/node_modules/kew/kew.js:47:28) Mar 04 20:31:20 volumiow volumio[1216]: info: MPD Permissions set Mar 04 20:31:20 volumiow volumio[1216]: info: MPD Permissions set Mar 04 20:31:20 volumiow sudo[1374]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow wireless.js[901]: sudo: unable to resolve host volumiow: System error Mar 04 20:31:20 volumiow wireless.js[901]: WIRELESS.JS - INFO: Regdomain already correct: IT Mar 04 20:31:20 volumiow wireless.js[901]: WIRELESS.JS - INFO: netconfigured file not found, starting hotspot Mar 04 20:31:20 volumiow wireless.js[901]: WIRELESS.JS - INFO: Single Network Mode: Ethernet active, maintaining WiFi scan capability Mar 04 20:31:20 volumiow wireless.js[901]: WIRELESS.JS - INFO: SNM: Maintaining wlan0 UP without IP (scan mode) Mar 04 20:31:20 volumiow wireless.js[901]: WIRELESS.JS - INFO: SNM: Users can configure WiFi via WebUI while ethernet is active Mar 04 20:31:20 volumiow volumio[1216]: verbose: New Socket.io Connection to localhost:3000 from 127.0.0.1 UA: node-XMLHttpRequest Engine version: 3 Transport: polling Total Clients: 1 Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getCPUCoresNumber Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getCPUCoresNumber Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Mar 04 20:31:20 volumiow volumio[1216]: info: VolumeController:: Volume=100 Mute =false Mar 04 20:31:20 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:31:20 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:31:20 volumiow volumio[1216]: info: Starting Shairport Sync Mar 04 20:31:20 volumiow volumio[1216]: info: Starting Shairport Sync Mar 04 20:31:20 volumiow volumio[1216]: info: Starting Shairport Sync Mar 04 20:31:20 volumiow sudo[1823]: volumio : unable to resolve host volumiow: System error Mar 04 20:31:20 volumiow sudo[1826]: root : unable to resolve host volumiow: System error Mar 04 20:31:20 volumiow sudo[1826]: root : PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 up Mar 04 20:31:20 volumiow sudo[1826]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Mar 04 20:31:20 volumiow sudo[1827]: volumio : unable to resolve host volumiow: System error Mar 04 20:31:20 volumiow sudo[1826]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:20 volumiow sudo[1827]: volumio : PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart shairport-sync Mar 04 20:31:20 volumiow sudo[1827]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow sudo[1823]: volumio : PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart shairport-sync Mar 04 20:31:20 volumiow sudo[1823]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:20 volumiow sudo[1830]: volumio : unable to resolve host volumiow: System error Mar 04 20:31:20 volumiow sudo[1830]: volumio : PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart shairport-sync Mar 04 20:31:20 volumiow sudo[1830]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:20 volumiow sudo[1834]: root : unable to resolve host volumiow: System error Mar 04 20:31:20 volumiow systemd[1]: Stopping shairport-sync.service - Shairport Sync - AirPlay Audio Receiver... Mar 04 20:31:20 volumiow systemd[1]: shairport-sync.service: Deactivated successfully. Mar 04 20:31:20 volumiow systemd[1]: Stopped shairport-sync.service - Shairport Sync - AirPlay Audio Receiver. Mar 04 20:31:20 volumiow systemd[1]: shairport-sync.service: Consumed 1.721s CPU time. Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:20 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:20 volumiow sudo[1834]: root : PWD=/ ; USER=root ; COMMAND=/sbin/ip addr flush dev wlan0 Mar 04 20:31:20 volumiow sudo[1834]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Mar 04 20:31:20 volumiow sudo[1834]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:20 volumiow wpa_supplicant[1839]: Successfully initialized wpa_supplicant Mar 04 20:31:20 volumiow systemd[1]: Started shairport-sync.service - Shairport Sync - AirPlay Audio Receiver. Mar 04 20:31:20 volumiow sudo[1827]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:20 volumiow sudo[1823]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:20 volumiow sudo[1830]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:20 volumiow volumio[1216]: info: Shairport-Sync Started Mar 04 20:31:20 volumiow volumio[1216]: Error adding Membership: Error: addMembership EINVAL Mar 04 20:31:20 volumiow volumio[1216]: info: Shairport-Sync Started Mar 04 20:31:20 volumiow volumio[1216]: info: Shairport-Sync Started Mar 04 20:31:20 volumiow wireless.js[901]: WIRELESS.JS - INFO: SNM: Transition to scan mode completed in 3408ms Mar 04 20:31:20 volumiow wireless.js[901]: WIRELESS.JS - INFO: SNM: wlan0 is UP without IP, scan capable Mar 04 20:31:20 volumiow volumio[1216]: info: Discovery: adding aa5f76d4-c3fa-4210-ad8e-2666b6f6cb6d Mar 04 20:31:20 volumiow volumio[1216]: info: Discovery: Found device Volumio_W Mar 04 20:31:20 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:20 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:20 volumiow wireless.js[901]: Failed to connect to non-global ctrl_ifname: wlan0 error: No such file or directory Mar 04 20:31:20 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:20 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:20 volumiow wireless.js[901]: WIRELESS.JS - INFO: Notified systemd about wireless ready Mar 04 20:31:20 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:20.991+01:00 level=INFO msg="running volumio5-device-gateway" version=30d1950e+CHANGES buildDate=2026-01-29T13:10:08Z Mar 04 20:31:21 volumiow volumio[1216]: verbose: New Socket.io Connection to localhost:3000 from 127.0.0.1 UA: Go-http-client/1.1 Engine version: 3 Transport: websocket Total Clients: 2 Mar 04 20:31:21 volumiow volumio[1216]: verbose: New Socket.io Connection to localhost:3000 from 127.0.0.1 UA: Go-http-client/1.1 Engine version: 3 Transport: websocket Total Clients: 2 Mar 04 20:31:21 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:21.019+01:00 level=WARN msg="failed to enable Bluetooth adapter" adapter=hci0 error="bluetooth: adapter /org/bluez/hci0 does not exist" Mar 04 20:31:21 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:21.019+01:00 level=WARN msg="failed to enable Bluetooth adapter" adapter=hci1 error="bluetooth: adapter /org/bluez/hci1 does not exist" Mar 04 20:31:21 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:21.020+01:00 level=WARN msg="failed to enable Bluetooth adapter" adapter=hci2 error="bluetooth: adapter /org/bluez/hci2 does not exist" Mar 04 20:31:21 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:21.020+01:00 level=WARN msg="failed to enable Bluetooth adapter" adapter=hci3 error="bluetooth: adapter /org/bluez/hci3 does not exist" Mar 04 20:31:21 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:21.020+01:00 level=WARN msg="failed to enable Bluetooth adapter" adapter=hci4 error="bluetooth: adapter /org/bluez/hci4 does not exist" Mar 04 20:31:21 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:21.021+01:00 level=WARN msg="no Bluetooth adapter found, BLE discovery disabled" Mar 04 20:31:21 volumiow volumio[1216]: info: Received Get System Info Mar 04 20:31:21 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo Mar 04 20:31:21 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice Mar 04 20:31:21 volumiow volumio[1216]: info: Discovery: Getting this device information Mar 04 20:31:21 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:21 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:21 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses Mar 04 20:31:21 volumiow volumio[1216]: info: Received Get System Info Mar 04 20:31:21 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:21.023+01:00 level=INFO msg="system info for 044162d970e8d1fd45c871202b56a80a" deviceName=Volumio_W deviceVariant=volumio deviceModel= softwareVersion=4.096 Mar 04 20:31:21 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo Mar 04 20:31:21 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice Mar 04 20:31:21 volumiow volumio[1216]: info: Discovery: Getting this device information Mar 04 20:31:21 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:21 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:21 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses Mar 04 20:31:21 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: wizard , getShowWizard Mar 04 20:31:21 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getShowWizard Mar 04 20:31:21 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:21.033+01:00 level=INFO msg="enabling local network discovery" Mar 04 20:31:21 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:21.040+01:00 level=INFO msg="bootstrapping state" hasInternet=false Mar 04 20:31:21 volumiow dhcpcd[806]: eth0: leased 192.168.1.43 for 86400 seconds Mar 04 20:31:21 volumiow sh[790]: eth0: leased 192.168.1.43 for 86400 seconds Mar 04 20:31:21 volumiow avahi-daemon[892]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.43. Mar 04 20:31:21 volumiow avahi-daemon[892]: New relevant interface eth0.IPv4 for mDNS. Mar 04 20:31:21 volumiow avahi-daemon[892]: Registering new address record for 192.168.1.43 on eth0.IPv4. Mar 04 20:31:21 volumiow dhcpcd[806]: eth0: adding route to 192.168.1.0/24 Mar 04 20:31:21 volumiow sh[790]: eth0: adding route to 192.168.1.0/24 Mar 04 20:31:21 volumiow sh[790]: eth0: adding default route via 192.168.1.1 Mar 04 20:31:21 volumiow sh[790]: forked to background, child pid 805 Mar 04 20:31:21 volumiow dhcpcd[806]: eth0: adding default route via 192.168.1.1 Mar 04 20:31:21 volumiow systemd[1]: welcome.service: Deactivated successfully. Mar 04 20:31:21 volumiow systemd[1]: Stopped welcome.service - Show a welcome message on console. Mar 04 20:31:21 volumiow systemd[1]: Stopping welcome.service - Show a welcome message on console... Mar 04 20:31:21 volumiow systemd[1]: Starting welcome.service - Show a welcome message on console... Mar 04 20:31:21 volumiow welcome[1923]: Resolved ip:[1] 192.168.1.43 Mar 04 20:31:21 volumiow systemd[1]: Finished welcome.service - Show a welcome message on console. Mar 04 20:31:21 volumiow systemd[1]: Reached target ip-changed@eth0.target - IP Address changed on eth0. Mar 04 20:31:21 volumiow ifplugd(eth0)[1062]: client: ifup: interface eth0 already configured Mar 04 20:31:21 volumiow sh[1949]: eth0=eth0 Mar 04 20:31:21 volumiow ifplugd(eth0)[1062]: Program executed successfully. Mar 04 20:31:21 volumiow volumio[1216]: verbose: New Socket.io Connection to 127.0.0.1:3000 from 127.0.0.1 UA: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36 Engine version: 3 Transport: polling Total Clients: 3 Mar 04 20:31:21 volumiow systemd[1]: Started nmbd.service - Samba NMB Daemon. Mar 04 20:31:21 volumiow systemd[1]: Starting winbind.service - Samba Winbind Daemon... Mar 04 20:31:22 volumiow winbindd[1955]: [2026/03/04 20:31:22.010588, 0] ../../source3/winbindd/winbindd.c:1440(main) Mar 04 20:31:22 volumiow winbindd[1955]: winbindd version 4.17.12-Debian started. Mar 04 20:31:22 volumiow winbindd[1955]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Mar 04 20:31:22 volumiow winbindd[1955]: [2026/03/04 20:31:22.020713, 0] ../../source3/winbindd/winbindd_cache.c:3117(initialize_winbindd_cache) Mar 04 20:31:22 volumiow winbindd[1955]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Mar 04 20:31:22 volumiow systemd[1]: Started winbind.service - Samba Winbind Daemon. Mar 04 20:31:22 volumiow mpd[1778]: 2026-03-04T20:31:22 decoder: Decoder plugin "wildmidi" is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg Mar 04 20:31:22 volumiow systemd[1]: Starting smbd.service - Samba SMB Daemon... Mar 04 20:31:22 volumiow volumio[1216]: info: Received Get System Info Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice Mar 04 20:31:22 volumiow volumio[1216]: info: Discovery: Getting this device information Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:22 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: wizard , getShowWizard Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getShowWizard Mar 04 20:31:22 volumiow systemd[1]: Started mpd.service - Music Player Daemon. Mar 04 20:31:22 volumiow sudo[1745]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:22 volumiow sudo[1733]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:22 volumiow volumio[1216]: info: Completed starting Core Plugins Mar 04 20:31:22 volumiow volumio[1216]: info: ------------------------------------------- Mar 04 20:31:22 volumiow volumio[1216]: info: ----- MyVolumio plugins startup ---- Mar 04 20:31:22 volumiow volumio[1216]: info: ------------------------------------------- Mar 04 20:31:22 volumiow volumio[1216]: info: [MyVolumio PluginManager] Fetching plans data.... Mar 04 20:31:22 volumiow volumio[1216]: info: MPD running with PID1778 Mar 04 20:31:22 volumiow volumio[1216]: ,establishing connection Mar 04 20:31:22 volumiow volumio[1216]: error: MPD error: The expression evaluated to a falsy value: Mar 04 20:31:22 volumiow volumio[1216]: assert.ok(self.idling) Mar 04 20:31:22 volumiow volumio[1216]: error: The expression evaluated to a falsy value: Mar 04 20:31:22 volumiow volumio[1216]: assert.ok(self.idling) Mar 04 20:31:22 volumiow volumio[1216]: error: MPD error: The expression evaluated to a falsy value: Mar 04 20:31:22 volumiow volumio[1216]: assert.ok(self.idling) Mar 04 20:31:22 volumiow volumio[1216]: error: The expression evaluated to a falsy value: Mar 04 20:31:22 volumiow volumio[1216]: assert.ok(self.idling) Mar 04 20:31:22 volumiow volumio[1216]: error: updateQueue error: null Mar 04 20:31:22 volumiow smbd[1975]: [2026/03/04 20:31:22.273390, 0] ../../source3/smbd/server.c:1741(main) Mar 04 20:31:22 volumiow smbd[1975]: smbd version 4.17.12-Debian started. Mar 04 20:31:22 volumiow smbd[1975]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Mar 04 20:31:22 volumiow volumio[1216]: verbose: New Socket.io Connection to 127.0.0.1:3000 from 127.0.0.1 UA: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36 Engine version: 3 Transport: polling Total Clients: 4 Mar 04 20:31:22 volumiow systemd[1]: Started smbd.service - Samba SMB Daemon. Mar 04 20:31:22 volumiow systemd[1]: Reached target multi-user.target - Multi-User System. Mar 04 20:31:22 volumiow systemd[1]: Reached target graphical.target - Graphical Interface. Mar 04 20:31:22 volumiow systemd[1]: Starting systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP... Mar 04 20:31:22 volumiow systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully. Mar 04 20:31:22 volumiow systemd[1]: Finished systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP. Mar 04 20:31:22 volumiow systemd[1]: Startup finished in 12.232s (kernel) + 13.048s (userspace) = 25.281s. Mar 04 20:31:22 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:31:22 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: my_volumio , getAutoUpdateCheckEnabled Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetVisibleSources Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:22 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: metavolumio , getInfinityPlayback Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetQueue Mar 04 20:31:22 volumiow volumio[1216]: info: CoreStateMachine::getQueue Mar 04 20:31:22 volumiow volumio[1216]: info: CorePlayQueue::getQueue Mar 04 20:31:22 volumiow volumio[1216]: info: Listing playlists Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: multiroom , getMultiroom Mar 04 20:31:22 volumiow volumio[1216]: info: Received Get System Info Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice Mar 04 20:31:22 volumiow volumio[1216]: info: Discovery: Getting this device information Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:22 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:22 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: appearance , getUiSettings Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getPrivacySettings Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice Mar 04 20:31:22 volumiow volumio[1216]: info: Discovery: Getting this device information Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:22 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses Mar 04 20:31:22 volumiow volumio[1216]: verbose: New Socket.io Connection to 192.168.1.43:3000 from 192.168.1.10 UA: Dart/3.10 (dart:io) Engine version: 3 Transport: websocket Total Clients: 5 Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: wizard , getShowWizard Mar 04 20:31:22 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getShowWizard Mar 04 20:31:23 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:23.080+01:00 level=INFO msg="established new WebSocket connection" component=conn/ws remoteAddr=192.168.1.10:49510 Mar 04 20:31:23 volumiow ntpd[1041]: IO: Listen normally on 3 eth0 192.168.1.43:123 Mar 04 20:31:23 volumiow ntpd[1041]: IO: new interface(s) found: waking up resolver Mar 04 20:31:23 volumiow ntpd[1041]: DNS: dns_probe: 3.debian.pool.ntp.org, cast_flags:8, flags:101 Mar 04 20:31:23 volumiow ntpd[1041]: DNS: dns_check: processing 3.debian.pool.ntp.org, 8, 101 Mar 04 20:31:23 volumiow ntpd[1041]: DNS: Pool taking: 151.22.209.90 Mar 04 20:31:23 volumiow ntpd[1041]: DNS: Pool taking: 162.159.200.123 Mar 04 20:31:23 volumiow ntpd[1041]: DNS: Pool taking: 172.232.209.103 Mar 04 20:31:23 volumiow ntpd[1041]: DNS: Pool taking: 31.14.133.122 Mar 04 20:31:23 volumiow ntpd[1041]: DNS: dns_take_status: 3.debian.pool.ntp.org=>good, 8 Mar 04 20:31:24 volumiow ntpd[1041]: DNS: dns_probe: 2.debian.pool.ntp.org, cast_flags:8, flags:101 Mar 04 20:31:24 volumiow ntpd[1041]: DNS: dns_check: processing 2.debian.pool.ntp.org, 8, 101 Mar 04 20:31:24 volumiow ntpd[1041]: DNS: Pool taking: 195.32.70.195 Mar 04 20:31:24 volumiow ntpd[1041]: DNS: Pool taking: 81.56.230.156 Mar 04 20:31:24 volumiow ntpd[1041]: DNS: Pool taking: 89.46.74.148 Mar 04 20:31:24 volumiow ntpd[1041]: DNS: Pool taking: 162.159.200.1 Mar 04 20:31:24 volumiow ntpd[1041]: DNS: Pool taking: 2a00:6d40:72:100::69a Mar 04 20:31:24 volumiow ntpd[1041]: DNS: Pool taking: 2a00:6d41:200:2::13 Mar 04 20:31:24 volumiow ntpd[1041]: DNS: Pool taking: 2a00:6d41:200:2::15 Mar 04 20:31:24 volumiow ntpd[1041]: DNS: Pool taking: 2a03:b020:0:404::51 Mar 04 20:31:24 volumiow ntpd[1041]: DNS: dns_take_status: 2.debian.pool.ntp.org=>good, 8 Mar 04 20:31:24 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: wizard , getOnboardingWizard Mar 04 20:31:24 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: my_volumio , getMyVolumioStatus Mar 04 20:31:24 volumiow volumio[1216]: info: Received Get System Info Mar 04 20:31:24 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo Mar 04 20:31:24 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice Mar 04 20:31:24 volumiow volumio[1216]: info: Discovery: Getting this device information Mar 04 20:31:24 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:24 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:24 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses Mar 04 20:31:24 volumiow volumio-remote-updater[899]: [2026-03-04 20:31:24] [connect] Successful connection Mar 04 20:31:24 volumiow volumio-remote-updater[899]: [2026-03-04 20:31:24] [connect] WebSocket Connection 127.0.0.1:3000 v-2 "WebSocket++/0.8.2" /socket.io/?EIO=3&transport=websocket&t=1772652684 101 Mar 04 20:31:24 volumiow volumio[1216]: verbose: New Socket.io Connection to 127.0.0.1:3000 from 127.0.0.1 UA: WebSocket++/0.8.2 Engine version: 3 Transport: websocket Total Clients: 5 Mar 04 20:31:25 volumiow ntpd[1041]: DNS: dns_probe: 1.debian.pool.ntp.org, cast_flags:8, flags:101 Mar 04 20:31:25 volumiow ntpd[1041]: DNS: dns_check: processing 1.debian.pool.ntp.org, 8, 101 Mar 04 20:31:25 volumiow ntpd[1041]: DNS: Pool taking: 95.110.254.234 Mar 04 20:31:25 volumiow ntpd[1041]: DNS: Pool taking: 129.152.16.145 Mar 04 20:31:25 volumiow ntpd[1041]: DNS: Pool taking: 172.232.208.229 Mar 04 20:31:25 volumiow ntpd[1041]: DNS: Pool taking: 85.199.214.99 Mar 04 20:31:25 volumiow ntpd[1041]: DNS: dns_take_status: 1.debian.pool.ntp.org=>good, 8 Mar 04 20:31:25 volumiow dhcpcd[926]: eth0: leased 192.168.1.43 for 86400 seconds Mar 04 20:31:25 volumiow dhcpcd[926]: eth0: adding route to 192.168.1.0/24 Mar 04 20:31:25 volumiow dhcpcd[926]: eth0: adding default route via 192.168.1.1 Mar 04 20:31:25 volumiow systemd[1]: Stopped target ip-changed@eth0.target - IP Address changed on eth0. Mar 04 20:31:25 volumiow systemd[1]: Stopping ip-changed@eth0.target - IP Address changed on eth0... Mar 04 20:31:25 volumiow systemd[1]: welcome.service: Deactivated successfully. Mar 04 20:31:25 volumiow systemd[1]: Stopped welcome.service - Show a welcome message on console. Mar 04 20:31:25 volumiow systemd[1]: Stopping welcome.service - Show a welcome message on console... Mar 04 20:31:25 volumiow systemd[1]: Starting welcome.service - Show a welcome message on console... Mar 04 20:31:25 volumiow welcome[2016]: Resolved ip:[1] 192.168.1.43 Mar 04 20:31:25 volumiow systemd[1]: Finished welcome.service - Show a welcome message on console. Mar 04 20:31:25 volumiow systemd[1]: Reached target ip-changed@eth0.target - IP Address changed on eth0. Mar 04 20:31:25 volumiow volumio[1216]: info: Received Get System Info Mar 04 20:31:25 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo Mar 04 20:31:25 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice Mar 04 20:31:25 volumiow volumio[1216]: info: Discovery: Getting this device information Mar 04 20:31:25 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:25 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:25 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses Mar 04 20:31:25 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: wizard , getShowWizard Mar 04 20:31:25 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getShowWizard Mar 04 20:31:25 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:25.989+01:00 level=INFO msg="app ready event" component=server event=CLIENT_EVENT_TYPE_APP_READY peer="192.168.1.10:49510 @ 0xc0002cac30" latency=16m54.837768158s platform=PLATFORM_IOS version=5.260120.0 Mar 04 20:31:25 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: wizard , getShowWizard Mar 04 20:31:25 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getShowWizard Mar 04 20:31:25 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:25.992+01:00 level=INFO msg="device data request" component=server type=REQUEST_TYPE_DEVICE_DATA peer="192.168.1.10:49510 @ 0xc0002cac30" latency=16m54.838019474s timeout=10s Mar 04 20:31:25 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:25.992+01:00 level=INFO msg="emitting device capabilities changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" Mar 04 20:31:25 volumiow volumio[1216]: info: Received Get System Info Mar 04 20:31:25 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo Mar 04 20:31:25 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice Mar 04 20:31:25 volumiow volumio[1216]: info: Discovery: Getting this device information Mar 04 20:31:25 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:25 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:25 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses Mar 04 20:31:25 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:25.993+01:00 level=INFO msg="emitting device name changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" name=Volumio_W Mar 04 20:31:25 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:25.994+01:00 level=INFO msg="emitting device language changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" language=it Mar 04 20:31:25 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getCurrentTimezone Mar 04 20:31:25 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:25.995+01:00 level=INFO msg="emitting device timezone changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" timezone=Europe/Rome Mar 04 20:31:25 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:25.996+01:00 level=INFO msg="emitting ethernet info changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" available=true connected=true macAddress=00:e0:4c:68:5e:ad ip4Address=192.168.1.43/24 ip6Address= Mar 04 20:31:25 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:25.996+01:00 level=INFO msg="emitting wifi info changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" available=true connected=false macAddress= ip4Address= ip6Address= ssid= Mar 04 20:31:25 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:25.996+01:00 level=INFO msg="emitting device setup status changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" setupComplete=true Mar 04 20:31:25 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getExtendedOutputDevices Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: i2s_dacs , getI2sOptions Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: i2s_dacs , getI2sStatus Mar 04 20:31:26 volumiow volumio[1216]: error: Cannot read Audio Device Capabilities Command failed: /usr/local/bin/alsacap -C 0 -D 0 Mar 04 20:31:26 volumiow volumio[1216]: /bin/sh: 1: /usr/local/bin/alsacap: not found Mar 04 20:31:26 volumiow volumio[1216]: {"cmd":"/usr/local/bin/alsacap -C 0 -D 0","code":127,"killed":false,"signal":null,"stack":"Error: Command failed: /usr/local/bin/alsacap -C 0 -D 0\n/bin/sh: 1: /usr/local/bin/alsacap: not found\n\n at ChildProcess.exithandler (node:child_process:421:12)\n at ChildProcess.emit (node:events:514:28)\n at maybeClose (node:internal/child_process:1105:16)\n at Socket. (node:internal/child_process:457:11)\n at Socket.emit (node:events:514:28)\n at Pipe. (node:net:337:12)"} Mar 04 20:31:26 volumiow volumio[1216]: error: Cannot read Audio Device Capabilities Command failed: /usr/local/bin/alsacap -C 5 Mar 04 20:31:26 volumiow volumio[1216]: /bin/sh: 1: /usr/local/bin/alsacap: not found Mar 04 20:31:26 volumiow volumio[1216]: {"cmd":"/usr/local/bin/alsacap -C 5","code":127,"killed":false,"signal":null,"stack":"Error: Command failed: /usr/local/bin/alsacap -C 5\n/bin/sh: 1: /usr/local/bin/alsacap: not found\n\n at ChildProcess.exithandler (node:child_process:421:12)\n at ChildProcess.emit (node:events:514:28)\n at maybeClose (node:internal/child_process:1105:16)\n at Socket. (node:internal/child_process:457:11)\n at Socket.emit (node:events:514:28)\n at Pipe. (node:net:337:12)"} Mar 04 20:31:26 volumiow volumio[1216]: amixer -c 5 info | grep "D50 III" Mar 04 20:31:26 volumiow volumio[1216]: Card sysdefault:5 'III'/'Topping D50 III at usb-0000:00:14.0-4, high speed' Mar 04 20:31:26 volumiow volumio[1216]: error: Cannot read Audio Device Capabilities Command failed: /usr/local/bin/alsacap -C 5 Mar 04 20:31:26 volumiow volumio[1216]: /bin/sh: 1: /usr/local/bin/alsacap: not found Mar 04 20:31:26 volumiow volumio[1216]: {"cmd":"/usr/local/bin/alsacap -C 5","code":127,"killed":false,"signal":null,"stack":"Error: Command failed: /usr/local/bin/alsacap -C 5\n/bin/sh: 1: /usr/local/bin/alsacap: not found\n\n at ChildProcess.exithandler (node:child_process:421:12)\n at ChildProcess.emit (node:events:514:28)\n at maybeClose (node:internal/child_process:1105:16)\n at Socket. (node:internal/child_process:457:11)\n at Socket.emit (node:events:514:28)\n at Pipe. (node:net:337:12)"} Mar 04 20:31:26 volumiow volumio[1216]: amixer -c 5 info | grep "D50 III" Mar 04 20:31:26 volumiow volumio[1216]: Card sysdefault:5 'III'/'Topping D50 III at usb-0000:00:14.0-4, high speed' Mar 04 20:31:26 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:26.024+01:00 level=INFO msg="emitting audio outputs changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" selectedOutputId=5 Mar 04 20:31:26 volumiow volumio[1216]: info: Received Get System Info Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice Mar 04 20:31:26 volumiow volumio[1216]: info: Discovery: Getting this device information Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:26 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses Mar 04 20:31:26 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:26.031+01:00 level=INFO msg="emitting software info changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" currentVersion=4.096 latestVersion=4.096 Mar 04 20:31:26 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:26.031+01:00 level=INFO msg="emitting software update progress event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" status=UPDATE_STATUS_NONE progress=0 Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: my_volumio , getMyVolumioStatus Mar 04 20:31:26 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:26.032+01:00 level=INFO msg="emitting user changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" userId= Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: my_volumio , getMyVolumioStatus Mar 04 20:31:26 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:26.033+01:00 level=WARN msg="could not read OAuth data for music provider" component=volumio provider=tidal error="could not open plugin config file for \"tidal\": open /data/configuration/music_service/tidal/config.json: no such file or directory" Mar 04 20:31:26 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:26.033+01:00 level=WARN msg="could not read OAuth data for music provider" component=volumio provider=qobuz error="could not open plugin config file for \"qobuz\": open /data/configuration/music_service/qobuz/config.json: no such file or directory" Mar 04 20:31:26 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:26.033+01:00 level=WARN msg="could not read username/password data for music provider" component=volumio provider=hi_res_audio error="could not open plugin config file for \"hi_res_audio\": open /data/configuration/music_service/hi_res_audio/config.json: no such file or directory" Mar 04 20:31:26 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:26.033+01:00 level=INFO msg="emitting music providers changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" providers=3 Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: my_volumio , getMyVolumioStatus Mar 04 20:31:26 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:26.034+01:00 level=INFO msg="emitting plugins changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" plugins=0 Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:26 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:26 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:26.035+01:00 level=INFO msg="emitting player state changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" state=STATUS_STOPPED positionMs=0 volume=100 Mar 04 20:31:26 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:26.035+01:00 level=INFO msg="emitting player metadata changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" id="mnt/USB/01DA612410BFC090/VA - Sweet Morning Chill Out And Lounge Collection Vol.1 (2021) FLAC/01 - Lounge Groove Avenue - Silk and Smooth (Original Mix).flac" title="Silk and Smooth (Original Mix)" Mar 04 20:31:26 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:31:26.047+01:00 level=INFO msg="navigate to next page" component=server type=REQUEST_TYPE_CONTINUE_NAVIGATION peer="192.168.1.10:49510 @ 0xc0002cac30" latency=16m54.834920967s timeout=10s from=APP_PAGE_ROOT to=APP_PAGE_LEGACY_DEVICE Mar 04 20:31:26 volumiow ntpd[1041]: DNS: dns_probe: 0.debian.pool.ntp.org, cast_flags:8, flags:101 Mar 04 20:31:26 volumiow ntpd[1041]: DNS: dns_check: processing 0.debian.pool.ntp.org, 8, 101 Mar 04 20:31:26 volumiow ntpd[1041]: DNS: Pool taking: 185.157.229.254 Mar 04 20:31:26 volumiow ntpd[1041]: DNS: Pool taking: 5.249.149.252 Mar 04 20:31:26 volumiow ntpd[1041]: DNS: Pool taking: 37.247.53.178 Mar 04 20:31:26 volumiow ntpd[1041]: DNS: Pool taking: 95.242.98.72 Mar 04 20:31:26 volumiow ntpd[1041]: DNS: dns_take_status: 0.debian.pool.ntp.org=>good, 8 Mar 04 20:31:26 volumiow sudo[2056]: volumio : PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 Mar 04 20:31:26 volumiow sudo[2054]: volumio : PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig eth0 Mar 04 20:31:26 volumiow sudo[2056]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:26 volumiow sudo[2054]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:26 volumiow sudo[2056]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:26 volumiow sudo[2054]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:26 volumiow volumio[1216]: verbose: New Socket.io Connection to 192.168.1.43 from 192.168.1.10 UA: Mozilla/5.0 (iPhone; CPU iPhone OS 18_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 Engine version: 3 Transport: polling Total Clients: 6 Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: my_volumio , getAutoUpdateCheckEnabled Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetVisibleSources Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:26 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: metavolumio , getInfinityPlayback Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: multiroom , getMultiroom Mar 04 20:31:26 volumiow volumio[1216]: info: Received Get System Info Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice Mar 04 20:31:26 volumiow volumio[1216]: info: Discovery: Getting this device information Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:26 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:26 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:26 volumiow volumio[1216]: info: Listing playlists Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: appearance , getUiSettings Mar 04 20:31:26 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getPrivacySettings Mar 04 20:31:27 volumiow sudo[2061]: volumio : PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig eth0 Mar 04 20:31:27 volumiow sudo[2063]: volumio : PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 Mar 04 20:31:27 volumiow sudo[2063]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:27 volumiow sudo[2061]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:27 volumiow sudo[2061]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:27 volumiow sudo[2063]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:27 volumiow volumio[1216]: verbose: New Socket.io Connection to 192.168.1.43 from 192.168.1.10 UA: Mozilla/5.0 (iPhone; CPU iPhone OS 18_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 Engine version: 3 Transport: polling Total Clients: 7 Mar 04 20:31:27 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: my_volumio , getAutoUpdateCheckEnabled Mar 04 20:31:27 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetVisibleSources Mar 04 20:31:27 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources Mar 04 20:31:27 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:27 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:27 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: metavolumio , getInfinityPlayback Mar 04 20:31:27 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: multiroom , getMultiroom Mar 04 20:31:27 volumiow volumio[1216]: info: Received Get System Info Mar 04 20:31:27 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo Mar 04 20:31:27 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice Mar 04 20:31:27 volumiow volumio[1216]: info: Discovery: Getting this device information Mar 04 20:31:27 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:27 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:27 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses Mar 04 20:31:27 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:27 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:27 volumiow volumio[1216]: info: Listing playlists Mar 04 20:31:27 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: appearance , getUiSettings Mar 04 20:31:27 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getPrivacySettings Mar 04 20:31:27 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:27 volumiow systemd[1]: upmpdcli.service: Scheduled restart job, restart counter is at 1. Mar 04 20:31:27 volumiow systemd[1]: Stopped upmpdcli.service - UPnP Renderer front-end to MPD. Mar 04 20:31:27 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:27 volumiow systemd[1]: Started upmpdcli.service - UPnP Renderer front-end to MPD. Mar 04 20:31:27 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:27 volumiow upmpdcli[2066]: Could not open config: /tmp/upmpdcli.conf Mar 04 20:31:27 volumiow systemd[1]: upmpdcli.service: Main process exited, code=exited, status=1/FAILURE Mar 04 20:31:27 volumiow systemd[1]: upmpdcli.service: Failed with result 'exit-code'. Mar 04 20:31:27 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:27 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:27 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:27 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:27 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:27 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:27 volumiow volumio[1216]: Cannot compose Albumart path Mar 04 20:31:27 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:27 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:27 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:27 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:27 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:31:28 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:31:28 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:31:28 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:31:28 volumiow volumio[1216]: info: Discovery: Restart already pending, ignoring duplicate call Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: wizard , getOnboardingWizard Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow volumio[1216]: info: Volumio Network Manager: Network status updated: 1 Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:28 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:28 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:29 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:29 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:29 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: my_volumio , getMyVolumioStatus Mar 04 20:31:29 volumiow volumio[1216]: info: Received Get System Info Mar 04 20:31:29 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo Mar 04 20:31:29 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice Mar 04 20:31:29 volumiow volumio[1216]: info: Discovery: Getting this device information Mar 04 20:31:29 volumiow volumio[1216]: info: CoreCommandRouter::volumioGetState Mar 04 20:31:29 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:31:29 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses Mar 04 20:31:29 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:29 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:29 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:29 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:29 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:29 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:29 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:31:29 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:31:29 volumiow sudo[2092]: volumio : PWD=/ ; USER=root ; COMMAND=/bin/systemctl start upmpdcli.service Mar 04 20:31:29 volumiow sudo[2092]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:29 volumiow sudo[2090]: volumio : PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 Mar 04 20:31:29 volumiow sudo[2088]: volumio : PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig eth0 Mar 04 20:31:29 volumiow sudo[2090]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:29 volumiow sudo[2088]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Mar 04 20:31:29 volumiow sudo[2090]: pam_unix(sudo:session): session closed for user root Mar 04 20:31:29 volumiow sudo[2088]: pam_unix(sudo:session): session closed for user root Mar 04 20:24:01 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:01 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:01 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:01 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:01 volumiow volumio[1216]: info: Discovery: Restart already pending, ignoring duplicate call Mar 04 20:24:01 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: mpd , handleBrowseUri Mar 04 20:24:01 volumiow volumio[1216]: info: CURURI: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010) Mar 04 20:24:02 volumiow volumio[1216]: info: Preload queue cleared Mar 04 20:24:02 volumiow volumio[1216]: info: Preloading song: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/01 - If I Ever Lose My Faith In You.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Preloading song: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Preloading song: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/03 - Fields Of Gold.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Preloading song: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/04 - Why Should I Cry For You.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Preloading song: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/05 - All Would Envy.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Preloading song: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/06 - Tomorrow We'll See.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Preloading song: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/07 - The End Of The Game.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Preloading song: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/08 - Whenever I Say Your Name.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Preloading song: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/09 - Shape Of My Heart.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Preloading song: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/10 - Moon Over Bourbon Street.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Preloading song: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/11 - Mad About You.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Preloading song: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/12 - King Of Pain.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Preloading song: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/13 - Desert Rose.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Preloading song: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/14 - Fragile.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Preloading song: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/Sting - Live In Berlin.m3u Mar 04 20:24:02 volumiow volumio[1216]: info: Exploding uri music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/01 - If I Ever Lose My Faith In You.flac in service mpd Mar 04 20:24:02 volumiow volumio[1216]: info: ALBUMART /albumart?cacheid=380&web=Sting/Live%20In%20Berlin/extralarge&path=%2Fmnt%2FUSB%2F01DA612410BFC090%2FSting%20-%20Live%20In%20Berlin%20(2010)%2F01%20-%20If%20I%20Ever%20Lose%20My%20Faith%20In%20You.flac&metadata=false Mar 04 20:24:02 volumiow volumio[1216]: info: URI /mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/01 - If I Ever Lose My Faith In You.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Exploding uri music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac in service mpd Mar 04 20:24:02 volumiow volumio[1216]: info: ALBUMART /albumart?cacheid=380&web=Sting/Live%20In%20Berlin/extralarge&path=%2Fmnt%2FUSB%2F01DA612410BFC090%2FSting%20-%20Live%20In%20Berlin%20(2010)%2F02%20-%20Englishman%20In%20New%20York.flac&metadata=false Mar 04 20:24:02 volumiow volumio[1216]: info: URI /mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Exploding uri music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/03 - Fields Of Gold.flac in service mpd Mar 04 20:24:02 volumiow volumio[1216]: info: ALBUMART /albumart?cacheid=380&web=Sting/Live%20In%20Berlin/extralarge&path=%2Fmnt%2FUSB%2F01DA612410BFC090%2FSting%20-%20Live%20In%20Berlin%20(2010)%2F03%20-%20Fields%20Of%20Gold.flac&metadata=false Mar 04 20:24:02 volumiow volumio[1216]: info: URI /mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/03 - Fields Of Gold.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Exploding uri music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/04 - Why Should I Cry For You.flac in service mpd Mar 04 20:24:02 volumiow volumio[1216]: info: ALBUMART /albumart?cacheid=380&web=Sting/Live%20In%20Berlin/extralarge&path=%2Fmnt%2FUSB%2F01DA612410BFC090%2FSting%20-%20Live%20In%20Berlin%20(2010)%2F04%20-%20Why%20Should%20I%20Cry%20For%20You.flac&metadata=false Mar 04 20:24:02 volumiow volumio[1216]: info: URI /mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/04 - Why Should I Cry For You.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Exploding uri music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/05 - All Would Envy.flac in service mpd Mar 04 20:24:02 volumiow volumio[1216]: info: ALBUMART /albumart?cacheid=380&web=Sting/Live%20In%20Berlin/extralarge&path=%2Fmnt%2FUSB%2F01DA612410BFC090%2FSting%20-%20Live%20In%20Berlin%20(2010)%2F05%20-%20All%20Would%20Envy.flac&metadata=false Mar 04 20:24:02 volumiow volumio[1216]: info: URI /mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/05 - All Would Envy.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Exploding uri music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/06 - Tomorrow We'll See.flac in service mpd Mar 04 20:24:02 volumiow volumio[1216]: info: ALBUMART /albumart?cacheid=380&web=Sting/Live%20In%20Berlin/extralarge&path=%2Fmnt%2FUSB%2F01DA612410BFC090%2FSting%20-%20Live%20In%20Berlin%20(2010)%2F06%20-%20Tomorrow%20We'll%20See.flac&metadata=false Mar 04 20:24:02 volumiow volumio[1216]: info: URI /mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/06 - Tomorrow We'll See.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Exploding uri music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/07 - The End Of The Game.flac in service mpd Mar 04 20:24:02 volumiow volumio[1216]: info: ALBUMART /albumart?cacheid=380&web=Sting/Live%20In%20Berlin/extralarge&path=%2Fmnt%2FUSB%2F01DA612410BFC090%2FSting%20-%20Live%20In%20Berlin%20(2010)%2F07%20-%20The%20End%20Of%20The%20Game.flac&metadata=false Mar 04 20:24:02 volumiow volumio[1216]: info: URI /mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/07 - The End Of The Game.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Exploding uri music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/08 - Whenever I Say Your Name.flac in service mpd Mar 04 20:24:02 volumiow volumio[1216]: info: ALBUMART /albumart?cacheid=380&web=Sting/Live%20In%20Berlin/extralarge&path=%2Fmnt%2FUSB%2F01DA612410BFC090%2FSting%20-%20Live%20In%20Berlin%20(2010)%2F08%20-%20Whenever%20I%20Say%20Your%20Name.flac&metadata=false Mar 04 20:24:02 volumiow volumio[1216]: info: URI /mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/08 - Whenever I Say Your Name.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Exploding uri music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/09 - Shape Of My Heart.flac in service mpd Mar 04 20:24:02 volumiow volumio[1216]: info: ALBUMART /albumart?cacheid=380&web=Sting/Live%20In%20Berlin/extralarge&path=%2Fmnt%2FUSB%2F01DA612410BFC090%2FSting%20-%20Live%20In%20Berlin%20(2010)%2F09%20-%20Shape%20Of%20My%20Heart.flac&metadata=false Mar 04 20:24:02 volumiow volumio[1216]: info: URI /mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/09 - Shape Of My Heart.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Exploding uri music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/10 - Moon Over Bourbon Street.flac in service mpd Mar 04 20:24:02 volumiow volumio[1216]: info: ALBUMART /albumart?cacheid=380&web=Sting/Live%20In%20Berlin/extralarge&path=%2Fmnt%2FUSB%2F01DA612410BFC090%2FSting%20-%20Live%20In%20Berlin%20(2010)%2F10%20-%20Moon%20Over%20Bourbon%20Street.flac&metadata=false Mar 04 20:24:02 volumiow volumio[1216]: info: URI /mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/10 - Moon Over Bourbon Street.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Exploding uri music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/11 - Mad About You.flac in service mpd Mar 04 20:24:02 volumiow volumio[1216]: info: ALBUMART /albumart?cacheid=380&web=Sting/Live%20In%20Berlin/extralarge&path=%2Fmnt%2FUSB%2F01DA612410BFC090%2FSting%20-%20Live%20In%20Berlin%20(2010)%2F11%20-%20Mad%20About%20You.flac&metadata=false Mar 04 20:24:02 volumiow volumio[1216]: info: URI /mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/11 - Mad About You.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Exploding uri music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/12 - King Of Pain.flac in service mpd Mar 04 20:24:02 volumiow volumio[1216]: info: ALBUMART /albumart?cacheid=380&web=Sting/Live%20In%20Berlin/extralarge&path=%2Fmnt%2FUSB%2F01DA612410BFC090%2FSting%20-%20Live%20In%20Berlin%20(2010)%2F12%20-%20King%20Of%20Pain.flac&metadata=false Mar 04 20:24:02 volumiow volumio[1216]: info: URI /mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/12 - King Of Pain.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Exploding uri music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/13 - Desert Rose.flac in service mpd Mar 04 20:24:02 volumiow volumio[1216]: info: ALBUMART /albumart?cacheid=380&web=Sting/Live%20In%20Berlin/extralarge&path=%2Fmnt%2FUSB%2F01DA612410BFC090%2FSting%20-%20Live%20In%20Berlin%20(2010)%2F13%20-%20Desert%20Rose.flac&metadata=false Mar 04 20:24:02 volumiow volumio[1216]: info: URI /mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/13 - Desert Rose.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Exploding uri music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/14 - Fragile.flac in service mpd Mar 04 20:24:02 volumiow volumio[1216]: info: ALBUMART /albumart?cacheid=380&web=Sting/Live%20In%20Berlin/extralarge&path=%2Fmnt%2FUSB%2F01DA612410BFC090%2FSting%20-%20Live%20In%20Berlin%20(2010)%2F14%20-%20Fragile.flac&metadata=false Mar 04 20:24:02 volumiow volumio[1216]: info: URI /mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/14 - Fragile.flac Mar 04 20:24:02 volumiow volumio[1216]: info: Exploding uri music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/Sting - Live In Berlin.m3u in service mpd Mar 04 20:24:03 volumiow volumio[1216]: info: Preload queue cleared Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioReplaceandPlayItems Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::ClearQueue Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::stop Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::setConsumeUpdateService undefined Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::stPlaybackTimer Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::updateTrackBlock Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrackBlock Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::serviceStop Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 0 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::serviceStop Mar 04 20:24:03 volumiow volumio[1216]: info: ControllerMpd::stop Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand stop Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::clearPlayQueue Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::saveQueue Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushQueue Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::addQueueItems Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::addQueueItems Mar 04 20:24:03 volumiow volumio[1216]: info: Preload queue cleared Mar 04 20:24:03 volumiow volumio[1216]: info: Adding Item to queue: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/01 - If I Ever Lose My Faith In You.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Using cached record of: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/01 - If I Ever Lose My Faith In You.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Adding Item to queue: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Using cached record of: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.438+01:00 level=INFO msg="emitting player state changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" state=STATUS_STOPPED positionMs=0 volume=100 Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.438+01:00 level=INFO msg="emitting player metadata changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" id="mnt/USB/01DA612410BFC090/50 Cent - Get Rich Or Die Tryin' (2003,2012 Japan) [FLAC] 88/21. Soldier (Freestyle).flac" title="Soldier (Freestyle)" Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushQueue Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::saveQueue Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::updateTrackBlock Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrackBlock Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPlay Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::play index 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::setConsumeUpdateService undefined Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::addQueueItems Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::addQueueItems Mar 04 20:24:03 volumiow volumio[1216]: info: Preload queue cleared Mar 04 20:24:03 volumiow volumio[1216]: info: Adding Item to queue: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/03 - Fields Of Gold.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Using cached record of: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/03 - Fields Of Gold.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Adding Item to queue: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/04 - Why Should I Cry For You.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Using cached record of: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/04 - Why Should I Cry For You.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Adding Item to queue: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/05 - All Would Envy.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Using cached record of: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/05 - All Would Envy.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Adding Item to queue: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/06 - Tomorrow We'll See.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Using cached record of: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/06 - Tomorrow We'll See.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Adding Item to queue: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/07 - The End Of The Game.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Using cached record of: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/07 - The End Of The Game.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Adding Item to queue: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/08 - Whenever I Say Your Name.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Using cached record of: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/08 - Whenever I Say Your Name.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Adding Item to queue: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/09 - Shape Of My Heart.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Using cached record of: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/09 - Shape Of My Heart.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Adding Item to queue: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/10 - Moon Over Bourbon Street.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Using cached record of: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/10 - Moon Over Bourbon Street.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Adding Item to queue: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/11 - Mad About You.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Using cached record of: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/11 - Mad About You.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Adding Item to queue: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/12 - King Of Pain.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Using cached record of: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/12 - King Of Pain.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Adding Item to queue: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/13 - Desert Rose.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Using cached record of: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/13 - Desert Rose.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Adding Item to queue: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/14 - Fragile.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Using cached record of: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/14 - Fragile.flac Mar 04 20:24:03 volumiow volumio[1216]: info: Adding Item to queue: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/Live In Berlin.cue Mar 04 20:24:03 volumiow volumio[1216]: info: Exploding uri music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/Live In Berlin.cue in service mpd Mar 04 20:24:03 volumiow volumio[1216]: info: Adding Item to queue: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/Live In Berlin.cue Mar 04 20:24:03 volumiow volumio[1216]: info: Exploding uri music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/Live In Berlin.cue in service mpd Mar 04 20:24:03 volumiow volumio[1216]: info: Adding Item to queue: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/Sting - Live In Berlin.m3u Mar 04 20:24:03 volumiow volumio[1216]: info: Using cached record of: music-library/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/Sting - Live In Berlin.m3u Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::stop Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::setConsumeUpdateService undefined Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::play index undefined Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::setConsumeUpdateService undefined Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::startPlaybackTimer Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::clearAddPlayTracks USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand stop Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushQueue Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::saveQueue Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::updateTrackBlock Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrackBlock Mar 04 20:24:03 volumiow volumio[1216]: info: Mar 04 20:24:03 volumiow volumio[1216]: ---------------------------- MPD announces state update: player Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand stop took 24 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: info: ControllerMpd::getState Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand status Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand stop took 3 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand clear Mar 04 20:24:03 volumiow volumio[1216]: info: Mar 04 20:24:03 volumiow volumio[1216]: ---------------------------- MPD announces state update: player Mar 04 20:24:03 volumiow volumio[1216]: info: ControllerMpd::getState Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand status Mar 04 20:24:03 volumiow volumio[1216]: info: Mar 04 20:24:03 volumiow volumio[1216]: ---------------------------- MPD announces state update: player Mar 04 20:24:03 volumiow volumio[1216]: info: ControllerMpd::getState Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand status Mar 04 20:24:03 volumiow volumio[1216]: info: Mar 04 20:24:03 volumiow volumio[1216]: ---------------------------- MPD announces system playlist update Mar 04 20:24:03 volumiow volumio[1216]: info: Ignoring MPD Status Update Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand status took 2 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand clear took 2 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand status took 2 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand status took 2 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::parseState Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand playlistinfo Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand add "USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac" Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::parseState Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::parseState Mar 04 20:24:03 volumiow volumio[1216]: info: ControllerMpd::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::servicePushState Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: verbose: STATE SERVICE {"status":"stop","position":null,"seek":null,"duration":null,"samplerate":null,"bitdepth":null,"channels":null,"random":false,"updatedb":false,"repeat":false,"bitrate":null,"isStreaming":false,"title":null,"artist":null,"album":null,"uri":null} Mar 04 20:24:03 volumiow volumio[1216]: verbose: CURRENT POSITION 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::syncState stateService stop Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::syncState currentStatus stop Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:24:03 volumiow volumio[1216]: info: No code Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:24:03 volumiow volumio[1216]: info: ControllerMpd::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::servicePushState Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: verbose: STATE SERVICE {"status":"stop","position":null,"seek":null,"duration":null,"samplerate":null,"bitdepth":null,"channels":null,"random":false,"updatedb":false,"repeat":false,"bitrate":null,"isStreaming":false,"title":null,"artist":null,"album":null,"uri":null} Mar 04 20:24:03 volumiow volumio[1216]: verbose: CURRENT POSITION 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::syncState stateService stop Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::syncState currentStatus stop Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:24:03 volumiow volumio[1216]: info: No code Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.467+01:00 level=INFO msg="emitting player state changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" state=STATUS_STOPPED positionMs=0 volume=100 Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.467+01:00 level=INFO msg="emitting player metadata changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" id="mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac" title="Englishman In New York" Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.467+01:00 level=INFO msg="emitting player state changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" state=STATUS_STOPPED positionMs=0 volume=100 Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.467+01:00 level=INFO msg="emitting player metadata changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" id="mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac" title="Englishman In New York" Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.467+01:00 level=INFO msg="emitting player state changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" state=STATUS_STOPPED positionMs=0 volume=100 Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.467+01:00 level=INFO msg="emitting player metadata changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" id="mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac" title="Englishman In New York" Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.467+01:00 level=INFO msg="emitting player state changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" state=STATUS_STOPPED positionMs=0 volume=100 Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.467+01:00 level=INFO msg="emitting player metadata changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" id="mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac" title="Englishman In New York" Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.468+01:00 level=INFO msg="emitting player state changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" state=STATUS_STOPPED positionMs=0 volume=100 Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.468+01:00 level=INFO msg="emitting player metadata changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" id="mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac" title="Englishman In New York" Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.468+01:00 level=INFO msg="emitting player state changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" state=STATUS_STOPPED positionMs=0 volume=100 Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.468+01:00 level=INFO msg="emitting player metadata changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" id="mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac" title="Englishman In New York" Mar 04 20:24:03 volumiow volumio[1216]: info: ------------------------------ 12ms Mar 04 20:24:03 volumiow volumio[1216]: info: ------------------------------ 13ms Mar 04 20:24:03 volumiow volumio[1216]: info: Mar 04 20:24:03 volumiow volumio[1216]: ---------------------------- MPD announces system playlist update Mar 04 20:24:03 volumiow volumio[1216]: info: Ignoring MPD Status Update Mar 04 20:24:03 volumiow volumio[1216]: info: Mar 04 20:24:03 volumiow volumio[1216]: ---------------------------- MPD announces system playlist update Mar 04 20:24:03 volumiow volumio[1216]: info: Ignoring MPD Status Update Mar 04 20:24:03 volumiow volumio[1216]: error: updateQueue error: null Mar 04 20:24:03 volumiow volumio[1216]: info: Mar 04 20:24:03 volumiow volumio[1216]: ---------------------------- MPD announces system playlist update Mar 04 20:24:03 volumiow volumio[1216]: info: Ignoring MPD Status Update Mar 04 20:24:03 volumiow volumio[1216]: info: ------------------------------ 12ms Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand playlistinfo took 12 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand add "USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac" took 12 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::parseTrackInfo Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand play Mar 04 20:24:03 volumiow volumio[1216]: error: ControllerMpd::pushError: TypeError: Cannot read properties of undefined (reading 'split') Mar 04 20:24:03 volumiow volumio[1216]: info: ------------------------------ 14ms Mar 04 20:24:03 volumiow volumio[1216]: info: Mar 04 20:24:03 volumiow volumio[1216]: ---------------------------- MPD announces system playlist update Mar 04 20:24:03 volumiow volumio[1216]: info: Ignoring MPD Status Update Mar 04 20:24:03 volumiow volumio[1216]: info: ------------------------------ 5ms Mar 04 20:24:03 volumiow volumio[1216]: info: ------------------------------ 5ms Mar 04 20:24:03 volumiow volumio[1216]: info: ------------------------------ 4ms Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand play took 4 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: info: Mar 04 20:24:03 volumiow volumio[1216]: ---------------------------- MPD announces system playlist update Mar 04 20:24:03 volumiow volumio[1216]: info: Ignoring MPD Status Update Mar 04 20:24:03 volumiow volumio[1216]: info: ------------------------------ 0ms Mar 04 20:24:03 volumiow volumio[1216]: info: ------------------------------ 1ms Mar 04 20:24:03 volumiow volumio[1216]: info: Mar 04 20:24:03 volumiow volumio[1216]: ---------------------------- MPD announces state update: player Mar 04 20:24:03 volumiow volumio[1216]: info: ControllerMpd::getState Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand status Mar 04 20:24:03 volumiow volumio[1216]: info: Mar 04 20:24:03 volumiow volumio[1216]: ---------------------------- MPD announces state update: player Mar 04 20:24:03 volumiow volumio[1216]: info: ControllerMpd::getState Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand status Mar 04 20:24:03 volumiow volumio[1216]: info: Mar 04 20:24:03 volumiow volumio[1216]: ---------------------------- MPD announces state update: player Mar 04 20:24:03 volumiow volumio[1216]: info: ControllerMpd::getState Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand status Mar 04 20:24:03 volumiow volumio[1216]: info: Mar 04 20:24:03 volumiow volumio[1216]: ---------------------------- MPD announces state update: player Mar 04 20:24:03 volumiow volumio[1216]: info: ControllerMpd::getState Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand status Mar 04 20:24:03 volumiow volumio[1216]: info: Mar 04 20:24:03 volumiow volumio[1216]: ---------------------------- MPD announces state update: player Mar 04 20:24:03 volumiow volumio[1216]: info: ControllerMpd::getState Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand status Mar 04 20:24:03 volumiow volumio[1216]: info: Mar 04 20:24:03 volumiow volumio[1216]: ---------------------------- MPD announces state update: player Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand status took 1 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: info: ControllerMpd::getState Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand status Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand status took 1 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand status took 0 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand status took 1 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::parseState Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand playlistinfo Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::parseState Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand playlistinfo Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::parseState Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand playlistinfo Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::parseState Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand playlistinfo Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand status took 1 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand status took 1 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand playlistinfo took 0 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand playlistinfo took 0 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand playlistinfo took 0 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand playlistinfo took 0 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::parseState Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand playlistinfo Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::parseState Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::sendMpdCommand playlistinfo Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::parseTrackInfo Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::parseTrackInfo Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::parseTrackInfo Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::parseTrackInfo Mar 04 20:24:03 volumiow volumio[1216]: info: ControllerMpd::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::servicePushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: verbose: STATE SERVICE {"status":"play","position":0,"seek":844,"duration":279,"samplerate":"44.1 kHz","bitdepth":"16 bit","channels":2,"random":false,"updatedb":false,"repeat":false,"bitrate":"1025 Kbps","isStreaming":false,"title":"Englishman In New York","artist":"Sting","album":"Live In Berlin","uri":"USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac","trackType":"flac"} Mar 04 20:24:03 volumiow volumio[1216]: verbose: CURRENT POSITION 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::syncState stateService play Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::syncState currentStatus stop Mar 04 20:24:03 volumiow volumio[1216]: info: ControllerMpd::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::servicePushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: verbose: STATE SERVICE {"status":"play","position":0,"seek":844,"duration":279,"samplerate":"44.1 kHz","bitdepth":"16 bit","channels":2,"random":false,"updatedb":false,"repeat":false,"bitrate":"1025 Kbps","isStreaming":false,"title":"Englishman In New York","artist":"Sting","album":"Live In Berlin","uri":"USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac","trackType":"flac"} Mar 04 20:24:03 volumiow volumio[1216]: verbose: CURRENT POSITION 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::syncState stateService play Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::syncState currentStatus play Mar 04 20:24:03 volumiow volumio[1216]: info: Received an update from plugin. extracting info from payload Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:24:03 volumiow volumio[1216]: info: ControllerMpd::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::servicePushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: verbose: STATE SERVICE {"status":"play","position":0,"seek":844,"duration":279,"samplerate":"44.1 kHz","bitdepth":"16 bit","channels":2,"random":false,"updatedb":false,"repeat":false,"bitrate":"1025 Kbps","isStreaming":false,"title":"Englishman In New York","artist":"Sting","album":"Live In Berlin","uri":"USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac","trackType":"flac"} Mar 04 20:24:03 volumiow volumio[1216]: verbose: CURRENT POSITION 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::syncState stateService play Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::syncState currentStatus play Mar 04 20:24:03 volumiow volumio[1216]: info: Received an update from plugin. extracting info from payload Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:24:03 volumiow volumio[1216]: info: ControllerMpd::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::servicePushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: verbose: STATE SERVICE {"status":"play","position":0,"seek":844,"duration":279,"samplerate":"44.1 kHz","bitdepth":"16 bit","channels":2,"random":false,"updatedb":false,"repeat":false,"bitrate":"1025 Kbps","isStreaming":false,"title":"Englishman In New York","artist":"Sting","album":"Live In Berlin","uri":"USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac","trackType":"flac"} Mar 04 20:24:03 volumiow volumio[1216]: verbose: CURRENT POSITION 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::syncState stateService play Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::syncState currentStatus play Mar 04 20:24:03 volumiow volumio[1216]: info: Received an update from plugin. extracting info from payload Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:24:03 volumiow volumio[1216]: info: ------------------------------ 10ms Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.503+01:00 level=INFO msg="emitting player state changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" state=STATUS_PLAYING positionMs=844 volume=100 Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.503+01:00 level=INFO msg="emitting player metadata changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" id="mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac" title="Englishman In New York" Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.503+01:00 level=INFO msg="emitting player state changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" state=STATUS_PLAYING positionMs=844 volume=100 Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.503+01:00 level=INFO msg="emitting player metadata changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" id="mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac" title="Englishman In New York" Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.503+01:00 level=INFO msg="emitting player state changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" state=STATUS_PLAYING positionMs=844 volume=100 Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.503+01:00 level=INFO msg="emitting player metadata changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" id="mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac" title="Englishman In New York" Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.503+01:00 level=INFO msg="emitting player state changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" state=STATUS_PLAYING positionMs=844 volume=100 Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.503+01:00 level=INFO msg="emitting player metadata changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" id="mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac" title="Englishman In New York" Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.503+01:00 level=INFO msg="emitting player state changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" state=STATUS_PLAYING positionMs=844 volume=100 Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.503+01:00 level=INFO msg="emitting player metadata changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" id="mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac" title="Englishman In New York" Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.504+01:00 level=INFO msg="emitting player state changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" state=STATUS_PLAYING positionMs=844 volume=100 Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.504+01:00 level=INFO msg="emitting player metadata changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" id="mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac" title="Englishman In New York" Mar 04 20:24:03 volumiow volumio[1216]: info: ------------------------------ 20ms Mar 04 20:24:03 volumiow volumio[1216]: info: ------------------------------ 19ms Mar 04 20:24:03 volumiow volumio[1216]: info: ------------------------------ 19ms Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand playlistinfo took 19 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: info: sendMpdCommand playlistinfo took 19 milliseconds Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::parseTrackInfo Mar 04 20:24:03 volumiow volumio[1216]: verbose: ControllerMpd::parseTrackInfo Mar 04 20:24:03 volumiow volumio[1216]: info: ControllerMpd::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::servicePushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: verbose: STATE SERVICE {"status":"play","position":0,"seek":844,"duration":279,"samplerate":"44.1 kHz","bitdepth":"16 bit","channels":2,"random":false,"updatedb":false,"repeat":false,"bitrate":"1025 Kbps","isStreaming":false,"title":"Englishman In New York","artist":"Sting","album":"Live In Berlin","uri":"USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac","trackType":"flac"} Mar 04 20:24:03 volumiow volumio[1216]: verbose: CURRENT POSITION 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::syncState stateService play Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::syncState currentStatus play Mar 04 20:24:03 volumiow volumio[1216]: info: Received an update from plugin. extracting info from payload Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:24:03 volumiow volumio[1216]: info: ControllerMpd::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::servicePushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: verbose: STATE SERVICE {"status":"play","position":0,"seek":844,"duration":279,"samplerate":"44.1 kHz","bitdepth":"16 bit","channels":2,"random":false,"updatedb":false,"repeat":false,"bitrate":"1025 Kbps","isStreaming":false,"title":"Englishman In New York","artist":"Sting","album":"Live In Berlin","uri":"USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac","trackType":"flac"} Mar 04 20:24:03 volumiow volumio[1216]: verbose: CURRENT POSITION 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::syncState stateService play Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::syncState currentStatus play Mar 04 20:24:03 volumiow volumio[1216]: info: Received an update from plugin. extracting info from payload Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:24:03 volumiow volumio[1216]: info: CoreStateMachine::pushState Mar 04 20:24:03 volumiow volumio[1216]: info: CorePlayQueue::getTrack 1 Mar 04 20:24:03 volumiow volumio[1216]: info: CoreCommandRouter::volumioPushState Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.519+01:00 level=INFO msg="emitting player state changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" state=STATUS_PLAYING positionMs=844 volume=100 Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.519+01:00 level=INFO msg="emitting player metadata changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" id="mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac" title="Englishman In New York" Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.520+01:00 level=INFO msg="emitting player state changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" state=STATUS_PLAYING positionMs=844 volume=100 Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.520+01:00 level=INFO msg="emitting player metadata changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" id="mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac" title="Englishman In New York" Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.520+01:00 level=INFO msg="emitting player state changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" state=STATUS_PLAYING positionMs=844 volume=100 Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.520+01:00 level=INFO msg="emitting player metadata changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" id="mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac" title="Englishman In New York" Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.520+01:00 level=INFO msg="emitting player state changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" state=STATUS_PLAYING positionMs=844 volume=100 Mar 04 20:24:03 volumiow volumio5-onboarding[1759]: time=2026-03-04T20:24:03.520+01:00 level=INFO msg="emitting player metadata changed event" component=server peer="192.168.1.10:49510 @ 0xc0002cac30" id="mnt/USB/01DA612410BFC090/Sting - Live In Berlin (2010)/02 - Englishman In New York.flac" title="Englishman In New York" Mar 04 20:24:03 volumiow volumio[1216]: info: ------------------------------ 32ms Mar 04 20:24:03 volumiow volumio[1216]: info: ------------------------------ 32ms Mar 04 20:24:04 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:04 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:04 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:04 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:04 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:04 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:04 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:04 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:04 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:04 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:04 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:04 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:04 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:04 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:04 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:04 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:04 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:04 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:04 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:04 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:04 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:04 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:04 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:04 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:06 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:06 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:06 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:06 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:06 volumiow volumio[1216]: info: Discovery: Restart already pending, ignoring duplicate call Mar 04 20:24:11 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:11 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:11 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:11 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:11 volumiow volumio[1216]: info: Discovery: Restart already pending, ignoring duplicate call Mar 04 20:24:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:14 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:14 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:14 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:14 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:16 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:16 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:16 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:16 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:16 volumiow volumio[1216]: info: Discovery: Restart already pending, ignoring duplicate call Mar 04 20:24:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:19 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:19 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:19 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:19 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:22 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:22 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:22 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:22 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:22 volumiow volumio[1216]: info: Discovery: Restart already pending, ignoring duplicate call Mar 04 20:24:24 volumiow kernel: pcieport 0000:00:1c.3: AER: Multiple Correctable error message received from 0000:02:00.0 Mar 04 20:24:24 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:24 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:24 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:25 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:25 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:25 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:25 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:27 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:27 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:27 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:27 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:27 volumiow volumio[1216]: info: Discovery: Restart already pending, ignoring duplicate call Mar 04 20:24:29 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:29 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:29 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:29 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:29 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:29 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:29 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:29 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:32 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:32 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:32 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:32 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:32 volumiow volumio[1216]: info: Discovery: Restart already pending, ignoring duplicate call Mar 04 20:24:34 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:34 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:34 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:34 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:35 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:35 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:35 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:35 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:35 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:35 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:35 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:35 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:37 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:37 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:37 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:37 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:37 volumiow volumio[1216]: info: Discovery: Restart already pending, ignoring duplicate call Mar 04 20:24:40 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:40 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:40 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:40 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:40 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:40 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:40 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:40 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:40 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:40 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:40 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:40 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:42 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:42 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:42 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:42 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:42 volumiow volumio[1216]: info: Discovery: Restart already pending, ignoring duplicate call Mar 04 20:24:45 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:45 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:45 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:45 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:45 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:45 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:45 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:45 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:45 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:45 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:45 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:45 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:45 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:45 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:45 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:45 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:45 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:45 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:45 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:45 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:47 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:47 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:47 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:47 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:47 volumiow volumio[1216]: info: Discovery: Restart already pending, ignoring duplicate call Mar 04 20:24:50 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:50 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:50 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:50 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:50 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:50 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:50 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:50 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:52 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:52 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:52 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:52 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:52 volumiow volumio[1216]: info: Discovery: Restart already pending, ignoring duplicate call Mar 04 20:24:55 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:55 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:55 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:55 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:55 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:55 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:55 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:55 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:56 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:56 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:57 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:57 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:24:57 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:24:57 volumiow volumio[1216]: info: Discovery: Restart already pending, ignoring duplicate call Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:57 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:57 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:58 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:58 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:58 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:58 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:58 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:58 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:58 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:58 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:58 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:58 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:58 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:58 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:58 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:58 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:58 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:58 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:59 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:59 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:59 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:59 volumiow kernel: pcieport 0000:00:1c.3: AER: Multiple Correctable error message received from 0000:02:00.0 Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:59 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:59 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:59 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:24:59 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:24:59 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:00 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:00 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID) Mar 04 20:25:00 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000080/00002000 Mar 04 20:25:00 volumiow kernel: ath9k 0000:02:00.0: [ 7] BadDLLP Mar 04 20:25:00 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:00 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:00 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:00 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:00 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:00 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:00 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:00 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:00 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:00 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:00 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:00 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:01 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:01 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:01 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:01 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:02 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:02 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:02 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:02 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:02 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:02 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:02 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:02 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:02 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:25:02 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:25:02 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:25:02 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:25:02 volumiow volumio[1216]: info: Discovery: Restart already pending, ignoring duplicate call Mar 04 20:25:03 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:03 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:03 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:03 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:03 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:03 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:03 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:03 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:03 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:03 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:03 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:03 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:03 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:03 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:03 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:03 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:03 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:03 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:03 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:03 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:03 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:03 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:03 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:03 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:05 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:05 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:05 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:05 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:05 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:05 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:05 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:05 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:05 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:05 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:05 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:05 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:05 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:05 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:05 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:05 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:07 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:25:07 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:25:07 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:25:07 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:25:07 volumiow volumio[1216]: info: Discovery: Restart already pending, ignoring duplicate call Mar 04 20:25:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:10 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:10 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:10 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:10 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:11 volumiow systemd[1]: Starting setdatetime-helper.service - Time Synchronization Helper Service... Mar 04 20:25:12 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:25:12 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:25:12 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:25:12 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:25:12 volumiow volumio[1216]: info: Discovery: Restart already pending, ignoring duplicate call Mar 04 20:25:13 volumiow systemd[1]: setdatetime-helper.service: Deactivated successfully. Mar 04 20:25:13 volumiow systemd[1]: Finished setdatetime-helper.service - Time Synchronization Helper Service. Mar 04 20:25:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:13 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:13 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:13 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:13 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:15 volumiow kernel: pcieport 0000:00:1c.3: AER: Correctable error message received from 0000:02:00.0 Mar 04 20:25:15 volumiow kernel: ath9k 0000:02:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) Mar 04 20:25:15 volumiow kernel: ath9k 0000:02:00.0: device [168c:0030] error status/mask=00000001/00002000 Mar 04 20:25:15 volumiow kernel: ath9k 0000:02:00.0: [ 0] RxErr Mar 04 20:25:17 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:25:17 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:25:17 volumiow volumio[1216]: info: Discovery: Browse raised the following error Error: getaddrinfo -3007 Mar 04 20:25:17 volumiow volumio[1216]: info: Discovery: Restarting Browsing Mar 04 20:25:17 volumiow volumio[1216]: info: Discovery: Restart already pending, ignoring duplicate call Mar 04 20:25:18 volumiow volumio[1216]: |||||||||||||||||||||||| WARNING: FATAL ERROR ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| Mar 04 20:25:18 volumiow volumio[1216]: TypeError: Cannot read properties of null (reading 'slice') Mar 04 20:25:18 volumiow volumio[1216]: at download (/volumio/app/plugins/miscellanea/albumart/albumart.js:718:41) Mar 04 20:25:18 volumiow volumio[1216]: at ClientRequest. (/volumio/app/plugins/miscellanea/albumart/albumart.js:728:7) Mar 04 20:25:18 volumiow volumio[1216]: at Object.onceWrapper (node:events:629:26) Mar 04 20:25:18 volumiow volumio[1216]: at ClientRequest.emit (node:events:514:28) Mar 04 20:25:18 volumiow volumio[1216]: at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:693:27) Mar 04 20:25:18 volumiow volumio[1216]: at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17) Mar 04 20:25:18 volumiow volumio[1216]: at TLSSocket.socketOnData (node:_http_client:535:22) Mar 04 20:25:18 volumiow volumio[1216]: at TLSSocket.emit (node:events:514:28) Mar 04 20:25:18 volumiow volumio[1216]: at addChunk (node:internal/streams/readable:343:12) Mar 04 20:25:18 volumiow volumio[1216]: at readableAddChunk (node:internal/streams/readable:316:9) Mar 04 20:25:18 volumiow volumio[1216]: at Readable.push (node:internal/streams/readable:253:10) Mar 04 20:25:18 volumiow volumio[1216]: at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23) Mar 04 20:25:18 volumiow volumio[1216]: ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| Mar 04 20:25:18 volumiow sudo[5389]: volumio : PWD=/ ; USER=root ; COMMAND=/bin/journalctl '--since=2026-03-04 20:24' Mar 04 20:25:18 volumiow sudo[5389]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" VOLUMIO_BUILD_VERSION="a78d359cf1dc63ac74e9d151015afd30d31a709a" VOLUMIO_FE_VERSION="35f8f4439f0076a62fefa72fd80b70701b3d6cbd" VOLUMIO_FE3_VERSION="bcca17b6b6b26edfb999e6fd7da1b222a88a61d2" VOLUMIO_BE_VERSION="c1ffe93b2136013fc1b5903a4ed7e3f34e0a7bec" VOLUMIO_ARCH="x64" VOLUMIO_VARIANT="volumio" VOLUMIO_TEST="FALSE" VOLUMIO_BUILD_DATE="Thu Feb 5 14:31:57 UTC 2026" VOLUMIO_VERSION="4.096" VOLUMIO_HARDWARE="x86_amd64" VOLUMIO_DEVICENAME="x86_64" VOLUMIO_HASH="6759e875c98b942866984e844891d6c1"