Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 23 Mar 2018 16:44:36 -0700
From:      Mark Peek <mark@peek.org>
To:        Konstantin Belousov <kostikbel@gmail.com>
Cc:        Peter Lei <peter.lei@ieee.org>, freebsd-current@freebsd.org, huanghwh@163.com, "Jonathan T. Looney" <jtl@freebsd.org>
Subject:   Re: amd64: panic on -CURRENT @r330539 for certain UEFI hosts
Message-ID:  <CAGGgMJfaUeQ9aAfC=3EWQ3UrC6rdf=G6yfFY1MVHOfG-983d_w@mail.gmail.com>
In-Reply-To: <20180323231902.GM76926@kib.kiev.ua>
References:  <8b8f1352-aa5c-716c-ef6c-3b3cd630043f@ieee.org> <20180316095627.GW76926@kib.kiev.ua> <CAGGgMJee0gW%2B9Rz0NHtC=6ZCgzs7jgLwqeE4pWMbMv66QRU6jg@mail.gmail.com> <20180323231902.GM76926@kib.kiev.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 23, 2018 at 4:19 PM, Konstantin Belousov <kostikbel@gmail.com>
wrote:

> On Fri, Mar 23, 2018 at 04:06:23PM -0700, Mark Peek wrote:
> > I ran into the original issue with r330539 on a Fusion VM. Trying this
> > patch causes a different panic:
> >
> > https://people.freebsd.org/~mp/r330539-patched.png
> >
> > Thoughts?
>
> r331290 should fixed this issue.  What is your kernel sources version ?
>

Thank you for the pointer to r331290. I missed it and thought your patch to
-current was the intended fix.

Updated my kernel to r331469 and it is booting on Fusion now.

Thanks!
Mark



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGGgMJfaUeQ9aAfC=3EWQ3UrC6rdf=G6yfFY1MVHOfG-983d_w>