Date: Sat, 24 Aug 2019 17:49:39 -0600 From: Rebecca Cran <rebecca@bsdio.com> To: Konstantin Belousov <kostikbel@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Panic on boot with r351461 (AMD ThreadRipper 2990WX) Message-ID: <3679b417-4c1c-440f-1747-f0ff5cfb5d49@bsdio.com> In-Reply-To: <20190824230801.GK71821@kib.kiev.ua> References: <6e5687b2-ab3f-a570-37ab-72c8a9776167@bsdio.com> <20190824203305.GF71821@kib.kiev.ua> <d7200dbc-62b3-fd86-ca61-32d559987338@bsdio.com> <20190824230801.GK71821@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-08-24 17:08, Konstantin Belousov wrote: > > Do you happen to have NUMA node without any local memory ? (Look at the > SRAT table). If yes, try this patch. I've just remembered, that's one of the big differences between ThreadRipper and EPYC: the EPYC has memory links on all four dies, while the ThreadRipper 2990WX only has links on half. From https://www.anandtech.com/show/13124/the-amd-threadripper-2990wx-and-2950x-review/15 "With the new processors, we have the situation on the right, where only some cores are directly attached to memory, and others are not. In order to go from one of these cores to main memory, it requires an extra hop, which adds latency. When all the cores are requesting access, this causes congestion." -- Rebecca Cran
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3679b417-4c1c-440f-1747-f0ff5cfb5d49>