Date: Wed, 18 May 2016 22:59:01 -0700 From: Matthew Macy <mmacy@nextbsd.org> To: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Cc: "Jeffrey E Pieper" <jeffrey.e.pieper@intel.com> Subject: VLANs are broken in HEAD Message-ID: <154c7988196.10a3baa10286893.3276882211551267263@nextbsd.org> In-Reply-To: <2A35EA60C3C77D438915767F458D6568838796D9@ORSMSX111.amr.corp.intel.com> References: <AAA72CDB6A683B409EB745E8707D5A1A59480269@ORSMSX112.amr.corp.intel.com> <154bf1bf4f0.10279edc1116021.5572808424442449486@nextbsd.org> <2A35EA60C3C77D438915767F458D65688387815B@ORSMSX111.amr.corp.intel.com> <154c0ace6c4.d71c0892202806.1154219357981220489@nextbsd.org> <2A35EA60C3C77D438915767F458D656883878618@ORSMSX111.amr.corp.intel.com> <154c15cb2fe.f3711ecb208365.5507130188198512895@nextbsd.org> <2A35EA60C3C77D438915767F458D6568838787DD@ORSMSX111.amr.corp.intel.com> <154c1d39579.1270ea37d211568.4788324171552547899@nextbsd.org> <2A35EA60C3C77D438915767F458D656883878B66@ORSMSX111.amr.corp.intel.com> <C7D9202A-1BDD-405F-BEC1-7DD372A01188@netflix.com> <2A35EA60C3C77D438915767F458D656883878BAF@ORSMSX111.amr.corp.intel.com> <154c5a78721.c1f61494271520.3569230795596300580@nextbsd.org> <2A35EA60C3C77D438915767F458D6568838792E3@ORSMSX111.amr.corp.intel.com> <154c5f1e976.e4edac45275059.6247516418110871953@nextbsd.org> <2A35EA60C3C77D438915767F458D65688387934C@ORSMSX111.amr.corp.intel.com> <154c6003527.100e552e4275595.7953652950752637683@nextbsd.org> <2A35EA60C3C77D438915767F458D65688387940E@ORSMSX111.amr.corp.intel.com> <154c636a6b8.115562e7b277188.2861547777631150226@nextbsd.org> <2A35EA60C3C77D438915767F458D6568838794B3@ORSMSX111.amr.corp.intel.com> <154c64ebda5.c6061825277678.8041659671495731876@nextbsd.org> <2A35EA60C3C77D438915767F458D6568838796D9@ORSMSX111.amr.corp.intel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeff is testing iflib intel drivers and ran in to an issue just getting up and running with the latest on VLANs. I haven't had time to look in to it. I'm hoping someone else might already know what was at fault. Thanks. -M > I can reproduce this with the latest snapshot (20160518) but not with 20160429, so it is fairly recent. > > Thanks, > Jeff > > -----Original Message----- > From: Pieper, Jeffrey E > Sent: Wednesday, May 18, 2016 5:08 PM > To: 'Matthew Macy' <mmacy@nextbsd.org> > Cc: Scott Long <scottl@netflix.com> > Subject: RE: Driver with Denverton support > > I believe I've been using 20160408, as 20160429 doesn't boot on Denverton. There is a new one from today, so I could check and see if the problem is there too. > > Jeff > > -----Original Message----- > From: Matthew Macy [mailto:mmacy@nextbsd.org] > Sent: Wednesday, May 18, 2016 4:59 PM > To: Pieper, Jeffrey E <jeffrey.e.pieper@intel.com> > Cc: Scott Long <scottl@netflix.com> > Subject: RE: Driver with Denverton support > > What was the release date of the working snapshot? I'll need to look at what has gone in to the tree since. So it would be very helpful to know where to start from. > > Thanks in advance. > -M > > > ---- On Wed, 18 May 2016 16:57:05 -0700 Pieper, Jeffrey E <jeffrey.e.pieper@intel.com> wrote ---- > > If I can't get a DCHP address, then I can't get past the proxy. That has been my bane today. I even got our IT Engineer involved at one point. > > > > Jeff > > > > -----Original Message----- > > From: Matthew Macy [mailto:mmacy@nextbsd.org] > > Sent: Wednesday, May 18, 2016 4:33 PM > > To: Pieper, Jeffrey E <jeffrey.e.pieper@intel.com> > > Cc: Scott Long <scottl@netflix.com> > > Subject: RE: Driver with Denverton support > > > > Boot to my branch that you _just_ synced. That is -CURRENT as of today. If so, what you're describing is a regression in VLAN support. > > > > -M > > > > > > > > ---- On Wed, 18 May 2016 16:26:10 -0700 Pieper, Jeffrey E <jeffrey.e.pieper@intel.com> wrote ---- > > > That leads to another issue...as soon as I boot to your branch, I cannot acquire a DHCP address through a switch using tagged VLANs. I've tried igb (i210 and i350) as well as several em devices. The latest 11 snapshot seems to work fine in this regard. > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?154c7988196.10a3baa10286893.3276882211551267263>