Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752570AbeAJXNC (ORCPT + 1 other); Wed, 10 Jan 2018 18:13:02 -0500 Received: from mail.skyhub.de ([5.9.137.197]:40500 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751607AbeAJXNB (ORCPT ); Wed, 10 Jan 2018 18:13:01 -0500 Date: Thu, 11 Jan 2018 00:12:35 +0100 From: Borislav Petkov To: Gabriel C Cc: linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: EDAC-AMD64: what is the ecc_msg good for ? Message-ID: <20180110231235.a3ts353lzajqywb5@pd.tnic> References: <5dea4184-8782-7b57-2624-2957c91fe4ac@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <5dea4184-8782-7b57-2624-2957c91fe4ac@gmail.com> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Thu, Jan 11, 2018 at 12:06:49AM +0100, Gabriel C wrote: > while doing some testings with a EPYC box I notice > these strange messages when a Node is disabled. > > I really do think the message is confusing since > we tell 'Node X: ... disabled' followed by a > INFO on the edac driver which tells the driver will not load. And that is confusing because? > Also even worse , we suggest to use ecc_enable_override then, > which can cause wrose things.. We really should not suggest > something like this by default. That is an remnant from the old times. Family 0x17 and newer doesn't allow that anymore. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.