From owner-freebsd-current@freebsd.org Tue Apr 3 01:13:39 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7CC8CF73A73 for ; Tue, 3 Apr 2018 01:13:39 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-wm0-f67.google.com (mail-wm0-f67.google.com [74.125.82.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EC4987D1BC for ; Tue, 3 Apr 2018 01:13:38 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-wm0-f67.google.com with SMTP id f125so30993533wme.4 for ; Mon, 02 Apr 2018 18:13:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=dUVlKD90GLqmyZR5Xcmy9q1Q+6eL0vu4p2Z2IR9iOLM=; b=mPGkOqpxNnTd+pmd3R7zXolWmLdz4f5ClWKRVL4lcLCn9Ga0g3QPFpOSkPJEQ/6rok HBEA6RbbHNigC7xWJka4EazO5mwnlGwksPBYgC4/917Ehwxp/aIrZtWbCsKN1EES4YxR 0wHUAFIRtFXT7iDMNwp6GF6o2BCFW71Wa5ct7kx88DKQJ++yfqK0xNMnUKoQtFiBjgnZ TcWxGmOZr5p9pQ14Nca6Y8GsCQS19GuhzrbG4btxlwsxOBgLmIBOQ9SJ9SHEKojJIEhx aYdvaKSZatIDaoTYkUJTWdfyWR8yBWjuApkGhZtjZ8c/Xp0yrDXq1U3PR3JRf/OzJEwk RU0g== X-Gm-Message-State: AElRT7Ek5sLePdZtXBVE1zJT9GIyHZFAQJJ9Bdcl1S9OdI5xPsSaFwHO 0ojWOGCSRPkoYMzBlqTPexMfCEyY X-Google-Smtp-Source: AIpwx4+RRiB+3/mTGVZT3dFLX+id41oQX050uJThcX1yRaWHR9bisuyul2JtIDJ2quXvUz4dsl/75w== X-Received: by 10.80.151.167 with SMTP id e36mr14622517edb.210.1522717676119; Mon, 02 Apr 2018 18:07:56 -0700 (PDT) Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com. [74.125.82.46]) by smtp.gmail.com with ESMTPSA id l25sm948834edb.49.2018.04.02.18.07.55 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Apr 2018 18:07:55 -0700 (PDT) Received: by mail-wm0-f46.google.com with SMTP id f125so30973568wme.4 for ; Mon, 02 Apr 2018 18:07:55 -0700 (PDT) X-Received: by 10.46.148.72 with SMTP id o8mr6987942ljh.74.1522717675268; Mon, 02 Apr 2018 18:07:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.129.90 with HTTP; Mon, 2 Apr 2018 18:07:34 -0700 (PDT) In-Reply-To: References: <5f663141-433c-951d-a350-7369b004415f@alvermark.net> <20180322225644.1480251c4547ce30f3d88de9@dec.sakura.ne.jp> <20180401213831.1535c7511c1d95a258318bc7@dec.sakura.ne.jp> From: Kyle Evans Date: Mon, 2 Apr 2018 20:07:34 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Call for Testing: UEFI Changes To: Zaphod Beeblebrox Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Apr 2018 01:13:39 -0000 On Mon, Apr 2, 2018 at 5:51 PM, Zaphod Beeblebrox wrote: > On Sun, Apr 1, 2018 at 7:41 PM, David NewHamlet > wrote: >> >> Fixed in: FreeBSD-12.0-CURRENT-amd64-20180329-r331740-disc1.iso >> >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176694 >> >> On Mon, Apr 2, 2018 at 12:38 AM, Tomoaki AOKI >> wrote: >> >> > 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 wrote: >> > >> > > On Thu, Mar 22, 2018 at 10:18 AM, Kyle Evans >> > > wrote: >> > > > On Thu, Mar 22, 2018 at 10:16 AM, Peter Lei >> > 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 >> > _______________________________________________ >> > 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" >> > >> _______________________________________________ >> 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" > > I've booted that image on my zbook 15. I show in the boot that I can > deliberately load efirt.ko ... and it doesn't help. I also show that I can > "type blind" after the system boots ... so everything but the screen is > working. > > In case you can't quite make it out, I hit right cursor twice (move to the > "live cd" choice) and hit enter. Then I type "root" enter and then "reboot" > ... That is interesting indeed... that's perhaps the polar opposite of what was being experienced before- it looks like it's setting a higher resolution but the firmware isn't actually putting it into the higher resolution. The firmware then lies to us about what resolution it's actually in, so we tell the kernel the wrong thing. You should be able to confirm this, as I recall, by bumping into the loader prompt and inspecting the output of `gop get`. That should report a higher resolution than it's actually in. > https://youtu.be/tlmaVJ-3aq0 > > (The rock sound track is just free audio to mask a barking dog and a radio > in the background.) > This was a most enjoyable soundtrack.