Date: Sun, 1 Apr 2018 21:38:31 +0900 From: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> To: freebsd-current@freebsd.org Cc: kevans@freebsd.org Subject: Re: Call for Testing: UEFI Changes Message-ID: <20180401213831.1535c7511c1d95a258318bc7@dec.sakura.ne.jp> In-Reply-To: <CACNAnaE237%2Bb9-ZD1AWpnsSeE5EnDU539QDMDDcdZ5KWJjQwQA@mail.gmail.com> References: <CACNAnaFmu2rFF1w4ar4xHUbN5vHitTLi0Ui6aCjL1MuTj3iJsQ@mail.gmail.com> <5f663141-433c-951d-a350-7369b004415f@alvermark.net> <CACNAnaE1UaqzS4bjQY9uqnhH2mX7XfUKT%2BVA%2Bn0v1=xF2FWXRg@mail.gmail.com> <20180322225644.1480251c4547ce30f3d88de9@dec.sakura.ne.jp> <dd6790b2-dfd2-d851-e851-99dfc489c5e5@ieee.org> <CACNAnaEfw2vzgnqrRkjgzqqtEyOYCeCR%2BP%2BVexPGzbOvNxsJ5A@mail.gmail.com> <CACNAnaE237%2Bb9-ZD1AWpnsSeE5EnDU539QDMDDcdZ5KWJjQwQA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Confirmed both loader (with boot1) part and efirt.ko part.
Working OK on my ThinkPad420 (with nvidia GPU) at r331864.
No benefit (VGA resolution) but no new harm (no panic nor silent
reboot).
*Maybe gracefully falling back to mode 0.
As I'm on x11/nvidia-driver, completely no test is done with
drm-next.
One more to mention.
I've cherry-picked r330868, r331241 and r331361 on stable/11 after
r331114, amd64 and works OK as on head.
Additional cherry-picking of r331365 is OK, too.
Without r330868, my ThinkPad silently reboots within about 10-60
minutes range, maybe by actual access to UEFI RS.
With r331241 without r331361 causes instant panic on loading efirt.ko.
So all 3 (4) revs should be MFC'ed together.
Sorry for delay.
On Thu, 22 Mar 2018 10:34:33 -0500
Kyle Evans <kevans@freebsd.org> wrote:
> On Thu, Mar 22, 2018 at 10:18 AM, Kyle Evans <kevans@freebsd.org> wrote:
> > On Thu, Mar 22, 2018 at 10:16 AM, Peter Lei <peter.lei@ieee.org> wrote:
> >> On 3/22/18 8:56 AM, Tomoaki AOKI wrote:
> >>> Hi.
> >>> For problem 2, try reverting r331241 alone.
> >>> This worked for my ThinkPad T420.
> >>
> >>
> >> I also hit this after updating to latest and was about to post when I
> >> saw this thread -
> >>
> >> I build efirt into the kernel and it's now doing a panic on boot. It
> >> appears to be due to this recent addition in dev/efidev/efirt.c by r331241:
> >>
> >>> if (!efi_is_in_map(map, efihdr->memory_size / efihdr->descriptor_size,
> >>> efihdr->descriptor_size, (vm_offset_t)efi_runtime->rt_gettime)) {
> >>
> >> The faulting address is for "efi_runtime->rt_gettime" (and is still a
> >> phys addr here).
> >>
> >
> > The following patch [1] (I can't guarantee how long he'll keep it
> > available there) should fix this class of problems.
> >
> > [1] https://people.freebsd.org/~andrew/0001-Enter-into-the-EFI-environment-before-check-the-GetT.patch
>
> Now committed as of r331361.
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>
--
Tomoaki AOKI <junchoon@dec.sakura.ne.jp>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180401213831.1535c7511c1d95a258318bc7>