Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upWifi card firmware not loading after Xen update (Qubes 3.2) #3217
Comments
andrewdavidwong
added
bug
C: other
labels
Oct 27, 2017
andrewdavidwong
added this to the Release 3.2 updates milestone
Oct 27, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
aoikonomopoulos
Oct 31, 2017
Had the same issue here, it was solved by reverting to 4.6.6-30. AFAICT from the xen-4.6 branch of the qubes-vmm-xen repo, the changes made from -30 to -33 that could be relevant are QubesOS/qubes-vmm-xen@d640b21 and, more likely, QubesOS/qubes-vmm-xen@3b37906. It's not immediately apparent to me which of the patches included in the latter would be the likely culprit.
aoikonomopoulos
commented
Oct 31, 2017
|
Had the same issue here, it was solved by reverting to 4.6.6-30. AFAICT from the xen-4.6 branch of the qubes-vmm-xen repo, the changes made from -30 to -33 that could be relevant are QubesOS/qubes-vmm-xen@d640b21 and, more likely, QubesOS/qubes-vmm-xen@3b37906. It's not immediately apparent to me which of the patches included in the latter would be the likely culprit. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Oct 31, 2017
Member
Do you have any more messages in dom0 kernel log, or Xen log (/var/log/xen/console/hypervisor.log)?
|
Do you have any more messages in dom0 kernel log, or Xen log ( |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
aoikonomopoulos
Oct 31, 2017
Nothing that stands out on the dom0 log (vimdiffing a boot when I was facing the issue and a current one after reverting back to 4.6.6-30).
Unfortunately I hadn't realized it was a xen issue when I was trying to work around it last week, so I only have messages from the kernel/firmware combinations that actually managed to load the firmware (though for all I know it was random). The firmware would crash soon (i.e. less than a minute) afterwards, leading the driver to request a hardware restart, "fail to run init UCODE" and it all went downhill from there.
But this all seems like a red herring. Perhaps @roasting223 have something more useful in their dom0 log? I'd offer to upgrade again and double-check (now that I know what to look for), but downgrading the xen packages was not terribly straightforward (the procedure described in https://www.qubes-os.org/doc/software-update-dom0/ failed to download the package for me), so not sure if I can spend the time this week.
aoikonomopoulos
commented
Oct 31, 2017
|
Nothing that stands out on the dom0 log (vimdiffing a boot when I was facing the issue and a current one after reverting back to 4.6.6-30). Unfortunately I hadn't realized it was a xen issue when I was trying to work around it last week, so I only have messages from the kernel/firmware combinations that actually managed to load the firmware (though for all I know it was random). The firmware would crash soon (i.e. less than a minute) afterwards, leading the driver to request a hardware restart, "fail to run init UCODE" and it all went downhill from there. But this all seems like a red herring. Perhaps @roasting223 have something more useful in their dom0 log? I'd offer to upgrade again and double-check (now that I know what to look for), but downgrading the xen packages was not terribly straightforward (the procedure described in https://www.qubes-os.org/doc/software-update-dom0/ failed to download the package for me), so not sure if I can spend the time this week. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
cc @HW42 |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
roasting223
Nov 1, 2017
dmesg from dom0, do you need anything else?
[ 0.000000] Linux version 4.9.45-21.pvops.qubes.x86_64 (user@) (gcc version 5.3.1 20160406 (Red Hat 5.3.1-6) (GCC) ) #1 SMP Tue Aug 29 14:21:02 UTC 2017
[ 0.000000] Command line: placeholder root=/dev/mapper/qubes_dom0-root ro rd.luks.uuid=luks-5b671ec1-b0b5-4397-9646-2c01689bd483 rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.preliminary_hw_support=1 rd.driver.pre=scsi_dh_rdac rhgb quiet
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ 0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
[ 0.000000] x86/fpu: Using 'eager' FPU context switches.
[ 0.000000] Released 0 page(s)
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] Xen: [mem 0x0000000000000000-0x000000000009cfff] usable
[ 0.000000] Xen: [mem 0x000000000009d000-0x00000000000fffff] reserved
[ 0.000000] Xen: [mem 0x0000000000100000-0x000000000fffffff] usable
[ 0.000000] Xen: [mem 0x0000000010000000-0x000000001000afff] reserved
[ 0.000000] Xen: [mem 0x000000001000b000-0x000000009f062fff] usable
[ 0.000000] Xen: [mem 0x000000009f063000-0x00000000acbfefff] reserved
[ 0.000000] Xen: [mem 0x00000000acbff000-0x00000000acd7efff] ACPI NVS
[ 0.000000] Xen: [mem 0x00000000acd7f000-0x00000000acdfefff] ACPI data
[ 0.000000] Xen: [mem 0x00000000acdff000-0x00000000afffffff] reserved
[ 0.000000] Xen: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
[ 0.000000] Xen: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] Xen: [mem 0x00000000fed08000-0x00000000fed08fff] reserved
[ 0.000000] Xen: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
[ 0.000000] Xen: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[ 0.000000] Xen: [mem 0x00000000fee00000-0x00000000feefffff] reserved
[ 0.000000] Xen: [mem 0x00000000ffa00000-0x00000000ffffffff] reserved
[ 0.000000] Xen: [mem 0x0000000100000000-0x000000016100afff] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] SMBIOS 2.7 present.
[ 0.000000] DMI: LENOVO 20CLS01104/20CLS01104, BIOS N10ET46W (1.25 ) 11/28/2016
[ 0.000000] Hypervisor detected: Xen
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] e820: last_pfn = 0x16100b max_arch_pfn = 0x400000000
[ 0.000000] MTRR: Disabled
[ 0.000000] x86/PAT: MTRRs disabled, skipping PAT initialization too.
[ 0.000000] x86/PAT: Configuration [0-7]: WB WT UC- UC WC WP UC UC
[ 0.000000] e820: last_pfn = 0x9f063 max_arch_pfn = 0x400000000
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] Base memory trampoline at [ffff880000097000] 97000 size 24576
[ 0.000000] BRK [0x020a5000, 0x020a5fff] PGTABLE
[ 0.000000] BRK [0x020a6000, 0x020a6fff] PGTABLE
[ 0.000000] BRK [0x020a7000, 0x020a7fff] PGTABLE
[ 0.000000] BRK [0x020a8000, 0x020a8fff] PGTABLE
[ 0.000000] BRK [0x020a9000, 0x020a9fff] PGTABLE
[ 0.000000] BRK [0x020aa000, 0x020aafff] PGTABLE
[ 0.000000] BRK [0x020ab000, 0x020abfff] PGTABLE
[ 0.000000] BRK [0x020ac000, 0x020acfff] PGTABLE
[ 0.000000] BRK [0x020ad000, 0x020adfff] PGTABLE
[ 0.000000] BRK [0x020ae000, 0x020aefff] PGTABLE
[ 0.000000] BRK [0x020af000, 0x020affff] PGTABLE
[ 0.000000] BRK [0x020b0000, 0x020b0fff] PGTABLE
[ 0.000000] RAMDISK: [mem 0x04000000-0x053b2fff]
[ 0.000000] ACPI: Early table checksum verification disabled
[ 0.000000] ACPI: RSDP 0x00000000000F0120 000024 (v02 LENOVO)
[ 0.000000] ACPI: XSDT 0x00000000ACDFE1C0 0000EC (v01 LENOVO TP-N10 00001250 PTEC 00000002)
[ 0.000000] ACPI: FACP 0x00000000ACDF8000 00010C (v05 LENOVO TP-N10 00001250 PTEC 00000002)
[ 0.000000] ACPI: DSDT 0x00000000ACDE3000 010E44 (v02 LENOVO TP-N10 00001250 INTL 20120711)
[ 0.000000] ACPI: FACS 0x00000000ACD68000 000040
[ 0.000000] ACPI: SLIC 0x00000000ACDFD000 000176 (v01 LENOVO TP-N10 00001250 PTEC 00000001)
[ 0.000000] ACPI: ASF! 0x00000000ACDFC000 0000A5 (v32 LENOVO TP-N10 00001250 PTEC 00000002)
[ 0.000000] ACPI: HPET 0x00000000ACDFB000 000038 (v01 LENOVO TP-N10 00001250 PTEC 00000002)
[ 0.000000] ACPI: ECDT 0x00000000ACDFA000 000052 (v01 LENOVO TP-N10 00001250 PTEC 00000002)
[ 0.000000] ACPI: APIC 0x00000000ACDF7000 000098 (v01 LENOVO TP-N10 00001250 PTEC 00000002)
[ 0.000000] ACPI: MCFG 0x00000000ACDF6000 00003C (v01 LENOVO TP-N10 00001250 PTEC 00000002)
[ 0.000000] ACPI: SSDT 0x00000000ACDF5000 000033 (v01 LENOVO TP-SSDT1 00000100 INTL 20120711)
[ 0.000000] ACPI: SSDT 0x00000000ACDF4000 000486 (v01 LENOVO TP-SSDT2 00000200 INTL 20120711)
[ 0.000000] ACPI: SSDT 0x00000000ACDE2000 0009CB (v01 LENOVO SataAhci 00001000 INTL 20120711)
[ 0.000000] ACPI: SSDT 0x00000000ACDE1000 000152 (v01 LENOVO Rmv_Batt 00001000 INTL 20120711)
[ 0.000000] ACPI: SSDT 0x00000000ACDE0000 000691 (v01 LENOVO Cpu0Ist 00003000 INTL 20120711)
[ 0.000000] ACPI: SSDT 0x00000000ACDDF000 000B74 (v02 LENOVO CpuSsdt 00003000 INTL 20120711)
[ 0.000000] ACPI: SSDT 0x00000000ACDDE000 000369 (v02 LENOVO CtdpB 00001000 INTL 20120711)
[ 0.000000] ACPI: SSDT 0x00000000ACDDC000 001475 (v01 LENOVO SaSsdt 00003000 INTL 20120711)
[ 0.000000] ACPI: SSDT 0x00000000ACDDB000 000394 (v02 LENOVO CppcTabl 00001000 INTL 20120711)
[ 0.000000] ACPI: PCCT 0x00000000ACDDA000 00006E (v05 LENOVO TP-N10 00001250 PTEC 00000002)
[ 0.000000] ACPI: SSDT 0x00000000ACDD9000 000AC4 (v02 LENOVO Cpc_Tabl 00001000 INTL 20120711)
[ 0.000000] ACPI: TCPA 0x00000000ACDD8000 000032 (v02 PTL LENOVO 06040000 LNVO 00000001)
[ 0.000000] ACPI: SSDT 0x00000000ACDD7000 0006B0 (v02 Intel_ TpmTable 00001000 INTL 20120711)
[ 0.000000] ACPI: UEFI 0x00000000ACDD6000 000042 (v01 LENOVO TP-N10 00001250 PTEC 00000002)
[ 0.000000] ACPI: MSDM 0x00000000ACCB1000 000055 (v03 LENOVO TP-N10 00001250 PTEC 00000002)
[ 0.000000] ACPI: BATB 0x00000000ACDD5000 000046 (v01 LENOVO TP-N10 00001250 PTEC 00000002)
[ 0.000000] ACPI: FPDT 0x00000000ACDD4000 000064 (v01 LENOVO TP-N10 00001250 PTEC 00000002)
[ 0.000000] ACPI: UEFI 0x00000000ACDD3000 00030A (v01 LENOVO TP-N10 00001250 PTEC 00000002)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] Setting APIC routing to Xen PV.
[ 0.000000] NUMA turned off
[ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000016100afff]
[ 0.000000] NODE_DATA(0) allocated [mem 0x9e869000-0x9e87afff]
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000000001000-0x0000000000ffffff]
[ 0.000000] DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
[ 0.000000] Normal [mem 0x0000000100000000-0x000000016100afff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000001000-0x000000000009cfff]
[ 0.000000] node 0: [mem 0x0000000000100000-0x000000000fffffff]
[ 0.000000] node 0: [mem 0x000000001000b000-0x000000009f062fff]
[ 0.000000] node 0: [mem 0x0000000100000000-0x000000016100afff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x000000016100afff]
[ 0.000000] On node 0 totalpages: 1048575
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 21 pages reserved
[ 0.000000] DMA zone: 3996 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 10114 pages used for memmap
[ 0.000000] DMA32 zone: 647256 pages, LIFO batch:31
[ 0.000000] Normal zone: 6209 pages used for memmap
[ 0.000000] Normal zone: 397323 pages, LIFO batch:31
[ 0.000000] p2m virtual area at ffffc90000000000, size is c00000
[ 0.000000] Remapped 397323 page(s)
[ 0.000000] Reserving Intel graphics memory at 0x00000000ae000000-0x00000000afffffff
[ 0.000000] ACPI: PM-Timer IO Port: 0x1808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-39
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a301 base: 0xfed00000
[ 0.000000] smpboot: Allowing 8 CPUs, 4 hotplug CPUs
[ 0.000000] e820: [mem 0xb0000000-0xf7ffffff] available for PCI devices
[ 0.000000] Booting paravirtualized kernel on Xen
[ 0.000000] Xen version: 4.6.6 (preserve-AD)
[ 0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns
[ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:8 nr_node_ids:1
[ 0.000000] percpu: Embedded 36 pages/cpu @ffff880160e00000 s107288 r8192 d31976 u262144
[ 0.000000] pcpu-alloc: s107288 r8192 d31976 u262144 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 6 7
[ 0.000000] xen: PV spinlocks enabled
[ 0.000000] PV qspinlock hash table entries: 256 (order: 0, 4096 bytes)
[ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 1032167
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line: placeholder root=/dev/mapper/qubes_dom0-root ro rd.luks.uuid=luks-5b671ec1-b0b5-4397-9646-2c01689bd483 rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.preliminary_hw_support=1 rd.driver.pre=scsi_dh_rdac rhgb quiet
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] software IO TLB [mem 0x15ce00000-0x160e00000] (64MB) mapped at [ffff88015ce00000-ffff880160dfffff]
[ 0.000000] Memory: 4005540K/4194300K available (8077K kernel code, 1402K rwdata, 3384K rodata, 2004K init, 1308K bss, 188760K reserved, 0K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] Build-time adjustment of leaf fanout to 64.
[ 0.000000] RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4
[ 0.000000] Using NULL legacy PIC
[ 0.000000] NR_IRQS:4352 nr_irqs:728 0
[ 0.000000] xen:events: Using FIFO-based ABI
[ 0.000000] xen: --> pirq=1 -> irq=1 (gsi=1)
[ 0.000000] xen: --> pirq=2 -> irq=2 (gsi=2)
[ 0.000000] xen: --> pirq=3 -> irq=3 (gsi=3)
[ 0.000000] xen: --> pirq=4 -> irq=4 (gsi=4)
[ 0.000000] xen: --> pirq=5 -> irq=5 (gsi=5)
[ 0.000000] xen: --> pirq=6 -> irq=6 (gsi=6)
[ 0.000000] xen: --> pirq=7 -> irq=7 (gsi=7)
[ 0.000000] xen: --> pirq=8 -> irq=8 (gsi=8)
[ 0.000000] xen: --> pirq=9 -> irq=9 (gsi=9)
[ 0.000000] xen: --> pirq=10 -> irq=10 (gsi=10)
[ 0.000000] xen: --> pirq=11 -> irq=11 (gsi=11)
[ 0.000000] xen: --> pirq=12 -> irq=12 (gsi=12)
[ 0.000000] xen: --> pirq=13 -> irq=13 (gsi=13)
[ 0.000000] xen: --> pirq=14 -> irq=14 (gsi=14)
[ 0.000000] xen: --> pirq=15 -> irq=15 (gsi=15)
[ 0.000000] Offload RCU callbacks from all CPUs
[ 0.000000] Offload RCU callbacks from CPUs: 0-3.
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] clocksource: xen: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
[ 0.000000] Xen: using vcpuop timer interface
[ 0.000000] installing Xen timer for CPU 0
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] tsc: Detected 2294.470 MHz processor
[ 4.722230] Calibrating delay loop (skipped), value calculated using timer frequency.. 4589.51 BogoMIPS (lpj=2294756)
[ 4.722232] pid_max: default: 32768 minimum: 301
[ 4.722251] ACPI: Core revision 20160831
[ 4.783682] ACPI: 12 ACPI AML tables successfully acquired and loaded
[ 4.783977] Security Framework initialized
[ 4.783978] Yama: becoming mindful.
[ 4.783985] AppArmor: AppArmor disabled by boot time parameter
[ 4.784642] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
[ 4.785733] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 4.786138] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
[ 4.786149] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)
[ 4.786549] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[ 4.786550] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[ 4.786552] CPU: Physical Processor ID: 0
[ 4.786552] CPU: Processor Core ID: 0
[ 4.786556] mce: CPU supports 2 MCE banks
[ 4.786574] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
[ 4.786574] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4
[ 4.786906] Freeing SMP alternatives memory: 32K
[ 4.789320] ftrace: allocating 30494 entries in 120 pages
[ 4.802156] cpu 0 spinlock event irq 41
[ 4.802161] smpboot: Max logical packages: 1
[ 4.802163] VPMU disabled by hypervisor.
[ 4.802174] Performance Events: Broadwell events, PMU not available due to virtualization, using software events only.
[ 4.802935] NMI watchdog: disabled (cpu0): hardware events not enabled
[ 4.802935] NMI watchdog: Shutting down hard lockup detector on all cpus
[ 4.803048] installing Xen timer for CPU 1
[ 4.803313] cpu 1 spinlock event irq 53
[ 4.803433] installing Xen timer for CPU 2
[ 4.803651] cpu 2 spinlock event irq 60
[ 4.803764] installing Xen timer for CPU 3
[ 4.803953] cpu 3 spinlock event irq 67
[ 4.803961] x86: Booted up 1 node, 4 CPUs
[ 4.804231] devtmpfs: initialized
[ 4.804289] x86/mm: Memory block size: 128MB
[ 4.811183] PM: Registering ACPI NVS region [mem 0xacbff000-0xacd7efff] (1572864 bytes)
[ 4.811263] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
[ 4.811279] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 4.811349] atomic64_test: passed for x86-64 platform with CX8 and with SSE
[ 4.811351] pinctrl core: initialized pinctrl subsystem
[ 4.811406] RTC time: 9:33:38, date: 11/01/17
[ 4.811496] NET: Registered protocol family 16
[ 4.811504] xen:grant_table: Grant tables using version 1 layout
[ 4.811512] Grant table initialized
[ 4.811921] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[ 4.811922] ACPI: bus type PCI registered
[ 4.812178] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
[ 4.812180] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
[ 4.820042] PCI: Using configuration type 1 for base access
[ 4.823548] ACPI: Added _OSI(Module Device)
[ 4.823550] ACPI: Added _OSI(Processor Device)
[ 4.823551] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 4.823552] ACPI: Added _OSI(Processor Aggregator Device)
[ 4.823560] ACPI : EC: EC started
[ 4.823560] ACPI : EC: interrupt blocked
[ 4.824659] ACPI: \: Used as first EC
[ 4.824661] ACPI: \: GPE=0x25, EC_CMD/EC_SC=0x66, EC_DATA=0x62
[ 4.824662] ACPI: \: Used as boot ECDT EC to handle transactions
[ 4.824859] xen: registering gsi 9 triggering 0 polarity 0
[ 4.830908] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 4.834806] random: fast init done
[ 4.837339] ACPI: Dynamic OEM Table Load:
[ 4.837349] ACPI: SSDT 0xFFFF88015BE7C000 000436 (v01 PmRef Cpu0Cst 00003001 INTL 20120711)
[ 4.837934] ACPI: Dynamic OEM Table Load:
[ 4.837943] ACPI: SSDT 0xFFFF88015BE7B000 0005AA (v01 PmRef ApIst 00003000 INTL 20120711)
[ 4.838395] ACPI: Dynamic OEM Table Load:
[ 4.838402] ACPI: SSDT 0xFFFF88015BED0000 000119 (v02 PmRef ApCst 00003000 INTL 20120711)
[ 4.839528] ACPI : EC: EC stopped
[ 4.839529] ACPI : EC: EC started
[ 4.839529] ACPI : EC: interrupt blocked
[ 4.839704] ACPI: \_SB_.PCI0.LPC_.EC__: Used as first EC
[ 4.839706] ACPI: \_SB_.PCI0.LPC_.EC__: GPE=0x25, EC_CMD/EC_SC=0x66, EC_DATA=0x62
[ 4.839707] ACPI: \_SB_.PCI0.LPC_.EC__: Used as boot DSDT EC to handle transactions
[ 4.839707] ACPI: Interpreter enabled
[ 4.839735] ACPI: (supports S0 S3 S5)
[ 4.839736] ACPI: Using IOAPIC for interrupt routing
[ 4.839767] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 4.842883] ACPI: Power Resource [PUBS] (on)
[ 4.843855] acpi PNP0C0A:01: ACPI dock station (docks/bays count: 1)
[ 4.844216] ACPI: Power Resource [NVP3] (on)
[ 4.844242] ACPI: Power Resource [NVP2] (on)
[ 4.848699] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11)
[ 4.848800] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *9 10 11)
[ 4.848898] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 *10 11)
[ 4.848994] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11)
[ 4.849091] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 *7 9 10 11)
[ 4.849170] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11) *0, disabled.
[ 4.849268] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 *6 7 9 10 11)
[ 4.849368] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 *11)
[ 4.849458] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3f])
[ 4.849462] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[ 4.849613] acpi PNP0A08:00: _OSC: platform does not support [PCIeCapability]
[ 4.849687] acpi PNP0A08:00: _OSC: not requesting control; platform does not support [PCIeCapability]
[ 4.849689] acpi PNP0A08:00: _OSC: OS requested [PCIeHotplug PME AER PCIeCapability]
[ 4.849690] acpi PNP0A08:00: _OSC: platform willing to grant [PCIeHotplug PME AER]
[ 4.849691] acpi PNP0A08:00: _OSC failed (AE_SUPPORT); disabling ASPM
[ 4.849785] PCI host bridge to bus 0000:00
[ 4.849787] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window]
[ 4.849788] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window]
[ 4.849789] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
[ 4.849790] pci_bus 0000:00: root bus resource [mem 0xb0000000-0xfebfffff window]
[ 4.849791] pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed4bfff window]
[ 4.849793] pci_bus 0000:00: root bus resource [bus 00-3f]
[ 4.849808] pci 0000:00:00.0: [8086:1604] type 00 class 0x060000
[ 4.849975] pci 0000:00:02.0: [8086:1616] type 00 class 0x030000
[ 4.850008] pci 0000:00:02.0: reg 0x10: [mem 0xe0000000-0xe0ffffff 64bit]
[ 4.850026] pci 0000:00:02.0: reg 0x18: [mem 0xc0000000-0xdfffffff 64bit pref]
[ 4.850038] pci 0000:00:02.0: reg 0x20: [io 0x3000-0x303f]
[ 4.850204] pci 0000:00:03.0: [8086:160c] type 00 class 0x040300
[ 4.850227] pci 0000:00:03.0: reg 0x10: [mem 0xe1230000-0xe1233fff 64bit]
[ 4.850458] pci 0000:00:14.0: [8086:9cb1] type 00 class 0x0c0330
[ 4.850492] pci 0000:00:14.0: reg 0x10: [mem 0xe1220000-0xe122ffff 64bit]
[ 4.850616] pci 0000:00:14.0: PME# supported from D3hot D3cold
[ 4.850659] pci 0000:00:14.0: System wakeup disabled by ACPI
[ 4.850729] pci 0000:00:16.0: [8086:9cba] type 00 class 0x078000
[ 4.850765] pci 0000:00:16.0: reg 0x10: [mem 0xe1239000-0xe123901f 64bit]
[ 4.850900] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
[ 4.851016] pci 0000:00:19.0: [8086:15a2] type 00 class 0x020000
[ 4.851044] pci 0000:00:19.0: reg 0x10: [mem 0xe1200000-0xe121ffff]
[ 4.851059] pci 0000:00:19.0: reg 0x14: [mem 0xe123e000-0xe123efff]
[ 4.851074] pci 0000:00:19.0: reg 0x18: [io 0x3080-0x309f]
[ 4.851192] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
[ 4.851229] pci 0000:00:19.0: System wakeup disabled by ACPI
[ 4.851301] pci 0000:00:1b.0: [8086:9ca0] type 00 class 0x040300
[ 4.851334] pci 0000:00:1b.0: reg 0x10: [mem 0xe1234000-0xe1237fff 64bit]
[ 4.851464] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 4.851563] pci 0000:00:1c.0: [8086:9c9a] type 01 class 0x060400
[ 4.851698] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 4.851731] pci 0000:00:1c.0: Enabling MPC IRBNCE
[ 4.851734] pci 0000:00:1c.0: Intel PCH root port ACS workaround enabled
[ 4.851882] pci 0000:00:1c.1: [8086:9c94] type 01 class 0x060400
[ 4.852021] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
[ 4.852052] pci 0000:00:1c.1: Enabling MPC IRBNCE
[ 4.852055] pci 0000:00:1c.1: Intel PCH root port ACS workaround enabled
[ 4.852126] pci 0000:00:1c.1: System wakeup disabled by ACPI
[ 4.852212] pci 0000:00:1d.0: [8086:9ca6] type 00 class 0x0c0320
[ 4.852244] pci 0000:00:1d.0: reg 0x10: [mem 0xe123d000-0xe123d3ff]
[ 4.852412] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
[ 4.852454] pci 0000:00:1d.0: System wakeup disabled by ACPI
[ 4.852530] pci 0000:00:1f.0: [8086:9cc3] type 00 class 0x060100
[ 4.852817] pci 0000:00:1f.2: [8086:9c83] type 00 class 0x010601
[ 4.852844] pci 0000:00:1f.2: reg 0x10: [io 0x30a8-0x30af]
[ 4.852858] pci 0000:00:1f.2: reg 0x14: [io 0x30b4-0x30b7]
[ 4.852872] pci 0000:00:1f.2: reg 0x18: [io 0x30a0-0x30a7]
[ 4.852886] pci 0000:00:1f.2: reg 0x1c: [io 0x30b0-0x30b3]
[ 4.852900] pci 0000:00:1f.2: reg 0x20: [io 0x3060-0x307f]
[ 4.852915] pci 0000:00:1f.2: reg 0x24: [mem 0xe123c000-0xe123c7ff]
[ 4.852991] pci 0000:00:1f.2: PME# supported from D3hot
[ 4.853085] pci 0000:00:1f.3: [8086:9ca2] type 00 class 0x0c0500
[ 4.853113] pci 0000:00:1f.3: reg 0x10: [mem 0xe1238000-0xe12380ff 64bit]
[ 4.853154] pci 0000:00:1f.3: reg 0x20: [io 0xefa0-0xefbf]
[ 4.853282] pci 0000:00:1f.6: [8086:9ca4] type 00 class 0x118000
[ 4.853327] pci 0000:00:1f.6: reg 0x10: [mem 0xe123b000-0xe123bfff 64bit]
[ 4.853723] pci 0000:02:00.0: [10ec:5227] type 00 class 0xff0000
[ 4.853799] pci 0000:02:00.0: reg 0x10: [mem 0xe1100000-0xe1100fff]
[ 4.854314] pci 0000:02:00.0: supports D1 D2
[ 4.854315] pci 0000:02:00.0: PME# supported from D1 D2 D3hot D3cold
[ 4.857528] pci 0000:00:1c.0: PCI bridge to [bus 02]
[ 4.857537] pci 0000:00:1c.0: bridge window [mem 0xe1100000-0xe11fffff]
[ 4.858226] pci 0000:03:00.0: [8086:095b] type 00 class 0x028000
[ 4.858963] pci 0000:03:00.0: reg 0x10: [mem 0xe1000000-0xe1001fff 64bit]
[ 4.862781] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
[ 4.867133] pci 0000:00:1c.1: PCI bridge to [bus 03]
[ 4.867143] pci 0000:00:1c.1: bridge window [mem 0xe1000000-0xe10fffff]
[ 4.867350] xen: registering gsi 13 triggering 1 polarity 0
[ 4.868322] ACPI: Enabled 4 GPEs in block 00 to 7F
[ 4.868408] ACPI : EC: interrupt unblocked
[ 4.868420] ACPI : EC: event unblocked
[ 4.868429] ACPI: \_SB_.PCI0.LPC_.EC__: GPE=0x25, EC_CMD/EC_SC=0x66, EC_DATA=0x62
[ 4.868430] ACPI: \_SB_.PCI0.LPC_.EC__: Used as boot DSDT EC to handle transactions and events
[ 4.868566] xen:balloon: Initialising balloon driver
[ 4.868597] xen_balloon: Initialising balloon driver
[ 4.868682] vgaarb: setting as boot device: PCI:0000:00:02.0
[ 4.868683] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
[ 4.868686] vgaarb: loaded
[ 4.868686] vgaarb: bridge control possible 0000:00:02.0
[ 4.868772] SCSI subsystem initialized
[ 4.868852] libata version 3.00 loaded.
[ 4.868878] ACPI: bus type USB registered
[ 4.868893] usbcore: registered new interface driver usbfs
[ 4.868902] usbcore: registered new interface driver hub
[ 4.868926] usbcore: registered new device driver usb
[ 4.869063] PCI: Using ACPI for IRQ routing
[ 4.872542] PCI: pci_cache_line_size set to 64 bytes
[ 4.872913] e820: reserve RAM buffer [mem 0x0009d000-0x0009ffff]
[ 4.872914] e820: reserve RAM buffer [mem 0x9f063000-0x9fffffff]
[ 4.872915] e820: reserve RAM buffer [mem 0x16100b000-0x163ffffff]
[ 4.873009] NetLabel: Initializing
[ 4.873009] NetLabel: domain hash size = 128
[ 4.873010] NetLabel: protocols = UNLABELED CIPSOv4
[ 4.873022] NetLabel: unlabeled traffic allowed by default
[ 4.873150] clocksource: Switched to clocksource xen
[ 4.880076] VFS: Disk quotas dquot_6.6.0
[ 4.880095] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 4.880116] hugetlbfs: disabling because there are no supported hugepage sizes
[ 4.880163] pnp: PnP ACPI init
[ 4.880716] system 00:00: [mem 0x00000000-0x0009ffff] could not be reserved
[ 4.880717] system 00:00: [mem 0x000c0000-0x000c3fff] could not be reserved
[ 4.880719] system 00:00: [mem 0x000c4000-0x000c7fff] could not be reserved
[ 4.880720] system 00:00: [mem 0x000c8000-0x000cbfff] could not be reserved
[ 4.880721] system 00:00: [mem 0x000cc000-0x000cffff] could not be reserved
[ 4.880722] system 00:00: [mem 0x000d0000-0x000d3fff] could not be reserved
[ 4.880723] system 00:00: [mem 0x000d4000-0x000d7fff] could not be reserved
[ 4.880724] system 00:00: [mem 0x000d8000-0x000dbfff] could not be reserved
[ 4.880725] system 00:00: [mem 0x000dc000-0x000dffff] could not be reserved
[ 4.880726] system 00:00: [mem 0x000e0000-0x000e3fff] could not be reserved
[ 4.880728] system 00:00: [mem 0x000e4000-0x000e7fff] could not be reserved
[ 4.880729] system 00:00: [mem 0x000e8000-0x000ebfff] could not be reserved
[ 4.880730] system 00:00: [mem 0x000ec000-0x000effff] could not be reserved
[ 4.880731] system 00:00: [mem 0x000f0000-0x000fffff] could not be reserved
[ 4.880732] system 00:00: [mem 0x00100000-0xafffffff] could not be reserved
[ 4.880734] system 00:00: [mem 0xfec00000-0xfed3ffff] could not be reserved
[ 4.880735] system 00:00: [mem 0xfed4c000-0xffffffff] could not be reserved
[ 4.880739] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 4.880841] pnp 00:01: [Firmware Bug]: PNP resource [mem 0xfed10000-0xfed13fff] covers only part of 0000:00:00.0 Intel MCH; extending to [mem 0xfed10000-0xfed17fff]
[ 4.880862] system 00:01: [io 0x1800-0x189f] has been reserved
[ 4.880864] system 00:01: [io 0x0800-0x087f] has been reserved
[ 4.880865] system 00:01: [io 0x0880-0x08ff] has been reserved
[ 4.880866] system 00:01: [io 0x0900-0x097f] has been reserved
[ 4.880867] system 00:01: [io 0x0980-0x09ff] has been reserved
[ 4.880869] system 00:01: [io 0x0a00-0x0a7f] has been reserved
[ 4.880870] system 00:01: [io 0x0a80-0x0aff] has been reserved
[ 4.880871] system 00:01: [io 0x0b00-0x0b7f] has been reserved
[ 4.880872] system 00:01: [io 0x0b80-0x0bff] has been reserved
[ 4.880873] system 00:01: [io 0x15e0-0x15ef] has been reserved
[ 4.880875] system 00:01: [io 0x1600-0x167f] has been reserved
[ 4.880876] system 00:01: [io 0x1640-0x165f] has been reserved
[ 4.880878] system 00:01: [mem 0xf8000000-0xfbffffff] has been reserved
[ 4.880879] system 00:01: [mem 0xfed1c000-0xfed1ffff] has been reserved
[ 4.880881] system 00:01: [mem 0xfed10000-0xfed17fff] has been reserved
[ 4.880882] system 00:01: [mem 0xfed18000-0xfed18fff] has been reserved
[ 4.880883] system 00:01: [mem 0xfed19000-0xfed19fff] has been reserved
[ 4.880884] system 00:01: [mem 0xfed45000-0xfed4bfff] has been reserved
[ 4.880886] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 4.880936] xen: registering gsi 8 triggering 1 polarity 0
[ 4.880956] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 4.880962] xen: registering gsi 1 triggering 1 polarity 0
[ 4.880981] pnp 00:03: Plug and Play ACPI device, IDs LEN0071 PNP0303 (active)
[ 4.880987] xen: registering gsi 12 triggering 1 polarity 0
[ 4.881004] pnp 00:04: Plug and Play ACPI device, IDs LEN0046 PNP0f13 (active)
[ 4.881459] pnp 00:05: Plug and Play ACPI device, IDs SMO1200 PNP0c31 (active)
[ 4.881663] system 00:06: [mem 0xb0010000-0xb001ffff] has been reserved
[ 4.881664] system 00:06: [mem 0xb0000000-0xb000ffff] has been reserved
[ 4.881666] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 4.881698] pnp: PnP ACPI: found 7 devices
[ 4.889397] PM-Timer failed consistency check (0xffffff) - aborting.
[ 4.889432] pci 0000:00:1c.0: PCI bridge to [bus 02]
[ 4.889440] pci 0000:00:1c.0: bridge window [mem 0xe1100000-0xe11fffff]
[ 4.889452] pci 0000:00:1c.1: PCI bridge to [bus 03]
[ 4.889460] pci 0000:00:1c.1: bridge window [mem 0xe1000000-0xe10fffff]
[ 4.889474] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window]
[ 4.889475] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window]
[ 4.889477] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
[ 4.889478] pci_bus 0000:00: resource 7 [mem 0xb0000000-0xfebfffff window]
[ 4.889479] pci_bus 0000:00: resource 8 [mem 0xfed40000-0xfed4bfff window]
[ 4.889480] pci_bus 0000:02: resource 1 [mem 0xe1100000-0xe11fffff]
[ 4.889481] pci_bus 0000:03: resource 1 [mem 0xe1000000-0xe10fffff]
[ 4.889582] NET: Registered protocol family 2
[ 4.889775] TCP established hash table entries: 32768 (order: 6, 262144 bytes)
[ 4.889892] TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
[ 4.889971] TCP: Hash tables configured (established 32768 bind 32768)
[ 4.890003] UDP hash table entries: 2048 (order: 4, 65536 bytes)
[ 4.890023] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
[ 4.890075] NET: Registered protocol family 1
[ 4.890095] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[ 4.890178] xen: registering gsi 16 triggering 0 polarity 1
[ 4.890196] xen: --> pirq=16 -> irq=16 (gsi=16)
[ 4.890379] xen: registering gsi 23 triggering 0 polarity 1
[ 4.890390] xen: --> pirq=23 -> irq=23 (gsi=23)
[ 4.890637] PCI: CLS 64 bytes, default 64
[ 4.890698] Unpacking initramfs...
[ 5.249920] Freeing initrd memory: 20172K
[ 5.250092] RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 655360 ms ovfl timer
[ 5.250092] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[ 5.250093] RAPL PMU: hw unit of domain package 2^-14 Joules
[ 5.250094] RAPL PMU: hw unit of domain dram 2^-14 Joules
[ 5.250094] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[ 5.250678] Scanning for low memory corruption every 60 seconds
[ 5.251033] audit: initializing netlink subsys (disabled)
[ 5.251049] audit: type=2000 audit(1509528819.129:1): initialized
[ 5.251365] Initialise system trusted keyrings
[ 5.251500] workingset: timestamp_bits=37 max_order=20 bucket_order=0
[ 5.253022] zbud: loaded
[ 5.262745] NET: Registered protocol family 38
[ 5.262748] Key type asymmetric registered
[ 5.262749] Asymmetric key parser 'x509' registered
[ 5.262803] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[ 5.262853] io scheduler noop registered
[ 5.262854] io scheduler deadline registered
[ 5.262868] io scheduler cfq registered (default)
[ 5.263119] xen: registering gsi 17 triggering 0 polarity 1
[ 5.263137] xen: --> pirq=17 -> irq=17 (gsi=17)
[ 5.263280] xen: registering gsi 18 triggering 0 polarity 1
[ 5.263291] xen: --> pirq=18 -> irq=18 (gsi=18)
[ 5.263403] intel_idle: MWAIT substates: 0x11142120
[ 5.263404] intel_idle: v0.4.1 model 0x3D
[ 5.263406] intel_idle: intel_idle yielding to none
[ 5.263589] ACPI: AC Adapter [AC] (on-line)
[ 5.263790] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
[ 5.263925] ACPI: Lid Switch [LID]
[ 5.263960] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
[ 5.263963] ACPI: Sleep Button [SLPB]
[ 5.264006] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[ 5.264008] ACPI: Power Button [PWRF]
[ 5.264436] Monitor-Mwait will be used to enter C-1 state
[ 5.264439] Monitor-Mwait will be used to enter C-2 state
[ 5.264442] Monitor-Mwait will be used to enter C-3 state
[ 5.265289] Warning: Processor Platform Limit not supported.
[ 5.266540] thermal LNXTHERM:00: registered as thermal_zone0
[ 5.266541] ACPI: Thermal Zone [THM0] (34 C)
[ 5.266582] GHES: HEST is not enabled!
[ 5.266729] xen:xen_evtchn: Event-channel device installed
[ 5.267168] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 5.267662] hpet_acpi_add: no address or irqs in _CRS
[ 5.267712] Non-volatile memory driver v1.3
[ 5.267742] Linux agpgart interface v0.103
[ 5.268195] ahci 0000:00:1f.2: version 3.0
[ 5.268262] xen: registering gsi 19 triggering 0 polarity 1
[ 5.268277] xen: --> pirq=19 -> irq=19 (gsi=19)
[ 5.268377] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 3 ports 6 Gbps 0x1 impl SATA mode
[ 5.268379] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo only pio slum part deso sadm sds apst
[ 5.268856] scsi host0: ahci
[ 5.268987] scsi host1: ahci
[ 5.269101] scsi host2: ahci
[ 5.269140] ata1: SATA max UDMA/133 abar m2048@0xe123c000 port 0xe123c100 irq 71
[ 5.269141] ata2: DUMMY
[ 5.269141] ata3: DUMMY
[ 5.269241] libphy: Fixed MDIO Bus: probed
[ 5.269343] usbcore: registered new interface driver usbserial
[ 5.269349] usbcore: registered new interface driver usbserial_generic
[ 5.269354] usbserial: USB Serial support registered for generic
[ 5.269385] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
[ 5.274488] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 5.274492] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 5.274634] mousedev: PS/2 mouse device common for all mice
[ 5.274787] rtc_cmos 00:02: RTC can wake from S4
[ 5.274988] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
[ 5.275026] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram
[ 5.275111] device-mapper: uevent: version 1.0.3
[ 5.275207] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised: dm-devel@redhat.com
[ 5.276004] hidraw: raw HID events driver (C) Jiri Kosina
[ 5.276040] usbcore: registered new interface driver usbhid
[ 5.276041] usbhid: USB HID core driver
[ 5.276207] drop_monitor: Initializing network drop monitor service
[ 5.276270] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 5.276476] Initializing XFRM netlink socket
[ 5.276516] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
[ 5.276800] NET: Registered protocol family 10
[ 5.277191] mip6: Mobile IPv6
[ 5.277193] NET: Registered protocol family 17
[ 5.277336] ACPI: Battery Slot [BAT0] (battery present)
[ 5.277493] microcode: sig=0x306d4, pf=0x40, revision=0x24
[ 5.277610] microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[ 5.277617] AVX2 version of gcm_enc/dec engaged.
[ 5.277617] AES CTR mode by8 optimization enabled
[ 5.286598] registered taskstats version 1
[ 5.286634] Loading compiled-in X.509 certificates
[ 5.286690] zswap: loaded using pool lzo/zbud
[ 5.287355] ACPI: Battery Slot [BAT1] (battery present)
[ 5.290249] Key type big_key registered
[ 5.293230] Key type encrypted registered
[ 5.293819] Magic number: 9:88:575
[ 5.293870] workqueue: hash matches
[ 5.293936] rtc_cmos 00:02: setting system clock to 2017-11-01 09:33:39 UTC (1509528819)
[ 5.581478] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 5.584154] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 5.584157] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 5.584158] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 5.584504] ata1.00: ACPI cmd ef/10:09:00:00:00:a0 (SET FEATURES) succeeded
[ 5.586076] ata1.00: supports DRM functions and may not be fully accessible
[ 5.586789] ata1.00: ATA-10: INTEL SSDSC2BF240A5L, LT2i, max UDMA/133
[ 5.586791] ata1.00: 468862128 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 5.594207] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 5.594209] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 5.594210] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 5.594591] ata1.00: ACPI cmd ef/10:09:00:00:00:a0 (SET FEATURES) succeeded
[ 5.596102] ata1.00: supports DRM functions and may not be fully accessible
[ 5.601613] ata1.00: configured for UDMA/133
[ 5.601801] scsi 0:0:0:0: Direct-Access ATA INTEL SSDSC2BF24 LT2i PQ: 0 ANSI: 5
[ 5.609387] sd 0:0:0:0: [sda] 468862128 512-byte logical blocks: (240 GB/224 GiB)
[ 5.609388] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 5.609522] sd 0:0:0:0: [sda] Write Protect is off
[ 5.609524] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 5.609552] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 5.610025] sda: sda1 sda2 sda3
[ 5.610412] sd 0:0:0:0: [sda] Attached SCSI disk
[ 5.611073] Freeing unused kernel memory: 2004K
[ 5.611074] Write protecting the kernel read-only data: 12288k
[ 5.614171] Freeing unused kernel memory: 100K
[ 5.614491] Freeing unused kernel memory: 712K
[ 5.621679] systemd[1]: systemd 222 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[ 5.621727] systemd[1]: Detected virtualization xen.
[ 5.621731] systemd[1]: Detected architecture x86-64.
[ 5.621734] systemd[1]: Running in initial RAM disk.
[ 5.621762] systemd[1]: Set hostname to <dom0>.
[ 5.691205] systemd[1]: Reached target Timers.
[ 5.691215] systemd[1]: Starting Timers.
[ 5.691530] systemd[1]: Created slice -.slice.
[ 5.691538] systemd[1]: Starting -.slice.
[ 5.691572] systemd[1]: Listening on udev Kernel Socket.
[ 5.701810] xen_pciback: backend is vpci
[ 5.703284] xen_acpi_processor: Uploading Xen processor PM info
[ 5.707722] audit: type=1130 audit(1509528819.913:2): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 5.713990] audit: type=1130 audit(1509528819.919:3): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 5.720188] audit: type=1130 audit(1509528819.926:4): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 5.734895] audit: type=1130 audit(1509528819.940:5): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 5.782410] audit: type=1130 audit(1509528819.988:6): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-vconsole-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 5.796917] pciback 0000:00:19.0: seizing device
[ 5.797011] xen: registering gsi 20 triggering 0 polarity 1
[ 5.797031] xen: --> pirq=20 -> irq=20 (gsi=20)
[ 5.904051] pciback 0000:03:00.0: seizing device
[ 5.905166] xen: registering gsi 17 triggering 0 polarity 1
[ 5.905176] Already setup the GSI :17
[ 6.148753] audit: type=1130 audit(1509528820.354:7): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dracut-cmdline comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 6.175345] rdac: device handler registered
[ 6.192338] audit: type=1130 audit(1509528820.398:8): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dracut-pre-udev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 6.198580] audit: type=1130 audit(1509528820.404:9): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 6.259862] audit: type=1130 audit(1509528820.465:10): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udev-trigger comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 6.282554] xen: registering gsi 16 triggering 0 polarity 1
[ 6.282560] Already setup the GSI :16
[ 6.282739] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 6.282891] rtsx_pci 0000:02:00.0: rtsx_pci_acquire_irq: pcr->msi_en = 1, pci->irq = 72
[ 6.283079] ehci-pci: EHCI PCI platform driver
[ 6.283203] xen: registering gsi 23 triggering 0 polarity 1
[ 6.283207] Already setup the GSI :23
[ 6.283280] ehci-pci 0000:00:1d.0: EHCI Host Controller
[ 6.283481] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 1
[ 6.283498] ehci-pci 0000:00:1d.0: debug port 2
[ 6.285720] [drm] Initialized
[ 6.287445] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
[ 6.287493] ehci-pci 0000:00:1d.0: irq 23, io mem 0xe123d000
[ 6.294169] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[ 6.294250] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 6.294251] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 6.294253] usb usb1: Product: EHCI Host Controller
[ 6.294254] usb usb1: Manufacturer: Linux 4.9.45-21.pvops.qubes.x86_64 ehci_hcd
[ 6.294255] usb usb1: SerialNumber: 0000:00:1d.0
[ 6.294465] Setting dangerous option preliminary_hw_support - tainting kernel
[ 6.294468] hub 1-0:1.0: USB hub found
[ 6.294478] hub 1-0:1.0: 3 ports detected
[ 6.294906] xen: registering gsi 16 triggering 0 polarity 1
[ 6.294912] Already setup the GSI :16
[ 6.294952] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 6.295023] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
[ 6.295163] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2113db4f3b3, max_idle_ns: 440795227758 ns
[ 6.296111] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0004b810
[ 6.296121] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
[ 6.296268] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 6.296270] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 6.296271] usb usb2: Product: xHCI Host Controller
[ 6.296273] usb usb2: Manufacturer: Linux 4.9.45-21.pvops.qubes.x86_64 xhci-hcd
[ 6.296274] usb usb2: SerialNumber: 0000:00:14.0
[ 6.296457] hub 2-0:1.0: USB hub found
[ 6.296471] hub 2-0:1.0: 11 ports detected
[ 6.298789] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 6.298995] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
[ 6.299042] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
[ 6.299044] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 6.299044] usb usb3: Product: xHCI Host Controller
[ 6.299045] usb usb3: Manufacturer: Linux 4.9.45-21.pvops.qubes.x86_64 xhci-hcd
[ 6.299046] usb usb3: SerialNumber: 0000:00:14.0
[ 6.299724] hub 3-0:1.0: USB hub found
[ 6.299736] hub 3-0:1.0: 4 ports detected
[ 6.300716] xen: registering gsi 16 triggering 0 polarity 1
[ 6.300722] Already setup the GSI :16
[ 6.302585] [drm] Memory usable by graphics device = 4096M
[ 6.302588] [drm] Replacing VGA console driver
[ 6.305257] Console: switching to colour dummy device 80x25
[ 6.323165] random: crng init done
[ 6.399297] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 6.399298] [drm] Driver supports precise vblank timestamp query.
[ 6.399660] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 6.423032] ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
[ 6.424360] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
[ 6.424489] [drm] Initialized i915 1.6.0 20160919 for 0000:00:02.0 on minor 0
[ 6.607300] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 6.699263] fbcon: inteldrmfb (fb0) is primary device
[ 6.725999] usb 1-1: New USB device found, idVendor=8087, idProduct=8001
[ 6.726003] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 6.726568] hub 1-1:1.0: USB hub found
[ 6.726685] hub 1-1:1.0: 8 ports detected
[ 7.319640] clocksource: Switched to clocksource tsc
[ 7.339384] usb 3-1: new SuperSpeed USB device number 2 using xhci_hcd
[ 7.352067] usb 3-1: New USB device found, idVendor=04e8, idProduct=61f3
[ 7.352073] usb 3-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 7.352077] usb 3-1: Product: Portable SSD T3
[ 7.352081] usb 3-1: Manufacturer: Samsung
[ 7.352084] usb 3-1: SerialNumber: 12345678D8E5
[ 7.360348] usbcore: registered new interface driver usb-storage
[ 7.363289] scsi host3: uas
[ 7.363359] usbcore: registered new interface driver uas
[ 7.363634] scsi 3:0:0:0: Direct-Access Samsung Portable SSD T3 0 PQ: 0 ANSI: 6
[ 7.396521] sd 3:0:0:0: Attached scsi generic sg1 type 0
[ 7.396601] sd 3:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 7.396993] sd 3:0:0:0: [sdb] Write Protect is off
[ 7.396994] sd 3:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 7.397143] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 7.400109] sdb: sdb1 sdb2 sdb3
[ 7.401523] sd 3:0:0:0: [sdb] Attached SCSI disk
[ 7.507296] usb 2-4: new high-speed USB device number 3 using xhci_hcd
[ 7.683338] usb 2-4: New USB device found, idVendor=1199, idProduct=a001
[ 7.683342] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 7.683344] usb 2-4: Product: Sierra Wireless EM7345 4G LTE
[ 7.683347] usb 2-4: Manufacturer: Sierra Wireless Inc.
[ 7.683349] usb 2-4: SerialNumber: 013937007232695
[ 7.829762] Console: switching to colour frame buffer device 170x48
[ 7.850220] usb 2-7: new full-speed USB device number 4 using xhci_hcd
[ 7.852684] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 8.019757] usb 2-7: New USB device found, idVendor=8087, idProduct=0a2a
[ 8.019759] usb 2-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 8.176229] usb 2-8: new high-speed USB device number 5 using xhci_hcd
[ 8.355549] usb 2-8: New USB device found, idVendor=5986, idProduct=0366
[ 8.355554] usb 2-8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 8.355557] usb 2-8: Product: Integrated Camera
[ 8.355560] usb 2-8: Manufacturer: SunplusIT Inc
[ 15.751131] audit_printk_skb: 6 callbacks suppressed
[ 15.751134] audit: type=1130 audit(1509528829.955:13): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-cryptsetup@luks\x2d5b671ec1\x2db0b5\x2d4397\x2d9646\x2d2c01689bd483 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 16.290891] audit: type=1130 audit(1509528830.495:14): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dracut-initqueue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 16.689616] audit: type=1130 audit(1509528830.894:15): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck-root comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 16.711551] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
[ 16.794816] audit: type=1130 audit(1509528830.999:16): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=initrd-parse-etc comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 16.794841] audit: type=1131 audit(1509528830.999:17): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=initrd-parse-etc comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 16.803347] audit: type=1130 audit(1509528831.007:18): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dracut-initqueue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 16.803380] audit: type=1131 audit(1509528831.007:19): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dracut-initqueue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 16.804108] audit: type=1130 audit(1509528831.008:20): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-ask-password-plymouth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 16.804129] audit: type=1131 audit(1509528831.008:21): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-ask-password-plymouth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 16.804628] audit: type=1130 audit(1509528831.009:22): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=initrd-cleanup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 16.847323] systemd-journald[192]: Received SIGTERM from PID 1 (systemd).
[ 16.868349] systemd: 34 output lines suppressed due to ratelimiting
[ 16.921665] systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
[ 17.108896] EXT4-fs (dm-1): re-mounted. Opts: (null)
[ 17.141517] systemd-journald[774]: Received request to flush runtime journal from PID 1
[ 17.151615] systemd-journald[774]: File /var/log/journal/4ac885487af94ac58bfc74887520940c/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 17.291516] tpm_tis 00:05: 1.2 TPM (device-id 0x0, rev-id 78)
[ 17.298903] FUJITSU Extended Socket Network Device Driver - version 1.1 - Copyright (c) 2015 FUJITSU LIMITED
[ 17.314724] thinkpad_acpi: ThinkPad ACPI Extras v0.25
[ 17.314726] thinkpad_acpi: http://ibm-acpi.sf.net/
[ 17.314727] thinkpad_acpi: ThinkPad BIOS N10ET46W (1.25 ), EC unknown
[ 17.314728] thinkpad_acpi: Lenovo ThinkPad X250, model 20CLS01104
[ 17.315627] thinkpad_acpi: radio switch found; radios are enabled
[ 17.315642] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver
[ 17.315642] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default...
[ 17.317476] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
[ 17.318407] wmi: Mapper loaded
[ 17.318614] thinkpad_acpi: rfkill switch tpacpi_wwan_sw: radio is unblocked
[ 17.329110] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input6
[ 17.345228] pps_core: LinuxPPS API ver. 1 registered
[ 17.345229] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 17.349472] PTP clock support registered
[ 17.351001] xen: registering gsi 16 triggering 0 polarity 1
[ 17.351008] Already setup the GSI :16
[ 17.351075] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 17.351192] xen: registering gsi 22 triggering 0 polarity 1
[ 17.351221] xen: --> pirq=22 -> irq=22 (gsi=22)
[ 17.355421] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 17.355422] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 17.361859] Intel(R) Wireless WiFi driver for Linux
[ 17.361860] Copyright(c) 2003- 2015 Intel Corporation
[ 17.367637] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC3232: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[ 17.367641] snd_hda_codec_realtek hdaudioC1D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 17.367643] snd_hda_codec_realtek hdaudioC1D0: hp_outs=2 (0x16/0x15/0x0/0x0/0x0)
[ 17.367644] snd_hda_codec_realtek hdaudioC1D0: mono: mono_out=0x0
[ 17.367645] snd_hda_codec_realtek hdaudioC1D0: inputs:
[ 17.367647] snd_hda_codec_realtek hdaudioC1D0: Dock Mic=0x19
[ 17.367649] snd_hda_codec_realtek hdaudioC1D0: Mic=0x1a
[ 17.367650] snd_hda_codec_realtek hdaudioC1D0: Internal Mic=0x12
[ 17.382764] input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/sound/card0/input7
[ 17.383147] input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/sound/card0/input8
[ 17.383227] input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/sound/card0/input9
[ 17.383325] xen: registering gsi 18 triggering 0 polarity 1
[ 17.383332] Already setup the GSI :18
[ 17.385238] xen: registering gsi 18 triggering 0 polarity 1
[ 17.385245] Already setup the GSI :18
[ 17.385275] i801_smbus 0000:00:1f.3: SPD Write Disable is set
[ 17.385315] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
[ 17.399689] input: PC Speaker as /devices/platform/pcspkr/input/input10
[ 17.433648] intel_rapl: Found RAPL domain package
[ 17.433654] intel_rapl: Found RAPL domain core
[ 17.433660] intel_rapl: Found RAPL domain uncore
[ 17.433663] intel_rapl: Found RAPL domain dram
[ 17.485219] cdc_acm 2-4:1.2: ttyACM0: USB ACM device
[ 17.486328] usbcore: registered new interface driver cdc_acm
[ 17.486330] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 17.508964] Bluetooth: Core ver 2.22
[ 17.508987] NET: Registered protocol family 31
[ 17.508988] Bluetooth: HCI device and connection manager initialized
[ 17.508992] Bluetooth: HCI socket layer initialized
[ 17.508995] Bluetooth: L2CAP socket layer initialized
[ 17.509000] Bluetooth: SCO socket layer initialized
[ 17.516020] usbcore: registered new interface driver cdc_ncm
[ 17.516592] usbcore: registered new interface driver btusb
[ 17.518331] usbcore: registered new interface driver cdc_wdm
[ 17.525596] media: Linux media interface: v0.10
[ 17.531541] Linux video capture interface: v2.00
[ 17.531819] Bluetooth: hci0: read Intel version: 370810011003110e00
[ 17.537108] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 17.545717] uvcvideo: Found UVC 1.00 device Integrated Camera (5986:0366)
[ 17.553882] uvcvideo 2-8:1.0: Entity type for entity Extension 4 was not initialized!
[ 17.553885] uvcvideo 2-8:1.0: Entity type for entity Extension 3 was not initialized!
[ 17.553887] uvcvideo 2-8:1.0: Entity type for entity Processing 2 was not initialized!
[ 17.553889] uvcvideo 2-8:1.0: Entity type for entity Camera 1 was not initialized!
[ 17.554395] input: Integrated Camera as /devices/pci0000:00/0000:00:14.0/usb2/2-8/2-8:1.0/input/input12
[ 17.554506] usbcore: registered new interface driver uvcvideo
[ 17.554507] USB Video Class driver (1.1.1)
[ 17.562606] iTCO_vendor_support: vendor-support=0
[ 17.563380] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[ 17.563431] iTCO_wdt: Found a Wildcat Point_LP TCO device (Version=2, TCOBASE=0x1860)
[ 17.563581] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 17.571197] cdc_mbim 2-4:1.0: setting rx_max = 16384
[ 17.571940] cdc_mbim 2-4:1.0: cdc-wdm0: USB WDM device
[ 17.572286] cdc_mbim 2-4:1.0 wwan0: register 'cdc_mbim' at usb-0000:00:14.0-4, CDC MBIM, 96:58:28:06:15:9f
[ 17.572314] usbcore: registered new interface driver cdc_mbim
[ 17.652212] cdc_mbim 2-4:1.0 wwp0s20u4: renamed from wwan0
[ 17.776911] Adding 7995388k swap on /dev/mapper/qubes_dom0-swap. Priority:-1 extents:1 across:7995388k SSFS
[ 17.851824] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
[ 18.137840] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 18.193287] psmouse serio1: synaptics: queried max coordinates: x [..5712], y [..4780]
[ 18.223772] psmouse serio1: synaptics: queried min coordinates: x [1232..], y [1074..]
[ 18.282567] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xf002a3/0x943300/0x12e800/0x10000, board id: 3075, fw id: 2560
[ 18.282575] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0
[ 18.319444] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input11
[ 18.394751] input: HDA Intel PCH Dock Mic as /devices/pci0000:00/0000:00:1b.0/sound/card1/input14
[ 18.394853] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card1/input15
[ 18.394951] input: HDA Intel PCH Dock Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card1/input16
[ 18.395052] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card1/input17
[ 18.977224] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3
[ 19.176289] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input13
[ 19.633046] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 19.655886] Ebtables v2.0 registered
[ 20.788272] audit_printk_skb: 228 callbacks suppressed
[ 20.788274] audit: type=1130 audit(1509525234.992:97): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=qubes-netvm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[ 20.795052] audit: type=1130 audit(1509525234.999:98): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-user-sessions comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 20.798193] audit: type=1130 audit(1509525235.002:99): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=crond comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 20.882849] audit: type=1130 audit(1509525235.087:100): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plymouth-quit-wait comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 20.882881] audit: type=1131 audit(1509525235.087:101): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plymouth-quit-wait comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 20.883661] audit: type=1130 audit(1509525235.088:102): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plymouth-quit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 20.883683] audit: type=1131 audit(1509525235.088:103): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plymouth-quit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 20.890161] audit: type=1130 audit(1509525235.094:104): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=serial-getty@hvc0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 20.892742] audit: type=1130 audit(1509525235.097:105): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plymouth-start comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 20.892767] audit: type=1131 audit(1509525235.097:106): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plymouth-start comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 25.367582] systemd-journald[774]: File /var/log/journal/4ac885487af94ac58bfc74887520940c/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[ 26.364675] audit_printk_skb: 66 callbacks suppressed
[ 26.364677] audit: type=1130 audit(1509525240.568:129): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rtkit-daemon comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 56.587128] loop: module loaded
[ 57.266420] xen_pciback: vpci: 0000:00:19.0: assign to virtual slot 0
[ 57.266607] pciback 0000:00:19.0: registering for 1
[ 57.266789] xen_pciback: vpci: 0000:03:00.0: assign to virtual slot 1
[ 57.267040] pciback 0000:03:00.0: registering for 1
[ 58.596909] xen-blkback: backend/vbd/1/51712: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 58.609760] xen-blkback: backend/vbd/1/51728: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 58.631639] xen-blkback: backend/vbd/1/51744: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 58.637984] xen-blkback: backend/vbd/1/51760: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 59.922408] pciback 0000:00:19.0: enabling device (0000 -> 0003)
[ 59.922599] xen: registering gsi 20 triggering 0 polarity 1
[ 59.922610] Already setup the GSI :20
[ 59.922980] xen: registering gsi 20 triggering 0 polarity 1
[ 59.922984] Already setup the GSI :20
[ 59.923230] xen: registering gsi 20 triggering 0 polarity 1
[ 59.923233] Already setup the GSI :20
[ 59.923659] xen: registering gsi 20 triggering 0 polarity 1
[ 59.923663] Already setup the GSI :20
[ 59.924029] xen: registering gsi 20 triggering 0 polarity 1
[ 59.924033] Already setup the GSI :20
[ 59.924321] xen: registering gsi 20 triggering 0 polarity 1
[ 59.924323] Already setup the GSI :20
[ 59.924538] xen: registering gsi 20 triggering 0 polarity 1
[ 59.924540] Already setup the GSI :20
[ 59.924731] pciback 0000:00:19.0: Driver tried to write to a read-only configuration space field at offset 0xd2, size 2. This may be harmless, but if you have problems with your device:
1) see permissive attribute in sysfs
2) report problems to the xen-devel mailing list along with details of your device obtained from lspci.
[ 59.935601] pciback 0000:03:00.0: enabling device (0000 -> 0002)
[ 59.935831] xen: registering gsi 17 triggering 0 polarity 1
[ 59.935836] Already setup the GSI :17
[ 59.937754] xen: registering gsi 17 triggering 0 polarity 1
[ 59.937759] Already setup the GSI :17
[ 59.939386] xen: registering gsi 17 triggering 0 polarity 1
[ 59.939395] Already setup the GSI :17
[ 59.941205] xen: registering gsi 17 triggering 0 polarity 1
[ 59.941209] Already setup the GSI :17
[ 59.942942] xen: registering gsi 17 triggering 0 polarity 1
[ 59.942946] Already setup the GSI :17
[ 59.944784] xen: registering gsi 17 triggering 0 polarity 1
[ 59.944790] Already setup the GSI :17
[ 59.948850] pciback 0000:03:00.0: Driver tried to write to a read-only configuration space field at offset 0xd2, size 2. This may be harmless, but if you have problems with your device:
1) see permissive attribute in sysfs
2) report problems to the xen-devel mailing list along with details of your device obtained from lspci.
[ 60.104653] pciback 0000:00:19.0: xen map irq failed -19 for 1 domain
[ 60.104656] xen_pciback: 0000:00:19.0: error enabling MSI for guest 1: err -19
[ 60.276322] pciback 0000:03:00.0: xen map irq failed -19 for 1 domain
[ 60.276331] xen_pciback: 0000:03:00.0: error enabling MSI for guest 1: err -19
[ 61.098936] irq 18: nobody cared (try booting with the "irqpoll" option)
[ 61.098944] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G U 4.9.45-21.pvops.qubes.x86_64 #1
[ 61.098945] Hardware name: LENOVO 20CLS01104/20CLS01104, BIOS N10ET46W (1.25 ) 11/28/2016
[ 61.098947] ffff880160e03e38 ffffffff813e62c3 ffff880158584800 ffff88015858489c
[ 61.098950] ffff880160e03e60 ffffffff810f9cf3 ffff880158584800 0000000000000000
[ 61.098953] 0000000000000012 ffff880160e03e98 ffffffff810fa06e ffff880158584800
[ 61.098955] Call Trace:
[ 61.098957] <IRQ>
[ 61.098963] [<ffffffff813e62c3>] dump_stack+0x63/0x90
[ 61.098965] [<ffffffff810f9cf3>] __report_bad_irq+0x33/0xc0
[ 61.098967] [<ffffffff810fa06e>] note_interrupt+0x23e/0x280
[ 61.098968] [<ffffffff810f7284>] handle_irq_event_percpu+0x54/0x80
[ 61.098970] [<ffffffff810f72eb>] handle_irq_event+0x3b/0x60
[ 61.098971] [<ffffffff810fa72f>] handle_fasteoi_irq+0x8f/0x140
[ 61.098972] [<ffffffff810f6482>] generic_handle_irq+0x22/0x30
[ 61.098975] [<ffffffff814ccedc>] __evtchn_fifo_handle_events+0x17c/0x1a0
[ 61.098977] [<ffffffff814ccf30>] evtchn_fifo_handle_events+0x10/0x20
[ 61.098978] [<ffffffff814c9b23>] __xen_evtchn_do_upcall+0x43/0x80
[ 61.098980] [<ffffffff814cbc30>] xen_evtchn_do_upcall+0x30/0x40
[ 61.098985] [<ffffffff817df87e>] xen_do_hypervisor_callback+0x1e/0x40
[ 61.098985] <EOI>
[ 61.098988] [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20
[ 61.098989] [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20
[ 61.098991] [<ffffffff81023be0>] ? xen_safe_halt+0x10/0x20
[ 61.098993] [<ffffffff817dddee>] ? default_idle+0x1e/0xd0
[ 61.098995] [<ffffffff81038fef>] ? arch_cpu_idle+0xf/0x20
[ 61.098997] [<ffffffff817de213>] ? default_idle_call+0x23/0x30
[ 61.098999] [<ffffffff810e5614>] ? cpu_startup_entry+0x1c4/0x230
[ 61.099001] [<ffffffff817cde97>] ? rest_init+0x77/0x80
[ 61.099005] [<ffffffff81d7cbe8>] ? start_kernel+0x5e0/0x621
[ 61.099006] [<ffffffff81d7b3b2>] ? x86_64_start_reservations+0x4f/0x70
[ 61.099008] [<ffffffff81d8740b>] ? xen_start_kernel+0x8c6/0x8e9
[ 61.099009] handlers:
[ 61.099013] [<ffffffffc02fd780>] i801_isr [i2c_i801]
[ 61.099014] Disabling IRQ #18
[ 63.043727] xen-blkback: backend/vbd/2/51712: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 63.059016] xen-blkback: backend/vbd/2/51728: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 63.090565] xen-blkback: backend/vbd/2/51744: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 63.099110] xen-blkback: backend/vbd/2/51760: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 72.230909] xen-blkback: backend/vbd/3/51712: using 4 queues, protocol 1 (x86_64-abi) persistent grants
[ 72.246484] xen-blkback: backend/vbd/3/51728: using 4 queues, protocol 1 (x86_64-abi) persistent grants
[ 72.272476] xen-blkback: backend/vbd/3/51744: using 4 queues, protocol 1 (x86_64-abi) persistent grants
[ 72.287406] xen-blkback: backend/vbd/3/51760: using 4 queues, protocol 1 (x86_64-abi) persistent grants
[ 85.425471] xen-blkback: backend/vbd/4/51712: using 1 queues, protocol 1 (x86_64-abi) persistent grants
[ 85.522045] xen-blkback: backend/vbd/4/51728: using 1 queues, protocol 1 (x86_64-abi) persistent grants
[ 85.538896] xen-blkback: backend/vbd/4/51744: using 1 queues, protocol 1 (x86_64-abi) persistent grants
[ 85.563092] xen-blkback: backend/vbd/4/51760: using 1 queues, protocol 1 (x86_64-abi) persistent grants
[ 199.957237] xen-blkback: backend/vbd/4/51840: using 1 queues, protocol 1 (x86_64-abi) persistent grants
[ 202.277129] xen-blkback: backend/vbd/5/51712: using 4 queues, protocol 1 (x86_64-abi) persistent grants
[ 202.290913] xen-blkback: backend/vbd/5/51728: using 4 queues, protocol 1 (x86_64-abi) persistent grants
[ 202.339190] xen-blkback: backend/vbd/5/51744: using 4 queues, protocol 1 (x86_64-abi) persistent grants
[ 202.361012] xen-blkback: backend/vbd/5/51760: using 4 queues, protocol 1 (x86_64-abi) persistent grants
[ 223.976659] xen-blkback: backend/vbd/6/51712: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 224.006874] xen-blkback: backend/vbd/6/51728: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 224.045401] xen-blkback: backend/vbd/6/51744: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 224.055641] xen-blkback: backend/vbd/6/51760: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 377.014915] xen_pciback: vpci: 0000:00:19.0: assign to virtual slot 0
[ 377.015371] pciback 0000:00:19.0: registering for 7
[ 377.015545] xen_pciback: vpci: 0000:03:00.0: assign to virtual slot 1
[ 377.016111] pciback 0000:03:00.0: registering for 7
[ 378.543952] xen-blkback: backend/vbd/7/51712: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 378.563712] xen-blkback: backend/vbd/7/51728: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 378.581919] xen-blkback: backend/vbd/7/51744: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 378.599857] xen-blkback: backend/vbd/7/51760: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 379.480413] pciback 0000:00:19.0: enabling device (0000 -> 0003)
[ 379.480508] xen: registering gsi 20 triggering 0 polarity 1
[ 379.480513] Already setup the GSI :20
[ 379.480736] xen: registering gsi 20 triggering 0 polarity 1
[ 379.480738] Already setup the GSI :20
[ 379.480927] xen: registering gsi 20 triggering 0 polarity 1
[ 379.480929] Already setup the GSI :20
[ 379.481116] xen: registering gsi 20 triggering 0 polarity 1
[ 379.481118] Already setup the GSI :20
[ 379.482078] xen: registering gsi 20 triggering 0 polarity 1
[ 379.482083] Already setup the GSI :20
[ 379.482313] xen: registering gsi 20 triggering 0 polarity 1
[ 379.482315] Already setup the GSI :20
[ 379.482503] xen: registering gsi 20 triggering 0 polarity 1
[ 379.482505] Already setup the GSI :20
[ 379.491013] pciback 0000:03:00.0: enabling device (0000 -> 0002)
[ 379.491242] xen: registering gsi 17 triggering 0 polarity 1
[ 379.491247] Already setup the GSI :17
[ 379.493143] xen: registering gsi 17 triggering 0 polarity 1
[ 379.493148] Already setup the GSI :17
[ 379.494633] xen: registering gsi 17 triggering 0 polarity 1
[ 379.494638] Already setup the GSI :17
[ 379.496878] xen: registering gsi 17 triggering 0 polarity 1
[ 379.496883] Already setup the GSI :17
[ 379.498739] xen: registering gsi 17 triggering 0 polarity 1
[ 379.498745] Already setup the GSI :17
[ 379.500577] xen: registering gsi 17 triggering 0 polarity 1
[ 379.500582] Already setup the GSI :17
[ 379.667093] pciback 0000:00:19.0: xen map irq failed -19 for 7 domain
[ 379.667097] xen_pciback: 0000:00:19.0: error enabling MSI for guest 7: err -19
[ 379.839998] pciback 0000:03:00.0: xen map irq failed -19 for 7 domain
[ 379.840004] xen_pciback: 0000:03:00.0: error enabling MSI for guest 7: err -19
[ 388.889729] xen-blkback: backend/vbd/8/51712: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 388.910431] xen-blkback: backend/vbd/8/51728: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 388.924601] xen-blkback: backend/vbd/8/51744: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 388.942126] xen-blkback: backend/vbd/8/51760: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 398.501822] xen-blkback: backend/vbd/9/51712: using 4 queues, protocol 1 (x86_64-abi) persistent grants
[ 398.529226] xen-blkback: backend/vbd/9/51728: using 4 queues, protocol 1 (x86_64-abi) persistent grants
[ 398.566068] xen-blkback: backend/vbd/9/51744: using 4 queues, protocol 1 (x86_64-abi) persistent grants
[ 398.592562] xen-blkback: backend/vbd/9/51760: using 4 queues, protocol 1 (x86_64-abi) persistent grants
[ 924.248817] audit: type=1130 audit(1509526138.426:130): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 924.248842] audit: type=1131 audit(1509526138.426:131): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 928.008787] xen-blkback: backend/vbd/10/51712: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 928.023568] xen-blkback: backend/vbd/10/51728: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 928.080522] xen-blkback: backend/vbd/10/51744: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 928.093847] xen-blkback: backend/vbd/10/51760: using 2 queues, protocol 1 (x86_64-abi) persistent grants
[ 943.604872] xen-blkback: backend/vbd/11/51712: using 4 queues, protocol 1 (x86_64-abi) persistent grants
[ 943.643494] xen-blkback: backend/vbd/11/51728: using 4 queues, protocol 1 (x86_64-abi) persistent grants
[ 943.707576] xen-blkback: backend/vbd/11/51744: using 4 queues, protocol 1 (x86_64-abi) persistent grants
[ 943.761215] xen-blkback: backend/vbd/11/51760: using 4 queues, protocol 1 (x86_64-abi) persistent grants
[ 945.449720] audit: type=1123 audit(1509526159.626:132): pid=9294 uid=1000 auid=1000 ses=1 msg='cwd="/home/abcdefg" cmd="dmesg" terminal=pts/5 res=success'
[ 945.449952] audit: type=1110 audit(1509526159.626:133): pid=9294 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/5 res=success'
[ 945.452884] audit: type=1105 audit(1509526159.629:134): pid=9294 uid=0 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/5 res=success'
[ 945.578277] audit: type=1106 audit(1509526159.755:135): pid=9294 uid=0 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/5 res=success'
[ 945.578380] audit: type=1104 audit(1509526159.755:136): pid=9294 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/5 res=success'
[ 1676.553604] audit: type=1123 audit(1509526890.708:137): pid=9434 uid=1000 auid=1000 ses=1 msg='cwd="/home/abcdefg" cmd="dmesg" terminal=pts/5 res=success'
[ 1676.554273] audit: type=1110 audit(1509526890.709:138): pid=9434 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/5 res=success'
[ 1676.558206] audit: type=1105 audit(1509526890.713:139): pid=9434 uid=0 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/5 res=success'
roasting223
commented
Nov 1, 2017
•
edited
Edited 3 times
-
roasting223
edited Nov 1, 2017 (most recent)
-
roasting223
edited
Nov 1, 2017
-
roasting223
edited
Nov 1, 2017
edited
Edited 3 times
-
Nov 1, 2017 (most recent) -
Nov 1, 2017 -
Nov 1, 2017
|
dmesg from dom0, do you need anything else? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
aoikonomopoulos
commented
Nov 1, 2017
|
@roasting223 thanks. How about |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
roasting223
Nov 1, 2017
There you go:
(XEN) Xen version 4.6.6 (user@[unknown]) (gcc (GCC) 5.3.1 20160406 (Red Hat 5.3.1-6)) debug=n Fri Oct 13 22:09:03 UTC 2017
(XEN) Latest ChangeSet:
(XEN) Bootloader: GRUB 2.02~beta2
(XEN) Command line: placeholder console=none dom0_mem=min:1024M dom0_mem=max:4096M
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN) Found 2 MBR signatures
(XEN) Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009d000 (usable)
(XEN) 000000000009d000 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 0000000010000000 (usable)
(XEN) 0000000010000000 - 000000001000b000 (reserved)
(XEN) 000000001000b000 - 000000009f063000 (usable)
(XEN) 000000009f063000 - 00000000acbff000 (reserved)
(XEN) 00000000acbff000 - 00000000acd7f000 (ACPI NVS)
(XEN) 00000000acd7f000 - 00000000acdff000 (ACPI data)
(XEN) 00000000acdff000 - 00000000b0000000 (reserved)
(XEN) 00000000f8000000 - 00000000fc000000 (reserved)
(XEN) 00000000fec00000 - 00000000fec01000 (reserved)
(XEN) 00000000fed08000 - 00000000fed09000 (reserved)
(XEN) 00000000fed10000 - 00000000fed1a000 (reserved)
(XEN) 00000000fed1c000 - 00000000fed20000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ffa00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 000000044e000000 (usable)
(XEN) ACPI: RSDP 000F0120, 0024 (r2 LENOVO)
(XEN) ACPI: XSDT ACDFE1C0, 00EC (r1 LENOVO TP-N10 1250 PTEC 2)
(XEN) ACPI: FACP ACDF8000, 010C (r5 LENOVO TP-N10 1250 PTEC 2)
(XEN) ACPI: DSDT ACDE3000, 10E44 (r2 LENOVO TP-N10 1250 INTL 20120711)
(XEN) ACPI: FACS ACD68000, 0040
(XEN) ACPI: SLIC ACDFD000, 0176 (r1 LENOVO TP-N10 1250 PTEC 1)
(XEN) ACPI: ASF! ACDFC000, 00A5 (r32 LENOVO TP-N10 1250 PTEC 2)
(XEN) ACPI: HPET ACDFB000, 0038 (r1 LENOVO TP-N10 1250 PTEC 2)
(XEN) ACPI: ECDT ACDFA000, 0052 (r1 LENOVO TP-N10 1250 PTEC 2)
(XEN) ACPI: APIC ACDF7000, 0098 (r1 LENOVO TP-N10 1250 PTEC 2)
(XEN) ACPI: MCFG ACDF6000, 003C (r1 LENOVO TP-N10 1250 PTEC 2)
(XEN) ACPI: SSDT ACDF5000, 0033 (r1 LENOVO TP-SSDT1 100 INTL 20120711)
(XEN) ACPI: SSDT ACDF4000, 0486 (r1 LENOVO TP-SSDT2 200 INTL 20120711)
(XEN) ACPI: SSDT ACDE2000, 09CB (r1 LENOVO SataAhci 1000 INTL 20120711)
(XEN) ACPI: SSDT ACDE1000, 0152 (r1 LENOVO Rmv_Batt 1000 INTL 20120711)
(XEN) ACPI: SSDT ACDE0000, 0691 (r1 LENOVO Cpu0Ist 3000 INTL 20120711)
(XEN) ACPI: SSDT ACDDF000, 0B74 (r2 LENOVO CpuSsdt 3000 INTL 20120711)
(XEN) ACPI: SSDT ACDDE000, 0369 (r2 LENOVO CtdpB 1000 INTL 20120711)
(XEN) ACPI: SSDT ACDDC000, 1475 (r1 LENOVO SaSsdt 3000 INTL 20120711)
(XEN) ACPI: SSDT ACDDB000, 0394 (r2 LENOVO CppcTabl 1000 INTL 20120711)
(XEN) ACPI: PCCT ACDDA000, 006E (r5 LENOVO TP-N10 1250 PTEC 2)
(XEN) ACPI: SSDT ACDD9000, 0AC4 (r2 LENOVO Cpc_Tabl 1000 INTL 20120711)
(XEN) ACPI: TCPA ACDD8000, 0032 (r2 PTL LENOVO 6040000 LNVO 1)
(XEN) ACPI: SSDT ACDD7000, 06B0 (r2 Intel_ TpmTable 1000 INTL 20120711)
(XEN) ACPI: UEFI ACDD6000, 0042 (r1 LENOVO TP-N10 1250 PTEC 2)
(XEN) ACPI: MSDM ACCB1000, 0055 (r3 LENOVO TP-N10 1250 PTEC 2)
(XEN) ACPI: BATB ACDD5000, 0046 (r1 LENOVO TP-N10 1250 PTEC 2)
(XEN) ACPI: FPDT ACDD4000, 0064 (r1 LENOVO TP-N10 1250 PTEC 2)
(XEN) ACPI: UEFI ACDD3000, 030A (r1 LENOVO TP-N10 1250 PTEC 2)
(XEN) System RAM: 16079MB (16465876kB)
(XEN) Domain heap initialised
(XEN) ACPI: 32/64X FACS address mismatch in FADT - acd68000/0000000000000000, using 32
(XEN) Processor #0 7:13 APIC version 21
(XEN) Processor #1 7:13 APIC version 21
(XEN) Processor #2 7:13 APIC version 21
(XEN) Processor #3 7:13 APIC version 21
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-39
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Not enabling x2APIC: depends on iommu_supports_eim.
(XEN) xstate_init: using cntxt_size: 0x340 and states: 0x7
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2294.757 MHz processor.
(XEN) Initing memory sharing.
(XEN) I/O virtualisation disabled
(XEN) Enabled directed EOI with ioapic_ack_old on!
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using old ACK method
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 16 KiB.
(XEN) mwait-idle: max C-state count of 8 reached
(XEN) VMX: Supported advanced features:
(XEN) - APIC MMIO access virtualisation
(XEN) - APIC TPR shadow
(XEN) - Extended Page Tables (EPT)
(XEN) - Virtual-Processor Identifiers (VPID)
(XEN) - Virtual NMI
(XEN) - MSR direct-access bitmap
(XEN) - Unrestricted Guest
(XEN) - VMCS shadowing
(XEN) - VM Functions
(XEN) - Virtualisation Exceptions
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) mwait-idle: max C-state count of 8 reached
(XEN) mwait-idle: max C-state count of 8 reached
(XEN) mwait-idle: max C-state count of 8 reached
(XEN) Brought up 4 CPUs
(XEN) Dom0 has maximum 616 PIRQs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x20d1000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000438000000->000000043c000000 (1027149 pages to be allocated)
(XEN) Init. ramdisk: 000000044cc4d000->000000044dfffa8f
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff820d1000
(XEN) Init. ramdisk: 0000000000000000->0000000000000000
(XEN) Phys-Mach map: 0000008000000000->0000008000800000
(XEN) Start info: ffffffff820d1000->ffffffff820d14b4
(XEN) Page tables: ffffffff820d2000->ffffffff820e7000
(XEN) Boot stack: ffffffff820e7000->ffffffff820e8000
(XEN) TOTAL: ffffffff80000000->ffffffff82400000
(XEN) ENTRY ADDRESS: ffffffff81d7b180
(XEN) Dom0 has maximum 4 VCPUs
(XEN) Scrubbing Free RAM on 1 nodes using 2 CPUs
(XEN) .....................................................................done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 304kB init memory.
(XEN) CPU0: Temperature above threshold
(XEN) CPU1: Temperature above threshold
(XEN) CPU0: Running in modulated clock mode
(XEN) CPU1: Running in modulated clock mode
roasting223
commented
Nov 1, 2017
|
There you go: |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
roasting223
commented
Nov 3, 2017
|
BTW: I can confirm that downgrading xen to 4.6.6-30 fixes the problem |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
aoikonomopoulos
Nov 4, 2017
FWIW, I don't see anything that could be linked to one of the applied patches in the log messages (there's only one message that could be relevant anyway). I guess the next step will be to setup an environment where we can rebuild the rpm and do binary search on the patches. Hopefully I can make time for that, eventually.
Probably a good idea to also keep track of patches to these files upstream, there weren't any obvious fixes last I checked.
aoikonomopoulos
commented
Nov 4, 2017
|
FWIW, I don't see anything that could be linked to one of the applied patches in the log messages (there's only one message that could be relevant anyway). I guess the next step will be to setup an environment where we can rebuild the rpm and do binary search on the patches. Hopefully I can make time for that, eventually. Probably a good idea to also keep track of patches to these files upstream, there weren't any obvious fixes last I checked. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
aoikonomopoulos
Nov 30, 2017
OK, finally got around to bisecting this. I can reproduce the effect after applying QubesOS/qubes-vmm-xen/patches.security/xsa237-0001-x86-dont-allow-MSI-pIRQ-mapping-on-unowned-device.patch, reproduced here:
From: Jan Beulich <jbeulich@suse.com>
Subject: x86: don't allow MSI pIRQ mapping on unowned device
MSI setup should be permitted only for existing devices owned by the
respective guest (the operation may still be carried out by the domain
controlling that guest).
This is part of XSA-237.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
--- a/xen/arch/x86/irq.c
+++ b/xen/arch/x86/irq.c
@@ -1961,7 +1961,10 @@ int map_domain_pirq(
if ( !cpu_has_apic )
goto done;
- pdev = pci_get_pdev(msi->seg, msi->bus, msi->devfn);
+ pdev = pci_get_pdev_by_domain(d, msi->seg, msi->bus, msi->devfn);
+ if ( !pdev )
+ goto done;
+
ret = pci_enable_msi(msi, &msi_desc);
if ( ret )
{
I've also verified that the issue is gone for xen-hypervisor-4.6.6-34 with the above patch modified to:
--- a/xen/arch/x86/irq.c
+++ b/xen/arch/x86/irq.c
@@ -1961,7 +1961,15 @@ int map_domain_pirq(
if ( !cpu_has_apic )
goto done;
- pdev = pci_get_pdev(msi->seg, msi->bus, msi->devfn);
+ pdev = pci_get_pdev_by_domain(d, msi->seg, msi->bus, msi->devfn);
+ if ( !pdev ) {
+ printk(XENLOG_G_ERR "dom%d: would error out b/c !pdev for (%d, %d, %d)\n", d->domain_id, msi->seg, msi->bus, msi->devfn);
+ pdev = pci_get_pdev(msi->seg, msi->bus, msi->devfn);
+ if (!pdev) {
+ printk(XENLOG_G_ERR "Couldn't pci_get_pdev either\n");
+ goto done;
+ }
+ }Booting xen-hypervisor-4.6.6-34 with this patch instead of xsa237-0001-x86-dont-allow-MSI-pIRQ-mapping-on-unowned-device.patch results in a working system. What's more, in /var/log/xen/console/hypervisor.log I get the first message (dom%d: would error error out ...) but not the second. I think this is conclusive evidence that this is the relevant change.
I haven't tried to figure out why the new test, using pci_get_pdev_by_domain, doesn't pass (isn't the device owned by the guest?). Perhaps someone can beat me to it.
aoikonomopoulos
commented
Nov 30, 2017
•
edited
Edited 1 time
-
aoikonomopoulos
edited Nov 30, 2017 (most recent)
edited
Edited 1 time
-
Nov 30, 2017 (most recent)
|
OK, finally got around to bisecting this. I can reproduce the effect after applying QubesOS/qubes-vmm-xen/patches.security/xsa237-0001-x86-dont-allow-MSI-pIRQ-mapping-on-unowned-device.patch, reproduced here: I've also verified that the issue is gone for xen-hypervisor-4.6.6-34 with the above patch modified to: --- a/xen/arch/x86/irq.c
+++ b/xen/arch/x86/irq.c
@@ -1961,7 +1961,15 @@ int map_domain_pirq(
if ( !cpu_has_apic )
goto done;
- pdev = pci_get_pdev(msi->seg, msi->bus, msi->devfn);
+ pdev = pci_get_pdev_by_domain(d, msi->seg, msi->bus, msi->devfn);
+ if ( !pdev ) {
+ printk(XENLOG_G_ERR "dom%d: would error out b/c !pdev for (%d, %d, %d)\n", d->domain_id, msi->seg, msi->bus, msi->devfn);
+ pdev = pci_get_pdev(msi->seg, msi->bus, msi->devfn);
+ if (!pdev) {
+ printk(XENLOG_G_ERR "Couldn't pci_get_pdev either\n");
+ goto done;
+ }
+ }Booting xen-hypervisor-4.6.6-34 with this patch instead of xsa237-0001-x86-dont-allow-MSI-pIRQ-mapping-on-unowned-device.patch results in a working system. What's more, in /var/log/xen/console/hypervisor.log I get the first message (dom%d: would error error out ...) but not the second. I think this is conclusive evidence that this is the relevant change. I haven't tried to figure out why the new test, using pci_get_pdev_by_domain, doesn't pass (isn't the device owned by the guest?). Perhaps someone can beat me to it. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
aoikonomopoulos
Nov 30, 2017
I should also mention there are no later fixes touching this file in xen (checked stable-4.6, stable-6.8 and master).
aoikonomopoulos
commented
Nov 30, 2017
|
I should also mention there are no later fixes touching this file in xen (checked stable-4.6, stable-6.8 and master). |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
HW42
Nov 30, 2017
OK, finally got around to bisecting this.
Thanks!
Booting xen-hypervisor-4.6.6-34 with this patch instead of xsa237-0001-x86-dont-allow-MSI-pIRQ-mapping-on-unowned-device.patch results in a working system. What's more, in /var/log/xen/console/hypervisor.log I get the first message (dom%d: would error error out ...) but not the second. I think this is conclusive evidence that this is the relevant change.
Can you please let it print the value of pdev->domain. It's strange that the device is not associated with the domain.
HW42
commented
Nov 30, 2017
Thanks!
Can you please let it print the value of |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
HW42
Nov 30, 2017
PS: I suspected that it's this patch, but I currently don't see why it should fail.
HW42
commented
Nov 30, 2017
|
PS: I suspected that it's this patch, but I currently don't see why it should fail. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
aoikonomopoulos
Nov 30, 2017
pdev->domain->domain_id is 0 (i.e. dom0). There's enough indirection in the pci-attach code that it's not obvious to me where/when pdev->domain should change. Grepping gives me xen/drivers/passthrough/vtd/iommu.c::reassign_device_ownership(), which only moves the device to the target domain conditionally. But, then again, xl pci-list sys-net shows the wifi card in sys-net, which implies that the conditional bit did run.
Perhaps @HW42 can make a more educated guess as to what might have gone wrong.
aoikonomopoulos
commented
Nov 30, 2017
|
Perhaps @HW42 can make a more educated guess as to what might have gone wrong. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
ths82
Dec 10, 2017
Same issue here!
@aoikonomopoulos, you mention that it works for you again after downgrading, although:
downgrading the xen packages was not terribly straightforward (the procedure described in https://www.qubes-os.org/doc/software-update-dom0/ failed to download the package for me)
How did you finally manage to downgrade? The documented process isn't working for me either
ths82
commented
Dec 10, 2017
|
Same issue here! @aoikonomopoulos, you mention that it works for you again after downgrading, although:
How did you finally manage to downgrade? The documented process isn't working for me either |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
roasting223
Dec 12, 2017
@ths82 In dom0 first run
sudo qubes-dom0-update xen-4.6.6-30.fc23 xen-libs-4.6.6-30.fc23 xen-hypervisor-4.6.6-30.fc23 xen-hvm-4.6.6-30.fc23 xen-licenses-4.6.6-30.fc23 xen-runtime-4.6.6-30.fc23
then
sudo yum downgrade xen-4.6.6-30.fc23 xen-libs-4.6.6-30.fc23 xen-hypervisor-4.6.6-30.fc23 xen-hvm-4.6.6-30.fc23 xen-licenses-4.6.6-30.fc23 xen-runtime-4.6.6-30.fc23
roasting223
commented
Dec 12, 2017
|
@ths82 In dom0 first run |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
ths82
Dec 17, 2017
@roasting223 Unfortunately, this is not working. qubes-dom0-update fails with "No package xen-4.6.6-30.fc23 available" (same message for all packages), and subsequently yum downgrade says that all packages are already installed in the lowest version
ths82
commented
Dec 17, 2017
|
@roasting223 Unfortunately, this is not working. qubes-dom0-update fails with "No package xen-4.6.6-30.fc23 available" (same message for all packages), and subsequently yum downgrade says that all packages are already installed in the lowest version |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
markf94
Jan 6, 2018
I've got the same problem here. I've updated my dom0 yesterday from 4.4.14-11.pvops.qubes.x86_64 (out of the box kernel) to 4.9.56-21.pvops.qubes.x86_64 and the newest xen version and I am running on a Lenovo ThinkPad T450 with Intel Wireless 7265. I've tried reloading the drivers as specified in the Wireless Troubleshooting section in the QubesOS documentation but it still doesn't work. I am currently connected to the web via ethernet cable. Unfortunately, same as @ths82 I can not downgrade my xen-hypervisor according to @roasting223's instructions. As I said, I am connected via ethernet but the qubes-dom0-update results in
No package xen-4.6.6-30.fc23 available.
No package xen-libs-4.6.6-30.fc23 available.
No package xen-hypervisor-4.6.6-30.fc23 available.
No package xen-hvm-4.6.6-30.fc23 available.
No package xen-licenses-4.6.6-30.fc23 available.
No package xen-runtime-4.6.6-30.fc23 available.
Error: Unable to find a match.
and running the yum downgrade tells me that all packages of lowest version are already installed and that it cannot downgrade it.
Here is my full dmesg from sys-net:
sys-net_dmesg.txt
Also for me nothing weird in /var/log/xen/console/hypervisor.log in dom0. But I will supply it anyway:
hypervisor_output.txt
And finally here comes the dmesg from dom0:
dom0_dmesg.txt
markf94
commented
Jan 6, 2018
•
edited
Edited 4 times
-
markf94
edited Jan 6, 2018 (most recent)
-
markf94
edited
Jan 6, 2018
-
markf94
edited
Jan 6, 2018
-
markf94
edited
Jan 6, 2018
edited
Edited 4 times
-
Jan 6, 2018 (most recent) -
Jan 6, 2018 -
Jan 6, 2018 -
Jan 6, 2018
|
I've got the same problem here. I've updated my dom0 yesterday from 4.4.14-11.pvops.qubes.x86_64 (out of the box kernel) to 4.9.56-21.pvops.qubes.x86_64 and the newest xen version and I am running on a Lenovo ThinkPad T450 with Intel Wireless 7265. I've tried reloading the drivers as specified in the Wireless Troubleshooting section in the QubesOS documentation but it still doesn't work. I am currently connected to the web via ethernet cable. Unfortunately, same as @ths82 I can not downgrade my xen-hypervisor according to @roasting223's instructions. As I said, I am connected via ethernet but the
and running the yum downgrade tells me that all packages of lowest version are already installed and that it cannot downgrade it. Here is my full dmesg from sys-net: Also for me nothing weird in And finally here comes the dmesg from dom0: |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
awokd
Jan 6, 2018
@markf94 For a temporary workaround, try appending pci=nomsi to the qvm-prefs sys-net kernelopts. Worked for someone in the mailing list.
awokd
commented
Jan 6, 2018
|
@markf94 For a temporary workaround, try appending pci=nomsi to the qvm-prefs sys-net kernelopts. Worked for someone in the mailing list. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
markf94
Jan 6, 2018
@awokd thanks for your swift reply! However, appending pci=nomsi doesn't solve the problem for me. I just reinstalled QubesOS and did the dom0 update and the problem persists. I really urgently need my Wi-Fi so I'll start with a clean QubesOS install and just won't update dom0 until this issue is resolved.
markf94
commented
Jan 6, 2018
|
@awokd thanks for your swift reply! However, appending pci=nomsi doesn't solve the problem for me. I just reinstalled QubesOS and did the dom0 update and the problem persists. I really urgently need my Wi-Fi so I'll start with a clean QubesOS install and just won't update dom0 until this issue is resolved. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
markf94
Jan 7, 2018
Okay from a fresh install I ran:
sudo qubes-dom0-update xen-2001:4.6.6-30.fc23 xen-libs-2001:4.6.6-30.fc23 xen-hypervisor-2001:4.6.6-30.fc23 xen-hvm-2001:4.6.6-30.fc23 xen-licenses-2001:4.6.6-30.fc23 xen-runtime-2001:4.6.6-30.fc23
which will only install until the version 4.6.6-30 for which Wi-Fi still works. I tested downgrading to 4.6.6-28 with @roasting223's approach but it also doesn't work here. Downgrade fails and says package is already at lowest version. Please let me know if anyone knows how to downgrade reliably.
markf94
commented
Jan 7, 2018
•
edited
Edited 1 time
-
markf94
edited
Jan 7, 2018 (most recent)
edited
Edited 1 time
-
Jan 7, 2018 (most recent)
|
Okay from a fresh install I ran:
which will only install until the version 4.6.6-30 for which Wi-Fi still works. I tested downgrading to 4.6.6-28 with @roasting223's approach but it also doesn't work here. Downgrade fails and says package is already at lowest version. Please let me know if anyone knows how to downgrade reliably. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Feb 25, 2018
Member
@HW42 not sure if the same, but I can reproduce very similar issue when running Qubes OS 4.0 in KVM, with sys-net as PV. Relevant sys-net kernel log:
[ 7.232497] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 7.232535] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 7.232901] e1000e 0000:00:00.0: Xen PCI mapped GSI10 to IRQ15
[ 7.239099] e1000e 0000:00:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 7.239661] e1000e 0000:00:00.0: enable msix get err fffffffb
[ 7.239684] e1000e 0000:00:00.0: Xen PCI frontend error: -22!
[ 7.239787] e1000e 0000:00:00.0 0000:00:00.0 (uninitialized): Failed to initialize MSI-X interrupts. Falling back to MSI interrupts.
[ 7.243329] e1000e 0000:00:00.0: pci frontend enable msi failed for dev 0:0
[ 7.243354] e1000e 0000:00:00.0: Xen PCI frontend error: -22!
[ 7.243452] e1000e 0000:00:00.0 0000:00:00.0 (uninitialized): Failed to initialize MSI interrupts. Falling back to legacy interrupts.
[ 7.294626] e1000e 0000:00:00.0 0000:00:00.0 (uninitialized): registered PHC clock
[ 7.354866] e1000e 0000:00:00.0 eth0: (PCI Express:2.5GT/s:Width x1) 52:54:00:12:34:56
[ 7.354907] e1000e 0000:00:00.0 eth0: Intel(R) PRO/1000 Network Connection
[ 7.354960] e1000e 0000:00:00.0 eth0: MAC: 3, PHY: 8, PBA No: 000000-000
[ 7.382171] e1000e 0000:00:00.0 enp0s0: renamed from eth0
And dom0 kernel log:
Feb 25 07:08:43 dom0 kernel: pciback 0000:00:04.0: enabling device (0000 -> 0003)
Feb 25 07:08:43 dom0 kernel: xen: registering gsi 10 triggering 0 polarity 0
Feb 25 07:08:43 dom0 kernel: Already setup the GSI :10
Feb 25 07:08:44 dom0 kernel: xen: registering gsi 10 triggering 0 polarity 0
Feb 25 07:08:44 dom0 kernel: Already setup the GSI :10
Feb 25 07:08:44 dom0 kernel: xen: registering gsi 10 triggering 0 polarity 0
Feb 25 07:08:44 dom0 kernel: Already setup the GSI :10
Feb 25 07:08:44 dom0 kernel: xen: registering gsi 10 triggering 0 polarity 0
Feb 25 07:08:44 dom0 kernel: Already setup the GSI :10
Feb 25 07:08:44 dom0 kernel: xen: registering gsi 10 triggering 0 polarity 0
Feb 25 07:08:44 dom0 kernel: Already setup the GSI :10
Feb 25 07:08:44 dom0 kernel: xen: registering gsi 10 triggering 0 polarity 0
Feb 25 07:08:44 dom0 kernel: Already setup the GSI :10
Feb 25 07:08:44 dom0 kernel: xen: registering gsi 10 triggering 0 polarity 0
Feb 25 07:08:44 dom0 kernel: Already setup the GSI :10
Feb 25 07:08:44 dom0 kernel: xen: registering gsi 10 triggering 0 polarity 0
Feb 25 07:08:44 dom0 kernel: Already setup the GSI :10
Feb 25 07:08:44 dom0 kernel: pciback 0000:00:04.0: Driver tried to write to a read-only configuration space field at offset 0xa2, size 2. This may be harmless, but if you have problems with your device:
1) see permissive attribute in sysfs
2) report problems to the xen-devel mailing list along with details of your device obtained from lspci.
Feb 25 07:08:45 dom0 kernel: pciback 0000:00:04.0: xen map irq failed -19 for 2 domain
Feb 25 07:08:45 dom0 kernel: xen_pciback: 0000:00:04.0: error enabling MSI-X for guest 2: err -19!
Feb 25 07:08:45 dom0 kernel: pciback 0000:00:04.0: xen map irq failed -19 for 2 domain
Feb 25 07:08:45 dom0 kernel: xen_pciback: 0000:00:04.0: error enabling MSI for guest 2: err -19
Full log: https://openqa.qubes-os.org/tests/136/file/serial0.txt
If you want, I can give you access to the machine.
|
@HW42 not sure if the same, but I can reproduce very similar issue when running Qubes OS 4.0 in KVM, with sys-net as PV. Relevant sys-net kernel log: And dom0 kernel log: Full log: https://openqa.qubes-os.org/tests/136/file/serial0.txt |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
HW42
Feb 25, 2018
Are you passing through a real device or one emualted by KVM?
How many patches are currently required for Xen inside KVM? Testing it locally would of course be even better than remote access.
HW42
commented
Feb 25, 2018
|
Are you passing through a real device or one emualted by KVM? How many patches are currently required for Xen inside KVM? Testing it locally would of course be even better than remote access. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Feb 25, 2018
Member
KVM emulated. Haven't tried with real one. If you look at os-autoinst.txt log in that test, you'll have full qemu command line.
Right now Qubes 4.0 works out of the box under KVM. Qubes 3.2 doesn't. This one is on AMD, but on Intel too. Nested HVM works too (so you can use PVH inside), but not that stable (sometimes hangs when multiple VMs are running, or multiple vcpus in one VM). I even got emulated IOMMU working once (on Intel), but it was even less stable (see this thread).
|
KVM emulated. Haven't tried with real one. If you look at Right now Qubes 4.0 works out of the box under KVM. Qubes 3.2 doesn't. This one is on AMD, but on Intel too. Nested HVM works too (so you can use PVH inside), but not that stable (sometimes hangs when multiple VMs are running, or multiple vcpus in one VM). I even got emulated IOMMU working once (on Intel), but it was even less stable (see this thread). |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
And use legacy boot, UEFI is problematic. |
marmarek
referenced this issue
Feb 26, 2018
Closed
sys-net can't establish ethernet connetcion after dom0 update #3546
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
aoikonomopoulos
Mar 25, 2018
One more data point: same issue occurs with xen 4.8.3-3 (i.e. the ones in 4.0-rc5).
aoikonomopoulos
commented
Mar 25, 2018
|
One more data point: same issue occurs with xen 4.8.3-3 (i.e. the ones in 4.0-rc5). |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
roasting223
Apr 25, 2018
I have more or less the same issue on 4.0 now. For explanation: I have Qubes installed on an external SSD, switching between two machines.
On my Thinkpad X250, where this issue first appeared with 3.2, it is now impossible to even start sys-net (in HVM mode) with any PCI device attached. Qubes manager just alerts "failed to create domain" (analogous) and refers to libxl log:
2018-04-24 16:26:24.874+0000: libxl: libxl_device.c:1081:device_backend_callback: unable to remove device with path /local/domain/4/backend/vif/9/0
2018-04-24 16:26:24.886+0000: libxl: libxl.c:1669:devices_destroy_cb: libxl__devices_destroy failed for 9
2018-04-24 16:27:10.489+0000: libxl: libxl_linux.c:155:libxl__loopdev_cleanup: unable to release device /dev/loop0: No such device or address
2018-04-24 16:27:10.585+0000: libxl: libxl_linux.c:155:libxl__loopdev_cleanup: unable to release device /dev/loop0: No such device or address
2018-04-24 16:33:00.192+0000: libxl: libxl_pci.c:1235:libxl__device_pci_add: PCI device 0000:00:19.0 cannot be assigned - no IOMMU?
2018-04-24 16:33:00.192+0000: libxl: libxl_pci.c:1338:libxl__add_pcidevs: libxl_device_pci_add failed: -1
2018-04-24 16:33:00.192+0000: libxl: libxl_create.c:1512:domcreate_attach_devices: unable to add pci devices
2018-04-24 16:33:00.393+0000: libxl: libxl_linux.c:155:libxl__loopdev_cleanup: unable to release device /dev/loop0: No such device or address
2018-04-24 16:33:33.650+0000: libxl: libxl_pci.c:1235:libxl__device_pci_add: PCI device 0000:00:19.0 cannot be assigned - no IOMMU?
2018-04-24 16:33:33.650+0000: libxl: libxl_pci.c:1338:libxl__add_pcidevs: libxl_device_pci_add failed: -1
2018-04-24 16:33:33.650+0000: libxl: libxl_create.c:1512:domcreate_attach_devices: unable to add pci devices
2018-04-24 16:33:33.847+0000: libxl: libxl_linux.c:155:libxl__loopdev_cleanup: unable to release device /dev/loop0: No such device or address
2018-04-24 16:33:59.971+0000: libxl: libxl_pci.c:1235:libxl__device_pci_add: PCI device 0000:03:00.0 cannot be assigned - no IOMMU?
2018-04-24 16:33:59.971+0000: libxl: libxl_pci.c:1338:libxl__add_pcidevs: libxl_device_pci_add failed: -1
2018-04-24 16:33:59.971+0000: libxl: libxl_create.c:1512:domcreate_attach_devices: unable to add pci devices
2018-04-24 16:34:00.183+0000: libxl: libxl_linux.c:155:libxl__loopdev_cleanup: unable to release device /dev/loop0: No such device or address
2018-04-24 16:34:22.153+0000: libxl: libxl.c:1853:libxl_console_get_tty: unable to read console tty path `/local/domain/9/console/tty': Resource
I then created a seperate sys-net as PV, which seems to behave the same as in my initial report (wifi card not available, but ethernet adapter works)
roasting223
commented
Apr 25, 2018
|
I have more or less the same issue on 4.0 now. For explanation: I have Qubes installed on an external SSD, switching between two machines. On my Thinkpad X250, where this issue first appeared with 3.2, it is now impossible to even start sys-net (in HVM mode) with any PCI device attached. Qubes manager just alerts "failed to create domain" (analogous) and refers to libxl log: I then created a seperate sys-net as PV, which seems to behave the same as in my initial report (wifi card not available, but ethernet adapter works) |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Apr 25, 2018
Member
On Wed, Apr 25, 2018 at 04:55:03AM -0700, roasting223 wrote:
2018-04-24 16:33:59.971+0000: libxl: libxl_pci.c:1235:libxl__device_pci_add: PCI device 0000:03:00.0 cannot be assigned - no IOMMU?
This looks to be the problem. Make sure you have VT-d present and
enabled in BIOS. You can verify it using qubes-hcl-report utility.
…--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
On Wed, Apr 25, 2018 at 04:55:03AM -0700, roasting223 wrote:
2018-04-24 16:33:59.971+0000: libxl: libxl_pci.c:1235:libxl__device_pci_add: PCI device 0000:03:00.0 cannot be assigned - no IOMMU?
This looks to be the problem. Make sure you have VT-d present and
enabled in BIOS. You can verify it using qubes-hcl-report utility.
…--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
roasting223
Apr 25, 2018
Make sure you have VT-d present and enabled in BIOS.
That fixed it, thanks! Interestingly, the wifi now also works in PV mode. I don't have a 3.2 installation anymore to test this, but maybe this was the cause for the initial issue?
roasting223
commented
Apr 25, 2018
That fixed it, thanks! Interestingly, the wifi now also works in PV mode. I don't have a 3.2 installation anymore to test this, but maybe this was the cause for the initial issue? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
roasting223 commentedOct 26, 2017
Qubes OS version:
Qubes relese 3.2 (R3.2)
Affected TemplateVMs:
any
Actual behavior:
After the latest xen update in dom0 my wifi card firmware does not seem to load anymore in sys-net (no matter if fedora-25 or debian-9)
dmesg:
General notes:
I tried reverting the dom0 update, but could not figure out how to do so since yum history does not seem to be working in qubes-dom0-update and I dont know the old version numbers