Date: Wed, 28 Mar 2018 11:16:49 -0500 From: Eric van Gyzen <eric@vangyzen.net> To: Slawa Olhovchenkov <slw@zxy.spb.ru> Cc: freebsd-stable@freebsd.org Subject: Re: KBI unexpexted change in stable/11 ? Message-ID: <0b3b3294-7de4-cb1c-f85b-b846b46e8d75@vangyzen.net> In-Reply-To: <20180328153529.GL4305@zxy.spb.ru> References: <20180328130903.GC6612@zxy.spb.ru> <316fb5cd-720b-e62a-cb56-5e9b722d05e9@vangyzen.net> <20180328153529.GL4305@zxy.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Eric
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0b3b3294-7de4-cb1c-f85b-b846b46e8d75>