From nobody Thu Mar 7 23:49:53 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TrQyf5ZCqz5CLPx for ; Thu, 7 Mar 2024 23:50:02 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from aws.ambrisko.com (aws.ambrisko.com [100.20.204.14]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "ambrisko.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TrQyf2kg4z469c for ; Thu, 7 Mar 2024 23:50:02 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Authentication-Results: mx1.freebsd.org; none Received: from ambrisko.com (localhost [127.0.0.1]) by aws.ambrisko.com (8.17.2/8.17.2) with ESMTPS id 427Nnslm024936 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 7 Mar 2024 15:49:54 -0800 (PST) (envelope-from ambrisko@ambrisko.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ambrisko.com; s=default; t=1709855394; bh=uqwmsr/TU5C14jh03sI/Xmyd2FkahRvJukpV0O1OK4E=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=XCvY+74+Qh4IL8IoOfo13YtLjnb6gYM9K5ETatggd8DGcqKzfxpIEwBjqB75QlJjX S1g9HJtAoWl1aILM6n0RsOEz2wmPKH6ACkzqvXb8fa0Re3w9fPSBrPtUcuAgY9WpTG 7TLPDadzX2qNq2Ow5KcDNz0Nn5aLimCXlOoot03s= X-Authentication-Warning: aws.ambrisko.com: Host localhost [127.0.0.1] claimed to be ambrisko.com Received: (from ambrisko@localhost) by ambrisko.com (8.17.2/8.17.2/Submit) id 427NnrMb024935; Thu, 7 Mar 2024 15:49:53 -0800 (PST) (envelope-from ambrisko) Date: Thu, 7 Mar 2024 15:49:53 -0800 From: Doug Ambrisko To: Philipp Ost Cc: current@freebsd.org, Klaus-Dieter Ost Subject: Re: Unable to boot -CURRENT on Thinkpad P16s G2 Message-ID: References: <283774ec-156b-4bc8-850d-261ea0e0ed07@smo.de> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <283774ec-156b-4bc8-850d-261ea0e0ed07@smo.de> X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16509, ipnet:100.20.0.0/14, country:US] X-Rspamd-Queue-Id: 4TrQyf2kg4z469c On Thu, Mar 07, 2024 at 07:15:48PM +0100, Philipp Ost wrote: | On 2/28/24 21:10, Philipp Ost wrote: | [boot log stripped] | > Does anyone have any suggestions on how to proceed at this point? [...] | | Short follow-up: disabling uart0 and uart1 at the loader prompt allowed us | to boot and install FreeBSD (the -CURRENT snapshot from 2024-02-29 in case | it matters). UARTS on AMD can be a bit different. Some BIOS implementations seem to set them up to work like legacy ports others do not. On a Naples platform I helped add support for them since they were not setup in the legacy configuration. The AMD servers I'm using now have them setup in legacy mode and just work like on other systems. If I remember right those UARTS were defined in ACPI. On a laptop they probably don't have serial ports and the probe is getting stuck on something. It might be good to instrument it to see what. Thanks, Doug A.