From nobody Mon May 23 16:31:31 2022 X-Original-To: freebsd-stable@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 2941F1B346F6 for ; Mon, 23 May 2022 16:35:24 +0000 (UTC) (envelope-from yasu@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4L6NGz6cRWz4swk; Mon, 23 May 2022 16:35:23 +0000 (UTC) (envelope-from yasu@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1653323723; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=lcSv8s3WL1RSa6rBFYyxw4o8/3bMbgONvx7lJg8ZZdY=; b=O1S7C3hsNCpyoGETydMu9Ic3YEuKzy9aDL/54oP4hBqaOGRGYXRyKV02RHXbKPq/kOdhtO PNywZtTtf//QpPeyGqQHx8eL1caQ486wKoa8bOsNqsb/nG7O9Pg3CLBA2CJmG+LZcZb2DQ /O89JmRjfzmVx4mRmD5Yr9onw96QovkDLN92BAl+0IgHkfujMgvEV6Ggn2ivrFZB6ADaU1 iSonjRRDfDq0iE025EdTq557SiUAbJMgrWWgjlynIhzzf4Ow7dwcjY6uhjMDUxOU1Ccog/ bqK4Acc3Ib/dN0zpzrCScgm8m+T/RNAwr1OfQ+q+rtKoL/QHJed/n40qTV+5zg== Received: from localhost (unknown [IPv6:240b:11:220:fe00:b03b:aea:a90b:bc]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: yasu/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 34BBF24DDE; Mon, 23 May 2022 16:35:23 +0000 (UTC) (envelope-from yasu@FreeBSD.org) Date: Tue, 24 May 2022 01:31:31 +0900 (JST) Message-Id: <20220524.013131.515312503672800488.yasu@FreeBSD.org> To: freebsd-stable@freebsd.org Subject: Re: Boot hangs up with Alderlake's intel GbE NIC From: Yasuhiro Kimura In-Reply-To: References: <20220523.164402.599295865361994545.yasu@FreeBSD.org> X-Mailer: Mew version 6.8 on Emacs 29.0.50 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1653323723; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=lcSv8s3WL1RSa6rBFYyxw4o8/3bMbgONvx7lJg8ZZdY=; b=tw+PXZk7E+rL5uno7j33NDWA0ctIMHFdg2LOC/of40k0ZgUVC1/1pluFb8L1F82Dzwg49z Twubey6j2QNcM55edW6uIPt5BJCrUfpm80R+FI5398tcNaX6+fuDQipXJBd8QOm+X+LiRQ DfFgTIRjrr9lGARmBA6zbQyHPFQu5Q9qpbgA/A0Q4wj9mA4bZb9Q2I94D2a0aL77oXb1mE t2Lwb12a6VQ33R/t6TkRIwWaPMwOFLI4fTCFryIdyC86ipYGiUZs/qZC1bp9SWjXehoG/M CCfIXtuf1Php96rAueQdSVUflSnV7T79E8J7GlapyKrMOBxlOFMVXMEPlRTf4g== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1653323723; a=rsa-sha256; cv=none; b=is/sg7sWs/tUENc2BFdaV137ht7oUt2D1QJVJ5NWnlMOq+fuRGvUQsRkJeBQgiPwUTIaoq 4NO3omRlfsYHjcY2lP0o9qXrVPymp4PyGcKjAGxI7S436+WTBNNhMlvh7z5A14hAqrMSfU qR+jDbF0Gq3uC+zF5LGrZXVyssu3tGr/pCD33/tkIJo2iAK0vqS3hCurFYhPmMs8odFzdq /FjeJ4UK/jOqPduezHO+LsP9QzARQYga4exvnmUJhQEocRO+j+4xWFqUqhkuyimLmu7N3x dJLwLD8nlOM63AwUzw9fUaiFZNEQwFHO9uC7V4TG0KPnAQT1k3jp7RwVl075wA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N From: Jonathan Vasquez Subject: Re: Boot hangs up with Alderlake's intel GbE NIC Date: Mon, 23 May 2022 11:41:48 +0000 > Hey yasu, > > I haven't looked into this but if there is a way you can disable the Intel nic's driver from loading (maybe > like this since it's early boot): > https://forums.freebsd.org/threads/how-to-boot-with-messed-up-boot-loader-conf.64019/post-371681 > > That way you can at least get in and do further troubleshooting. You'll need another way to get internet > though, or maybe you can load the module manually post boot and see what happens. On OK prompt I typed 'disable-module em' and them 'boot'. But onboard NIS is still ditected as 'em1'. Did I do something wroing? --- Yasuhiro Kimura