Date: Tue, 24 May 2022 01:34:40 +0900 (JST) From: Yasuhiro Kimura <yasu@FreeBSD.org> To: freebsd-stable@freebsd.org Subject: Re: Boot hangs up with Alderlake's intel GbE NIC Message-ID: <20220524.013440.566321238952738651.yasu@FreeBSD.org> In-Reply-To: <20220524003106.f29dccb9215d533c20326b36@dec.sakura.ne.jp> References: <20220523.164402.599295865361994545.yasu@FreeBSD.org> <20220524003106.f29dccb9215d533c20326b36@dec.sakura.ne.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> Subject: Re: Boot hangs up with Alderlake's intel GbE NIC Date: Tue, 24 May 2022 00:31:06 +0900 > 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 <junchoon@dec.sakura.ne.jp> > On OK prompt I typed 'set vm.pmap.pcid_enabled=0' and then 'boot'. But boot still hangs up with just same way. --- Yasuhiro Kimura
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220524.013440.566321238952738651.yasu>