From owner-freebsd-stable@freebsd.org  Wed Mar 28 16:46:50 2018
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 89FA1F6BE40
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Wed, 28 Mar 2018 16:46:50 +0000 (UTC)
 (envelope-from gpalmer@freebsd.org)
Received: from mail.in-addr.com (mail.in-addr.com
 [IPv6:2a01:4f8:191:61e8::2525:2525])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2756B76084
 for <freebsd-stable@freebsd.org>; Wed, 28 Mar 2018 16:46:50 +0000 (UTC)
 (envelope-from gpalmer@freebsd.org)
Received: from gjp by mail.in-addr.com with local (Exim 4.90_1 (FreeBSD))
 (envelope-from <gpalmer@freebsd.org>)
 id 1f1EDm-000Axb-Ki; Wed, 28 Mar 2018 17:46:46 +0100
Date: Wed, 28 Mar 2018 17:46:46 +0100
From: Gary Palmer <gpalmer@freebsd.org>
To: Slawa Olhovchenkov <slw@zxy.spb.ru>
Cc: Eric van Gyzen <eric@vangyzen.net>, freebsd-stable@freebsd.org
Subject: Re: KBI unexpexted change in stable/11 ?
Message-ID: <20180328164646.GC59700@in-addr.com>
References: <20180328130903.GC6612@zxy.spb.ru>
 <316fb5cd-720b-e62a-cb56-5e9b722d05e9@vangyzen.net>
 <20180328153529.GL4305@zxy.spb.ru>
 <0b3b3294-7de4-cb1c-f85b-b846b46e8d75@vangyzen.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0b3b3294-7de4-cb1c-f85b-b846b46e8d75@vangyzen.net>
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: gpalmer@freebsd.org
X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Mar 2018 16:46:50 -0000

On Wed, Mar 28, 2018 at 11:16:49AM -0500, Eric van Gyzen wrote:
> On 03/28/2018 10:35, Slawa Olhovchenkov wrote:
> > On Wed, Mar 28, 2018 at 10:29:10AM -0500, Eric van Gyzen wrote:
> > 
> >> On 03/28/2018 08:09, Slawa Olhovchenkov wrote:
> >>> I am upgrade system to latest -STABLE and now see kernel crash:
> >>>
> >>> - loading virtualbox modules build on 11.1-RELEASE-p6
> >>> - loading nvidia module build on 11.1-RELEASE-p6 and start xdm
> >>>
> >>> Is this expected? I am mean about loading modules builded on
> >>> 11.1-RELEASE on any 11.1-STABLE.
> >>
> >> This is not expected.  Can you bisect to find the stable/11 commit that
> >> broke this?
> >>
> >> If you can roll back to 11.1-RELEASE, you could probably just
> >> buildkernel and installkernel from various points along stable/11.  That
> >> would save a lot of time by avoiding buildworld.
> > 
> > r325665 is previos point and is good.
> > r331615 crashed.
> > Can I use some script for bisect?
> 
> I'm not aware of a script for this.  The only tool I've used is "git
> bisect", which is very handy if you're already familiar with git.

You may want to try devel/p5-App-SVN-Bisect.  Never used it, so
no idea if it's functional or helpful, just found it doing a quick
search

Regards,

Gary