Re: [Xen-devel] no-carrier on qlogic 8242 10gig with linux 3.x running xen

[Wei Liu <wei.liu2@xxxxxxxxxx>]

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@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel