From nobody Mon May 23 15:31:06 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 5929C1B55A05 for ; Mon, 23 May 2022 15:31:17 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4L6Ls00sjfz4hBg; Mon, 23 May 2022 15:31:15 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from kalamity.joker.local (123-1-111-80.area1b.commufa.jp [123.1.111.80]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 24NFV6FW063794; Tue, 24 May 2022 00:31:06 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Tue, 24 May 2022 00:31:06 +0900 From: Tomoaki AOKI To: Yasuhiro Kimura Cc: freebsd-stable@freebsd.org Subject: Re: Boot hangs up with Alderlake's intel GbE NIC Message-Id: <20220524003106.f29dccb9215d533c20326b36@dec.sakura.ne.jp> In-Reply-To: <20220523.164402.599295865361994545.yasu@FreeBSD.org> References: <20220523.164402.599295865361994545.yasu@FreeBSD.org> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) 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 X-Rspamd-Queue-Id: 4L6Ls00sjfz4hBg X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp X-Spamd-Result: default: False [-1.60 / 15.00]; RCVD_TLS_LAST(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[sakura.ne.jp]; AUTH_NA(1.00)[]; HAS_ORG_HEADER(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MLMMJ_DEST(0.00)[freebsd-stable]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[123.1.111.80:received] X-ThisMailContainsUnwantedMimeParts: N On Mon, 23 May 2022 16:44:02 +0900 (JST) Yasuhiro Kimura wrote: > Hello, > > 2 months ago I updated my home server to Intel Alderlake Core i3 12100 > and GIGABYTE H610I DDR4 (rev. 1.0) motherboard. > > The latter has onboard Intel GbE NIC. But unfortunately 13.0-RELEASE > doesn't detect it. So I inserted Intel PCI-E GbE adaptor to the PCI-E > slot of the motherbord and used it as network interface of the server. > > And now 13.1-RELEASE is released. I tried updating with > `freebsd-update update -r 13.1-RELEASE`, `freebsd install` and > `shutdown -r now`. But after that system hangs up in the middle of > boot. > > At first boot stops after onboard Intel GbE NIC is detected. > > https://people.freebsd.org/~yasu/Alderlake-GbE-boot-hangup.01.jpg > > It keeps about a minute and then boot process resumes. But soon it > stops again. > > https://people.freebsd.org/~yasu/Alderlake-GbE-boot-hangup.02.jpg > > I waited about 20 minites in this state but boot never go ahead. > > Removing PCE-E GbE adopter doesn't change the situation. > > I also tried boot image of 14.0-CURRENT 20220519 snapshot and boot > hangs up just same as 13.1-RELEASE. > > --- > Yasuhiro Kimura > Possibly not related (as it was P- E- core related complaint), if vm.pmap.pcid_enabled tunable is non-zero, does it change anything if you set it to 0 in /boot/loader.conf to disable pcid? In February, discussion about AlderLake CPU were in -current ML, starting from [1] and disabling pcid was proposed by kib@ at [2]. Looking sysctl descrintion, I "feel" this can affect P- core only AlderLake, too. % sysctl -d vm.pmap.pcid_enabled vm.pmap.pcid_enabled: Is TLB Context ID enabled ? For example, it was 1 on Intel(R) Core(TM) i7-8750H CPU (Coffee Lake) and on board Intel(R) I219-V CNP(7) is working as em0. FreeBSD 13.1-STABLE #460 stable/13-n250911-b92a06875045-dirty, amd64. So if I didn't miss any AlderLake-related commit, this would be 1 on AlderLake, too. [1] https://lists.freebsd.org/archives/freebsd-current/2022-February/001550.html [2] https://lists.freebsd.org/archives/freebsd-current/2022-February/001589.html -- Tomoaki AOKI