Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752171AbdGaMEm (ORCPT ); Mon, 31 Jul 2017 08:04:42 -0400 Received: from www.llwyncelyn.cymru ([82.70.14.225]:47858 "EHLO fuzix.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751935AbdGaMEl (ORCPT ); Mon, 31 Jul 2017 08:04:41 -0400 Date: Mon, 31 Jul 2017 13:04:35 +0100 From: Alan Cox To: Satoru Takeuchi Cc: LKML , x86@kernel.org Subject: Re: [FYI] GCC segfaults under heavy multithreaded compilation with AMD Ryzen Message-ID: <20170731130435.6cb4f00f@alans-desktop> In-Reply-To: References: Organization: Intel Corporation X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 955 Lines: 24 On Wed, 26 Jul 2017 06:54:01 +0900 Satoru Takeuchi wrote: > # I'm a LKML subscriber, but not a x86 list subscriber > > I found the following new linux kernel bugzilla about Ryzen related problem. > Since many developers don't check this bugzilla and I've also > encountered this problem, > I decided to introduce this problem here. Historically we've seen exactly these symptoms on all kinds of systems where the memory is at fault, even in cases where memtest86 passes. Whether there's a specific problem on some Ryzen boards is a question for AMD, but if I saw this without knowing the CPU I'd suspect memory firstly. GCC it turns out is by accident an amazingly effective memory testing tool. If it is memory corruption problems then no - the kernel cannot work around that level of hardware failure. The BIOS may be able to if it is a board or compatibility problem as memory tuning is usually done by the BIOS. Alan