From owner-freebsd-net@FreeBSD.ORG Thu Nov 4 05:12:11 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 7D783106566B for ; Thu, 4 Nov 2010 05:12:11 +0000 (UTC) (envelope-from RCharlet@adaranet.com) Received: from barracuda.adaranet.com (smtp.adaranet.com [72.5.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 550218FC12 for ; Thu, 4 Nov 2010 05:12:11 +0000 (UTC) X-ASG-Debug-ID: 1288846383-0d0f33a70001-QdxwpM Received: from SJ-EXCH-1.adaranet.com ([10.10.1.29]) by barracuda.adaranet.com with ESMTP id AH3uI5RQACDyEUgI; Wed, 03 Nov 2010 21:53:03 -0700 (PDT) X-Barracuda-Envelope-From: RCharlet@adaranet.com Received: from SJ-EXCH-1.adaranet.com ([fe80::7042:d8c2:5973:c523]) by SJ-EXCH-1.adaranet.com ([fe80::7042:d8c2:5973:c523%14]) with mapi; Wed, 3 Nov 2010 21:53:03 -0700 From: "Ricky Charlet" X-Barracuda-BBL-IP: fe80::7042:d8c2:5973:c523 X-Barracuda-RBL-IP: fe80::7042:d8c2:5973:c523 To: "Ricky Charlet" , Jack Vogel , Juli Mallett Date: Wed, 3 Nov 2010 21:53:02 -0700 X-ASG-Orig-Subj: RE: em driver problem on vmware Thread-Topic: em driver problem on vmware Thread-Index: Act4DiiarsMAP3YqQ5iNBurl6b/5TwAPlrcgAOO2JUA= Message-ID: <32AB5C9615CC494997D9ABB1DB12783C024C6FC072@SJ-EXCH-1.adaranet.com> References: <32AB5C9615CC494997D9ABB1DB12783C024CA4A7BF@SJ-EXCH-1.adaranet.com> <32AB5C9615CC494997D9ABB1DB12783C024CA4A7DF@SJ-EXCH-1.adaranet.com> <32AB5C9615CC494997D9ABB1DB12783C024CA4A7E3@SJ-EXCH-1.adaranet.com> <32AB5C9615CC494997D9ABB1DB12783C024CA4A7EA@SJ-EXCH-1.adaranet.com> <32AB5C9615CC494997D9ABB1DB12783C024CA4A7F3@SJ-EXCH-1.adaranet.com> In-Reply-To: <32AB5C9615CC494997D9ABB1DB12783C024CA4A7F3@SJ-EXCH-1.adaranet.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Barracuda-Connect: UNKNOWN[10.10.1.29] X-Barracuda-Start-Time: 1288846383 X-Barracuda-URL: http://172.16.10.203:8000/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at adaranet.com Cc: FreeBSD Net 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: Thu, 04 Nov 2010 05:12:11 -0000 FYI, to close this thread off, I just had a build problem, I forgot to b= uild e1000/if_lem.c. Did that and now it works. So this becomes a success report of sorts... if anyone else is hand= cuffed (like me) to 8.0 but you want the 8.1 e1000 driver (for altq), it is= possible to port backwards. However, everyone is by far better served if you can just straight = away use 8.1. --- 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: Saturday, October 30, 2010 9:10 AM > To: Jack Vogel; Juli Mallett > Cc: FreeBSD Net > Subject: RE: em driver problem on vmware > > Ah, Thanks for the direction. I'll take it as a self project from here. > And I'll update this thread with my results hopefully by mid next week. > > Ricky > > > From: Jack Vogel [mailto:jfvogel@gmail.com] > Sent: Saturday, October 30, 2010 1:41 AM > To: Juli Mallett > Cc: Ricky Charlet; FreeBSD Net > Subject: Re: em driver problem on vmware > > Uh, the emulated device in vmware is an OLD 82543 or something like > that right? > So, the e1000 driver in 8.1 is split into two parts, em and lem, its > lem that has > all the old pci support, so if you only pulled if_em then you dont > have that code. > > Sounds like maybe you should just install 8.1 on your guest and avoid > these > kinds of problems. > > Regards, > > Jack > > On Fri, Oct 29, 2010 at 11:26 PM, Juli Mallett > > wrote: > dmesg is not cleared at boot; your devices are not being detected, > they merely showed up in a previous boot. > > On Fri, Oct 29, 2010 at 23:13, Ricky Charlet > > wrote: > > Hi Julie, > > > > My entire dmesg output is attached. > > > > With much appreciation > > > > Ricky > > > > > > > >> -----Original Message----- > >> From: juli@clockworksquid.com > [mailto:juli@clockworksquid.com] On > >> Behalf Of Juli Mallett > >> Sent: Friday, October 29, 2010 8:01 PM > >> To: Ricky Charlet > >> Subject: Re: em driver problem on vmware > >> > >> Can you send me your full dmesg? You must be missing some relevant > >> message, because the only circumstances under which you'd see the > >> device attaching but then it wouldn't be present would also generate > >> some error messages. > >> > >> On Fri, Oct 29, 2010 at 19:22, 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 > >> > aranet.com>> 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 net@freebsd.org> > >> net@freebsd.org> [mailto:owner-freebsd- > net@freebsd.org > >> freebsd-net@freebsd.org>] On Behalf > Of Ricky Charlet > >> > Sent: Friday, October 29, 2010 5:07 PM > >> > To: freebsd-net@freebsd.org net@freebsd.org> 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 net@freebsd.org> net@freebsd.org>> mailing list > >> > http://lists.freebsd.org/mailman/listinfo/freebsd-net > >> > To unsubscribe, send any mail to "freebsd-net- > >> > unsubscribe@freebsd.org net-unsubscribe@freebsd.org unsubscribe@freebsd.org>>" > >> > _______________________________________________ > >> > freebsd-net@freebsd.org net@freebsd.org> net@freebsd.org>> mailing list > >> > http://lists.freebsd.org/mailman/listinfo/freebsd-net > >> > To unsubscribe, send any mail to "freebsd-net- > >> > unsubscribe@freebsd.org net-unsubscribe@freebsd.org 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"