From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 12324 invoked from network); 19 Nov 2022 04:24:15 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 19 Nov 2022 04:24:15 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Received: from mail-pl1-f176.google.com ([209.85.214.176]) by 9front; Fri Nov 18 23:20:22 -0500 2022 Received: by mail-pl1-f176.google.com with SMTP id p21so6222727plr.7 for <9front@9front.org>; Fri, 18 Nov 2022 20:20:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mforney.org; s=google; h=user-agent:message-id:in-reply-to:references:from:subject:cc:to :date:from:to:cc:subject:date:message-id:reply-to; bh=huiwjfVKmScfDH2hcFiPBbW+91EclHanDC3ItJ29cqc=; b=MOzBA88gSaeHBpnV3usCdyZASb53KBw6ACsK5+5Ux3VWP/EqBbRuDhULd11rhM1NAx NkxygOmd8CqD2OE8Z0s2CDjzxuAvSN/nKvWKbN8Y+4j/7sLlsq3tt6bdo9b1gWhCSdOU 9MSi9eHWecyBVAUOFVNHqe1PGUEgD4rBhjFdcUu9c1LcSU6BAjcV8oOeIqQKtolQB6YF KXSbuAn/gOuLl93/JpnaFFU42lJilGLbDzSU5BKGtLHdkjxYDWjWmpdSbR/zLX7sAYtM gZW8sF0AKgN6nXeKgZEccEYgT2qCIUyAoggx1cdHR/kl096UQWA4r5xYgISgl1ZLiq+j DP6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=user-agent:message-id:in-reply-to:references:from:subject:cc:to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=huiwjfVKmScfDH2hcFiPBbW+91EclHanDC3ItJ29cqc=; b=HL4RHaByzPD/WFgcbI2ClEa+1JZ7Gv4LPzvYvK8rTzrjn98dnGKlZI16w5Wjhxexvj hJql5b9ARIsqxJ+EHjgxyW7LxfBrLddjyCuKu7+HIB8tlP09SL4Mv06z77dKCZAquwin 4JgettzhvnwyLQ+U+V3olkpcVP3zRjopDUarkonOyD9R2MXx1+vYusxYHcvfjuTRyv4u eY1ZxDY/ZXEpcVxxxG/hKhra78k47+wJSFEvmFQ+ZkGGOjZhiVfNXDOwCgWIkKU0Vw99 8x1NPzx/h0PG3ixL9dgfXMhZfOhhP3RDGKFJ+BABzZqhBJlvni0kQdy8FfWqrl14MgBe S65g== X-Gm-Message-State: ANoB5pn8s/t7dUSZpamkLm7/6LMOUwCcvWnxCcXWZLG67JCgr9YdfwAs 0u/D5sTNALujU/Qt8XIH/PPx5qhW5Md0+uezvrk= X-Google-Smtp-Source: AA0mqf467QHpxVxAez4Xh0q8y/uem3dFtMkvIDeJpUklT8DBnp18tAqae5wCq0zsE6wh5hoEzgstXg== X-Received: by 2002:a17:90a:7c4e:b0:218:985d:f914 with SMTP id e14-20020a17090a7c4e00b00218985df914mr1526372pjl.182.1668831618582; Fri, 18 Nov 2022 20:20:18 -0800 (PST) Return-Path: Received: from localhost ([2601:647:6400:20b0:cab2:9bff:fe88:d09c]) by smtp.gmail.com with ESMTPSA id u203-20020a6279d4000000b0056abfa74eddsm4115655pfc.147.2022.11.18.20.20.16 (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Fri, 18 Nov 2022 20:20:17 -0800 (PST) Date: Fri, 18 Nov 2022 20:20:15 -0800 To: 9front@9front.org Cc: akw@oneirism.org From: Michael Forney References: <4833AF9EC7D2CF63D5C30CC6057A1DA9@oneirism.org> In-Reply-To: <4833AF9EC7D2CF63D5C30CC6057A1DA9@oneirism.org> Message-Id: <3U1941GU6D3PQ.3T4BU9350MI49@mforney.org> User-Agent: mblaze/1.2 List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: immutable mobile grid-scale browser Subject: Re: [9front] Thinkpad T14 hung boot Reply-To: 9front@9front.org Precedence: bulk akw@oneirism.org wrote: > Has anyone else had any experience with the T14 (gen1), or maybe > similar, newer Ryzen based thinkpads? It always exhibits the > behavior as evidenced in the attachement. I can only boot from a > USB drive if I 'secure wipe' the NVME disk *and then* load the > UEFI to default settings, at which point I can install it as > normal, and then reboot back to the same problem (which "hangs" > indefinitely). I have tried most plan9.ini boot combinations > (*acpi=0, nousb options, and a select other few), but with no > success. I have also tried some combinations of UEFI settings, > but those also do not work. > > I am pretty certain it is something with this troublesome UEFI, > and was just wondering if anyone else had the same/similar issues? > > My uneducated guess is that it's related to the NVME disk, as it > is usually the next boot message there. I have the same laptop, and until recently it had been working fine with 9front. However, a little while ago I updated the BIOS and started having the same issue as you. I determined the hang was when aux/kbdfs tried to open /dev/scancode, since devsd's walk function calls nvmeenable, and sdnvme doesn't detect device errors during initialization and waits indefinitely for the identify command to complete. The device error was caused (as cinap predicted) by the IOMMU being enabled, and blocking the device's attempts to access memory. This prevented it from completing the identify command. The root cause (as you predicted) was the UEFI being overly strict about GetMemoryMap and ExitBootServices, and requiring that the MapKey we pass to ExitBootServices be obtained *immediately* before the call. To get this working, you can build a new bootx64.efi with the patch posted to this list a few days ago (not committed yet, we are still working out some stylistic things). Or, you can use some multiboot loader (like grub) to load the kernel instead. Using multiboot requires a very recent kernel to fix multiboot with a 64-bit framebuffer address.