Ward Vandewege
2009-May-27 19:18 UTC
[Xen-devel] dom0 forcedeth driver broken in recent xen 2.6.18.8 tree?
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? Thanks, Ward. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2009-May-27 19:27 UTC
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@lists.xensource.com http://lists.xensource.com/xen-devel
Carsten Schiers
2009-May-27 20:31 UTC
AW: Re: [Xen-devel] dom0 forcedeth driver broken in recent xen 2.6.18.8 tree?
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@iki.fi] 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 latest2.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. Theywork> 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 allthree.> > 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@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ward Vandewege
2009-May-28 12:52 UTC
Re: Re: [Xen-devel] dom0 forcedeth driver broken in recent xen 2.6.18.8 tree?
On Wed, May 27, 2009 at 10:31:09PM +0200, Carsten Schiers wrote:> 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.Hmm, I briefly tried that last night with 3.4.0 but am not sure that my change was picked up - it didn''t help so perhaps not. Will try again tomorrow and report back. Thanks, Ward. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2009-May-28 13:02 UTC
Re: [Xen-devel] dom0 forcedeth driver broken in recent xen 2.6.18.8 tree?
On 28/05/2009 13:52, "Ward Vandewege" <ward@gnu.org> wrote:> On Wed, May 27, 2009 at 10:31:09PM +0200, Carsten Schiers wrote: >> 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. > > Hmm, I briefly tried that last night with 3.4.0 but am not sure that my > change was picked up - it didn''t help so perhaps not. Will try again > tomorrow and report back.I checked the newer driver into linux-2.6.18-xen.hg earlier, so a fresh build of an up-to-date clone of that repository will also get you the new driver. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel