[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] no-carrier on qlogic 8242 10gig with linux 3.x running xen
On Thu, Mar 29, 2012 at 01:30:08AM -0700, Kristoffer Harthing Egefelt wrote: > >Can you attach the /proc/interrupts please - for both Xen and baremetal. > > *Bare metal:* > CPU0 > 0: 0 IR-IO-APIC-edge timer > 8: 0 IR-IO-APIC-edge rtc0 > 9: 0 IR-IO-APIC-fasteoi acpi > 17: 0 IR-IO-APIC-fasteoi uhci_hcd:usb3, ata_piix > 18: 0 IR-IO-APIC-fasteoi uhci_hcd:usb4 > 19: 0 IR-IO-APIC-fasteoi ehci_hcd:usb1 > 20: 0 IR-IO-APIC-fasteoi uhci_hcd:usb6 > 21: 0 IR-IO-APIC-fasteoi ehci_hcd:usb2, uhci_hcd:usb5, uhci_hcd:usb7 > 72: 0 DMAR_MSI-edge dmar0 > 73: 0 IR-PCI-MSI-edge PCIe PME > 74: 0 IR-PCI-MSI-edge PCIe PME > 75: 0 IR-PCI-MSI-edge PCIe PME > 76: 0 IR-PCI-MSI-edge PCIe PME > 77: 0 IR-PCI-MSI-edge megasas > 78: 0 IR-PCI-MSI-edge eth0[0] > 79: 0 IR-PCI-MSI-edge eth0[1] > 80: 0 IR-PCI-MSI-edge eth0[2] > 81: 0 IR-PCI-MSI-edge eth0[3] > 82: 0 IR-PCI-MSI-edge eth1[0] > 83: 0 IR-PCI-MSI-edge eth1[1] > 84: 0 IR-PCI-MSI-edge eth1[2] > 85: 0 IR-PCI-MSI-edge eth1[3] > NMI: 0 Non-maskable interrupts > LOC: 1288 Local timer interrupts > SPU: 0 Spurious interrupts > PMI: 0 Performance monitoring interrupts > IWI: 0 IRQ work interrupts > RES: 295 Rescheduling interrupts > CAL: 675 Function call interrupts > TLB: 5 TLB shootdowns > TRM: 0 Thermal event interrupts > THR: 0 Threshold APIC interrupts > MCE: 0 Machine check exceptions > MCP: 2 Machine check polls > ERR: > MIS: > > *Xen:* > CPU0 > 8: 0 xen-pirq-ioapic-edge rtc0 > 9: 0 xen-pirq-ioapic-level acpi > 17: 0 xen-pirq-ioapic-level ata_piix, uhci_hcd:usb3 > 18: 0 xen-pirq-ioapic-level uhci_hcd:usb4 > 19: 0 xen-pirq-ioapic-level ehci_hcd:usb1 > 20: 0 xen-pirq-ioapic-level uhci_hcd:usb6 > 21: 0 xen-pirq-ioapic-level ehci_hcd:usb2, uhci_hcd:usb5, uhci_hcd:usb7 > 304: 0 xen-percpu-virq timer0 > 305: 0 xen-percpu-ipi resched0 > 306: 0 xen-percpu-ipi callfunc0 > 307: 0 xen-percpu-virq debug0 > 308: 0 xen-percpu-ipi callfuncsingle0 > 424: 0 xen-dyn-event xenbus > 425: 0 xen-pirq-msi PCIe PME > 426: 0 xen-pirq-msi PCIe PME > 427: 0 xen-pirq-msi PCIe PME > 428: 0 xen-pirq-msi PCIe PME So something is bogus here. There should be a bunch of ethX[Y] - and it looks like the MSI's just didn't get setup. What kernel version are you using? > 430: 0 xen-pirq-msi-x megasas Hm, but the megasas got an MSI, so... this really looks like something of the driver and Linux kernel (and the Xen PCI code) not working well. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |