Date: Fri, 16 Mar 2018 11:57:23 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Warner Losh <imp@bsdimp.com> Cc: huanghwh <huanghwh@163.com>, FreeBSD Current <freebsd-current@freebsd.org>, jtl@freebsd.org Subject: Re: r330538 broken CURRENT on MacBookPro Message-ID: <20180316095723.GX76926@kib.kiev.ua> In-Reply-To: <CANCZdfo5Jey1Zdb8VUvxzfLfkdugZdDCucE63WeWSC1y94kdGA@mail.gmail.com> References: <7aae5d78.2e20.1622c847a87.Coremail.huanghwh@163.com> <CANCZdfo5Jey1Zdb8VUvxzfLfkdugZdDCucE63WeWSC1y94kdGA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 15, 2018 at 08:56:23PM -0600, Warner Losh wrote: > On Thu, Mar 15, 2018 at 7:55 PM, huanghwh <huanghwh@163.com> wrote: > > > Hi, > > I got this panic: > > http://sw.gddsn.org.cn/freebsd/panic.jpg > > > > > > r330538 broken CURRENT found by svn bisect > > > > > > any idea? > > > > 'trace' at the db> prompt would let us know better what's going on. See the other thread on current@, 'amd64: panic on -CURRENT @r330539 for certain UEFI hosts'.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180316095723.GX76926>