From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kristoffer Harthing Egefelt Subject: Re: no-carrier on qlogic 8242 10gig with linux 3.x running xen Date: Tue, 27 Mar 2012 09:23:35 -0700 (PDT) Message-ID: <1332865415525-5598276.post@n5.nabble.com> References: <1332838109433-5597283.post@n5.nabble.com> <1332840330.2485.70.camel@leeds.uk.xensource.com> <1332841414026-5597400.post@n5.nabble.com> <1332842573.2485.88.camel@leeds.uk.xensource.com> <20120327124113.GP12984@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20120327124113.GP12984@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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.