Date: Sat, 1 Sep 2018 23:22:14 +0200 From: Harry Schmalzbauer <freebsd@omnilan.de> To: Konstantin Belousov <kostikbel@gmail.com> 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: <40eab93f-6a64-92fe-15d8-c3a8c36db1a0@omnilan.de> In-Reply-To: <20180901190129.GE2340@kib.kiev.ua> References: <201808151248.w7FCmnfQ012183@repo.freebsd.org> <37ef34d3-3d23-aa08-504c-c9f3c1dc8cf0@omnilan.de> <20180901190129.GE2340@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 01.09.2018 um 21:01 schrieb Konstantin Belousov: > 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. Sorry, I confused it with INVPCID which is nonsense too. IBPB was firmware related, but this is completely different to this EFIRT... Ignore please. >> 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 Panic vanished, boots fine with D16972-47525, nothing more checked. Thanks a lot, -harry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40eab93f-6a64-92fe-15d8-c3a8c36db1a0>