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-devel

AW: Re: [Xen-devel] dom0 forcedeth driver broken in recent xen 2.6.18.8

To: pasik <pasik@xxxxxx>, ward <ward@xxxxxxx>
Subject: AW: Re: [Xen-devel] dom0 forcedeth driver broken in recent xen 2.6.18.8 tree?
From: "Carsten Schiers" <carsten@xxxxxxxxxx>
Date: Wed, 27 May 2009 22:31:09 +0200
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 27 May 2009 13:32:46 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090527192757.GO24960@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I use 0.62-Driver from nVidia Package V1.25 without problems. I simply
exchanged the file forcedeth.c in drivers/net. I attached it, maybe it
is a good idea to simply put it into the repo.

BR,
Carsten.


-----Ursprüngliche Nachricht-----
Von: Pasi Kärkkäinen [mailto:pasik@xxxxxx] 
Gesendet: Mittwoch, 27. Mai 2009 21:28
An: Ward Vandewege
Cc: xen-devel
Betreff: Re: [Xen-devel] dom0 forcedeth driver broken in recent xen 
2.6.18.8 tree?

On Wed, May 27, 2009 at 03:18:24PM -0400, Ward Vandewege wrote:
> Hi there,
> 
> I can't seem to get forcedeth nics working anymore with the latest 
2.6.18.8
> xen tree.
> 
> I'm using a supermicro h8dme board with dual onboard mcp55 nics:
> 
> 00:08.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a3)
> 00:09.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a3)
> 
> The symptom I see is that the link never comes up on the interface. 
Dmesg
> output:
> 
> May 27 15:06:58 kernel: eth0: no link during initialization.
> May 27 15:06:58 kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
> May 27 15:07:00 kernel: Bridge firewalling registered
> May 27 15:07:03 kernel: peth0: no link during initialization.
> May 27 15:07:03 kernel: ADDRCONF(NETDEV_UP): peth0: link is not ready
> May 27 15:07:13 kernel: peth0: Promiscuous mode enabled.
> May 27 15:07:13 kernel: device peth0 entered promiscuous mode
> May 27 15:07:13 kernel: audit(1243451233.462:2): dev=peth0 prom=256
> old_prom=0 auid=4294967295
> 
> I've connected the nics to two different switches, same result. They 
work
> fine under a Debian 2.6.29 kernel from backports.org.
> 
> I've tried Xen 3.2.3, Xen 3.3.1 and Xen 3.4.0 - same result for all 
three. 
> 
> When I put an intel nic in there, it works fine with all Xen versions.
> 
> Suggestions?
> 

Have you tried upgrading the driver to a newer version?

-- Pasi

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


Attachment: forcedeth.c
Description: Binary data

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