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

[Pasi Kärkkäinen <pasik@xxxxxx>]

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