wm(4) interrupt timeouts under Xen (as a dom0)

To: port-xen%netbsd.org@localhost
Subject: wm(4) interrupt timeouts under Xen (as a dom0)
From: Dustin Marquess <dmarquess%gmail.com@localhost>
Date: Thu, 8 Oct 2020 00:28:01 -0500

Just when I thought things were finally working...

A XEN3_DOM0 kernel built today from -current:

NetBSD apu2.fdf.net 9.99.73 NetBSD 9.99.73 (XEN3_DOM0) #0: Thu Oct  8
00:02:41 CDT 2020

Running under Xen 4.13 (xenkernel413) on a PC Engines apu4d4, the
onboard Intel NIC is really flakey:

[   125.039792] wm0: device timeout (lost interrupt)
[   173.015794] wm0: device timeout (lost interrupt)
[   192.006321] wm0: device timeout (lost interrupt)
[   202.001142] wm0: device timeout (lost interrupt)
[   208.997794] wm0: device timeout (lost interrupt)
[   241.981164] wm0: device timeout (lost interrupt)
[   257.973293] wm0: device timeout (lost interrupt)
[   331.966900] wm0: device timeout (lost interrupt)
[   347.966998] wm0: device timeout (lost interrupt)

Booting into a normal GENERIC kernel built from the exact same source
(without Xen), it works fine.

I'm not using any special Xen command line options.  Comparing 'xl
dmesg' to a working L*x Xen 4.12 box, I don't see any obvious
differences between the two.

xl dmesg is:

(XEN) Xen version 4.13.1nb1 (pbulk@) (gcc (nb3 20190319) 7.4.0)
debug=n  Fri Aug 28 22:31:17 UTC 2020
(XEN) Latest ChangeSet:
(XEN) Bootloader: NetBSD/x86 BIOS Boot, Revision 5.11 (Thu Oct  8
00:32:18 UTC 2020) (from NetBSD 9.99.73)
(XEN) Command line: dom0_mem=512M console=com1 com1=115200,8n1
(XEN) Xen image load base address: 0
(XEN) Video information:
(XEN)  No VGA detected
(XEN) Disc information:
(XEN)  Found 2 MBR signatures
(XEN)  Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009fc00 (usable)
(XEN)  000000000009fc00 - 00000000000a0000 (reserved)
(XEN)  00000000000f0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000cfe8a000 (usable)
(XEN)  00000000cfe8a000 - 00000000d0000000 (reserved)
(XEN)  00000000f8000000 - 00000000fc000000 (reserved)
(XEN)  00000000fed40000 - 00000000fed45000 (reserved)
(XEN)  0000000100000000 - 000000012f000000 (usable)
(XEN) New Xen image base address: 0xcf800000
(XEN) ACPI: RSDP 000F3AF0, 0024 (r2 COREv4)
(XEN) ACPI: XSDT CFE9D0E0, 007C (r1 COREv4 COREBOOT        0 CORE 20180531)
(XEN) ACPI: FACP CFE9EE40, 0114 (r6 COREv4 COREBOOT        0 CORE 20180531)
(XEN) ACPI: DSDT CFE9D280, 1BB3 (r2 COREv4 COREBOOT    10001 INTL 20180531)
(XEN) ACPI: FACS CFE9D240, 0040
(XEN) ACPI: SSDT CFE9EF60, 01F8 (r2 COREv4 COREBOOT       2A CORE 20180531)
(XEN) ACPI: MCFG CFE9F160, 003C (r1 COREv4 COREBOOT        0 CORE 20180531)
(XEN) ACPI: TPM2 CFE9F1A0, 004C (r4 COREv4 COREBOOT        0 CORE 20180531)
(XEN) ACPI: APIC CFE9F1F0, 007E (r3 COREv4 COREBOOT        0 CORE 20180531)
(XEN) ACPI: HEST CFE9F270, 01D0 (r1 COREv4 COREBOOT        0 CORE 20180531)
(XEN) ACPI: IVRS CFE9F440, 00D0 (r2 COREv4 COREBOOT        0 CORE 20180531)
(XEN) ACPI: SSDT CFE9F510, 48A6 (r2 AMD    AGESA           2 MSFT  4000000)
(XEN) ACPI: SSDT CFEA3DC0, 07C8 (r1 AMD    AGESA           1 AMD         1)
(XEN) ACPI: DRTM CFEA4590, 007C (r1 COREv4 COREBOOT        0 CORE 20180531)
(XEN) ACPI: HPET CFEA4610, 0038 (r1 COREv4 COREBOOT        0 CORE 20180531)
(XEN) System RAM: 4078MB (4176036kB)
(XEN) Domain heap initialised
(XEN) ACPI: 32/64X FACS address mismatch in FADT -
cfe9d240/0000000000000000, using 32
(XEN) IOAPIC[0]: apic_id 4, version 33, address 0xfec00000, GSI 0-23
(XEN) IOAPIC[1]: apic_id 5, version 33, address 0xfec20000, GSI 24-55
(XEN) Enabling APIC mode:  Flat.  Using 2 I/O APICs
(XEN) xstate: size: 0x340 and states: 0x7
(XEN) Speculative mitigation facilities:
(XEN)   Hardware features:
(XEN)   Compiled-in support: INDIRECT_THUNK SHADOW_PAGING
(XEN)   Xen settings: BTI-Thunk JMP, SPEC_CTRL: No, Other:
(XEN)   Support for HVM VMs: None
(XEN)   Support for PV VMs: None
(XEN)   XPTI (64-bit PV only): Dom0 disabled, DomU disabled (without PCID)
(XEN)   PV L1TF shadowing: Dom0 disabled, DomU disabled
(XEN) Using scheduler: SMP Credit Scheduler rev2 (credit2)
(XEN) Initializing Credit2 scheduler
(XEN) Platform timer is 14.318MHz HPET
(XEN) Detected 998.147 MHz processor.
(XEN) AMD-Vi: IOMMU Extended Features:
(XEN) - Peripheral Page Service Request
(XEN) - Invalidate All Command
(XEN) - Guest APIC
(XEN) - Performance Counters
(XEN) - Host Address Translation Size: 0x2
(XEN) - Guest Address Translation Size: 0
(XEN) - Guest CR3 Root Table Level: 0
(XEN) - Maximum PASID: 0x8
(XEN) - SMI Filter Register: 0x1
(XEN) - SMI Filter Register Count: 0x2
(XEN) - Guest Virtual APIC Modes: 0x1
(XEN) - Dual PPR Log: 0
(XEN) - Dual Event Log: 0
(XEN) - Device Table Segmentation: 0
(XEN) - Memory Access Routing and Control: 0
(XEN) - VM Table Size: 0
(XEN) AMD-Vi: IOMMU 0 Enabled.
(XEN) I/O virtualisation enabled
(XEN)  - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) Allocated console ring of 16 KiB.
(XEN) HVM: ASIDs enabled.
(XEN) SVM: Supported advanced features:
(XEN)  - Nested Page Tables (NPT)
(XEN)  - Last Branch Record (LBR) Virtualisation
(XEN)  - Next-RIP Saved on #VMEXIT
(XEN)  - DecodeAssists
(XEN)  - Pause-Intercept Filter
(XEN)  - Pause-Intercept Filter Threshold
(XEN)  - TSC Rate MSR
(XEN) HVM: SVM enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) Brought up 4 CPUs
(XEN) mtrr: your CPUs had inconsistent variable MTRR settings
(XEN) Dom0 has maximum 632 PIRQs
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0xffffffff80200000 ->
0xffffffff80e7d000
(XEN)  Dom0 symbol map 0xffffffff80e7d000 -> 0xffffffff80fc4980
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000128000000->000000012a000000 (122880 pages
to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff80200000->ffffffff80fc4980
(XEN)  Init. ramdisk: ffffffff80fc5000->ffffffff80fc5000
(XEN)  Phys-Mach map: ffffffff80fc5000->ffffffff810c5000
(XEN)  Start info:    ffffffff810c5000->ffffffff810c54b8
(XEN)  Xenstore ring: 0000000000000000->0000000000000000
(XEN)  Console ring:  0000000000000000->0000000000000000
(XEN)  Page tables:   ffffffff810c6000->ffffffff810d3000
(XEN)  Boot stack:    ffffffff810d3000->ffffffff810d4000
(XEN)  TOTAL:         ffffffff80000000->ffffffff81400000
(XEN)  ENTRY ADDRESS: ffffffff80232000
(XEN) Dom0 has maximum 4 VCPUs
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Scrubbing Free RAM in background
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) Freed 536kB init memory


-Dustin

Follow-Ups:
- Re: wm(4) interrupt timeouts under Xen (as a dom0)
  - From: Manuel Bouyer

Prev by Date: Re: Illegal instruction errors under XEN3_DOM0 on -CURRENT
Next by Date: Disinfectant
Previous by Thread: Panic in 9.0_STABLE with ZFS module on DOMU PV with recent build
Next by Thread: Re: wm(4) interrupt timeouts under Xen (as a dom0)
Indexes:

Home | Main Index | Thread Index | Old Index