Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 16 Sep 2017 13:46:37 +1000 (EST)
From:      Bruce Evans <brde@optusnet.com.au>
To:        Scott Long <scottl@samsco.org>
Cc:        Sean Bruno <sbruno@freebsd.org>, Stephen Hurd <shurd@freebsd.org>,  Cy Schubert <Cy.Schubert@komquats.com>,  Ngie Cooper <yaneurabeya@gmail.com>, src-committers@freebsd.org,  svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   Re: svn commit: r323516 - in head/sys: dev/bnxt dev/e1000 kern net sys
Message-ID:  <20170916124826.P1107@besplex.bde.org>
In-Reply-To: <1EBD0641-002D-409C-B18E-AAB5FCDECEBA@samsco.org>
References:  <201709130711.v8D7BlTS003204@slippy.cwsent.com> <48654d1f-4cc7-da05-7a73-ef538b431560@freebsd.org> <1EBD0641-002D-409C-B18E-AAB5FCDECEBA@samsco.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 15 Sep 2017, Scott Long wrote:

>> On Sep 13, 2017, at 9:12 AM, Sean Bruno <sbruno@freebsd.org> wrote:
>>
>>>>> #blamebruno

A large burden.

>>>>> Reviewed by:    sbruno
>>>>> Approved by:    sbruno (mentor)
>>>>> Sponsored by:    Limelight Networks
>>>>> Differential Revision:    https://reviews.freebsd.org/D12235
>>>>
>>>> *gasps at the LoC count and number of changed drivers*
>>>>
>>>> Could someone please better break this up in the future..?
>>
>> This ridiculous loc was due to the amount of restructuring needed to get
>> us back to being in sync with our development.  The future will not have
>> this big of a commit/change and should be more bite/fun sized.
>>
>> The #blamebruno tag in the commit log was to indicate that this was not
>> something Stephen was doing on his own, but was something that I had
>> induced over the last few months during testing.
>
> This breaks my system.  I prior to this commit, I had igb0 and igb1.  Now I
> only have igb0, and it\xe2]x80\x99s like igb1 isn\xe2\x80\x99tt even trying to attach.  Unfortunately,
> this breaks my nfsroot setup, so I need to roll back my tree.  Please let me
> know if there\xe2\x80\x99ss anything I can provide to help debugging.

It gives lesser breakage here:
- with an old PCI em, an error that occur every few makeworlds over nfs now
   hang the hardware.  It used to be recovered from afger about 10 seconds.
   This only happened once.  I then applied my old fix which ignores the
   error better so as to recover from it immediately.  This seems to work as
   before.
- with a newer PCI-e em, throughput as measured by netblast is down by
   more that a factor of 2 since last month.

Bruce



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170916124826.P1107>