From owner-freebsd-current@freebsd.org Thu Mar 22 20:09:43 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 8CAC7F67524 for ; Thu, 22 Mar 2018 20:09:43 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-lf0-f53.google.com (mail-lf0-f53.google.com [209.85.215.53]) (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 EEE1D68FF6 for ; Thu, 22 Mar 2018 20:09:42 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-lf0-f53.google.com with SMTP id x205-v6so15059391lfa.0 for ; Thu, 22 Mar 2018 13:09:42 -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=Sk58a/O4up+eSCX+himeXM+3mg+KDOH0N64ir+MLF/A=; b=j6wGAsjeoSxI5vWUKYaUgGN0TnqX4yNhhaLDWHL0Rv5cnCEmX9F0D1T1jZ+J3Ce35j s79NzekH8BehuxseXbSsyCtBmUA/l6tn/D0gQBn5uBPjv0kTU9GYXnqUioc26s/jMSe2 sIYRFiEWWri+XuqxfjzZ4CKrjXDGIUiYRWlmnl0xzw6qn2mymGxIa8Cm3ZIc7amA9wKe BYHCJMelyR/nizlQ9hlqDlKrsmgIo/jGpAE775Iv025HxYA7f5HZHOW5tgTG1w6kRB7X T0rtqnGtPpn2AsCEkCrGttgCRy3X8TwNeG4M08TIu2GsCvtj3F89pGTO43698MZKOZeg GW9w== X-Gm-Message-State: AElRT7GRSWx0oGQiwu/8L0dqYy3t5MU6VLORutELqM13Dwxtxl7Mc5FF XA9Dy2bUfAsaj0nUoIrUOxrrz9KXFLo= X-Google-Smtp-Source: AG47ELvVEtcLXcy7ZqsMOT0iJfh/SCS/U5Crda1m+qz1rLK11BgHcjh0u5+aHjEYBtMidXl7MdGwcA== X-Received: by 10.46.128.132 with SMTP id i4mr11508722ljg.51.1521749380714; Thu, 22 Mar 2018 13:09:40 -0700 (PDT) Received: from mail-lf0-f46.google.com (mail-lf0-f46.google.com. [209.85.215.46]) by smtp.gmail.com with ESMTPSA id u15sm1533901ljj.9.2018.03.22.13.09.40 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Mar 2018 13:09:40 -0700 (PDT) Received: by mail-lf0-f46.google.com with SMTP id c78-v6so10367189lfh.1 for ; Thu, 22 Mar 2018 13:09:40 -0700 (PDT) X-Received: by 2002:a19:9e95:: with SMTP id h143-v6mr18556614lfe.129.1521749380282; Thu, 22 Mar 2018 13:09:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.129.90 with HTTP; Thu, 22 Mar 2018 13:09:19 -0700 (PDT) In-Reply-To: <02f4f83b-7cbc-feff-8858-87570c58640c@gmail.com> References: <02f4f83b-7cbc-feff-8858-87570c58640c@gmail.com> From: Kyle Evans Date: Thu, 22 Mar 2018 15:09:19 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Call for Testing: UEFI Changes To: Renato Botelho 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: Thu, 22 Mar 2018 20:09:43 -0000 On Thu, Mar 22, 2018 at 11:56 AM, Renato Botelho wrote: > On 21/03/18 21:45, Kyle Evans wrote: >> Hello! >> >> A number of changes have gone in recently pertaining to UEFI booting >> and UEFI runtime services. The changes with the most damaging >> potential are: >> >> We now put UEFI runtime services into virtual address mode, fixing >> runtime services with U-Boot/UEFI as well as the firmware >> implementation in many Lenovos. The previously observed behavior was a >> kernel panic upon invocation of efibootmgr/efivar, or a kernel panic >> just loading efirt.ko or compiling EFIRT into the kernel. >> >> Graphics mode selection is now done differently to avoid regression >> caused by r327058 while still achieving the same effect. The observed >> regression was that the kernel would usually end up drawing >> incorrectly at the old resolution on a subset of the screen, due to >> incorrect framebuffer information. >> >> Explicit testing of these changes, the latest of which happened in >> r331326, and any feedback from this testing would be greatly >> appreciated. Testing should be done with either `options EFIRT` in >> your kernel config or efirt.ko loaded along with updated bootloader >> bits. >> >> I otherwise plan to MFC commits involved with the above-mentioned >> changes by sometime in the first week of April, likely no earlier than >> two (2) weeks from now on April 4th. > > Just FYI, > > After upgrade to r331350 on a Thinkpad X230 using drm-next-kmod > trackpoint stopped working and touchpad worked but 3 buttons above it > didn't. Removing drm-next-kmod and start using i915kms.ko from > /boot/kernel fixed it. > I tend to think that's probably unrelated to the things I've poked- I can't quite imagine how I might have broken it =/. Any chance you can bissect that to the exact commit? Thanks! Kyle Evans