* no-carrier on qlogic 8242 10gig with linux 3.x running xen @ 2012-03-27 8:48 Kristoffer Harthing Egefelt 2012-03-27 9:25 ` Wei Liu 0 siblings, 1 reply; 35+ messages in thread From: Kristoffer Harthing Egefelt @ 2012-03-27 8:48 UTC (permalink / raw) To: xen-devel Hi, Booting a plain debian linux with kernel 3.2 with xen 4.1.2, theres no link. When we boot the same kernel, without xen, there is link. We're using dell m610 blades with qlogic 8242 10gig nic's. Anybody seen this before or have an idea? Thanks Kristoffer -- View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5597283.html Sent from the Xen - Dev mailing list archive at Nabble.com. ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-27 8:48 no-carrier on qlogic 8242 10gig with linux 3.x running xen Kristoffer Harthing Egefelt @ 2012-03-27 9:25 ` Wei Liu 2012-03-27 9:43 ` Kristoffer Harthing Egefelt 0 siblings, 1 reply; 35+ messages in thread From: Wei Liu @ 2012-03-27 9:25 UTC (permalink / raw) To: Kristoffer Harthing Egefelt; +Cc: xen-devel@lists.xensource.com, wei.liu2 On Tue, 2012-03-27 at 09:48 +0100, Kristoffer Harthing Egefelt wrote: > Hi, > > Booting a plain debian linux with kernel 3.2 with xen 4.1.2, theres no link. > > When we boot the same kernel, without xen, there is link. > > We're using dell m610 blades with qlogic 8242 10gig nic's. > > Anybody seen this before or have an idea? > I play with 10G nic from time to time. Booting from Xen may change identifier of a nic (ethA -> ethB). Could you please check dmesg to see if there is any nic information? Wei. > Thanks > > Kristoffer > > -- > View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5597283.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-27 9:25 ` Wei Liu @ 2012-03-27 9:43 ` Kristoffer Harthing Egefelt 2012-03-27 10:02 ` Wei Liu 0 siblings, 1 reply; 35+ messages in thread From: Kristoffer Harthing Egefelt @ 2012-03-27 9:43 UTC (permalink / raw) To: xen-devel Please find dmesg below - do you see any hints? The onboard 1gig network cards are in fabric A, the 10gig's are in fabric B. I have disabled the onboard NICs so the 10gigs is eth0 and eth1. I have tried enabling the onboard NICs, making the 10gig's eth2 and eth3 without luck. Thanks oot@node0301:/var/log# cat dmesg.0 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.2.0-2-amd64 (Debian 3.2.9-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Sun Mar 4 22:48:17 UTC 2012 [ 0.000000] Command line: placeholder root=UUID=207d00d6-07a6-40e8-89dd-f0dd8a0cdbd1 ro quiet [ 0.000000] Freeing a0-100 pfn range: 96 pages freed [ 0.000000] 1-1 mapping on a0->100 [ 0.000000] Freeing cf379-100000 pfn range: 199815 pages freed [ 0.000000] 1-1 mapping on cf379->100000 [ 0.000000] Released 199911 pages of unused memory [ 0.000000] Set 199911 page(s) to 1-1 mapping [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] Xen: 0000000000000000 - 00000000000a0000 (usable) [ 0.000000] Xen: 00000000000a0000 - 0000000000100000 (reserved) [ 0.000000] Xen: 0000000000100000 - 00000000cf379000 (usable) [ 0.000000] Xen: 00000000cf379000 - 00000000cf38f000 (reserved) [ 0.000000] Xen: 00000000cf38f000 - 00000000cf3ce000 (ACPI data) [ 0.000000] Xen: 00000000cf3ce000 - 00000000d0000000 (reserved) [ 0.000000] Xen: 00000000e0000000 - 00000000f0000000 (reserved) [ 0.000000] Xen: 00000000fe000000 - 0000000100000000 (reserved) [ 0.000000] Xen: 0000000100000000 - 0000000c30000000 (usable) [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] DMI 2.6 present. [ 0.000000] DMI: Dell Inc. PowerEdge M610/0V56FN, BIOS 6.0.7 08/18/2011 [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable) [ 0.000000] No AGP bridge found [ 0.000000] last_pfn = 0xc30000 max_arch_pfn = 0x400000000 [ 0.000000] last_pfn = 0xcf379 max_arch_pfn = 0x400000000 [ 0.000000] found SMP MP-table at [ffff8800000fe710] fe710 [ 0.000000] initial memory mapped : 0 - 02017000 [ 0.000000] Base memory trampoline at [ffff88000009b000] 9b000 size 20480 [ 0.000000] init_memory_mapping: 0000000000000000-00000000cf379000 [ 0.000000] 0000000000 - 00cf379000 page 4k [ 0.000000] kernel direct mapping tables up to cf379000 @ 981000-1000000 [ 0.000000] xen: setting RW the range fba000 - 1000000 [ 0.000000] init_memory_mapping: 0000000100000000-0000000c30000000 [ 0.000000] 0100000000 - 0c30000000 page 4k [ 0.000000] kernel direct mapping tables up to c30000000 @ c91c7000-cf379000 [ 0.000000] xen: setting RW the range ceb74000 - cf379000 [ 0.000000] RAMDISK: 0193b000 - 02017000 [ 0.000000] ACPI: RSDP 00000000000f1840 00024 (v02 DELL ) [ 0.000000] ACPI: XSDT 00000000000f1944 0009C (v01 DELL PE_SC3 00000001 DELL 00000001) [ 0.000000] ACPI: FACP 00000000cf3b3f9c 000F4 (v03 DELL PE_SC3 00000001 DELL 00000001) [ 0.000000] ACPI: DSDT 00000000cf38f000 039D9 (v01 DELL PE_SC3 00000001 INTL 20050624) [ 0.000000] ACPI: FACS 00000000cf3b6000 00040 [ 0.000000] ACPI: APIC 00000000cf3b3478 0015E (v01 DELL PE_SC3 00000001 DELL 00000001) [ 0.000000] ACPI: SPCR 00000000cf3b35d8 00050 (v01 DELL PE_SC3 00000001 DELL 00000001) [ 0.000000] ACPI: HPET 00000000cf3b362c 00038 (v01 DELL PE_SC3 00000001 DELL 00000001) [ 0.000000] ACPI: XMAR 00000000cf3b3668 001C0 (v01 DELL PE_SC3 00000001 DELL 00000001) [ 0.000000] ACPI: MCFG 00000000cf3b38c4 0003C (v01 DELL PE_SC3 00000001 DELL 00000001) [ 0.000000] ACPI: WD__ 00000000cf3b3904 00134 (v01 DELL PE_SC3 00000001 DELL 00000001) [ 0.000000] ACPI: SLIC 00000000cf3b3a3c 00024 (v01 DELL PE_SC3 00000001 DELL 00000001) [ 0.000000] ACPI: ERST 00000000cf392b5c 00270 (v01 DELL PE_SC3 00000001 DELL 00000001) [ 0.000000] ACPI: HEST 00000000cf392dcc 003A8 (v01 DELL PE_SC3 00000001 DELL 00000001) [ 0.000000] ACPI: BERT 00000000cf3929dc 00030 (v01 DELL PE_SC3 00000001 DELL 00000001) [ 0.000000] ACPI: EINJ 00000000cf392a0c 00150 (v01 DELL PE_SC3 00000001 DELL 00000001) [ 0.000000] ACPI: SRAT 00000000cf3b3bc0 00370 (v01 DELL PE_SC3 00000001 DELL 00000001) [ 0.000000] ACPI: TCPA 00000000cf3b3f34 00064 (v02 DELL PE_SC3 00000001 DELL 00000001) [ 0.000000] ACPI: SSDT 00000000cf3b7000 065DC (v01 INTEL PPM RCM 80000001 INTL 20061109) [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at 0000000000000000-0000000c30000000 [ 0.000000] Initmem setup node 0 0000000000000000-0000000c30000000 [ 0.000000] NODE_DATA [0000000bcf691000 - 0000000bcf695fff] [ 0.000000] Zone PFN ranges: [ 0.000000] DMA 0x00000010 -> 0x00001000 [ 0.000000] DMA32 0x00001000 -> 0x00100000 [ 0.000000] Normal 0x00100000 -> 0x00c30000 [ 0.000000] Movable zone start PFN for each node [ 0.000000] early_node_map[3] active PFN ranges [ 0.000000] 0: 0x00000010 -> 0x000000a0 [ 0.000000] 0: 0x00000100 -> 0x000cf379 [ 0.000000] 0: 0x00100000 -> 0x00c30000 [ 0.000000] On node 0 totalpages: 12579593 [ 0.000000] DMA zone: 56 pages used for memmap [ 0.000000] DMA zone: 1598 pages reserved [ 0.000000] DMA zone: 2330 pages, LIFO batch:0 [ 0.000000] DMA32 zone: 14280 pages used for memmap [ 0.000000] DMA32 zone: 830385 pages, LIFO batch:31 [ 0.000000] Normal zone: 160384 pages used for memmap [ 0.000000] Normal zone: 11570560 pages, LIFO batch:31 [ 0.000000] ACPI: PM-Timer IO Port: 0x808 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x20] enabled) [ 0.000000] BIOS bug: APIC version is 0 for CPU 1/0x20, fixing up to 0x10 [ 0.000000] BIOS bug: APIC version mismatch, boot CPU: 0, CPU 1: version 10 [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x00] enabled) [ 0.000000] BIOS bug: APIC version is 0 for CPU 0/0x0, fixing up to 0x10 [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x22] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x02] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x24] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x04] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x30] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x10] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x32] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x12] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x34] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x14] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x21] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x01] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x23] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x03] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x25] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x05] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x31] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x14] lapic_id[0x11] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x15] lapic_id[0x33] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x16] lapic_id[0x13] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x17] lapic_id[0x35] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x15] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0xff] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0xff] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0xff] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x1c] lapic_id[0xff] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x1d] lapic_id[0xff] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x1e] lapic_id[0xff] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x1f] lapic_id[0xff] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x20] lapic_id[0xff] disabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0]) [ 0.000000] IOAPIC[0]: apic_id 0, version 255, address 0xfec00000, GSI 0-255 [ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec80000] gsi_base[32]) [ 0.000000] IOAPIC[1]: apic_id 1, version 255, address 0xfec80000, GSI 32-287 [ 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: IRQ2 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] SMP: Allowing 32 CPUs, 8 hotplug CPUs [ 0.000000] nr_irqs_gsi: 304 [ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 0000000000100000 [ 0.000000] PM: Registered nosave memory: 00000000cf379000 - 00000000cf38f000 [ 0.000000] PM: Registered nosave memory: 00000000cf38f000 - 00000000cf3ce000 [ 0.000000] PM: Registered nosave memory: 00000000cf3ce000 - 00000000d0000000 [ 0.000000] PM: Registered nosave memory: 00000000d0000000 - 00000000e0000000 [ 0.000000] PM: Registered nosave memory: 00000000e0000000 - 00000000f0000000 [ 0.000000] PM: Registered nosave memory: 00000000f0000000 - 00000000fe000000 [ 0.000000] PM: Registered nosave memory: 00000000fe000000 - 0000000100000000 [ 0.000000] Allocating PCI resources starting at d0000000 (gap: d0000000:10000000) [ 0.000000] Booting paravirtualized kernel on Xen [ 0.000000] Xen version: 4.1.2 (preserve-AD) [ 0.000000] setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:32 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff880bcf2be000 s82304 r8192 d24192 u114688 [ 0.000000] pcpu-alloc: s82304 r8192 d24192 u114688 alloc=28*4096 [ 0.000000] pcpu-alloc: [0] 00 [0] 01 [0] 02 [0] 03 [0] 04 [0] 05 [0] 06 [0] 07 [ 0.000000] pcpu-alloc: [0] 08 [0] 09 [0] 10 [0] 11 [0] 12 [0] 13 [0] 14 [0] 15 [ 0.000000] pcpu-alloc: [0] 16 [0] 17 [0] 18 [0] 19 [0] 20 [0] 21 [0] 22 [0] 23 [ 0.000000] pcpu-alloc: [0] 24 [0] 25 [0] 26 [0] 27 [0] 28 [0] 29 [0] 30 [0] 31 [ 9.437371] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 12403275 [ 9.437373] Policy zone: Normal [ 9.437376] Kernel command line: placeholder root=UUID=207d00d6-07a6-40e8-89dd-f0dd8a0cdbd1 ro quiet [ 9.437424] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 9.470012] Placing 64MB software IO TLB between ffff880bcae00000 - ffff880bcee00000 [ 9.470016] software IO TLB at phys 0xbcae00000 - 0xbcee00000 [ 9.708326] Memory: 47765528k/51118080k available (3371k kernel code, 799708k absent, 2552844k reserved, 3360k data, 568k init) [ 9.708508] Hierarchical RCU implementation. [ 9.708510] RCU dyntick-idle grace-period acceleration is enabled. [ 9.708550] NR_IRQS:33024 nr_irqs:5424 16 [ 9.708659] xen: sci override: global_irq=9 trigger=0 polarity=0 [ 9.708662] xen: registering gsi 9 triggering 0 polarity 0 [ 9.708674] xen: --> pirq=9 -> irq=9 (gsi=9) [ 9.708707] xen: acpi sci 9 [ 9.708711] xen: --> pirq=1 -> irq=1 (gsi=1) [ 9.708715] xen: --> pirq=2 -> irq=2 (gsi=2) [ 9.708718] xen: --> pirq=3 -> irq=3 (gsi=3) [ 9.708721] xen: --> pirq=4 -> irq=4 (gsi=4) [ 9.708724] xen: --> pirq=5 -> irq=5 (gsi=5) [ 9.708728] xen: --> pirq=6 -> irq=6 (gsi=6) [ 9.708731] xen: --> pirq=7 -> irq=7 (gsi=7) [ 9.708734] xen: --> pirq=8 -> irq=8 (gsi=8) [ 9.708737] xen_map_pirq_gsi: returning irq 9 for gsi 9 [ 9.708739] xen: --> pirq=9 -> irq=9 (gsi=9) [ 9.708742] xen: --> pirq=10 -> irq=10 (gsi=10) [ 9.708745] xen: --> pirq=11 -> irq=11 (gsi=11) [ 9.708749] xen: --> pirq=12 -> irq=12 (gsi=12) [ 9.708752] xen: --> pirq=13 -> irq=13 (gsi=13) [ 9.708756] xen: --> pirq=14 -> irq=14 (gsi=14) [ 9.708759] xen: --> pirq=15 -> irq=15 (gsi=15) [ 9.714847] Console: colour VGA+ 80x25 [ 9.714873] console [tty0] enabled [ 9.714932] Xen: using vcpuop timer interface [ 9.714938] installing Xen timer for CPU 0 [ 9.714963] Detected 2394.050 MHz processor. [ 9.714977] Calibrating delay loop (skipped), value calculated using timer frequency.. 4788.10 BogoMIPS (lpj=9576200) [ 9.714981] pid_max: default: 32768 minimum: 301 [ 9.715038] Security Framework initialized [ 9.715044] AppArmor: AppArmor disabled by boot time parameter [ 9.731180] Dentry cache hash table entries: 8388608 (order: 14, 67108864 bytes) [ 9.754400] Inode-cache hash table entries: 4194304 (order: 13, 33554432 bytes) [ 9.762236] Mount-cache hash table entries: 256 [ 9.762443] Initializing cgroup subsys cpuacct [ 9.762451] Initializing cgroup subsys memory [ 9.762476] Initializing cgroup subsys devices [ 9.762479] Initializing cgroup subsys freezer [ 9.762482] Initializing cgroup subsys net_cls [ 9.762484] Initializing cgroup subsys blkio [ 9.762494] Initializing cgroup subsys perf_event [ 9.762569] CPU: Physical Processor ID: 1 [ 9.762571] CPU: Processor Core ID: 0 [ 9.763087] ACPI: Core revision 20110623 [ 9.774492] Performance Events: unsupported p6 CPU model 44 no PMU driver, software events only. [ 9.774695] NMI watchdog disabled (cpu0): hardware events not enabled [ 9.774835] installing Xen timer for CPU 1 [ 9.775022] NMI watchdog disabled (cpu1): hardware events not enabled [ 9.775154] installing Xen timer for CPU 2 [ 9.775277] NMI watchdog disabled (cpu2): hardware events not enabled [ 9.775405] installing Xen timer for CPU 3 [ 9.775521] NMI watchdog disabled (cpu3): hardware events not enabled [ 9.775651] installing Xen timer for CPU 4 [ 9.775773] NMI watchdog disabled (cpu4): hardware events not enabled [ 9.775898] installing Xen timer for CPU 5 [ 9.776016] NMI watchdog disabled (cpu5): hardware events not enabled [ 9.776145] installing Xen timer for CPU 6 [ 9.776267] NMI watchdog disabled (cpu6): hardware events not enabled [ 9.776393] installing Xen timer for CPU 7 [ 9.776511] NMI watchdog disabled (cpu7): hardware events not enabled [ 9.776638] installing Xen timer for CPU 8 [ 9.776760] NMI watchdog disabled (cpu8): hardware events not enabled [ 9.776889] installing Xen timer for CPU 9 [ 9.777009] NMI watchdog disabled (cpu9): hardware events not enabled [ 9.777136] installing Xen timer for CPU 10 [ 9.777259] NMI watchdog disabled (cpu10): hardware events not enabled [ 9.777390] installing Xen timer for CPU 11 [ 9.777507] NMI watchdog disabled (cpu11): hardware events not enabled [ 9.777644] installing Xen timer for CPU 12 [ 9.777826] NMI watchdog disabled (cpu12): hardware events not enabled [ 9.777960] installing Xen timer for CPU 13 [ 9.778111] NMI watchdog disabled (cpu13): hardware events not enabled [ 9.778243] installing Xen timer for CPU 14 [ 9.778400] NMI watchdog disabled (cpu14): hardware events not enabled [ 9.778535] installing Xen timer for CPU 15 [ 9.778686] NMI watchdog disabled (cpu15): hardware events not enabled [ 9.778815] installing Xen timer for CPU 16 [ 9.778977] NMI watchdog disabled (cpu16): hardware events not enabled [ 9.779107] installing Xen timer for CPU 17 [ 9.779260] NMI watchdog disabled (cpu17): hardware events not enabled [ 9.779394] installing Xen timer for CPU 18 [ 9.779554] NMI watchdog disabled (cpu18): hardware events not enabled [ 9.779683] installing Xen timer for CPU 19 [ 9.779837] NMI watchdog disabled (cpu19): hardware events not enabled [ 9.779969] installing Xen timer for CPU 20 [ 9.780127] NMI watchdog disabled (cpu20): hardware events not enabled [ 9.780256] installing Xen timer for CPU 21 [ 9.780408] NMI watchdog disabled (cpu21): hardware events not enabled [ 9.780540] installing Xen timer for CPU 22 [ 9.780699] NMI watchdog disabled (cpu22): hardware events not enabled [ 9.780828] installing Xen timer for CPU 23 [ 9.780982] NMI watchdog disabled (cpu23): hardware events not enabled [ 9.781006] Brought up 24 CPUs [ 9.781867] devtmpfs: initialized [ 9.789356] Grant table initialized [ 9.789440] print_constraints: dummy: [ 9.789642] NET: Registered protocol family 16 [ 9.789890] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [ 9.789893] ACPI: bus type pci registered [ 9.790011] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000) [ 9.790015] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820 [ 9.850148] PCI: Using configuration type 1 for base access [ 9.853088] bio: create slab <bio-0> at 0 [ 9.853502] ACPI: Added _OSI(Module Device) [ 9.853506] ACPI: Added _OSI(Processor Device) [ 9.853509] ACPI: Added _OSI(3.0 _SCP Extensions) [ 9.853511] ACPI: Added _OSI(Processor Aggregator Device) [ 9.854952] ACPI: EC: Look up EC in DSDT [ 9.857408] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored [ 9.865597] ACPI: Interpreter enabled [ 9.865602] ACPI: (supports S0 S4 S5) [ 9.865618] ACPI: Using IOAPIC for interrupt routing [ 9.871351] ACPI: No dock devices found. [ 9.871638] HEST: Table parsing has been initialized. [ 9.871642] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 9.872209] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) [ 9.872677] pci_root PNP0A08:00: host bridge window [io 0x0000-0x0cf7] [ 9.872680] pci_root PNP0A08:00: host bridge window [io 0x0d00-0xffff] [ 9.872683] pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff] [ 9.872685] pci_root PNP0A08:00: host bridge window [mem 0xd0000000-0xfdffffff] [ 9.872688] pci_root PNP0A08:00: host bridge window [mem 0xfed40000-0xfed44fff] [ 9.872715] pci 0000:00:00.0: [8086:3403] type 0 class 0x000600 [ 9.872829] pci 0000:00:00.0: PME# supported from D0 D3hot D3cold [ 9.872835] pci 0000:00:00.0: PME# disabled [ 9.872881] pci 0000:00:01.0: [8086:3408] type 1 class 0x000604 [ 9.873000] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold [ 9.873006] pci 0000:00:01.0: PME# disabled [ 9.873058] pci 0000:00:07.0: [8086:340e] type 1 class 0x000604 [ 9.873179] pci 0000:00:07.0: PME# supported from D0 D3hot D3cold [ 9.873184] pci 0000:00:07.0: PME# disabled [ 9.873231] pci 0000:00:09.0: [8086:3410] type 1 class 0x000604 [ 9.873351] pci 0000:00:09.0: PME# supported from D0 D3hot D3cold [ 9.873357] pci 0000:00:09.0: PME# disabled [ 9.873409] pci 0000:00:14.0: [8086:342e] type 0 class 0x000800 [ 9.873550] pci 0000:00:14.1: [8086:3422] type 0 class 0x000800 [ 9.873689] pci 0000:00:14.2: [8086:3423] type 0 class 0x000800 [ 9.873854] pci 0000:00:1a.0: [8086:2937] type 0 class 0x000c03 [ 9.873932] pci 0000:00:1a.0: reg 20: [io 0xe8c0-0xe8df] [ 9.874026] pci 0000:00:1a.1: [8086:2938] type 0 class 0x000c03 [ 9.874104] pci 0000:00:1a.1: reg 20: [io 0xe8e0-0xe8ff] [ 9.874215] pci 0000:00:1a.7: [8086:293c] type 0 class 0x000c03 [ 9.874251] pci 0000:00:1a.7: reg 10: [mem 0xdffff800-0xdffffbff] [ 9.874410] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold [ 9.874417] pci 0000:00:1a.7: PME# disabled [ 9.874454] pci 0000:00:1c.0: [8086:2940] type 1 class 0x000604 [ 9.874589] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold [ 9.874594] pci 0000:00:1c.0: PME# disabled [ 9.874646] pci 0000:00:1d.0: [8086:2934] type 0 class 0x000c03 [ 9.874724] pci 0000:00:1d.0: reg 20: [io 0xec00-0xec1f] [ 9.874818] pci 0000:00:1d.1: [8086:2935] type 0 class 0x000c03 [ 9.874897] pci 0000:00:1d.1: reg 20: [io 0xec20-0xec3f] [ 9.874990] pci 0000:00:1d.2: [8086:2936] type 0 class 0x000c03 [ 9.875068] pci 0000:00:1d.2: reg 20: [io 0xec40-0xec5f] [ 9.875178] pci 0000:00:1d.7: [8086:293a] type 0 class 0x000c03 [ 9.875214] pci 0000:00:1d.7: reg 10: [mem 0xdffffc00-0xdfffffff] [ 9.875373] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold [ 9.875380] pci 0000:00:1d.7: PME# disabled [ 9.875414] pci 0000:00:1e.0: [8086:244e] type 1 class 0x000604 [ 9.875532] pci 0000:00:1f.0: [8086:2918] type 0 class 0x000601 [ 9.875666] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0c00 (mask 007f) [ 9.875670] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 0ca0 (mask 000f) [ 9.875675] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 3 PIO at 00e0 (mask 000f) [ 9.875758] pci 0000:00:1f.5: [8086:2926] type 0 class 0x000101 [ 9.875787] pci 0000:00:1f.5: reg 10: [io 0xece0-0xece7] [ 9.875801] pci 0000:00:1f.5: reg 14: [io 0xecf8-0xecfb] [ 9.875815] pci 0000:00:1f.5: reg 18: [io 0xece8-0xecef] [ 9.875830] pci 0000:00:1f.5: reg 1c: [io 0xecfc-0xecff] [ 9.875844] pci 0000:00:1f.5: reg 20: [io 0xecb0-0xecbf] [ 9.875859] pci 0000:00:1f.5: reg 24: [io 0xecc0-0xeccf] [ 9.876012] pci 0000:00:01.0: PCI bridge to [bus 01-01] [ 9.876127] pci 0000:03:00.0: [1077:8020] type 0 class 0x000200 [ 9.876153] pci 0000:03:00.0: reg 10: [mem 0xdf800000-0xdf9fffff 64bit] [ 9.876198] pci 0000:03:00.0: reg 20: [mem 0xdfde0000-0xdfdeffff 64bit] [ 9.876213] pci 0000:03:00.0: reg 30: [mem 0xdfd80000-0xdfdbffff pref] [ 9.876297] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold [ 9.876303] pci 0000:03:00.0: PME# disabled [ 9.876353] pci 0000:03:00.1: [1077:8020] type 0 class 0x000200 [ 9.876379] pci 0000:03:00.1: reg 10: [mem 0xdfa00000-0xdfbfffff 64bit] [ 9.876424] pci 0000:03:00.1: reg 20: [mem 0xdfdf0000-0xdfdfffff 64bit] [ 9.876439] pci 0000:03:00.1: reg 30: [mem 0xdfd80000-0xdfdbffff pref] [ 9.876523] pci 0000:03:00.1: PME# supported from D0 D3hot D3cold [ 9.876529] pci 0000:03:00.1: PME# disabled [ 9.881935] pci 0000:00:07.0: PCI bridge to [bus 03-03] [ 9.881948] pci 0000:00:07.0: bridge window [mem 0xdf800000-0xdfdfffff] [ 9.882041] pci 0000:00:09.0: PCI bridge to [bus 04-04] [ 9.882152] pci 0000:02:00.0: [1000:0079] type 0 class 0x000104 [ 9.882176] pci 0000:02:00.0: reg 10: [io 0xfc00-0xfcff] [ 9.882202] pci 0000:02:00.0: reg 14: [mem 0xdfefc000-0xdfefffff 64bit] [ 9.882229] pci 0000:02:00.0: reg 1c: [mem 0xdfe40000-0xdfe7ffff 64bit] [ 9.882262] pci 0000:02:00.0: reg 30: [mem 0xdfe80000-0xdfebffff pref] [ 9.882368] pci 0000:02:00.0: supports D1 D2 [ 9.890028] pci 0000:00:1c.0: PCI bridge to [bus 02-02] [ 9.890038] pci 0000:00:1c.0: bridge window [io 0xf000-0xffff] [ 9.890046] pci 0000:00:1c.0: bridge window [mem 0xdfe00000-0xdfefffff] [ 9.890133] pci 0000:05:03.0: [102b:0532] type 0 class 0x000300 [ 9.890162] pci 0000:05:03.0: reg 10: [mem 0xde000000-0xde7fffff pref] [ 9.890178] pci 0000:05:03.0: reg 14: [mem 0xdf7fc000-0xdf7fffff] [ 9.890194] pci 0000:05:03.0: reg 18: [mem 0xde800000-0xdeffffff] [ 9.890251] pci 0000:05:03.0: reg 30: [mem 0x00000000-0x0000ffff pref] [ 9.890364] pci 0000:00:1e.0: PCI bridge to [bus 05-05] (subtractive decode) [ 9.890374] pci 0000:00:1e.0: bridge window [mem 0xde800000-0xdf7fffff] [ 9.890383] pci 0000:00:1e.0: bridge window [mem 0xde000000-0xde7fffff 64bit pref] [ 9.890387] pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode) [ 9.890390] pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode) [ 9.890393] pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode) [ 9.890396] pci 0000:00:1e.0: bridge window [mem 0xd0000000-0xfdffffff] (subtractive decode) [ 9.890399] pci 0000:00:1e.0: bridge window [mem 0xfed40000-0xfed44fff] (subtractive decode) [ 9.890440] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] [ 9.891385] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT] [ 9.891559] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX7._PRT] [ 9.891725] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX9._PRT] [ 9.891887] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.SBEX._PRT] [ 9.892044] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.COMP._PRT] [ 9.892454] pci0000:00: Requesting ACPI _OSC control (0x15) [ 9.893138] pci0000:00: ACPI _OSC control (0x15) granted [ 9.898687] ACPI: PCI Interrupt Link [LK00] (IRQs 3 4 5 6 7 10 11 14 *15) [ 9.898815] ACPI: PCI Interrupt Link [LK01] (IRQs 3 4 5 6 7 10 11 *14 15) [ 9.898943] ACPI: PCI Interrupt Link [LK02] (IRQs 3 4 5 6 7 10 *11 14 15) [ 9.899066] ACPI: PCI Interrupt Link [LK03] (IRQs 3 4 5 6 7 *10 11 14 15) [ 9.899188] ACPI: PCI Interrupt Link [LK04] (IRQs 3 4 *5 6 7 10 11 14 15) [ 9.899311] ACPI: PCI Interrupt Link [LK05] (IRQs 3 4 5 *6 7 10 11 14 15) [ 9.899433] ACPI: PCI Interrupt Link [LK06] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled. [ 9.899557] ACPI: PCI Interrupt Link [LK07] (IRQs 3 *4 5 6 7 10 11 14 15) [ 9.899623] xen/balloon: Initialising balloon driver. [ 9.907655] xen-balloon: Initialising balloon driver. [ 9.907830] vgaarb: device added: PCI:0000:05:03.0,decodes=io+mem,owns=io+mem,locks=none [ 9.907833] vgaarb: loaded [ 9.907835] vgaarb: bridge control possible 0000:05:03.0 [ 9.907884] PCI: Using ACPI for IRQ routing [ 9.919996] PCI: Discovered peer bus fe [ 9.920065] pci 0000:fe:00.0: [8086:2c70] type 0 class 0x000600 [ 9.920129] pci 0000:fe:00.1: [8086:2d81] type 0 class 0x000600 [ 9.920194] pci 0000:fe:02.0: [8086:2d90] type 0 class 0x000600 [ 9.920251] pci 0000:fe:02.1: [8086:2d91] type 0 class 0x000600 [ 9.920307] pci 0000:fe:02.2: [8086:2d92] type 0 class 0x000600 [ 9.920363] pci 0000:fe:02.3: [8086:2d93] type 0 class 0x000600 [ 9.920420] pci 0000:fe:02.4: [8086:2d94] type 0 class 0x000600 [ 9.920476] pci 0000:fe:02.5: [8086:2d95] type 0 class 0x000600 [ 9.920535] pci 0000:fe:03.0: [8086:2d98] type 0 class 0x000600 [ 9.920591] pci 0000:fe:03.1: [8086:2d99] type 0 class 0x000600 [ 9.920647] pci 0000:fe:03.2: [8086:2d9a] type 0 class 0x000600 [ 9.920705] pci 0000:fe:03.4: [8086:2d9c] type 0 class 0x000600 [ 9.920765] pci 0000:fe:04.0: [8086:2da0] type 0 class 0x000600 [ 9.920821] pci 0000:fe:04.1: [8086:2da1] type 0 class 0x000600 [ 9.920877] pci 0000:fe:04.2: [8086:2da2] type 0 class 0x000600 [ 9.920933] pci 0000:fe:04.3: [8086:2da3] type 0 class 0x000600 [ 9.920995] pci 0000:fe:05.0: [8086:2da8] type 0 class 0x000600 [ 9.921051] pci 0000:fe:05.1: [8086:2da9] type 0 class 0x000600 [ 9.921107] pci 0000:fe:05.2: [8086:2daa] type 0 class 0x000600 [ 9.921166] pci 0000:fe:05.3: [8086:2dab] type 0 class 0x000600 [ 9.921232] pci 0000:fe:06.0: [8086:2db0] type 0 class 0x000600 [ 9.921289] pci 0000:fe:06.1: [8086:2db1] type 0 class 0x000600 [ 9.921345] pci 0000:fe:06.2: [8086:2db2] type 0 class 0x000600 [ 9.921401] pci 0000:fe:06.3: [8086:2db3] type 0 class 0x000600 [ 9.922214] PCI: Discovered peer bus ff [ 9.922260] pci 0000:ff:00.0: [8086:2c70] type 0 class 0x000600 [ 9.922320] pci 0000:ff:00.1: [8086:2d81] type 0 class 0x000600 [ 9.922388] pci 0000:ff:02.0: [8086:2d90] type 0 class 0x000600 [ 9.922447] pci 0000:ff:02.1: [8086:2d91] type 0 class 0x000600 [ 9.922506] pci 0000:ff:02.2: [8086:2d92] type 0 class 0x000600 [ 9.922564] pci 0000:ff:02.3: [8086:2d93] type 0 class 0x000600 [ 9.922623] pci 0000:ff:02.4: [8086:2d94] type 0 class 0x000600 [ 9.922682] pci 0000:ff:02.5: [8086:2d95] type 0 class 0x000600 [ 9.922743] pci 0000:ff:03.0: [8086:2d98] type 0 class 0x000600 [ 9.922802] pci 0000:ff:03.1: [8086:2d99] type 0 class 0x000600 [ 9.922860] pci 0000:ff:03.2: [8086:2d9a] type 0 class 0x000600 [ 9.922920] pci 0000:ff:03.4: [8086:2d9c] type 0 class 0x000600 [ 9.922983] pci 0000:ff:04.0: [8086:2da0] type 0 class 0x000600 [ 9.923042] pci 0000:ff:04.1: [8086:2da1] type 0 class 0x000600 [ 9.923100] pci 0000:ff:04.2: [8086:2da2] type 0 class 0x000600 [ 9.923159] pci 0000:ff:04.3: [8086:2da3] type 0 class 0x000600 [ 9.923223] pci 0000:ff:05.0: [8086:2da8] type 0 class 0x000600 [ 9.923282] pci 0000:ff:05.1: [8086:2da9] type 0 class 0x000600 [ 9.923341] pci 0000:ff:05.2: [8086:2daa] type 0 class 0x000600 [ 9.923399] pci 0000:ff:05.3: [8086:2dab] type 0 class 0x000600 [ 9.923465] pci 0000:ff:06.0: [8086:2db0] type 0 class 0x000600 [ 9.923524] pci 0000:ff:06.1: [8086:2db1] type 0 class 0x000600 [ 9.923582] pci 0000:ff:06.2: [8086:2db2] type 0 class 0x000600 [ 9.923643] pci 0000:ff:06.3: [8086:2db3] type 0 class 0x000600 [ 9.924469] PCI: pci_cache_line_size set to 64 bytes [ 9.924766] reserve RAM buffer: 00000000cf379000 - 00000000cfffffff [ 9.924963] Switching to clocksource xen [ 9.927723] pnp: PnP ACPI init [ 9.927740] ACPI: bus type pnp registered [ 9.928034] pnp 00:00: [bus 00-ff] [ 9.928037] pnp 00:00: [io 0x0cf8-0x0cff] [ 9.928040] pnp 00:00: [io 0x0000-0x0cf7 window] [ 9.928044] pnp 00:00: [io 0x0d00-0xffff window] [ 9.928047] pnp 00:00: [mem 0x000a0000-0x000bffff window] [ 9.928050] pnp 00:00: [mem 0xd0000000-0xfdffffff window] [ 9.928052] pnp 00:00: [mem 0xfed40000-0xfed44fff window] [ 9.928144] pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active) [ 9.928236] pnp 00:01: [io 0x0080-0x009f] [ 9.928239] pnp 00:01: [io 0x0000-0x001f] [ 9.928242] pnp 00:01: [io 0x00c0-0x00df] [ 9.928244] pnp 00:01: [dma 4] [ 9.928287] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active) [ 9.928328] pnp 00:02: [io 0x00f0-0x00ff] [ 9.928332] xen: registering gsi 13 triggering 1 polarity 0 [ 9.928338] xen_map_pirq_gsi: returning irq 13 for gsi 13 [ 9.928341] xen: --> pirq=13 -> irq=13 (gsi=13) [ 9.928374] pnp 00:02: [irq 13] [ 9.928418] pnp 00:02: Plug and Play ACPI device, IDs PNP0c04 (active) [ 9.928461] pnp 00:03: [io 0x0061] [ 9.928554] system 00:03: Plug and Play ACPI device, IDs PNP0c01 (active) [ 9.928596] pnp 00:04: [io 0x0070-0x007f] [ 9.928599] xen: registering gsi 8 triggering 1 polarity 0 [ 9.928602] xen_map_pirq_gsi: returning irq 8 for gsi 8 [ 9.928604] xen: --> pirq=8 -> irq=8 (gsi=8) [ 9.928634] pnp 00:04: [irq 8] [ 9.928676] pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active) [ 9.928913] pnp 00:05: Plug and Play ACPI device, IDs PNP0501 (disabled) [ 9.929754] pnp 00:06: [io 0x0800-0x087f] [ 9.929757] pnp 00:06: [io 0x00e0-0x00e7] [ 9.929759] pnp 00:06: [io 0x0880-0x08ff] [ 9.929762] pnp 00:06: [io 0x0900-0x091f] [ 9.929764] pnp 00:06: [io 0x0920-0x0923] [ 9.929767] pnp 00:06: [io 0x0924] [ 9.929769] pnp 00:06: [io 0x0ca0-0x0ca7] [ 9.929773] pnp 00:06: [io 0x0ca9-0x0cab] [ 9.929775] pnp 00:06: [io 0x0cad-0x0caf] [ 9.929778] pnp 00:06: [io 0x0060-0x005f disabled] [ 9.929781] pnp 00:06: [io 0x0064-0x0063 disabled] [ 9.929882] system 00:06: [io 0x0800-0x087f] has been reserved [ 9.929885] system 00:06: [io 0x0880-0x08ff] has been reserved [ 9.929888] system 00:06: [io 0x0900-0x091f] has been reserved [ 9.929892] system 00:06: [io 0x0920-0x0923] has been reserved [ 9.929895] system 00:06: [io 0x0924] has been reserved [ 9.929898] system 00:06: [io 0x0ca0-0x0ca7] has been reserved [ 9.929901] system 00:06: [io 0x0ca9-0x0cab] has been reserved [ 9.929904] system 00:06: [io 0x0cad-0x0caf] has been reserved [ 9.929908] system 00:06: Plug and Play ACPI device, IDs PNP0c01 (active) [ 9.930002] pnp 00:07: [io 0x0ca8] [ 9.930004] pnp 00:07: [io 0x0cac] [ 9.930007] pnp 00:07: [irq 0 disabled] [ 9.930098] system 00:07: [io 0x0ca8] has been reserved [ 9.930102] system 00:07: [io 0x0cac] has been reserved [ 9.930105] system 00:07: Plug and Play ACPI device, IDs IPI0001 PNP0c01 (active) [ 9.931369] pnp 00:08: [mem 0xe0000000-0xefffffff] [ 9.931473] system 00:08: [mem 0xe0000000-0xefffffff] has been reserved [ 9.931477] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active) [ 9.931578] pnp 00:09: [mem 0xfed00000-0xfed003ff] [ 9.931625] pnp 00:09: Plug and Play ACPI device, IDs PNP0103 (active) [ 9.931652] pnp 00:0a: [mem 0xfed90000-0xfed91fff] [ 9.931745] system 00:0a: [mem 0xfed90000-0xfed91fff] has been reserved [ 9.931749] system 00:0a: Plug and Play ACPI device, IDs PNP0c02 (active) [ 9.932093] pnp: PnP ACPI: found 11 devices [ 9.932095] ACPI: ACPI bus type pnp unregistered [ 9.939973] PM-Timer failed consistency check (0x0xffffff) - aborting. [ 9.939990] pci 0000:03:00.1: address space collision: [mem 0xdfd80000-0xdfdbffff pref] conflicts with 0000:03:00.0 [mem 0xdfd80000-0xdfdbffff pref] [ 9.940022] PCI: max bus depth: 1 pci_try_num: 2 [ 9.940090] pci 0000:00:07.0: BAR 15: assigned [mem 0xd0000000-0xd00fffff pref] [ 9.940094] pci 0000:00:01.0: PCI bridge to [bus 01-01] [ 9.940111] pci 0000:03:00.1: BAR 6: assigned [mem 0xd0000000-0xd003ffff pref] [ 9.940114] pci 0000:00:07.0: PCI bridge to [bus 03-03] [ 9.940121] pci 0000:00:07.0: bridge window [mem 0xdf800000-0xdfdfffff] [ 9.940127] pci 0000:00:07.0: bridge window [mem 0xd0000000-0xd00fffff pref] [ 9.940136] pci 0000:00:09.0: PCI bridge to [bus 04-04] [ 9.940152] pci 0000:00:1c.0: PCI bridge to [bus 02-02] [ 9.940156] pci 0000:00:1c.0: bridge window [io 0xf000-0xffff] [ 9.940164] pci 0000:00:1c.0: bridge window [mem 0xdfe00000-0xdfefffff] [ 9.940178] pci 0000:05:03.0: BAR 6: assigned [mem 0xdf000000-0xdf00ffff pref] [ 9.940180] pci 0000:00:1e.0: PCI bridge to [bus 05-05] [ 9.940188] pci 0000:00:1e.0: bridge window [mem 0xde800000-0xdf7fffff] [ 9.940194] pci 0000:00:1e.0: bridge window [mem 0xde000000-0xde7fffff 64bit pref] [ 9.940212] xen: registering gsi 53 triggering 0 polarity 1 [ 9.940233] xen: --> pirq=53 -> irq=53 (gsi=53) [ 9.940264] pci 0000:00:01.0: PCI INT A -> GSI 53 (level, low) -> IRQ 53 [ 9.940271] pci 0000:00:01.0: setting latency timer to 64 [ 9.940280] xen: registering gsi 53 triggering 0 polarity 1 [ 9.940283] xen_map_pirq_gsi: returning irq 53 for gsi 53 [ 9.940285] xen: --> pirq=53 -> irq=53 (gsi=53) [ 9.940287] Already setup the GSI :53 [ 9.940289] pci 0000:00:07.0: PCI INT A -> GSI 53 (level, low) -> IRQ 53 [ 9.940295] pci 0000:00:07.0: setting latency timer to 64 [ 9.940303] xen: registering gsi 53 triggering 0 polarity 1 [ 9.940306] xen_map_pirq_gsi: returning irq 53 for gsi 53 [ 9.940308] xen: --> pirq=53 -> irq=53 (gsi=53) [ 9.940310] Already setup the GSI :53 [ 9.940312] pci 0000:00:09.0: PCI INT A -> GSI 53 (level, low) -> IRQ 53 [ 9.940318] pci 0000:00:09.0: setting latency timer to 64 [ 9.940327] xen: registering gsi 16 triggering 0 polarity 1 [ 9.940339] xen: --> pirq=16 -> irq=16 (gsi=16) [ 9.940367] pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 9.940373] pci 0000:00:1c.0: setting latency timer to 64 [ 9.940384] pci 0000:00:1e.0: setting latency timer to 64 [ 9.940390] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7] [ 9.940392] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff] [ 9.940395] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff] [ 9.940397] pci_bus 0000:00: resource 7 [mem 0xd0000000-0xfdffffff] [ 9.940400] pci_bus 0000:00: resource 8 [mem 0xfed40000-0xfed44fff] [ 9.940403] pci_bus 0000:03: resource 1 [mem 0xdf800000-0xdfdfffff] [ 9.940405] pci_bus 0000:03: resource 2 [mem 0xd0000000-0xd00fffff pref] [ 9.940408] pci_bus 0000:02: resource 0 [io 0xf000-0xffff] [ 9.940410] pci_bus 0000:02: resource 1 [mem 0xdfe00000-0xdfefffff] [ 9.940413] pci_bus 0000:05: resource 1 [mem 0xde800000-0xdf7fffff] [ 9.940416] pci_bus 0000:05: resource 2 [mem 0xde000000-0xde7fffff 64bit pref] [ 9.940418] pci_bus 0000:05: resource 4 [io 0x0000-0x0cf7] [ 9.940421] pci_bus 0000:05: resource 5 [io 0x0d00-0xffff] [ 9.940423] pci_bus 0000:05: resource 6 [mem 0x000a0000-0x000bffff] [ 9.940426] pci_bus 0000:05: resource 7 [mem 0xd0000000-0xfdffffff] [ 9.940428] pci_bus 0000:05: resource 8 [mem 0xfed40000-0xfed44fff] [ 9.940430] pci_bus 0000:fe: resource 0 [io 0x0000-0xffff] [ 9.940433] pci_bus 0000:fe: resource 1 [mem 0x00000000-0xffffffffff] [ 9.940436] pci_bus 0000:ff: resource 0 [io 0x0000-0xffff] [ 9.940438] pci_bus 0000:ff: resource 1 [mem 0x00000000-0xffffffffff] [ 9.940731] NET: Registered protocol family 2 [ 9.941979] IP route cache hash table entries: 524288 (order: 10, 4194304 bytes) [ 9.945109] TCP established hash table entries: 524288 (order: 11, 8388608 bytes) [ 9.947245] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) [ 9.947498] TCP: Hash tables configured (established 524288 bind 65536) [ 9.947501] TCP reno registered [ 9.947762] UDP hash table entries: 32768 (order: 8, 1048576 bytes) [ 9.948303] UDP-Lite hash table entries: 32768 (order: 8, 1048576 bytes) [ 9.948922] NET: Registered protocol family 1 [ 9.948973] xen: registering gsi 17 triggering 0 polarity 1 [ 9.948999] xen: --> pirq=17 -> irq=17 (gsi=17) [ 9.949034] pci 0000:00:1a.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 9.949060] pci 0000:00:1a.0: PCI INT A disabled [ 9.949069] xen: registering gsi 18 triggering 0 polarity 1 [ 9.949077] xen: --> pirq=18 -> irq=18 (gsi=18) [ 9.949121] pci 0000:00:1a.1: PCI INT B -> GSI 18 (level, low) -> IRQ 18 [ 9.949145] pci 0000:00:1a.1: PCI INT B disabled [ 9.949155] xen: registering gsi 19 triggering 0 polarity 1 [ 9.949164] xen: --> pirq=19 -> irq=19 (gsi=19) [ 9.949193] pci 0000:00:1a.7: PCI INT C -> GSI 19 (level, low) -> IRQ 19 [ 9.965133] pci 0000:00:1a.7: PCI INT C disabled [ 9.965152] xen: registering gsi 21 triggering 0 polarity 1 [ 9.965174] xen: --> pirq=21 -> irq=21 (gsi=21) [ 9.965203] pci 0000:00:1d.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 [ 9.965228] pci 0000:00:1d.0: PCI INT A disabled [ 9.965237] xen: registering gsi 20 triggering 0 polarity 1 [ 9.965245] xen: --> pirq=20 -> irq=20 (gsi=20) [ 9.965273] pci 0000:00:1d.1: PCI INT B -> GSI 20 (level, low) -> IRQ 20 [ 9.965298] pci 0000:00:1d.1: PCI INT B disabled [ 9.965306] xen: registering gsi 21 triggering 0 polarity 1 [ 9.965310] xen_map_pirq_gsi: returning irq 21 for gsi 21 [ 9.965312] xen: --> pirq=21 -> irq=21 (gsi=21) [ 9.965313] Already setup the GSI :21 [ 9.965316] pci 0000:00:1d.2: PCI INT C -> GSI 21 (level, low) -> IRQ 21 [ 9.965340] pci 0000:00:1d.2: PCI INT C disabled [ 9.965350] xen: registering gsi 21 triggering 0 polarity 1 [ 9.965353] xen_map_pirq_gsi: returning irq 21 for gsi 21 [ 9.965355] xen: --> pirq=21 -> irq=21 (gsi=21) [ 9.965357] Already setup the GSI :21 [ 9.965360] pci 0000:00:1d.7: PCI INT A -> GSI 21 (level, low) -> IRQ 21 [ 9.965428] pci 0000:00:1d.7: PCI INT A disabled [ 9.965460] pci 0000:05:03.0: Boot video device [ 9.965589] PCI: CLS 64 bytes, default 64 [ 9.965654] Unpacking initramfs... [ 9.973773] Freeing initrd memory: 7024k freed [ 9.977353] audit: initializing netlink socket (disabled) [ 9.977372] type=2000 audit(1332837366.954:1): initialized [ 10.085691] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 10.086520] VFS: Disk quotas dquot_6.5.2 [ 10.086605] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 10.086754] msgmni has been set to 32768 [ 10.087049] alg: No test for stdrng (krng) [ 10.087130] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [ 10.087134] io scheduler noop registered [ 10.087137] io scheduler deadline registered [ 10.087230] io scheduler cfq registered (default) [ 10.087524] pcieport 0000:00:01.0: setting latency timer to 64 [ 10.087747] pcieport 0000:00:07.0: setting latency timer to 64 [ 10.087931] pcieport 0000:00:09.0: setting latency timer to 64 [ 10.088112] pcieport 0000:00:1c.0: setting latency timer to 64 [ 10.088384] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt [ 10.088391] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded [ 10.088434] pcieport 0000:00:07.0: Signaling PME through PCIe PME interrupt [ 10.088437] pci 0000:03:00.0: Signaling PME through PCIe PME interrupt [ 10.088440] pci 0000:03:00.1: Signaling PME through PCIe PME interrupt [ 10.088446] pcie_pme 0000:00:07.0:pcie01: service driver pcie_pme loaded [ 10.088488] pcieport 0000:00:09.0: Signaling PME through PCIe PME interrupt [ 10.088495] pcie_pme 0000:00:09.0:pcie01: service driver pcie_pme loaded [ 10.088536] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt [ 10.088539] pci 0000:02:00.0: Signaling PME through PCIe PME interrupt [ 10.088546] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded [ 10.088889] ERST: Error Record Serialization Table (ERST) support is initialized. [ 10.089314] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC. [ 10.089794] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 10.281389] serial 00:05: [io 0x03f8-0x03ff] [ 10.281682] serial 00:05: [irq 4] [ 10.282732] serial 00:05: activated [ 10.303488] 00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 10.345589] hpet_acpi_add: no address or irqs in _CRS [ 10.345610] Linux agpgart interface v0.103 [ 10.346005] i8042: PNP: No PS/2 controller found. Probing ports directly. [ 10.346899] i8042: No controller found [ 10.347135] mousedev: PS/2 mouse device common for all mice [ 10.347209] rtc_cmos 00:04: RTC can wake from S4 [ 10.347419] rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0 [ 10.347505] rtc0: alarms up to one day, y3k, 242 bytes nvram [ 10.347888] TCP cubic registered [ 10.348243] NET: Registered protocol family 10 [ 10.349231] Mobile IPv6 [ 10.349236] NET: Registered protocol family 17 [ 10.349244] Registering the dns_resolver key type [ 10.349528] PM: Hibernation image not present or could not be loaded. [ 10.349544] registered taskstats version 1 [ 10.350564] rtc_cmos 00:04: setting system clock to 2012-03-27 08:36:06 UTC (1332837366) [ 10.350629] Initializing network drop monitor service [ 10.351155] Freeing unused kernel memory: 568k freed [ 10.351327] Write protecting the kernel read-only data: 6144k [ 10.355543] Freeing unused kernel memory: 708k freed [ 10.356179] Freeing unused kernel memory: 684k freed [ 10.399054] udevd[137]: starting version 175 [ 10.459886] SCSI subsystem initialized [ 10.463090] megasas: 00.00.06.12-rc1 Wed. Oct. 5 17:00:00 PDT 2011 [ 10.463140] megasas: 0x1000:0x0079:0x1028:0x1f18: bus 2:slot 0:func 0 [ 10.463176] xen: registering gsi 16 triggering 0 polarity 1 [ 10.463192] xen_map_pirq_gsi: returning irq 16 for gsi 16 [ 10.463200] xen: --> pirq=16 -> irq=16 (gsi=16) [ 10.463208] Already setup the GSI :16 [ 10.463217] megaraid_sas 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 10.463237] megaraid_sas 0000:02:00.0: setting latency timer to 64 [ 10.463521] megasas: FW now in Ready state [ 10.493120] megasas_init_mfi: fw_support_ieee=67108864 [ 10.493124] megasas: INIT adapter done [ 10.565189] scsi0 : LSI SAS based MegaRAID driver [ 10.566278] scsi 0:0:0:0: Direct-Access SEAGATE ST9600205SS CS05 PQ: 0 ANSI: 5 [ 10.566872] scsi 0:0:1:0: Direct-Access SEAGATE ST9600205SS CS05 PQ: 0 ANSI: 5 [ 10.621790] scsi 0:0:32:0: Enclosure DP BACKPLANE 1.07 PQ: 0 ANSI: 5 [ 10.645346] scsi 0:2:0:0: Direct-Access DELL PERC H700 2.10 PQ: 0 ANSI: 5 [ 10.673255] sd 0:2:0:0: [sda] 1170997248 512-byte logical blocks: (599 GB/558 GiB) [ 10.673377] sd 0:2:0:0: [sda] Write Protect is off [ 10.673382] sd 0:2:0:0: [sda] Mode Sense: 1f 00 00 08 [ 10.673460] sd 0:2:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 10.674583] sda: sda1 sda2 sda3 [ 10.675266] sd 0:2:0:0: [sda] Attached SCSI disk [ 11.001691] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 11.002597] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 11.021365] device-mapper: uevent: version 1.0.3 [ 11.021562] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-devel@redhat.com [ 11.237755] PM: Starting manual resume from disk [ 11.237761] PM: Hibernation image partition 8:2 present [ 11.237764] PM: Looking for hibernation image. [ 11.237953] PM: Image not found (code -22) [ 11.237956] PM: Hibernation image not present or could not be loaded. [ 11.254893] EXT4-fs (sda1): INFO: recovery required on readonly filesystem [ 11.254898] EXT4-fs (sda1): write access will be enabled during recovery [ 11.280435] EXT4-fs (sda1): recovery complete [ 11.280594] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 12.225576] udevd[386]: starting version 175 [ 12.502908] ACPI Error: No handler for Region [IPMI] (ffff880b9a0c6420) [IPMI] (20110623/evregion-373) [ 12.502923] ACPI Error: Region IPMI (ID=7) has no handler (20110623/exfldio-292) [ 12.502938] ACPI Error: Method parse/execution failed [\_SB_.PMI0._GHL] (Node ffff880b9a0c54c0), AE_NOT_EXIST (20110623/psparse-536) [ 12.502964] ACPI Error: Method parse/execution failed [\_SB_.PMI0._PMC] (Node ffff880b9a0c5560), AE_NOT_EXIST (20110623/psparse-536) [ 12.502995] ACPI Exception: AE_NOT_EXIST, Evaluating _PMC (20110623/power_meter-773) [ 12.569083] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0 [ 12.569101] ACPI: Power Button [PWRF] [ 12.593188] libata version 3.00 loaded. [ 12.599014] ata_piix 0000:00:1f.5: version 2.13 [ 12.599040] xen: registering gsi 17 triggering 0 polarity 1 [ 12.599054] xen_map_pirq_gsi: returning irq 17 for gsi 17 [ 12.599058] xen: --> pirq=17 -> irq=17 (gsi=17) [ 12.599062] Already setup the GSI :17 [ 12.599067] ata_piix 0000:00:1f.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17 [ 12.599078] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ] [ 12.605513] usbcore: registered new interface driver usbfs [ 12.605563] usbcore: registered new interface driver hub [ 12.605654] usbcore: registered new device driver usb [ 12.629687] EDAC MC: Ver: 2.1.0 [ 12.631709] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 12.636599] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2) [ 12.639344] iTCO_vendor_support: vendor-support=0 [ 12.642455] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07 [ 12.642595] iTCO_wdt: Found a ICH9 TCO device (Version=2, TCOBASE=0x0860) [ 12.642715] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 12.646309] input: PC Speaker as /devices/platform/pcspkr/input/input1 [ 12.696167] QLogic 1/10 GbE Converged/Intelligent Ethernet Driver v5.0.25 [ 12.696278] xen: registering gsi 38 triggering 0 polarity 1 [ 12.696304] xen: --> pirq=38 -> irq=38 (gsi=38) [ 12.696340] qlcnic 0000:03:00.0: PCI INT A -> GSI 38 (level, low) -> IRQ 38 [ 12.696355] qlcnic 0000:03:00.0: setting latency timer to 64 [ 12.697214] qlcnic 0000:03:00.0: 2MB memory map [ 12.706141] Error: Driver 'pcspkr' is already registered, aborting... [ 12.724504] ses 0:0:32:0: Attached Enclosure device [ 12.753170] ata_piix 0000:00:1f.5: setting latency timer to 64 [ 12.753758] scsi1 : ata_piix [ 12.753916] scsi2 : ata_piix [ 12.754013] ata1: SATA max UDMA/133 cmd 0xece0 ctl 0xecf8 bmdma 0xecb0 irq 17 [ 12.754021] ata2: SATA max UDMA/133 cmd 0xece8 ctl 0xecfc bmdma 0xecb8 irq 17 [ 12.754076] xen: registering gsi 19 triggering 0 polarity 1 [ 12.754089] xen_map_pirq_gsi: returning irq 19 for gsi 19 [ 12.754093] xen: --> pirq=19 -> irq=19 (gsi=19) [ 12.754097] Already setup the GSI :19 [ 12.754102] ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 19 (level, low) -> IRQ 19 [ 12.754203] ehci_hcd 0000:00:1a.7: setting latency timer to 64 [ 12.754211] ehci_hcd 0000:00:1a.7: EHCI Host Controller [ 12.754260] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1 [ 12.754342] ehci_hcd 0000:00:1a.7: debug port 1 [ 12.758246] ehci_hcd 0000:00:1a.7: cache line size of 64 is not supported [ 12.758338] ehci_hcd 0000:00:1a.7: irq 19, io mem 0xdffff800 [ 12.773129] ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00 [ 12.773166] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 12.773170] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 12.773174] usb usb1: Product: EHCI Host Controller [ 12.773178] usb usb1: Manufacturer: Linux 3.2.0-2-amd64 ehci_hcd [ 12.773181] usb usb1: SerialNumber: 0000:00:1a.7 [ 12.773367] hub 1-0:1.0: USB hub found [ 12.773374] hub 1-0:1.0: 4 ports detected [ 12.773531] xen: registering gsi 21 triggering 0 polarity 1 [ 12.773539] xen_map_pirq_gsi: returning irq 21 for gsi 21 [ 12.773542] xen: --> pirq=21 -> irq=21 (gsi=21) [ 12.773545] Already setup the GSI :21 [ 12.773550] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 21 (level, low) -> IRQ 21 [ 12.773637] ehci_hcd 0000:00:1d.7: setting latency timer to 64 [ 12.773644] ehci_hcd 0000:00:1d.7: EHCI Host Controller [ 12.773658] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2 [ 12.773735] ehci_hcd 0000:00:1d.7: debug port 1 [ 12.777625] ehci_hcd 0000:00:1d.7: cache line size of 64 is not supported [ 12.777699] ehci_hcd 0000:00:1d.7: irq 21, io mem 0xdffffc00 [ 12.793120] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00 [ 12.793153] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 12.793158] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 12.793162] usb usb2: Product: EHCI Host Controller [ 12.793165] usb usb2: Manufacturer: Linux 3.2.0-2-amd64 ehci_hcd [ 12.793169] usb usb2: SerialNumber: 0000:00:1d.7 [ 12.793349] hub 2-0:1.0: USB hub found [ 12.793356] hub 2-0:1.0: 6 ports detected [ 12.794027] EDAC MC1: Giving out device to 'i7core_edac.c' 'i7 core #1': DEV 0000:fe:03.0 [ 12.794072] EDAC PCI0: Giving out device to module 'i7core_edac' controller 'EDAC PCI controller': DEV '0000:fe:03.0' (POLLED) [ 12.794706] EDAC MC0: Giving out device to 'i7core_edac.c' 'i7 core #0': DEV 0000:ff:03.0 [ 12.794734] EDAC PCI1: Giving out device to module 'i7core_edac' controller 'EDAC PCI controller': DEV '0000:ff:03.0' (POLLED) [ 12.795151] EDAC i7core: Driver loaded, 2 memory controller(s) found. [ 12.841807] uhci_hcd: USB Universal Host Controller Interface driver [ 12.841908] xen: registering gsi 17 triggering 0 polarity 1 [ 12.841917] xen_map_pirq_gsi: returning irq 17 for gsi 17 [ 12.841920] xen: --> pirq=17 -> irq=17 (gsi=17) [ 12.841923] Already setup the GSI :17 [ 12.841928] uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 12.841945] uhci_hcd 0000:00:1a.0: setting latency timer to 64 [ 12.841952] uhci_hcd 0000:00:1a.0: UHCI Host Controller [ 12.841966] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3 [ 12.842013] uhci_hcd 0000:00:1a.0: irq 17, io base 0x0000e8c0 [ 12.842096] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [ 12.842101] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 12.842105] usb usb3: Product: UHCI Host Controller [ 12.842108] usb usb3: Manufacturer: Linux 3.2.0-2-amd64 uhci_hcd [ 12.842112] usb usb3: SerialNumber: 0000:00:1a.0 [ 12.842318] hub 3-0:1.0: USB hub found [ 12.842330] hub 3-0:1.0: 2 ports detected [ 12.842497] xen: registering gsi 18 triggering 0 polarity 1 [ 12.842505] xen_map_pirq_gsi: returning irq 18 for gsi 18 [ 12.842510] xen: --> pirq=18 -> irq=18 (gsi=18) [ 12.842513] Already setup the GSI :18 [ 12.842518] uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 18 (level, low) -> IRQ 18 [ 12.842534] uhci_hcd 0000:00:1a.1: setting latency timer to 64 [ 12.842540] uhci_hcd 0000:00:1a.1: UHCI Host Controller [ 12.842552] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4 [ 12.842666] uhci_hcd 0000:00:1a.1: irq 18, io base 0x0000e8e0 [ 12.842753] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001 [ 12.842757] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 12.842761] usb usb4: Product: UHCI Host Controller [ 12.842765] usb usb4: Manufacturer: Linux 3.2.0-2-amd64 uhci_hcd [ 12.842768] usb usb4: SerialNumber: 0000:00:1a.1 [ 12.842946] hub 4-0:1.0: USB hub found [ 12.842957] hub 4-0:1.0: 2 ports detected [ 12.843105] xen: registering gsi 21 triggering 0 polarity 1 [ 12.843113] xen_map_pirq_gsi: returning irq 21 for gsi 21 [ 12.843116] xen: --> pirq=21 -> irq=21 (gsi=21) [ 12.843119] Already setup the GSI :21 [ 12.843124] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 [ 12.843138] uhci_hcd 0000:00:1d.0: setting latency timer to 64 [ 12.843145] uhci_hcd 0000:00:1d.0: UHCI Host Controller [ 12.843156] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 5 [ 12.843197] uhci_hcd 0000:00:1d.0: irq 21, io base 0x0000ec00 [ 12.843282] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001 [ 12.843287] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 12.843291] usb usb5: Product: UHCI Host Controller [ 12.843294] usb usb5: Manufacturer: Linux 3.2.0-2-amd64 uhci_hcd [ 12.843298] usb usb5: SerialNumber: 0000:00:1d.0 [ 12.843479] hub 5-0:1.0: USB hub found [ 12.843488] hub 5-0:1.0: 2 ports detected [ 12.843645] xen: registering gsi 20 triggering 0 polarity 1 [ 12.843653] xen_map_pirq_gsi: returning irq 20 for gsi 20 [ 12.843657] xen: --> pirq=20 -> irq=20 (gsi=20) [ 12.843660] Already setup the GSI :20 [ 12.843664] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 20 (level, low) -> IRQ 20 [ 12.843679] uhci_hcd 0000:00:1d.1: setting latency timer to 64 [ 12.843685] uhci_hcd 0000:00:1d.1: UHCI Host Controller [ 12.843698] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 6 [ 12.843804] uhci_hcd 0000:00:1d.1: irq 20, io base 0x0000ec20 [ 12.843895] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001 [ 12.843902] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 12.843906] usb usb6: Product: UHCI Host Controller [ 12.843911] usb usb6: Manufacturer: Linux 3.2.0-2-amd64 uhci_hcd [ 12.843916] usb usb6: SerialNumber: 0000:00:1d.1 [ 12.844107] hub 6-0:1.0: USB hub found [ 12.844116] hub 6-0:1.0: 2 ports detected [ 12.844281] xen: registering gsi 21 triggering 0 polarity 1 [ 12.844289] xen_map_pirq_gsi: returning irq 21 for gsi 21 [ 12.844293] xen: --> pirq=21 -> irq=21 (gsi=21) [ 12.844296] Already setup the GSI :21 [ 12.844300] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 21 (level, low) -> IRQ 21 [ 12.844317] uhci_hcd 0000:00:1d.2: setting latency timer to 64 [ 12.844324] uhci_hcd 0000:00:1d.2: UHCI Host Controller [ 12.844336] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 7 [ 12.844378] uhci_hcd 0000:00:1d.2: irq 21, io base 0x0000ec40 [ 12.844483] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001 [ 12.844487] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 12.844491] usb usb7: Product: UHCI Host Controller [ 12.844495] usb usb7: Manufacturer: Linux 3.2.0-2-amd64 uhci_hcd [ 12.844498] usb usb7: SerialNumber: 0000:00:1d.2 [ 12.844677] hub 7-0:1.0: USB hub found [ 12.844685] hub 7-0:1.0: 2 ports detected [ 13.077174] ata1: SATA link down (SStatus 0 SControl 300) [ 13.077266] ata2: SATA link down (SStatus 0 SControl 300) [ 13.221115] usb 2-3: new high-speed USB device number 3 using ehci_hcd [ 13.345114] qlcnic 0000:03:00.0: phy port: 0 switch_mode: 0, [ 13.345116] max_tx_q: 1 max_rx_q: 8 min_tx_bw: 0x0, [ 13.345117] max_tx_bw: 0x64 max_mtu:0x2580, capabilities: 0x6affae [ 13.361103] qlcnic 0000:03:00.0: failed card response code:0x10 [ 13.361162] qlcnic 0000:03:00.0: Can't get template size 16 [ 13.361167] qlcnic 0000:03:00.0: firmware v4.7.83 [ 13.371640] usb 2-3: New USB device found, idVendor=046b, idProduct=ff90 [ 13.371646] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 13.371650] usb 2-3: Product: Composite Device [ 13.371653] usb 2-3: Manufacturer: American Megatrends Inc. [ 13.371657] usb 2-3: SerialNumber: serial [ 13.393138] qlcnic: 24:b6:fd:64:1e:45: QME8242-k 10GbE Dual Port Mezzanine Card Board Chip rev 0x54 [ 13.393460] usbcore: registered new interface driver uas [ 13.393559] qlcnic 0000:03:00.0: using msi-x interrupts [ 13.394251] qlcnic 0000:03:00.0: eth0: XGbE port initialized [ 13.394290] xen: registering gsi 38 triggering 0 polarity 1 [ 13.394304] xen_map_pirq_gsi: returning irq 38 for gsi 38 [ 13.394308] xen: --> pirq=38 -> irq=38 (gsi=38) [ 13.394311] Already setup the GSI :38 [ 13.394316] qlcnic 0000:03:00.1: PCI INT A -> GSI 38 (level, low) -> IRQ 38 [ 13.394331] qlcnic 0000:03:00.1: setting latency timer to 64 [ 13.395317] qlcnic 0000:03:00.1: 2MB memory map [ 13.404052] Initializing USB Mass Storage driver... [ 13.404264] scsi3 : usb-storage 2-3:1.0 [ 13.404487] scsi4 : usb-storage 2-3:1.1 [ 13.404693] scsi5 : usb-storage 2-3:1.2 [ 13.404799] usbcore: registered new interface driver usb-storage [ 13.404802] USB Mass Storage support registered. [ 13.409136] qlcnic 0000:03:00.1: phy port: 1 switch_mode: 0, [ 13.409138] max_tx_q: 1 max_rx_q: 8 min_tx_bw: 0x0, [ 13.409139] max_tx_bw: 0x64 max_mtu:0x2580, capabilities: 0x6affae [ 13.425118] qlcnic 0000:03:00.1: failed card response code:0x10 [ 13.425174] qlcnic 0000:03:00.1: Can't get template size 16 [ 13.425178] qlcnic 0000:03:00.1: firmware v4.7.83 [ 13.449525] qlcnic 0000:03:00.1: using msi-x interrupts [ 13.450132] qlcnic 0000:03:00.1: eth1: XGbE port initialized [ 13.677120] usb 5-2: new full-speed USB device number 2 using uhci_hcd [ 13.840290] usb 5-2: New USB device found, idVendor=046b, idProduct=ff10 [ 13.840296] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 13.840300] usb 5-2: Product: Virtual Keyboard and Mouse [ 13.840304] usb 5-2: Manufacturer: American Megatrends Inc. [ 13.840307] usb 5-2: SerialNumber: serial [ 13.905626] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.0/input/input2 [ 13.905800] generic-usb 0003:046B:FF10.0001: input,hidraw0: USB HID v1.10 Keyboard [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0000:00:1d.0-2/input0 [ 13.912572] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.1/input/input3 [ 13.912816] generic-usb 0003:046B:FF10.0002: input,hidraw1: USB HID v1.10 Mouse [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0000:00:1d.0-2/input1 [ 13.912843] usbcore: registered new interface driver usbhid [ 13.912846] usbhid: USB HID core driver [ 14.085125] usb 6-2: new low-speed USB device number 2 using uhci_hcd [ 14.262910] usb 6-2: New USB device found, idVendor=0624, idProduct=de11 [ 14.262915] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 14.262919] usb 6-2: Product: Avocent KVM [ 14.262923] usb 6-2: Manufacturer: Avocent [ 14.298214] input: Avocent Avocent KVM as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/input/input4 [ 14.298395] generic-usb 0003:0624:DE11.0003: input,hidraw2: USB HID v1.10 Keyboard [Avocent Avocent KVM] on usb-0000:00:1d.1-2/input0 [ 14.307733] Adding 1952764k swap on /dev/sda2. Priority:-1 extents:1 across:1952764k [ 14.319436] EXT4-fs (sda1): re-mounted. Opts: (null) [ 14.328276] input: Avocent Avocent KVM as /devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.1/input/input5 [ 14.328523] generic-usb 0003:0624:DE11.0004: input,hidraw3: USB HID v1.10 Mouse [Avocent Avocent KVM] on usb-0000:00:1d.1-2/input1 [ 14.445936] scsi 3:0:0:0: Direct-Access iDRAC LCDRIVE 1.00 PQ: 0 ANSI: 0 CCS [ 14.449814] scsi 4:0:0:0: CD-ROM iDRAC Virtual CDROM 1.00 PQ: 0 ANSI: 0 CCS [ 14.450813] scsi 5:0:0:0: Direct-Access iDRAC Virtual Floppy 1.00 PQ: 0 ANSI: 0 CCS [ 14.460804] sd 3:0:0:0: [sdb] Attached SCSI removable disk [ 14.462790] sd 5:0:0:0: [sdc] Attached SCSI removable disk [ 14.557541] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro [ 14.562159] sr0: scsi-1 drive [ 14.562164] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 14.562421] sr 4:0:0:0: Attached scsi CD-ROM sr0 [ 14.642111] Event-channel device installed. [ 14.805454] loop: module loaded [ 15.261328] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: errors=remount-ro [ 16.987146] openvswitch_mod: Open vSwitch switching datapath 1.4.0, built Mar 6 2012 12:16:33 [ 18.325633] ip_tables: (C) 2000-2006 Netfilter Core Team [ 18.434036] device xenbr0 entered promiscuous mode [ 18.445825] device eth1 entered promiscuous mode [ 18.446092] device eth0 entered promiscuous mode [ 18.457027] device vlan100 entered promiscuous mode [ 18.484409] device vlan900 entered promiscuous mode [ 18.508746] device vlan500 entered promiscuous mode [ 18.629208] qlcnic 0000:03:00.0: restoring config space at offset 0x1 (was 0x100400, writing 0x100406) [ 19.374883] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 19.481194] qlcnic 0000:03:00.1: restoring config space at offset 0x1 (was 0x100400, writing 0x100406) [ 20.382891] ADDRCONF(NETDEV_UP): eth1: link is not ready [ 20.688307] RPC: Registered named UNIX socket transport module. [ 20.688312] RPC: Registered udp transport module. [ 20.688315] RPC: Registered tcp transport module. [ 20.688318] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 20.715885] FS-Cache: Loaded [ 20.741906] FS-Cache: Netfs 'nfs' registered for caching [ 20.755536] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). -- View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5597400.html Sent from the Xen - Dev mailing list archive at Nabble.com. ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-27 9:43 ` Kristoffer Harthing Egefelt @ 2012-03-27 10:02 ` Wei Liu 2012-03-27 12:41 ` Pasi Kärkkäinen 2012-07-31 21:50 ` Anirban Chakraborty 0 siblings, 2 replies; 35+ messages in thread From: Wei Liu @ 2012-03-27 10:02 UTC (permalink / raw) To: Kristoffer Harthing Egefelt; +Cc: xen-devel@lists.xensource.com, wei.liu2 On Tue, 2012-03-27 at 10:43 +0100, Kristoffer Harthing Egefelt wrote: > Please find dmesg below - do you see any hints? > The onboard 1gig network cards are in fabric A, the 10gig's are in fabric B. > I have disabled the onboard NICs so the 10gigs is eth0 and eth1. > I have tried enabling the onboard NICs, making the 10gig's eth2 and eth3 > without luck. > > Thanks > > oot@node0301:/var/log# cat dmesg.0 <snip> > [ 12.646309] input: PC Speaker as /devices/platform/pcspkr/input/input1 > [ 12.696167] QLogic 1/10 GbE Converged/Intelligent Ethernet Driver v5.0.25 > [ 12.696278] xen: registering gsi 38 triggering 0 polarity 1 > [ 12.696304] xen: --> pirq=38 -> irq=38 (gsi=38) > [ 12.696340] qlcnic 0000:03:00.0: PCI INT A -> GSI 38 (level, low) -> IRQ > 38 This one. > [ 12.696355] qlcnic 0000:03:00.0: setting latency timer to 64 > [ 12.697214] qlcnic 0000:03:00.0: 2MB memory map <snip> > [ 13.077174] ata1: SATA link down (SStatus 0 SControl 300) > [ 13.077266] ata2: SATA link down (SStatus 0 SControl 300) > [ 13.221115] usb 2-3: new high-speed USB device number 3 using ehci_hcd > [ 13.345114] qlcnic 0000:03:00.0: phy port: 0 switch_mode: 0, > [ 13.345116] max_tx_q: 1 max_rx_q: 8 min_tx_bw: 0x0, > [ 13.345117] max_tx_bw: 0x64 max_mtu:0x2580, capabilities: 0x6affae > [ 13.361103] qlcnic 0000:03:00.0: failed card response code:0x10 > [ 13.361162] qlcnic 0000:03:00.0: Can't get template size 16 > [ 13.361167] qlcnic 0000:03:00.0: firmware v4.7.83 Failed. :-( > [ 13.371640] usb 2-3: New USB device found, idVendor=046b, idProduct=ff90 > [ 13.371646] usb 2-3: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [ 13.371650] usb 2-3: Product: Composite Device > [ 13.371653] usb 2-3: Manufacturer: American Megatrends Inc. > [ 13.371657] usb 2-3: SerialNumber: serial > [ 13.393138] qlcnic: 24:b6:fd:64:1e:45: QME8242-k 10GbE Dual Port > Mezzanine Card Board Chip rev 0x54 > [ 13.393460] usbcore: registered new interface driver uas > [ 13.393559] qlcnic 0000:03:00.0: using msi-x interrupts > [ 13.394251] qlcnic 0000:03:00.0: eth0: XGbE port initialized And this one. > [ 13.394290] xen: registering gsi 38 triggering 0 polarity 1 > [ 13.394304] xen_map_pirq_gsi: returning irq 38 for gsi 38 > [ 13.394308] xen: --> pirq=38 -> irq=38 (gsi=38) > [ 13.394311] Already setup the GSI :38 > [ 13.394316] qlcnic 0000:03:00.1: PCI INT A -> GSI 38 (level, low) -> IRQ > 38 > [ 13.394331] qlcnic 0000:03:00.1: setting latency timer to 64 > [ 13.395317] qlcnic 0000:03:00.1: 2MB memory map > [ 13.404052] Initializing USB Mass Storage driver... > [ 13.404264] scsi3 : usb-storage 2-3:1.0 > [ 13.404487] scsi4 : usb-storage 2-3:1.1 > [ 13.404693] scsi5 : usb-storage 2-3:1.2 > [ 13.404799] usbcore: registered new interface driver usb-storage > [ 13.404802] USB Mass Storage support registered. > [ 13.409136] qlcnic 0000:03:00.1: phy port: 1 switch_mode: 0, > [ 13.409138] max_tx_q: 1 max_rx_q: 8 min_tx_bw: 0x0, > [ 13.409139] max_tx_bw: 0x64 max_mtu:0x2580, capabilities: 0x6affae > [ 13.425118] qlcnic 0000:03:00.1: failed card response code:0x10 > [ 13.425174] qlcnic 0000:03:00.1: Can't get template size 16 > [ 13.425178] qlcnic 0000:03:00.1: firmware v4.7.83 > [ 13.449525] qlcnic 0000:03:00.1: using msi-x interrupts > [ 13.450132] qlcnic 0000:03:00.1: eth1: XGbE port initialized And this one. > [ 13.677120] usb 5-2: new full-speed USB device number 2 using uhci_hcd > [ 13.840290] usb 5-2: New USB device found, idVendor=046b, idProduct=ff10 > [ 13.840296] usb 5-2: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 <snip> > [ 18.325633] ip_tables: (C) 2000-2006 Netfilter Core Team > [ 18.434036] device xenbr0 entered promiscuous mode > [ 18.445825] device eth1 entered promiscuous mode > [ 18.446092] device eth0 entered promiscuous mode I have no idea about the "failed card response", but there are eth0 and eth1 presented. :-) And it looks like that they are both bridged to xenbr0 by userspace tools? Wei. ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-27 10:02 ` Wei Liu @ 2012-03-27 12:41 ` Pasi Kärkkäinen 2012-03-27 16:23 ` Kristoffer Harthing Egefelt 2012-07-31 21:50 ` Anirban Chakraborty 1 sibling, 1 reply; 35+ messages in thread From: Pasi Kärkkäinen @ 2012-03-27 12:41 UTC (permalink / raw) To: Wei Liu; +Cc: Kristoffer Harthing Egefelt, xen-devel@lists.xensource.com On Tue, Mar 27, 2012 at 11:02:53AM +0100, Wei Liu wrote: > On Tue, 2012-03-27 at 10:43 +0100, Kristoffer Harthing Egefelt wrote: > > Please find dmesg below - do you see any hints? > > The onboard 1gig network cards are in fabric A, the 10gig's are in fabric B. > > I have disabled the onboard NICs so the 10gigs is eth0 and eth1. > > I have tried enabling the onboard NICs, making the 10gig's eth2 and eth3 > > without luck. > > > > Thanks > > > > oot@node0301:/var/log# cat dmesg.0 > > <snip> > > > [ 12.646309] input: PC Speaker as /devices/platform/pcspkr/input/input1 > > [ 12.696167] QLogic 1/10 GbE Converged/Intelligent Ethernet Driver v5.0.25 > > [ 12.696278] xen: registering gsi 38 triggering 0 polarity 1 > > [ 12.696304] xen: --> pirq=38 -> irq=38 (gsi=38) > > [ 12.696340] qlcnic 0000:03:00.0: PCI INT A -> GSI 38 (level, low) -> IRQ > > 38 > > This one. > > > [ 12.696355] qlcnic 0000:03:00.0: setting latency timer to 64 > > [ 12.697214] qlcnic 0000:03:00.0: 2MB memory map > > <snip> > > > [ 13.077174] ata1: SATA link down (SStatus 0 SControl 300) > > [ 13.077266] ata2: SATA link down (SStatus 0 SControl 300) > > [ 13.221115] usb 2-3: new high-speed USB device number 3 using ehci_hcd > > [ 13.345114] qlcnic 0000:03:00.0: phy port: 0 switch_mode: 0, > > [ 13.345116] max_tx_q: 1 max_rx_q: 8 min_tx_bw: 0x0, > > [ 13.345117] max_tx_bw: 0x64 max_mtu:0x2580, capabilities: 0x6affae > > [ 13.361103] qlcnic 0000:03:00.0: failed card response code:0x10 > > [ 13.361162] qlcnic 0000:03:00.0: Can't get template size 16 > > [ 13.361167] qlcnic 0000:03:00.0: firmware v4.7.83 > > Failed. :-( > > > [ 13.371640] usb 2-3: New USB device found, idVendor=046b, idProduct=ff90 > > [ 13.371646] usb 2-3: New USB device strings: Mfr=1, Product=2, > > SerialNumber=3 > > [ 13.371650] usb 2-3: Product: Composite Device > > [ 13.371653] usb 2-3: Manufacturer: American Megatrends Inc. > > [ 13.371657] usb 2-3: SerialNumber: serial > > [ 13.393138] qlcnic: 24:b6:fd:64:1e:45: QME8242-k 10GbE Dual Port > > Mezzanine Card Board Chip rev 0x54 > > [ 13.393460] usbcore: registered new interface driver uas > > [ 13.393559] qlcnic 0000:03:00.0: using msi-x interrupts > > [ 13.394251] qlcnic 0000:03:00.0: eth0: XGbE port initialized > > And this one. > > > [ 13.394290] xen: registering gsi 38 triggering 0 polarity 1 > > [ 13.394304] xen_map_pirq_gsi: returning irq 38 for gsi 38 > > [ 13.394308] xen: --> pirq=38 -> irq=38 (gsi=38) > > [ 13.394311] Already setup the GSI :38 > > [ 13.394316] qlcnic 0000:03:00.1: PCI INT A -> GSI 38 (level, low) -> IRQ > > 38 > > [ 13.394331] qlcnic 0000:03:00.1: setting latency timer to 64 > > [ 13.395317] qlcnic 0000:03:00.1: 2MB memory map > > [ 13.404052] Initializing USB Mass Storage driver... > > [ 13.404264] scsi3 : usb-storage 2-3:1.0 > > [ 13.404487] scsi4 : usb-storage 2-3:1.1 > > [ 13.404693] scsi5 : usb-storage 2-3:1.2 > > [ 13.404799] usbcore: registered new interface driver usb-storage > > [ 13.404802] USB Mass Storage support registered. > > [ 13.409136] qlcnic 0000:03:00.1: phy port: 1 switch_mode: 0, > > [ 13.409138] max_tx_q: 1 max_rx_q: 8 min_tx_bw: 0x0, > > [ 13.409139] max_tx_bw: 0x64 max_mtu:0x2580, capabilities: 0x6affae > > [ 13.425118] qlcnic 0000:03:00.1: failed card response code:0x10 > > [ 13.425174] qlcnic 0000:03:00.1: Can't get template size 16 > > [ 13.425178] qlcnic 0000:03:00.1: firmware v4.7.83 > > [ 13.449525] qlcnic 0000:03:00.1: using msi-x interrupts > > [ 13.450132] qlcnic 0000:03:00.1: eth1: XGbE port initialized > > And this one. > > > [ 13.677120] usb 5-2: new full-speed USB device number 2 using uhci_hcd > > [ 13.840290] usb 5-2: New USB device found, idVendor=046b, idProduct=ff10 > > [ 13.840296] usb 5-2: New USB device strings: Mfr=1, Product=2, > > SerialNumber=3 > > <snip> > > > [ 18.325633] ip_tables: (C) 2000-2006 Netfilter Core Team > > [ 18.434036] device xenbr0 entered promiscuous mode > > [ 18.445825] device eth1 entered promiscuous mode > > [ 18.446092] device eth0 entered promiscuous mode > > I have no idea about the "failed card response", but there are eth0 and > eth1 presented. :-) > Some distros do rename tricks for eth-interfaces, so it's good to verify the NICs with: ethtool -i ethX > And it looks like that they are both bridged to xenbr0 by userspace > tools? > Run "brctl show" to verify. -- Pasi ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-27 12:41 ` Pasi Kärkkäinen @ 2012-03-27 16:23 ` Kristoffer Harthing Egefelt 2012-03-27 16:37 ` Wei Liu 2012-03-27 19:26 ` Pasi Kärkkäinen 0 siblings, 2 replies; 35+ messages in thread From: Kristoffer Harthing Egefelt @ 2012-03-27 16:23 UTC (permalink / raw) To: xen-devel I get these errors booting kernel 3.x without xen also - but then the NICs work. > > [ 13.361103] qlcnic 0000:03:00.0: failed card response code:0x10 > > [ 13.361162] qlcnic 0000:03:00.0: Can't get template size 16 > > [ 13.361167] qlcnic 0000:03:00.0: firmware v4.7.83 The two interfaces are bridged, but the link is missing in any configuration with xen. ethtool identifies the NICs correctly, trying ethtool -i eth{2,3,4,5} we get "No such device" I have searched the web for the failed card response error without luck. Wei - your 10gig NIC wouldn't be a qlogic by any chance? Any ideas? Even long shots? Thanks -- View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5598276.html Sent from the Xen - Dev mailing list archive at Nabble.com. ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-27 16:23 ` Kristoffer Harthing Egefelt @ 2012-03-27 16:37 ` Wei Liu 2012-03-27 18:45 ` Kristoffer Harthing Egefelt 2012-03-27 19:26 ` Pasi Kärkkäinen 1 sibling, 1 reply; 35+ messages in thread From: Wei Liu @ 2012-03-27 16:37 UTC (permalink / raw) To: Kristoffer Harthing Egefelt; +Cc: xen-devel@lists.xensource.com, wei.liu2 On Tue, 2012-03-27 at 17:23 +0100, Kristoffer Harthing Egefelt wrote: > I get these errors booting kernel 3.x without xen also - but then the NICs > work. > > > > [ 13.361103] qlcnic 0000:03:00.0: failed card response code:0x10 > > > [ 13.361162] qlcnic 0000:03:00.0: Can't get template size 16 > > > [ 13.361167] qlcnic 0000:03:00.0: firmware v4.7.83 > > The two interfaces are bridged, but the link is missing in any configuration > with xen. > In this case, it is the bridge ought to get a IP address and NICs should not have IP address. Did you mis-configure them? > ethtool identifies the NICs correctly, trying ethtool -i eth{2,3,4,5} we get > "No such device" > > I have searched the web for the failed card response error without luck. > > Wei - your 10gig NIC wouldn't be a qlogic by any chance? > Let me check -- no, it's Intel 82599EB. And the failure doesn't necessary means the NIC fails to initialize. It might fall back to other configuration. Better check for the same message on baremetal to rule out. Wei. > Any ideas? Even long shots? > > Thanks > > > -- > View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5598276.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-27 16:37 ` Wei Liu @ 2012-03-27 18:45 ` Kristoffer Harthing Egefelt 2012-03-27 18:58 ` Konrad Rzeszutek Wilk 0 siblings, 1 reply; 35+ messages in thread From: Kristoffer Harthing Egefelt @ 2012-03-27 18:45 UTC (permalink / raw) To: xen-devel It works with plain linux 3.x. I expect the NIC should have link in any configuration, bridge or openvswitch etc... This is really strange - it seems to me that the driver is not compatible with linux 3 running xen - but could this really be the case? I have opened a case with qlogic and waiting for a reply. If you have any other ideas I'm very happy to test. Kristoffer -- View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5598612.html Sent from the Xen - Dev mailing list archive at Nabble.com. ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-27 18:45 ` Kristoffer Harthing Egefelt @ 2012-03-27 18:58 ` Konrad Rzeszutek Wilk 2012-03-27 18:59 ` Konrad Rzeszutek Wilk 0 siblings, 1 reply; 35+ messages in thread From: Konrad Rzeszutek Wilk @ 2012-03-27 18:58 UTC (permalink / raw) To: Kristoffer Harthing Egefelt; +Cc: xen-devel On Tue, Mar 27, 2012 at 11:45:55AM -0700, Kristoffer Harthing Egefelt wrote: > It works with plain linux 3.x. > I expect the NIC should have link in any configuration, bridge or > openvswitch etc... > > This is really strange - it seems to me that the driver is not compatible > with linux 3 running xen - but could this really be the case? > I have opened a case with qlogic and waiting for a reply. > If you have any other ideas I'm very happy to test. Just on a off-chance .. is this with a 32-bit kernel or 64-bit? What happens if you boot the kernel with 'mem=3G dom0_mem=max:1G' (on your Xen hypervisor line)? Does the card work? > > Kristoffer > > -- > View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5598612.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-27 18:58 ` Konrad Rzeszutek Wilk @ 2012-03-27 18:59 ` Konrad Rzeszutek Wilk 0 siblings, 0 replies; 35+ messages in thread From: Konrad Rzeszutek Wilk @ 2012-03-27 18:59 UTC (permalink / raw) To: Kristoffer Harthing Egefelt; +Cc: xen-devel On Tue, Mar 27, 2012 at 02:58:32PM -0400, Konrad Rzeszutek Wilk wrote: > On Tue, Mar 27, 2012 at 11:45:55AM -0700, Kristoffer Harthing Egefelt wrote: > > It works with plain linux 3.x. > > I expect the NIC should have link in any configuration, bridge or > > openvswitch etc... > > > > This is really strange - it seems to me that the driver is not compatible > > with linux 3 running xen - but could this really be the case? > > I have opened a case with qlogic and waiting for a reply. > > If you have any other ideas I'm very happy to test. > > Just on a off-chance .. is this with a 32-bit kernel or 64-bit? > What happens if you boot the kernel with 'mem=3G dom0_mem=max:1G' (on your Xen hypervisor line)? > > Does the card work? Or on native, bootup it with these parameters on the Linux command line: "iommu=soft swiotlb=force". Does it work then? ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-27 16:23 ` Kristoffer Harthing Egefelt 2012-03-27 16:37 ` Wei Liu @ 2012-03-27 19:26 ` Pasi Kärkkäinen 2012-03-27 20:29 ` Kristoffer Harthing Egefelt 1 sibling, 1 reply; 35+ messages in thread From: Pasi Kärkkäinen @ 2012-03-27 19:26 UTC (permalink / raw) To: Kristoffer Harthing Egefelt; +Cc: xen-devel On Tue, Mar 27, 2012 at 09:23:35AM -0700, Kristoffer Harthing Egefelt wrote: > I get these errors booting kernel 3.x without xen also - but then the NICs > work. > > > > [ 13.361103] qlcnic 0000:03:00.0: failed card response code:0x10 > > > [ 13.361162] qlcnic 0000:03:00.0: Can't get template size 16 > > > [ 13.361167] qlcnic 0000:03:00.0: firmware v4.7.83 > > The two interfaces are bridged, but the link is missing in any configuration > with xen. > > ethtool identifies the NICs correctly, trying ethtool -i eth{2,3,4,5} we get > "No such device" > That's weird - "ethtool -i ethX" should show the nic driver name, firmware, PCI info etc. -- Pasi ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-27 19:26 ` Pasi Kärkkäinen @ 2012-03-27 20:29 ` Kristoffer Harthing Egefelt 2012-03-27 21:31 ` Kristoffer Harthing Egefelt 2012-03-28 9:15 ` Ian Campbell 0 siblings, 2 replies; 35+ messages in thread From: Kristoffer Harthing Egefelt @ 2012-03-27 20:29 UTC (permalink / raw) To: xen-devel >mem=3G dom0_mem=max:1G' (on your Xen hypervisor line) Same situation - No link on NICs. >"iommu=soft swiotlb=force". on native linux (no xen) Same situation. Without xen, errors are still present in dmesg (when mod probing the driver) but the NICs have link and work. > That's weird - "ethtool -i ethX" should show the nic driver name, > firmware, PCI info etc. I think my description was unclear - ethtool -i with eth0 and eth1 works as expected - I get driver and firmware version etc. Ethtool -i with eth2, eth3, eth4, eth5 returns "device not found" (This were to check if linux were renaming devices, this seems not to be the case?) Any other things to try? Thanks -- View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5598838.html Sent from the Xen - Dev mailing list archive at Nabble.com. ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-27 20:29 ` Kristoffer Harthing Egefelt @ 2012-03-27 21:31 ` Kristoffer Harthing Egefelt 2012-03-27 21:51 ` Konrad Rzeszutek Wilk 2012-03-28 8:55 ` Fajar A. Nugraha 2012-03-28 9:15 ` Ian Campbell 1 sibling, 2 replies; 35+ messages in thread From: Kristoffer Harthing Egefelt @ 2012-03-27 21:31 UTC (permalink / raw) To: xen-devel Diffing the dmesg's from native linux 3.x and linux 3.x with xen shows 4 more lines on the native: Native: qlcnic 0000:03:00.0: phy port: 0 switch_mode: 0, max_tx_q: 1 max_rx_q: 8 min_tx_bw: 0x0, max_tx_bw: 0x64 max_mtu:0x2580, capabilities: 0x6affae qlcnic 0000:03:00.0: failed card response code:0x10 qlcnic 0000:03:00.0: Can't get template size 16 qlcnic 0000:03:00.0: firmware v4.7.83 qlcnic: 24:b6:fd:64:1e:45: QME8242-k 10GbE Dual Port Mezzanine Card Board Chip rev 0x54 * qlcnic 0000:03:00.0: irq 78 for MSI/MSI-X qlcnic 0000:03:00.0: irq 79 for MSI/MSI-X qlcnic 0000:03:00.0: irq 80 for MSI/MSI-X qlcnic 0000:03:00.0: irq 81 for MSI/MSI-X* qlcnic 0000:03:00.0: using msi-x interrupts qlcnic 0000:03:00.0: eth0: XGbE port initialized The xen version of dmesg does not have these irq's: XEN: qlcnic 0000:03:00.0: phy port: 0 switch_mode: 0, max_tx_q: 1 max_rx_q: 8 min_tx_bw: 0x0, max_tx_bw: 0x64 max_mtu:0x2580, capabilities: 0x6affae qlcnic 0000:03:00.0: failed card response code:0x10 qlcnic 0000:03:00.0: Can't get template size 16 qlcnic 0000:03:00.0: firmware v4.7.83 qlcnic: 24:b6:fd:64:1e:45: QME8242-k 10GbE Dual Port Mezzanine Card Board Chip rev 0x54 qlcnic 0000:03:00.0: using msi-x interrupts qlcnic 0000:03:00.0: eth0: XGbE port initialized xen: registering gsi 38 triggering 0 polarity 1 xen_map_pirq_gsi: returning irq 38 for gsi 38 xen: --> pirq=38 -> irq=38 (gsi=38) Already setup the GSI :38 Does this make any sense? I'm able to mod probe the qlcnic driver with options: use_msi=0 and use_msi_x=0 but this has no effect. -- View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5598955.html Sent from the Xen - Dev mailing list archive at Nabble.com. ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-27 21:31 ` Kristoffer Harthing Egefelt @ 2012-03-27 21:51 ` Konrad Rzeszutek Wilk 2012-03-27 22:35 ` Kristoffer Harthing Egefelt 2012-03-28 8:55 ` Fajar A. Nugraha 1 sibling, 1 reply; 35+ messages in thread From: Konrad Rzeszutek Wilk @ 2012-03-27 21:51 UTC (permalink / raw) To: Kristoffer Harthing Egefelt; +Cc: xen-devel On Tue, Mar 27, 2012 at 02:31:43PM -0700, Kristoffer Harthing Egefelt wrote: > Diffing the dmesg's from native linux 3.x and linux 3.x with xen shows 4 more > lines on the native: > > Native: > qlcnic 0000:03:00.0: phy port: 0 switch_mode: 0, > max_tx_q: 1 max_rx_q: 8 min_tx_bw: 0x0, > max_tx_bw: 0x64 max_mtu:0x2580, capabilities: 0x6affae > qlcnic 0000:03:00.0: failed card response code:0x10 > qlcnic 0000:03:00.0: Can't get template size 16 > qlcnic 0000:03:00.0: firmware v4.7.83 > qlcnic: 24:b6:fd:64:1e:45: QME8242-k 10GbE Dual Port Mezzanine Card Board > Chip rev 0x54 > * qlcnic 0000:03:00.0: irq 78 for MSI/MSI-X > qlcnic 0000:03:00.0: irq 79 for MSI/MSI-X > qlcnic 0000:03:00.0: irq 80 for MSI/MSI-X > qlcnic 0000:03:00.0: irq 81 for MSI/MSI-X* > qlcnic 0000:03:00.0: using msi-x interrupts > qlcnic 0000:03:00.0: eth0: XGbE port initialized > > The xen version of dmesg does not have these irq's: > > XEN: > qlcnic 0000:03:00.0: phy port: 0 switch_mode: 0, > max_tx_q: 1 max_rx_q: 8 min_tx_bw: 0x0, > max_tx_bw: 0x64 max_mtu:0x2580, capabilities: 0x6affae > qlcnic 0000:03:00.0: failed card response code:0x10 > qlcnic 0000:03:00.0: Can't get template size 16 > qlcnic 0000:03:00.0: firmware v4.7.83 > qlcnic: 24:b6:fd:64:1e:45: QME8242-k 10GbE Dual Port Mezzanine Card Board > Chip rev 0x54 > qlcnic 0000:03:00.0: using msi-x interrupts > qlcnic 0000:03:00.0: eth0: XGbE port initialized > xen: registering gsi 38 triggering 0 polarity 1 > xen_map_pirq_gsi: returning irq 38 for gsi 38 > xen: --> pirq=38 -> irq=38 (gsi=38) > Already setup the GSI :38 And is 38 assigned to this device or to another one? You shold be able to see that in /proc/interrupts. > > Does this make any sense? You would be better of comparing the /proc/interrupts - see if the one that is associated with the driver has the same number of them (the numbers will differ). > I'm able to mod probe the qlcnic driver with options: > use_msi=0 and > use_msi_x=0 > but this has no effect. > > > > -- > View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5598955.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-27 21:51 ` Konrad Rzeszutek Wilk @ 2012-03-27 22:35 ` Kristoffer Harthing Egefelt 2012-03-28 14:37 ` Konrad Rzeszutek Wilk 0 siblings, 1 reply; 35+ messages in thread From: Kristoffer Harthing Egefelt @ 2012-03-27 22:35 UTC (permalink / raw) To: xen-devel Strange - theres is no irq 38. There is irq 1-21 and 304-440. Looking at /proc/interrupts eth0 have irq 431 and eth1 have irq 435. Should there be a irq 38? I don't really understand the gsi -> irq mapping... -- View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5599061.html Sent from the Xen - Dev mailing list archive at Nabble.com. ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-27 22:35 ` Kristoffer Harthing Egefelt @ 2012-03-28 14:37 ` Konrad Rzeszutek Wilk 2012-03-29 8:30 ` Kristoffer Harthing Egefelt 0 siblings, 1 reply; 35+ messages in thread From: Konrad Rzeszutek Wilk @ 2012-03-28 14:37 UTC (permalink / raw) To: Kristoffer Harthing Egefelt; +Cc: xen-devel On Tue, Mar 27, 2012 at 03:35:27PM -0700, Kristoffer Harthing Egefelt wrote: > Strange - theres is no irq 38. > There is irq 1-21 and 304-440. > > Looking at /proc/interrupts eth0 have irq 431 and eth1 have irq 435. Can you attach the /proc/interrupts please - for both Xen and baremetal. > > Should there be a irq 38? No. It is much further up. > I don't really understand the gsi -> irq mapping... > > > > -- > View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5599061.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-28 14:37 ` Konrad Rzeszutek Wilk @ 2012-03-29 8:30 ` Kristoffer Harthing Egefelt 2012-03-29 14:59 ` Konrad Rzeszutek Wilk 0 siblings, 1 reply; 35+ messages in thread From: Kristoffer Harthing Egefelt @ 2012-03-29 8:30 UTC (permalink / raw) To: xen-devel >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 430: 0 xen-pirq-msi-x megasas 439: 0 xen-dyn-event evtchn:xenstored 440: 0 xen-dyn-event evtchn:xenstored NMI: 0 Non-maskable interrupts LOC: 0 Local timer interrupts SPU: 0 Spurious interrupts PMI: 0 Performance monitoring interrupts IWI: 0 IRQ work interrupts RES: 2037 Rescheduling interrupts CAL: 910 Function call interrupts TLB: 0 TLB shootdowns TRM: 0 Thermal event interrupts THR: 0 Threshold APIC interrupts MCE: 0 Machine check exceptions MCP: 0 Machine check polls ERR: MIS: *Xen w. pci=nomsi:* CPU0 8: 0 xen-pirq-ioapic-edge rtc0 9: 0 xen-pirq-ioapic-level acpi 16: 22714 xen-pirq-ioapic-level megasas 17: 0 xen-pirq-ioapic-level uhci_hcd:usb2, ata_piix 18: 0 xen-pirq-ioapic-level uhci_hcd:usb3 19: 0 xen-pirq-ioapic-level ehci_hcd:usb1 20: 52 xen-pirq-ioapic-level uhci_hcd:usb5 21: 337 xen-pirq-ioapic-level uhci_hcd:usb4, uhci_hcd:usb6, ehci_hcd:usb7 38: 2211501 xen-pirq-ioapic-level eth0[0], eth1[0] 304: 3051685 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 309: 1564 xen-dyn-event xenbus 311: 731 xen-dyn-event evtchn:xenstored 312: 2 xen-dyn-event evtchn:xenstored 313: 202 xen-dyn-event evtchn:xenstored 314: 817 xen-dyn-event evtchn:xenconsoled 315: 1095 xen-dyn-event vif2.0 316: 152442 xen-dyn-event vif2.1 NMI: 0 Non-maskable interrupts LOC: 0 Local timer interrupts SPU: 0 Spurious interrupts PMI: 0 Performance monitoring interrupts IWI: 0 IRQ work interrupts RES: 0 Rescheduling interrupts CAL: 0 Function call interrupts TLB: 0 TLB shootdowns TRM: 0 Thermal event interrupts THR: 0 Threshold APIC interrupts MCE: 0 Machine check exceptions MCP: 0 Machine check polls ERR: 0 MIS: 0 -- View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5602999.html Sent from the Xen - Dev mailing list archive at Nabble.com. ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-29 8:30 ` Kristoffer Harthing Egefelt @ 2012-03-29 14:59 ` Konrad Rzeszutek Wilk 2012-03-29 18:43 ` Kristoffer Harthing Egefelt 0 siblings, 1 reply; 35+ messages in thread From: Konrad Rzeszutek Wilk @ 2012-03-29 14:59 UTC (permalink / raw) To: Kristoffer Harthing Egefelt; +Cc: xen-devel 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. ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-29 14:59 ` Konrad Rzeszutek Wilk @ 2012-03-29 18:43 ` Kristoffer Harthing Egefelt 2012-05-10 15:42 ` Konrad Rzeszutek Wilk 0 siblings, 1 reply; 35+ messages in thread From: Kristoffer Harthing Egefelt @ 2012-03-29 18:43 UTC (permalink / raw) To: xen-devel 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. I'm still trying to get qlogic and dell to find out why qlogics firmwares does not work on the OEM cards from Dell - I'm not sure this will do anything though. I'll try and downgrade the linux driver to .24 >What kernel version are you using? I have tried 3.1.8-2 and 3.2.9-1 (debian wheezy) -- View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5604684.html Sent from the Xen - Dev mailing list archive at Nabble.com. ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-29 18:43 ` Kristoffer Harthing Egefelt @ 2012-05-10 15:42 ` Konrad Rzeszutek Wilk 2012-05-13 20:24 ` Kristoffer Harthing Egefelt 0 siblings, 1 reply; 35+ messages in thread From: Konrad Rzeszutek Wilk @ 2012-05-10 15:42 UTC (permalink / raw) To: Kristoffer Harthing Egefelt; +Cc: xen-devel On Thu, Mar 29, 2012 at 11:43:50AM -0700, Kristoffer Harthing Egefelt wrote: > > 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. > I'm still trying to get qlogic and dell to find out why qlogics firmwares > does not work on the OEM cards from Dell - I'm not sure this will do > anything though. I'll try and downgrade the linux driver to .24 Any luck? > > >What kernel version are you using? > I have tried 3.1.8-2 and 3.2.9-1 (debian wheezy) > > > -- > View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5604684.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-05-10 15:42 ` Konrad Rzeszutek Wilk @ 2012-05-13 20:24 ` Kristoffer Harthing Egefelt 2012-05-23 9:40 ` Kristoffer Harthing Egefelt 0 siblings, 1 reply; 35+ messages in thread From: Kristoffer Harthing Egefelt @ 2012-05-13 20:24 UTC (permalink / raw) To: xen-devel > Any luck? Actually after finding out about the pci=nomsi kernel parameter, I have not had any problems. Regarding the firmware upgrade, qlogic and dell need a supported OS to run their diag tools on, I'm tired of dealing with them, so I have not gathered this info yet. Didn't try to downgrade the driver either. But I'm about to try pci passthrough, to have 10gig directly in the domU. I'll let you know if it works. -- View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5708399.html Sent from the Xen - Dev mailing list archive at Nabble.com. ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-05-13 20:24 ` Kristoffer Harthing Egefelt @ 2012-05-23 9:40 ` Kristoffer Harthing Egefelt 2012-05-23 14:27 ` Pasi Kärkkäinen 2012-05-25 21:03 ` Konrad Rzeszutek Wilk 0 siblings, 2 replies; 35+ messages in thread From: Kristoffer Harthing Egefelt @ 2012-05-23 9:40 UTC (permalink / raw) To: xen-devel > Any luck? >Actually after finding out about the pci=nomsi kernel parameter, I have not had any problems. >Regarding the firmware upgrade, qlogic and dell need a supported OS to run their diag tools on, I'm tired of >dealing with them, so I have not gathered this info yet. >Didn't try to downgrade the driver either. >But I'm about to try pci passthrough, to have 10gig directly in the domU. >I'll let you know if it works. The pci=nomsi actually seems to create problems for us when using pci passthrough. We could not get more than 2.5 Gbit from a domU, using netback/netfront. It was suggested that we use pci passthrough to get the full 10Gbit. However dom0 and domU crashes periodically with: kernel irq 60: nobody cared (try booting with the "irqpoll" option) kernel Pid: 0, comm: swapper Not tainted Booting with irqpoll has no effect. So I tried to upgrade the firmware on the qlogic cards to 1.09.22 - no change. Qlogic's latest firmware is 1.09.65 - but is not installable on the DELL oem cards. I was not able to downgrade the qlogic driver in linux 3.2 to 5.0.24 from 5.0.25 as suggested in this thread, the driver will not compile - struct dev_mc_list is no longer defined in netdevice.h. As far as I can tell the pci=nomsi disables the irq handling needed for pci passthrough. Could someone confirm this? Could someone also clarify if this is a qlogic driver issue or a xen issue. Thanks Kristoffer -- View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5709087.html Sent from the Xen - Dev mailing list archive at Nabble.com. ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-05-23 9:40 ` Kristoffer Harthing Egefelt @ 2012-05-23 14:27 ` Pasi Kärkkäinen 2012-05-25 21:03 ` Konrad Rzeszutek Wilk 1 sibling, 0 replies; 35+ messages in thread From: Pasi Kärkkäinen @ 2012-05-23 14:27 UTC (permalink / raw) To: Kristoffer Harthing Egefelt; +Cc: xen-devel On Wed, May 23, 2012 at 02:40:04AM -0700, Kristoffer Harthing Egefelt wrote: > > Any luck? > > >Actually after finding out about the pci=nomsi kernel parameter, I have not > had any problems. > >Regarding the firmware upgrade, qlogic and dell need a supported OS to run > their diag tools on, I'm tired of >dealing with them, so I have not gathered > this info yet. > >Didn't try to downgrade the driver either. > >But I'm about to try pci passthrough, to have 10gig directly in the domU. > >I'll let you know if it works. > > The pci=nomsi actually seems to create problems for us when using pci > passthrough. > We could not get more than 2.5 Gbit from a domU, using netback/netfront. > It was suggested that we use pci passthrough to get the full 10Gbit. > However dom0 and domU crashes periodically with: > > kernel irq 60: nobody cared (try booting with the "irqpoll" option) > kernel Pid: 0, comm: swapper Not tainted > > Booting with irqpoll has no effect. > > So I tried to upgrade the firmware on the qlogic cards to 1.09.22 - no > change. > Qlogic's latest firmware is 1.09.65 - but is not installable on the DELL oem > cards. > I was not able to downgrade the qlogic driver in linux 3.2 to 5.0.24 from > 5.0.25 as suggested in this thread, the driver will not compile - struct > dev_mc_list is no longer defined in netdevice.h. > > As far as I can tell the pci=nomsi disables the irq handling needed for pci > passthrough. > Could someone confirm this? > Could someone also clarify if this is a qlogic driver issue or a xen issue. > What Xen hypervisor version are you running? Did you already try Xen 4.1.3-rc1 ? (it has irq related fixes compared to 4.1.2). -- Pasi ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-05-23 9:40 ` Kristoffer Harthing Egefelt 2012-05-23 14:27 ` Pasi Kärkkäinen @ 2012-05-25 21:03 ` Konrad Rzeszutek Wilk 1 sibling, 0 replies; 35+ messages in thread From: Konrad Rzeszutek Wilk @ 2012-05-25 21:03 UTC (permalink / raw) To: Kristoffer Harthing Egefelt; +Cc: xen-devel On Wed, May 23, 2012 at 02:40:04AM -0700, Kristoffer Harthing Egefelt wrote: > > Any luck? > > >Actually after finding out about the pci=nomsi kernel parameter, I have not > had any problems. > >Regarding the firmware upgrade, qlogic and dell need a supported OS to run > their diag tools on, I'm tired of >dealing with them, so I have not gathered > this info yet. > >Didn't try to downgrade the driver either. > >But I'm about to try pci passthrough, to have 10gig directly in the domU. > >I'll let you know if it works. > > The pci=nomsi actually seems to create problems for us when using pci > passthrough. > We could not get more than 2.5 Gbit from a domU, using netback/netfront. That is kind of expected - you are using the legacy IRQ and it can only handle so much. > It was suggested that we use pci passthrough to get the full 10Gbit. > However dom0 and domU crashes periodically with: > > kernel irq 60: nobody cared (try booting with the "irqpoll" option) > kernel Pid: 0, comm: swapper Not tainted Hmm. Is that from dom0 or from domU? > > Booting with irqpoll has no effect. On whatever host that showed that? > > So I tried to upgrade the firmware on the qlogic cards to 1.09.22 - no > change. > Qlogic's latest firmware is 1.09.65 - but is not installable on the DELL oem > cards. > I was not able to downgrade the qlogic driver in linux 3.2 to 5.0.24 from > 5.0.25 as suggested in this thread, the driver will not compile - struct > dev_mc_list is no longer defined in netdevice.h. > > As far as I can tell the pci=nomsi disables the irq handling needed for pci > passthrough. > Could someone confirm this? > Could someone also clarify if this is a qlogic driver issue or a xen issue. No idea. Without access to the hardware it is really hard to come up with any reasonable idea on this. > > Thanks > Kristoffer > > > -- > View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5709087.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-27 21:31 ` Kristoffer Harthing Egefelt 2012-03-27 21:51 ` Konrad Rzeszutek Wilk @ 2012-03-28 8:55 ` Fajar A. Nugraha 2012-03-28 9:29 ` Kristoffer Harthing Egefelt 1 sibling, 1 reply; 35+ messages in thread From: Fajar A. Nugraha @ 2012-03-28 8:55 UTC (permalink / raw) To: Kristoffer Harthing Egefelt; +Cc: xen-devel On Wed, Mar 28, 2012 at 4:31 AM, Kristoffer Harthing Egefelt <k@itoc.dk> wrote: > I'm able to mod probe the qlcnic driver with options: > use_msi=0 and > use_msi_x=0 > but this has no effect. How about pci=nomsi on kernel (i.e. vmlinuz) command line? -- Fajar ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-28 8:55 ` Fajar A. Nugraha @ 2012-03-28 9:29 ` Kristoffer Harthing Egefelt 2012-03-28 13:27 ` Andrew Cooper 0 siblings, 1 reply; 35+ messages in thread From: Kristoffer Harthing Egefelt @ 2012-03-28 9:29 UTC (permalink / raw) To: xen-devel >How about pci=nomsi on kernel (i.e. vmlinuz) command line? That worked! The card is now working with legacy interrupts: [ 143.767091] QLogic 1/10 GbE Converged/Intelligent Ethernet Driver v5.0.25 [ 143.767222] xen: registering gsi 38 triggering 0 polarity 1 [ 143.767238] xen_map_pirq_gsi: returning irq 38 for gsi 38 [ 143.767242] xen: --> pirq=38 -> irq=38 (gsi=38) [ 143.767245] Already setup the GSI :38 [ 143.767250] qlcnic 0000:03:00.0: PCI INT A -> GSI 38 (level, low) -> IRQ 38 [ 143.767267] qlcnic 0000:03:00.0: setting latency timer to 64 [ 143.768057] qlcnic 0000:03:00.0: 2MB memory map [ 144.403025] qlcnic 0000:03:00.0: phy port: 0 switch_mode: 0, [ 144.403027] max_tx_q: 1 max_rx_q: 8 min_tx_bw: 0x0, [ 144.403029] max_tx_bw: 0x64 max_mtu:0x2580, capabilities: 0x6affae [ 144.411026] qlcnic 0000:03:00.0: failed card response code:0x10 [ 144.411099] qlcnic 0000:03:00.0: Can't get template size 16 [ 144.411102] qlcnic 0000:03:00.0: firmware v4.7.83 [ 144.419028] qlcnic: 24:b6:fd:64:1e:45: QME8242-k 10GbE Dual Port Mezzanine Card Board Chip rev 0x54 [ 144.419075] qlcnic 0000:03:00.0: using legacy interrupts [ 144.419842] qlcnic 0000:03:00.0: eth0: XGbE port initialized Irq 38 is now visible in /proc/interrupts But what might the consequences be of this? The NIC currently share irq with the raid card - should I expect a performance hit? The dom0 is going to have 1 core dedicated. -- View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5599935.html Sent from the Xen - Dev mailing list archive at Nabble.com. ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-28 9:29 ` Kristoffer Harthing Egefelt @ 2012-03-28 13:27 ` Andrew Cooper 2012-03-29 8:35 ` Kristoffer Harthing Egefelt 0 siblings, 1 reply; 35+ messages in thread From: Andrew Cooper @ 2012-03-28 13:27 UTC (permalink / raw) To: Kristoffer Harthing Egefelt; +Cc: xen-devel@lists.xensource.com On 28/03/12 10:29, Kristoffer Harthing Egefelt wrote: >> How about pci=nomsi on kernel (i.e. vmlinuz) command line? > That worked! The card is now working with legacy interrupts: > > [ 143.767091] QLogic 1/10 GbE Converged/Intelligent Ethernet Driver v5.0.25 > [ 143.767222] xen: registering gsi 38 triggering 0 polarity 1 > [ 143.767238] xen_map_pirq_gsi: returning irq 38 for gsi 38 > [ 143.767242] xen: --> pirq=38 -> irq=38 (gsi=38) > [ 143.767245] Already setup the GSI :38 > [ 143.767250] qlcnic 0000:03:00.0: PCI INT A -> GSI 38 (level, low) -> IRQ > 38 > [ 143.767267] qlcnic 0000:03:00.0: setting latency timer to 64 > [ 143.768057] qlcnic 0000:03:00.0: 2MB memory map > [ 144.403025] qlcnic 0000:03:00.0: phy port: 0 switch_mode: 0, > [ 144.403027] max_tx_q: 1 max_rx_q: 8 min_tx_bw: 0x0, > [ 144.403029] max_tx_bw: 0x64 max_mtu:0x2580, capabilities: 0x6affae > [ 144.411026] qlcnic 0000:03:00.0: failed card response code:0x10 > [ 144.411099] qlcnic 0000:03:00.0: Can't get template size 16 > [ 144.411102] qlcnic 0000:03:00.0: firmware v4.7.83 > [ 144.419028] qlcnic: 24:b6:fd:64:1e:45: QME8242-k 10GbE Dual Port > Mezzanine Card Board Chip rev 0x54 > [ 144.419075] qlcnic 0000:03:00.0: using legacy interrupts > [ 144.419842] qlcnic 0000:03:00.0: eth0: XGbE port initialized > > Irq 38 is now visible in /proc/interrupts > > But what might the consequences be of this? > The NIC currently share irq with the raid card - should I expect a > performance hit? > The dom0 is going to have 1 core dedicated. Out of interest, which version of Xen are you using? (if you have already said, I apologize - i cant find it from a quick scan of this thread) There is most certainly a performance hit. From my bugfixing of hardware interrupts in the past, line level interrupts take ~30ms to be services, ranging between extremes of 10ms to 150ms. XenServer sees an order of magnitude hard drive performance increase by simply switching from legacy line interrupts to MSI interrupts for the host disks. There is no good reason why legacy line interrupts would work while MSIs don't, which means you have probably found a bug (and indeed, there is a reason why line level interrupts are legacy and Message Signaled Interrupts were introduced into the PCI spec in 1995). ~Andrew > -- > View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5599935.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900, http://www.citrix.com ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-28 13:27 ` Andrew Cooper @ 2012-03-29 8:35 ` Kristoffer Harthing Egefelt 2012-03-29 11:50 ` Andrew Cooper 0 siblings, 1 reply; 35+ messages in thread From: Kristoffer Harthing Egefelt @ 2012-03-29 8:35 UTC (permalink / raw) To: xen-devel >Out of interest, which version of Xen are you using? (if you have >already said, I apologize - i cant find it from a quick scan of this thread) We're running xen-4.1.2. If this is a bug I'd very much like to help to test a fix :-) -- View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5603011.html Sent from the Xen - Dev mailing list archive at Nabble.com. ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-29 8:35 ` Kristoffer Harthing Egefelt @ 2012-03-29 11:50 ` Andrew Cooper 0 siblings, 0 replies; 35+ messages in thread From: Andrew Cooper @ 2012-03-29 11:50 UTC (permalink / raw) To: xen-devel, Kristoffer Harthing Egefelt On 29/03/12 09:35, Kristoffer Harthing Egefelt wrote: >> Out of interest, which version of Xen are you using? (if you have >> already said, I apologize - i cant find it from a quick scan of this > thread) > > We're running xen-4.1.2. > If this is a bug I'd very much like to help to test a fix :-) For XenServer, we currently use Xen based from 4.1-testing, a Linux 2.6.32 based kernel, and currently use the qlcnic version 5.0.24 driver, and I can find any issues we have had matching this description. Can you also make completely certain that you are loading the correct version of the firmware for driver you are using. dmesg indicates that the driver can talk to the card, but is getting weird replies. After that, try downgrading the driver to 5.0.24. > -- > View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5603011.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900, http://www.citrix.com ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-27 20:29 ` Kristoffer Harthing Egefelt 2012-03-27 21:31 ` Kristoffer Harthing Egefelt @ 2012-03-28 9:15 ` Ian Campbell 2012-03-28 9:55 ` Kristoffer Harthing Egefelt 1 sibling, 1 reply; 35+ messages in thread From: Ian Campbell @ 2012-03-28 9:15 UTC (permalink / raw) To: Kristoffer Harthing Egefelt; +Cc: xen-devel@lists.xensource.com On Tue, 2012-03-27 at 21:29 +0100, Kristoffer Harthing Egefelt wrote: > >mem=3G dom0_mem=max:1G' (on your Xen hypervisor line) > Same situation - No link on NICs. Please can you share the literal output of "ifconfig -a", "brctl show" and "ethtool <ethN>" (the last one for each device), perhaps someone can spot something of interest. Can you also share your /etc/network/interfaces file. How are you configuring bridged networking? Are you doing it via /e/n/interfaces or using the xend network-script support? I would strongly recommend disabling the xend network script support (it is disabled by default in the Debian packages) and configuring via /e/n/interfaces as described in http://wiki.xen.org/wiki/HostConfiguration/Networking Ian. ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-28 9:15 ` Ian Campbell @ 2012-03-28 9:55 ` Kristoffer Harthing Egefelt 2012-03-28 10:23 ` Andrew Cooper 0 siblings, 1 reply; 35+ messages in thread From: Kristoffer Harthing Egefelt @ 2012-03-28 9:55 UTC (permalink / raw) To: xen-devel This is ip a showing no-carrier, even if the NIC is upped with ip link set dev eth0 up *ip a * 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000 link/ether 24:b6:fd:64:1e:45 brd ff:ff:ff:ff:ff:ff 3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000 link/ether 24:b6:fd:64:1e:46 brd ff:ff:ff:ff:ff:ff *This is ifconfig:* eth0 Link encap:Ethernet HWaddr 24:b6:fd:64:1e:45 UP BROADCAST PROMISC MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:175 *Interrupt 175 does not exist in /proc/interrupts* *This is dmesg while loading the qlcnic driver* [ 12.009860] qlcnic 0000:03:00.0: phy port: 0 switch_mode: 0, [ 12.009862] max_tx_q: 1 max_rx_q: 8 min_tx_bw: 0x0, [ 12.009864] max_tx_bw: 0x64 max_mtu:0x2580, capabilities: 0x6affae [ 12.025831] qlcnic 0000:03:00.0: failed card response code:0x10 [ 12.025889] qlcnic 0000:03:00.0: Can't get template size 16 [ 12.025893] qlcnic 0000:03:00.0: firmware v4.7.83 [ 12.057837] qlcnic: 24:b6:fd:64:1e:45: QME8242-k 10GbE Dual Port Mezzanine Card Board Chip rev 0x54 [ 12.058243] qlcnic 0000:03:00.0: using msi-x interrupts [ 12.058810] qlcnic 0000:03:00.0: eth0: XGbE port initialized [ 12.058844] xen: registering gsi 38 triggering 0 polarity 1 [ 12.058856] xen_map_pirq_gsi: returning irq 38 for gsi 38 [ 12.058859] xen: --> pirq=38 -> irq=38 (gsi=38) [ 12.058863] Already setup the GSI :38 *Interrupt 38 does not exist in /proc/interrupts* This is before any network configuration is run. /etc/network/interfaces is disabled - I run openvswitch and do all network configuration in some custom scripts. Without xen it works - the irq's exist. -- View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5599996.html Sent from the Xen - Dev mailing list archive at Nabble.com. ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-28 9:55 ` Kristoffer Harthing Egefelt @ 2012-03-28 10:23 ` Andrew Cooper 2012-03-28 12:57 ` Kristoffer Harthing Egefelt 0 siblings, 1 reply; 35+ messages in thread From: Andrew Cooper @ 2012-03-28 10:23 UTC (permalink / raw) To: xen-devel On 28/03/12 10:55, Kristoffer Harthing Egefelt wrote: > This is ip a showing no-carrier, even if the NIC is upped with ip link set > dev eth0 up > > *ip a * > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc > pfifo_fast state DOWN qlen 1000 > link/ether 24:b6:fd:64:1e:45 brd ff:ff:ff:ff:ff:ff > 3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc > pfifo_fast state DOWN qlen 1000 > link/ether 24:b6:fd:64:1e:46 brd ff:ff:ff:ff:ff:ff > > *This is ifconfig:* > eth0 Link encap:Ethernet HWaddr 24:b6:fd:64:1e:45 > UP BROADCAST PROMISC MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > Interrupt:175 > > *Interrupt 175 does not exist in /proc/interrupts* > > *This is dmesg while loading the qlcnic driver* > [ 12.009860] qlcnic 0000:03:00.0: phy port: 0 switch_mode: 0, > [ 12.009862] max_tx_q: 1 max_rx_q: 8 min_tx_bw: 0x0, > [ 12.009864] max_tx_bw: 0x64 max_mtu:0x2580, capabilities: 0x6affae > [ 12.025831] qlcnic 0000:03:00.0: failed card response code:0x10 > [ 12.025889] qlcnic 0000:03:00.0: Can't get template size 16 > [ 12.025893] qlcnic 0000:03:00.0: firmware v4.7.83 > [ 12.057837] qlcnic: 24:b6:fd:64:1e:45: QME8242-k 10GbE Dual Port > Mezzanine Card Board Chip rev 0x54 > [ 12.058243] qlcnic 0000:03:00.0: using msi-x interrupts > [ 12.058810] qlcnic 0000:03:00.0: eth0: XGbE port initialized > [ 12.058844] xen: registering gsi 38 triggering 0 polarity 1 > [ 12.058856] xen_map_pirq_gsi: returning irq 38 for gsi 38 > [ 12.058859] xen: --> pirq=38 -> irq=38 (gsi=38) > [ 12.058863] Already setup the GSI :38 > > *Interrupt 38 does not exist in /proc/interrupts* > > This is before any network configuration is run. > /etc/network/interfaces is disabled - I run openvswitch and do all network > configuration in some custom scripts. > > Without xen it works - the irq's exist. The IRQs listed when querying the hardware are the Xen IRQs, not dom0 IRQs. You can find the mapping with the 'i' debug key. If you have a Xen serial console: CTRL-a three times to switch input to Xen, followed by 'i' If you are using xl, then something like: xl debug-keys 'i' xl dmesg | less ~Andrew > -- > View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5599996.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900, http://www.citrix.com ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-28 10:23 ` Andrew Cooper @ 2012-03-28 12:57 ` Kristoffer Harthing Egefelt 2012-03-28 13:06 ` Jan Beulich 0 siblings, 1 reply; 35+ messages in thread From: Kristoffer Harthing Egefelt @ 2012-03-28 12:57 UTC (permalink / raw) To: xen-devel >The IRQs listed when querying the hardware are the Xen IRQs, not dom0 IRQs. >You can find the mapping with the 'i' debug key. >If you are using xl, then something like: > xl debug-keys 'i' > xl dmesg | less Good stuff - but can you explain how come, in the BIOS, the NIC and the RAID controller share IRQ 15, but in /proc/interrupts they have different irqs: 16: 6326 xen-pirq-ioapic-level megasas 38: 83524 xen-pirq-ioapic-level eth0[0], eth1[0] Does this mean that there shouldn't be any interrupt collisions using pci=nomsi ? -- View this message in context: http://xen.1045712.n5.nabble.com/no-carrier-on-qlogic-8242-10gig-with-linux-3-x-running-xen-tp5597283p5600390.html Sent from the Xen - Dev mailing list archive at Nabble.com. ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-28 12:57 ` Kristoffer Harthing Egefelt @ 2012-03-28 13:06 ` Jan Beulich 0 siblings, 0 replies; 35+ messages in thread From: Jan Beulich @ 2012-03-28 13:06 UTC (permalink / raw) To: Kristoffer Harthing Egefelt; +Cc: xen-devel >>> On 28.03.12 at 14:57, Kristoffer Harthing Egefelt <k@itoc.dk> wrote: > Good stuff - but can you explain how come, in the BIOS, the NIC and the RAID > controller share IRQ 15, but in /proc/interrupts they have different irqs: > > 16: 6326 xen-pirq-ioapic-level megasas > 38: 83524 xen-pirq-ioapic-level eth0[0], eth1[0] The BIOS certainly runs the IO-APICs in legacy mode (required to be able to boot legacy OSes), using just IRQs 0...15 (on a single IO-APIC). Once ACPI gets enabled, all IO-APIC pins can be used, and hence sharing of interrupts is generally not needed if there are sufficiently many pins (and things are properly wired up on the mainboard). > Does this mean that there shouldn't be any interrupt collisions using > pci=nomsi ? Yes. Jan ^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen 2012-03-27 10:02 ` Wei Liu 2012-03-27 12:41 ` Pasi Kärkkäinen @ 2012-07-31 21:50 ` Anirban Chakraborty 1 sibling, 0 replies; 35+ messages in thread From: Anirban Chakraborty @ 2012-07-31 21:50 UTC (permalink / raw) To: Wei Liu; +Cc: Kristoffer Harthing Egefelt, xen-devel@lists.xensource.com Do not worry about failed card response code. It indicates that the driver was not able to get the FW dump template during initialization as that CDRP command is not supported by the onboard FW. In order to get line rate, it is important that you run the driver with all the msi-x vectors. Looks like the driver could get only legacy interrupt in this case. -Anirban On Tue, Mar 27, 2012 at 3:02 AM, Wei Liu <wei.liu2@citrix.com> wrote: > On Tue, 2012-03-27 at 10:43 +0100, Kristoffer Harthing Egefelt wrote: >> Please find dmesg below - do you see any hints? >> The onboard 1gig network cards are in fabric A, the 10gig's are in fabric B. >> I have disabled the onboard NICs so the 10gigs is eth0 and eth1. >> I have tried enabling the onboard NICs, making the 10gig's eth2 and eth3 >> without luck. >> >> Thanks >> >> oot@node0301:/var/log# cat dmesg.0 > > <snip> > >> [ 12.646309] input: PC Speaker as /devices/platform/pcspkr/input/input1 >> [ 12.696167] QLogic 1/10 GbE Converged/Intelligent Ethernet Driver v5.0.25 >> [ 12.696278] xen: registering gsi 38 triggering 0 polarity 1 >> [ 12.696304] xen: --> pirq=38 -> irq=38 (gsi=38) >> [ 12.696340] qlcnic 0000:03:00.0: PCI INT A -> GSI 38 (level, low) -> IRQ >> 38 > > This one. > >> [ 12.696355] qlcnic 0000:03:00.0: setting latency timer to 64 >> [ 12.697214] qlcnic 0000:03:00.0: 2MB memory map > > <snip> > >> [ 13.077174] ata1: SATA link down (SStatus 0 SControl 300) >> [ 13.077266] ata2: SATA link down (SStatus 0 SControl 300) >> [ 13.221115] usb 2-3: new high-speed USB device number 3 using ehci_hcd >> [ 13.345114] qlcnic 0000:03:00.0: phy port: 0 switch_mode: 0, >> [ 13.345116] max_tx_q: 1 max_rx_q: 8 min_tx_bw: 0x0, >> [ 13.345117] max_tx_bw: 0x64 max_mtu:0x2580, capabilities: 0x6affae >> [ 13.361103] qlcnic 0000:03:00.0: failed card response code:0x10 >> [ 13.361162] qlcnic 0000:03:00.0: Can't get template size 16 >> [ 13.361167] qlcnic 0000:03:00.0: firmware v4.7.83 > > Failed. :-( > >> [ 13.371640] usb 2-3: New USB device found, idVendor=046b, idProduct=ff90 >> [ 13.371646] usb 2-3: New USB device strings: Mfr=1, Product=2, >> SerialNumber=3 >> [ 13.371650] usb 2-3: Product: Composite Device >> [ 13.371653] usb 2-3: Manufacturer: American Megatrends Inc. >> [ 13.371657] usb 2-3: SerialNumber: serial >> [ 13.393138] qlcnic: 24:b6:fd:64:1e:45: QME8242-k 10GbE Dual Port >> Mezzanine Card Board Chip rev 0x54 >> [ 13.393460] usbcore: registered new interface driver uas >> [ 13.393559] qlcnic 0000:03:00.0: using msi-x interrupts >> [ 13.394251] qlcnic 0000:03:00.0: eth0: XGbE port initialized > > And this one. > >> [ 13.394290] xen: registering gsi 38 triggering 0 polarity 1 >> [ 13.394304] xen_map_pirq_gsi: returning irq 38 for gsi 38 >> [ 13.394308] xen: --> pirq=38 -> irq=38 (gsi=38) >> [ 13.394311] Already setup the GSI :38 >> [ 13.394316] qlcnic 0000:03:00.1: PCI INT A -> GSI 38 (level, low) -> IRQ >> 38 >> [ 13.394331] qlcnic 0000:03:00.1: setting latency timer to 64 >> [ 13.395317] qlcnic 0000:03:00.1: 2MB memory map >> [ 13.404052] Initializing USB Mass Storage driver... >> [ 13.404264] scsi3 : usb-storage 2-3:1.0 >> [ 13.404487] scsi4 : usb-storage 2-3:1.1 >> [ 13.404693] scsi5 : usb-storage 2-3:1.2 >> [ 13.404799] usbcore: registered new interface driver usb-storage >> [ 13.404802] USB Mass Storage support registered. >> [ 13.409136] qlcnic 0000:03:00.1: phy port: 1 switch_mode: 0, >> [ 13.409138] max_tx_q: 1 max_rx_q: 8 min_tx_bw: 0x0, >> [ 13.409139] max_tx_bw: 0x64 max_mtu:0x2580, capabilities: 0x6affae >> [ 13.425118] qlcnic 0000:03:00.1: failed card response code:0x10 >> [ 13.425174] qlcnic 0000:03:00.1: Can't get template size 16 >> [ 13.425178] qlcnic 0000:03:00.1: firmware v4.7.83 >> [ 13.449525] qlcnic 0000:03:00.1: using msi-x interrupts >> [ 13.450132] qlcnic 0000:03:00.1: eth1: XGbE port initialized > > And this one. > >> [ 13.677120] usb 5-2: new full-speed USB device number 2 using uhci_hcd >> [ 13.840290] usb 5-2: New USB device found, idVendor=046b, idProduct=ff10 >> [ 13.840296] usb 5-2: New USB device strings: Mfr=1, Product=2, >> SerialNumber=3 > > <snip> > >> [ 18.325633] ip_tables: (C) 2000-2006 Netfilter Core Team >> [ 18.434036] device xenbr0 entered promiscuous mode >> [ 18.445825] device eth1 entered promiscuous mode >> [ 18.446092] device eth0 entered promiscuous mode > > I have no idea about the "failed card response", but there are eth0 and > eth1 presented. :-) > > And it looks like that they are both bridged to xenbr0 by userspace > tools? > > > Wei. > > > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 35+ messages in thread
end of thread, other threads:[~2012-07-31 21:50 UTC | newest] Thread overview: 35+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2012-03-27 8:48 no-carrier on qlogic 8242 10gig with linux 3.x running xen Kristoffer Harthing Egefelt 2012-03-27 9:25 ` Wei Liu 2012-03-27 9:43 ` Kristoffer Harthing Egefelt 2012-03-27 10:02 ` Wei Liu 2012-03-27 12:41 ` Pasi Kärkkäinen 2012-03-27 16:23 ` Kristoffer Harthing Egefelt 2012-03-27 16:37 ` Wei Liu 2012-03-27 18:45 ` Kristoffer Harthing Egefelt 2012-03-27 18:58 ` Konrad Rzeszutek Wilk 2012-03-27 18:59 ` Konrad Rzeszutek Wilk 2012-03-27 19:26 ` Pasi Kärkkäinen 2012-03-27 20:29 ` Kristoffer Harthing Egefelt 2012-03-27 21:31 ` Kristoffer Harthing Egefelt 2012-03-27 21:51 ` Konrad Rzeszutek Wilk 2012-03-27 22:35 ` Kristoffer Harthing Egefelt 2012-03-28 14:37 ` Konrad Rzeszutek Wilk 2012-03-29 8:30 ` Kristoffer Harthing Egefelt 2012-03-29 14:59 ` Konrad Rzeszutek Wilk 2012-03-29 18:43 ` Kristoffer Harthing Egefelt 2012-05-10 15:42 ` Konrad Rzeszutek Wilk 2012-05-13 20:24 ` Kristoffer Harthing Egefelt 2012-05-23 9:40 ` Kristoffer Harthing Egefelt 2012-05-23 14:27 ` Pasi Kärkkäinen 2012-05-25 21:03 ` Konrad Rzeszutek Wilk 2012-03-28 8:55 ` Fajar A. Nugraha 2012-03-28 9:29 ` Kristoffer Harthing Egefelt 2012-03-28 13:27 ` Andrew Cooper 2012-03-29 8:35 ` Kristoffer Harthing Egefelt 2012-03-29 11:50 ` Andrew Cooper 2012-03-28 9:15 ` Ian Campbell 2012-03-28 9:55 ` Kristoffer Harthing Egefelt 2012-03-28 10:23 ` Andrew Cooper 2012-03-28 12:57 ` Kristoffer Harthing Egefelt 2012-03-28 13:06 ` Jan Beulich 2012-07-31 21:50 ` Anirban Chakraborty
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).