From owner-freebsd-net@FreeBSD.ORG Sat Oct 30 06:11:22 2010 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B8651106566B for ; Sat, 30 Oct 2010 06:11:22 +0000 (UTC) (envelope-from kevlo@kevlo.org) Received: from ns.kevlo.org (kevlo.org [220.128.136.52]) by mx1.freebsd.org (Postfix) with ESMTP id 993AB8FC18 for ; Sat, 30 Oct 2010 06:11:21 +0000 (UTC) Received: from [127.0.0.1] (kevlo@kevlo.org [220.128.136.52]) by ns.kevlo.org (8.14.3/8.14.3) with ESMTP id o9U5fHl2030601; Sat, 30 Oct 2010 13:41:18 +0800 (CST) From: Kevin Lo To: Ricky Charlet In-Reply-To: <32AB5C9615CC494997D9ABB1DB12783C024CA4A7E3@SJ-EXCH-1.adaranet.com> References: <32AB5C9615CC494997D9ABB1DB12783C024CA4A7BF@SJ-EXCH-1.adaranet.com> <32AB5C9615CC494997D9ABB1DB12783C024CA4A7DF@SJ-EXCH-1.adaranet.com> <32AB5C9615CC494997D9ABB1DB12783C024CA4A7E3@SJ-EXCH-1.adaranet.com> Content-Type: text/plain; charset="UTF-8" Date: Sat, 30 Oct 2010 13:42:05 +0800 Message-ID: <1288417325.14588.6.camel@nsl> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Cc: "freebsd-net@freebsd.org" , Jack Vogel Subject: RE: em driver problem on vmware X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Oct 2010 06:11:22 -0000 Hi Rick, The FreeBSD -current works fine for me with the newest em(4) under the VMware player. Kevin On Friday, 2010-10-29 at 19:22 -0700, Ricky Charlet wrote: > Thanks Jack, > > The failure is that ifconfig is unaware of em0. My em0 is not configured, so link partners are also unaware of it. > ifconfig em0 > ifconfig: interface em0 does not exist > > and you already have my dmes stuff on em0 (which I am now up to agreeing looks positive and would not indicate a problem) > > > My amalgamated file is a private combination of some 8.1, some 9.0, some stuff a cohort did. We have been motivated to 'upgrade' from e1000 in 8.0 to a newer/modified e1000 because of our desire to incorporate the altq patches. > > For the curious and the diligent, the e1000/if_em.c file I am using is attached. > > Ricky > > > From: Jack Vogel [mailto:jfvogel@gmail.com] > Sent: Friday, October 29, 2010 7:13 PM > To: Ricky Charlet > Cc: freebsd-net@freebsd.org > Subject: Re: em driver problem on vmware > > I remember seeing the same thing when running a FreeBSD guest on > Linux/KVM, its informational, the code will enable said bits right after > it says that. > > So, the focus should be on the data, you are saying the delivered > driver in 8.0 out of the box works and which driver exactly are you > trying to use, my last checked in? > > More on the failure, does it ping, does its link partner see anything, > etc, etc.. > > Jack > > On Fri, Oct 29, 2010 at 6:27 PM, Ricky Charlet > wrote: > FYI, > That dmesg output I get from my franken-driver on vmware is exactly the same output I get from the *working* bsd80Release on vmware: > > ------------cut-------------------- > [root@npx7511 /usr/src/sys/dev/e1000]# dmesg | grep em0 > em0: port 0x2000-0x203f mem 0xd8940000-0xd895ffff,0xd8900000-0xd890ffff irq 18 at device 0.0 on pci2 > em0: Memory Access and/or Bus Master bits were not set! > em0: [FILTER] > em0: Ethernet address: 00:0c:29:57:d7:7f > -----------paste------------------- > > > So I don't think the clue is hiding in dmesg. > > --- > Ricky Charlet > Adara Networks > USA 408-433-4942 > > -----Original Message----- > From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] On Behalf Of Ricky Charlet > Sent: Friday, October 29, 2010 5:07 PM > To: freebsd-net@freebsd.org > Subject: em driver problem on vmware > > Howdy, > I have freebsd80-release with an upgraded em0 driver from freebsd8.1 (and an appropriate touch of if_var.h). I'm running an amd64 on a vmware vm. And I see this in dmesg: > > ------------cut------------- > em0: port 0x2000-203f mem 0xd8940000-0xd895ffff, 0xd8900000-0xd890ffff irq 18 at device 0.0 on pci2 > em0: Memory Access and/or Bus Master bits were not set > em0: [FILTER] > em0: Ethernet address: 00:0c:29:57:d7:7f > ------------paste------------ > > Now, I certainly may have done something wrong with my code switch (just copied over the sys/dev/e1000 directory from 8.1 and defined drbr_needs_enqueue in if_var.h). I'll start double checking. > > But, on the other hand, has anyone seen the new em driver working/failing on a vmware vm? > > > Thanks > > > --- > Ricky Charlet > Adara Networks > USA 408-433-4942 > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"