Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 52D56C433B4 for ; Sat, 8 May 2021 14:33:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1B6B36140F for ; Sat, 8 May 2021 14:33:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229559AbhEHOea (ORCPT ); Sat, 8 May 2021 10:34:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60432 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229500AbhEHOea (ORCPT ); Sat, 8 May 2021 10:34:30 -0400 Received: from mail.skyhub.de (mail.skyhub.de [IPv6:2a01:4f8:190:11c2::b:1457]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C6472C061574 for ; Sat, 8 May 2021 07:33:28 -0700 (PDT) Received: from zn.tnic (p200300ec2f1c5300aeec222591b28502.dip0.t-ipconnect.de [IPv6:2003:ec:2f1c:5300:aeec:2225:91b2:8502]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id CA7011EC047F; Sat, 8 May 2021 16:33:25 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1620484405; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=L7RlPNfIo6n+0Rz/6M2EkUySHWS8IV9BUg50l99rBQg=; b=BNuJgciceD3iEqsE65sn+voaca2IlKBUSCh+1cJ0AmJhEu1WyUGZVsHl869BverZqNbkk/ /YHxQMR+AVWT1Zjs4eGKWbutlqWWNianQAGq71J638TcEGccBNGvVJBGLUQlvY8u8LnkOd Nz+pNiABPLup4ukPGxosHunYalkL0/k= Date: Sat, 8 May 2021 16:33:23 +0200 From: Borislav Petkov To: Lv Ying Cc: tony.luck@intel.com, linux-edac@vger.kernel.org, fanwentao@huawei.com Subject: Re: [RFC PATCH] x86/mce/inject: Fix printk deadlock causing mce_timed_out panic Message-ID: References: <20210509053229.GA2477949@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20210509053229.GA2477949@localhost.localdomain> Precedence: bulk List-ID: X-Mailing-List: linux-edac@vger.kernel.org On Sun, May 09, 2021 at 01:32:29PM +0800, Lv Ying wrote: > The mce-inject SRAO broadcast error injection on 4-core CPU caused mce_timed_out > panic as following: > Kernel panic - not syncing: Timeout: Not all CPUs entered broadcast exception handler A couple of things: - how exactly do you do that injection, please give exact steps - on which kernel, dmesg, .config etc - anything specific about the hardware you're using - always Cc lkml on patches. Thx. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette