WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] XEN - Broadcom issue: survey

To: Pezza <mario.beccia@xxxxxxxxxx>
Subject: Re: [Xen-users] XEN - Broadcom issue: survey
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Wed, 14 Nov 2007 11:28:15 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 14 Nov 2007 01:28:57 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <13735207.post@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4739C3AF.2060705@xxxxxxxxxxxxx> <4739C56C.9040204@xxxxxxxx> <13735207.post@xxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
On Tue, Nov 13, 2007 at 01:39:27PM -0800, Pezza wrote:
> 
> Hey,
> 
> please note that if you're using the tg3 driver, it means you're using
> NetXTreme *not* NetXTreme II (the latter is using the 5708/5706 chipsets,
> the former some previous releases). 
> The problem has been observed (but I'd like some confirmations here ;-))
> using the bnx2 driver, which is specific to NetEXtreme II.
> 
> To make sure what driver/version/firmware you're using you can run 'ethtool
> -i eth0' (replace eth0 with the ethernet device you want to show).
> 
> In my case, the "bad" machine shows:
> 
> [root@sofia ~]# ethtool -i peth0
> driver: bnx2
> version: 1.5.10c
> firmware-version: 1.9.3
> bus-info: 0000:03:00.0
> 
> while the "good" machine shows:
> [root@camogli scripts]# ethtool -i eth0
> driver: bnx2
> version: 1.5.1c
> firmware-version: 2.9.1
> bus-info: 0000:08:00.0
> 
> As I said before, the only relevant difference I can find between the 2
> machines is the eth0 firmware version, but I don't now if and how I can
> update it on the other one (ref to my previous message for the complete
> details on the good and bad machine configuration).
> 

My IBM blades have tg3 NIC, and out-of-the-box they had broken firmware..
network would die after 10 seconds after starting xen network bridging.. 

IBM has firmware upgrade CD (.iso) available, which you can use to upgrade
the NIC firmware.

I'm sure other vendors have their own updates available too. 

-- Pasi

>                                                                               
>                           
> M.
> 
> 
> 
> 
> mangoo wrote:
> > 
> > Ivan Porro schrieb:
> >> I totally agree with Luc Boudreau about this problem.
> >> 
> >> On modern branded server they ALL use Broadcom chipset... I must admit 
> >> that:
> >> 
> >> a) lot of people are experiencing the problem but can tolerate it
> >> 
> >> or
> >> 
> >> b) someone already experienced this problem and solved it
> > 
> > Too bad you started a new topic without even trying to describe what 
> > your problem with broadcom chipsets is?
> > 
> > I'm running Xen 3.1 (2.6.18 kernel), compiled from sources, on HP 
> > ProLiant DL320 G3. It uses tg3 for its network cards.
> > 
> > Works fine.
> > 
> > 06:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 
> > Gigabit Ethernet (rev 10)
> > 06:01.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 
> > Gigabit Ethernet (rev 10)
> > 
> > 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users