Re: Xen dom0 interrupt storm detected on irq16:; throttling interrupt source
Unfortunately, the storm is still there with this patch.
On 2015-5-15, at 18:28, Roger Pau Monné roger@citrix.com wrote:
El 15/05/15 a les 16.42, Eggert, Lars ha escrit:
On 2015-5-15, at 16:35, Roger Pau Monné roger@citrix.com wrote:
Yes, but I've realized that isci for example passes an uint32_t instead
of an int, so it might be best to set it to 0.
Here is what I see now:
isci0: Intel(R) C600 Series Chipset SAS Controller (SATA mode) port
0x6000-0x60ff mem 0xde07c000-0xde07,0xddc0-0xddff irq 16 at
device 0.0 on pci10
isci0: attempting to allocate 2 MSI-X vectors (2 supported)
ISCI: isci-num_interrupts: 2 max_msix_messages: 2
isci: 1:89 ISCI bus_alloc_resource failed
The storm is still there.
Yes, after looking at the code, isci really needs to check for the
return value of pci_alloc_msix, because num_interrupts is not updated
if the allocation fails. Following patch should hopefully fix it,
please give it a try.
Roger.
---
diff --git a/sys/dev/isci/isci_interrupt.c b/sys/dev/isci/isci_interrupt.c
index 52c64f7..f331f3c 100644
--- a/sys/dev/isci/isci_interrupt.c
+++ b/sys/dev/isci/isci_interrupt.c
@@ -128,6 +128,7 @@ isci_interrupt_setup(struct isci_softc *isci)
isci-controller_count;
BOOL use_msix = FALSE;
uint32_t force_legacy_interrupts = 0;
+ int rc;
TUNABLE_INT_FETCH(hw.isci.force_legacy_interrupts,
force_legacy_interrupts);
@@ -136,8 +137,8 @@ isci_interrupt_setup(struct isci_softc *isci)
pci_msix_count(isci-device) = max_msix_messages) {
isci-num_interrupts = max_msix_messages;
- pci_alloc_msix(isci-device, isci-num_interrupts);
- if (isci-num_interrupts == max_msix_messages)
+ rc = pci_alloc_msix(isci-device, isci-num_interrupts);
+ if (rc == 0 isci-num_interrupts == max_msix_messages)
use_msix = TRUE;
}
signature.asc
Description: Message signed with OpenPGP using GPGMail
Re: Xen dom0 crash
El 18/05/15 a les 15.04, Eggert, Lars ha escrit: Hi, I'm trying to boot a Xen dom0 on another machine (Fujitsu RX308) and Xen crashes when starting the kernel. Log below; any ideas? Thanks, Lars B2 __ _ _ | | | _ \ / | __ \ | |___ _ __ ___ ___ | |_) | (___ | | | | | ___| '__/ _ \/ _ \| _ \___ \| | | | | | | | | __/ __/| |_) |) | |__| | | | | | |||| | | |_| |_| \___|\___||/|_/|_/```` s` `.---...--.``` -/ +Welcome to FreeBSD +4H+ .--` /y:` +. /boot/kernel/cc_vegas.ko size 0x30d0 at 0x1068000:.:o `+- Booting...el/cc_hd.ko size 0x2c00 at 0x106200 -/` -o/ Xen 4.6-unstabletcp.ko size 0x2f90 at 0x1065000 ::/sy+:. (XEN) Xen version 4.6-unstable (r...@netapp.com) (gcc47 (FreeBSD Ports Collection) 4.7.4) debug=y Mon May 18 14:50:17 CEST 2015 :` (XEN) Latest ChangeSet:| `: :` (XEN) Bootloader: FreeBSD Loader | / / (XEN) Command line: dom0_mem=4096M dom0pvh=1 com1=115200,8n1 console=com1. (XEN) Video information:]ptions... | -- -. (XEN) VGA is text mode 80x25, font 8x16 |`:` `:` (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds `--. (XEN) EDID info not retrieved because no DDC retrieval method detected=(XEN) Disc information: (XEN) Found 0 MBR signatures (XEN) Found 0 EDD information structures (XEN) Xen-e820 RAM map:+0x50db0 - (XEN) - 0008b800 (usable) (XEN) 0008b800 - 000a (reserved) (XEN) 000e - 0010 (reserved) (XEN) 0010 - 7cb09000 (usable) (XEN) 7cb09000 - 7cb39000 (reserved) (XEN) 7cb39000 - 7cc52000 (ACPI data) (XEN) 7cc52000 - 7d4b (ACPI NVS) (XEN) 7d4b - 7eafb000 (reserved) (XEN) 7eafb000 - 7eafc000 (usable) (XEN) 7eafc000 - 7eb82000 (ACPI NVS) (XEN) 7eb82000 - 7f00 (usable) (XEN) 8000 - 9000 (reserved) (XEN) fed1c000 - fed2 (reserved) (XEN) ff00 - 0001 (reserved) (XEN) 0001 - 00208000 (usable) (XEN) ACPI: RSDP 000F04A0, 0024 (r2 FTS ) (XEN) ACPI: XSDT 7CB71090, 00A4 (r1 FTSD2939-B1 1072009 AMI 10013) (XEN) ACPI: FACP 7CB7FAA8, 010C (r5 FTSD2939-B1 1072009 AMI 10013) (XEN) ACPI: DSDT 7CB711C8, E8DD (r2 FTSD2939-B1 114 INTL 20091112) (XEN) ACPI: FACS 7D4A7080, 0040 (XEN) ACPI: APIC 7CB7FBB8, 0294 (r3 FTSD2939-B1 1072009 AMI 10013) (XEN) ACPI: FPDT 7CB7FE50, 0044 (r1 FTSD2939-B1 1072009 AMI 10013) (XEN) ACPI: MCFG 7CB7FE98, 003C (r1 FTSOEMMCFG. 1072009 MSFT 97) (XEN) ACPI: SRAT 7CB7FED8, 0530 (r1 A M I AMI SRAT1 AMI.0) (XEN) ACPI: SLIT 7CB80408, 0030 (r1 A M I AMI SLIT0 AMI.0) (XEN) ACPI: HPET 7CB80438, 0038 (r1 FTSD2939-B1 1072009 AMI.5) (XEN) ACPI: PRAD 7CB80470, 00BE (r2 PRADID PRADTID1 MSFT 301) (XEN) ACPI: SPMI 7CB80530, 0040 (r5 A M I OEMSPMI0 AMI.0) (XEN) ACPI: SSDT 7CB80570, D0CB0 (r2 INTELCpuPm 4000 INTL 20051117) (XEN) ACPI: SPCR 7CC51220, 0050 (r1 A M I APTIO4 1072009 AMI.5) (XEN) ACPI: EINJ 7CC51270, 0130 (r1AMI AMI EINJ0 0) (XEN) ACPI: ERST 7CC513A0, 0230 (r1 AMIER AMI ERST0 0) (XEN) ACPI: HEST 7CC515D0, 00A8 (r1AMI AMI HEST0 0) (XEN) ACPI: BERT 7CC51678, 0030 (r1AMI AMI BERT0 0) (XEN) ACPI: DMAR 7CC516A8, 0110 (r1 A M I OEMDMAR1 INTL1) (XEN) System RAM: 131023MB (134167628kB) (XEN) SRAT: PXM 0 - APIC 0 - Node 0 (XEN) SRAT: PXM 0 - APIC 1 - Node 0 (XEN) SRAT: PXM 0 - APIC 2 - Node 0 (XEN) SRAT: PXM 0 - APIC 3 - Node 0 (XEN) SRAT: PXM 0 - APIC 4 - Node 0 (XEN) SRAT: PXM 0 - APIC 5 - Node 0 (XEN) SRAT: PXM 0 - APIC 6 - Node 0 (XEN) SRAT: PXM 0 - APIC 7 - Node 0 (XEN) SRAT: PXM 0 - APIC 8 - Node 0 (XEN) SRAT: PXM 0 - APIC 9 - Node 0 (XEN) SRAT: PXM 0 - APIC 16 - Node 0 (XEN) SRAT: PXM 0 - APIC 17 - Node 0 (XEN) SRAT: PXM 0 - APIC 18 - Node 0 (XEN) SRAT: PXM 0 - APIC 19 - Node 0 (XEN) SRAT: PXM 0 - APIC 20 - Node 0 (XEN) SRAT: PXM 0 - APIC 21 - Node 0 (XEN) SRAT: PXM 0 - APIC 22 - Node 0 (XEN) SRAT: PXM 0 - APIC 23 - Node 0 (XEN) SRAT: PXM 0 - APIC 24 - Node 0 (XEN) SRAT: PXM 0 - APIC 25 - Node 0 (XEN) SRAT: PXM 1 - APIC 32 - Node 1 (XEN) SRAT: PXM 1 - APIC 33 - Node
Xen dom0 crash
Hi, I'm trying to boot a Xen dom0 on another machine (Fujitsu RX308) and Xen crashes when starting the kernel. Log below; any ideas? Thanks, Lars B2 __ _ _ | | | _ \ / | __ \ | |___ _ __ ___ ___ | |_) | (___ | | | | | ___| '__/ _ \/ _ \| _ \___ \| | | | | | | | | __/ __/| |_) |) | |__| | | | | | |||| | | |_| |_| \___|\___||/|_/|_/```` s` `.---...--.``` -/ +Welcome to FreeBSD +4H+ .--` /y:` +. /boot/kernel/cc_vegas.ko size 0x30d0 at 0x1068000:.:o `+- Booting...el/cc_hd.ko size 0x2c00 at 0x106200 -/` -o/ Xen 4.6-unstabletcp.ko size 0x2f90 at 0x1065000 ::/sy+:. (XEN) Xen version 4.6-unstable (r...@netapp.com) (gcc47 (FreeBSD Ports Collection) 4.7.4) debug=y Mon May 18 14:50:17 CEST 2015 :` (XEN) Latest ChangeSet:| `: :` (XEN) Bootloader: FreeBSD Loader | / / (XEN) Command line: dom0_mem=4096M dom0pvh=1 com1=115200,8n1 console=com1. (XEN) Video information:]ptions... | -- -. (XEN) VGA is text mode 80x25, font 8x16 |`:` `:` (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds `--. (XEN) EDID info not retrieved because no DDC retrieval method detected=(XEN) Disc information: (XEN) Found 0 MBR signatures (XEN) Found 0 EDD information structures (XEN) Xen-e820 RAM map:+0x50db0 - (XEN) - 0008b800 (usable) (XEN) 0008b800 - 000a (reserved) (XEN) 000e - 0010 (reserved) (XEN) 0010 - 7cb09000 (usable) (XEN) 7cb09000 - 7cb39000 (reserved) (XEN) 7cb39000 - 7cc52000 (ACPI data) (XEN) 7cc52000 - 7d4b (ACPI NVS) (XEN) 7d4b - 7eafb000 (reserved) (XEN) 7eafb000 - 7eafc000 (usable) (XEN) 7eafc000 - 7eb82000 (ACPI NVS) (XEN) 7eb82000 - 7f00 (usable) (XEN) 8000 - 9000 (reserved) (XEN) fed1c000 - fed2 (reserved) (XEN) ff00 - 0001 (reserved) (XEN) 0001 - 00208000 (usable) (XEN) ACPI: RSDP 000F04A0, 0024 (r2 FTS ) (XEN) ACPI: XSDT 7CB71090, 00A4 (r1 FTSD2939-B1 1072009 AMI 10013) (XEN) ACPI: FACP 7CB7FAA8, 010C (r5 FTSD2939-B1 1072009 AMI 10013) (XEN) ACPI: DSDT 7CB711C8, E8DD (r2 FTSD2939-B1 114 INTL 20091112) (XEN) ACPI: FACS 7D4A7080, 0040 (XEN) ACPI: APIC 7CB7FBB8, 0294 (r3 FTSD2939-B1 1072009 AMI 10013) (XEN) ACPI: FPDT 7CB7FE50, 0044 (r1 FTSD2939-B1 1072009 AMI 10013) (XEN) ACPI: MCFG 7CB7FE98, 003C (r1 FTSOEMMCFG. 1072009 MSFT 97) (XEN) ACPI: SRAT 7CB7FED8, 0530 (r1 A M I AMI SRAT1 AMI.0) (XEN) ACPI: SLIT 7CB80408, 0030 (r1 A M I AMI SLIT0 AMI.0) (XEN) ACPI: HPET 7CB80438, 0038 (r1 FTSD2939-B1 1072009 AMI.5) (XEN) ACPI: PRAD 7CB80470, 00BE (r2 PRADID PRADTID1 MSFT 301) (XEN) ACPI: SPMI 7CB80530, 0040 (r5 A M I OEMSPMI0 AMI.0) (XEN) ACPI: SSDT 7CB80570, D0CB0 (r2 INTELCpuPm 4000 INTL 20051117) (XEN) ACPI: SPCR 7CC51220, 0050 (r1 A M I APTIO4 1072009 AMI.5) (XEN) ACPI: EINJ 7CC51270, 0130 (r1AMI AMI EINJ0 0) (XEN) ACPI: ERST 7CC513A0, 0230 (r1 AMIER AMI ERST0 0) (XEN) ACPI: HEST 7CC515D0, 00A8 (r1AMI AMI HEST0 0) (XEN) ACPI: BERT 7CC51678, 0030 (r1AMI AMI BERT0 0) (XEN) ACPI: DMAR 7CC516A8, 0110 (r1 A M I OEMDMAR1 INTL1) (XEN) System RAM: 131023MB (134167628kB) (XEN) SRAT: PXM 0 - APIC 0 - Node 0 (XEN) SRAT: PXM 0 - APIC 1 - Node 0 (XEN) SRAT: PXM 0 - APIC 2 - Node 0 (XEN) SRAT: PXM 0 - APIC 3 - Node 0 (XEN) SRAT: PXM 0 - APIC 4 - Node 0 (XEN) SRAT: PXM 0 - APIC 5 - Node 0 (XEN) SRAT: PXM 0 - APIC 6 - Node 0 (XEN) SRAT: PXM 0 - APIC 7 - Node 0 (XEN) SRAT: PXM 0 - APIC 8 - Node 0 (XEN) SRAT: PXM 0 - APIC 9 - Node 0 (XEN) SRAT: PXM 0 - APIC 16 - Node 0 (XEN) SRAT: PXM 0 - APIC 17 - Node 0 (XEN) SRAT: PXM 0 - APIC 18 - Node 0 (XEN) SRAT: PXM 0 - APIC 19 - Node 0 (XEN) SRAT: PXM 0 - APIC 20 - Node 0 (XEN) SRAT: PXM 0 - APIC 21 - Node 0 (XEN) SRAT: PXM 0 - APIC 22 - Node 0 (XEN) SRAT: PXM 0 - APIC 23 - Node 0 (XEN) SRAT: PXM 0 - APIC 24 - Node 0 (XEN) SRAT: PXM 0 - APIC 25 - Node 0 (XEN) SRAT: PXM 1 - APIC 32 - Node 1 (XEN) SRAT: PXM 1 - APIC 33 - Node 1 (XEN) SRAT: PXM 1 - APIC 34 - Node 1 (XEN) SRAT: PXM 1 - APIC 35 - Node 1 (XEN) SRAT: PXM 1 - APIC 36 - Node 1 (XEN) SRAT: PXM 1 - APIC 37 -
Re: Xen dom0 interrupt storm detected on irq16:; throttling interrupt source
El 18/05/15 a les 15.01, Eggert, Lars ha escrit: Unfortunately, the storm is still there with this patch. I guess you will have to resort to using hw.isci.force_legacy_interrupts=1 until I get around to implement MSI-X support for Xen Dom0, sorry for the trouble. Roger. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: Xen dom0 interrupt storm detected on irq16:; throttling interrupt source
On 2015-5-18, at 15:39, Roger Pau Monné roger@citrix.com wrote: I guess you will have to resort to using hw.isci.force_legacy_interrupts=1 until I get around to implement MSI-X support for Xen Dom0, sorry for the trouble. No worries, that's a fine workaround. Thanks for all the help! Lars signature.asc Description: Message signed with OpenPGP using GPGMail
[Bug 154428] [xen] xn0 network interface and PF - Massive performance drop
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154428 Bryan Drewery bdrew...@freebsd.org changed: What|Removed |Added CC||bdrew...@freebsd.org --- Comment #11 from Bryan Drewery bdrew...@freebsd.org --- I just hit this on 10.1-GENERIC on EC2. Empty pf.conf with pf enabled = horrible performance. Disabling pf or TSO with pf fixes it. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
[Bug 135178] [xen] Xen domU outgoing data transfer stall when TSO is enabled
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=135178 --- Comment #5 from Roger Pau Monné roy...@freebsd.org --- This bug is not about TSO + PF, just about TSO, which seems to work fine now (when not used in conjunction with PF). -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
[Bug 135178] [xen] Xen domU outgoing data transfer stall when TSO is enabled
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=135178 Colin Percival cperc...@freebsd.org changed: What|Removed |Added CC||cperc...@freebsd.org --- Comment #7 from Colin Percival cperc...@freebsd.org --- PF is inserting bogus TCP checksums into TSO segments. Some interfaces say gee, some idiot didn't read the spec and ignore the checksums, while other interfaces say hey, this is not a TSO packet and drop it. The Xen network (at least as implemented in EC2) falls into the second category. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
