Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 1 Sep 2018 22:01:29 +0300
From:      Konstantin Belousov <kostikbel@gmail.com>
To:        Harry Schmalzbauer <freebsd@omnilan.de>
Cc:        src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   Re: Post r337773 EFIRT-boot-panic still happening with r337838 [Was: Re: svn commit: r337838 - head/sys/amd64/amd64]
Message-ID:  <20180901190129.GE2340@kib.kiev.ua>
In-Reply-To: <37ef34d3-3d23-aa08-504c-c9f3c1dc8cf0@omnilan.de>
References:  <201808151248.w7FCmnfQ012183@repo.freebsd.org> <37ef34d3-3d23-aa08-504c-c9f3c1dc8cf0@omnilan.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 01, 2018 at 08:16:15PM +0200, Harry Schmalzbauer wrote:
> I'm testing ALPHA4 on a Ivy bridge machine, without recent firmware 
> update, so no PCID.
I have no idea what is the connection between firware updates and PCID.
Ivy CPUs do have the PCID feature.

> This fix doesn't cover that hardware.
> Setting efi.rt.disabled=1 in loader.conf makes it bootable.
> 
> Without this tweak, the following panic happens:
> Fatal trap 12: Page fault while in kernel mode
> :
> cpuid = 5; apic id = 05
> :
> fault code: supervisor read data, page not present.
> :
Try https://reviews.freebsd.org/D16972



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