Received: by 2002:a05:6a10:8395:0:0:0:0 with SMTP id n21csp602576pxh; Tue, 9 Nov 2021 16:01:31 -0800 (PST) X-Google-Smtp-Source: ABdhPJxtjqYsMMKveztljQqumf0ttORCqhBQIKIzkzh/hCxmiuM++S8PCtZsFm9Y+/PLeil4/VYv X-Received: by 2002:a05:6e02:1b01:: with SMTP id i1mr8049345ilv.53.1636502491513; Tue, 09 Nov 2021 16:01:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1636502491; cv=none; d=google.com; s=arc-20160816; b=FNdpUx6IXND5if6FVYbyMojNNj0taKz3U399MkG/dVE3RWnEWPAONMU/nkYicNt7/e lLylUFk16flU5v0jBP5CLBES751N1Kd70NcRGF/Vld74ECuyXhgZFgZoGsNGIw+Iz+hp MSNrDXap/wYiRQ6pQ6/W3/Cg6POfpg+gOsHA3xQrxv/y+RwnNGWgA5GqamSWsbI3THyz zPM973gV6Bg0kWOnIJprH1jFYWLa0HXkYDy174V/eTVe4HO9qYG5t7wObcTPOIsDpd3N ieUpqjK89AztUj4b8EcC70WlXl7YHXzT4mcIVBr/UMevgTCr31y5bjU4TYzHGuic05zT l23g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :message-id:subject:cc:to:from:date:dkim-signature; bh=Xa6+0ik7rlr3XnSAVhKT2o91LthKH2xIuD6maF1wBnA=; b=Vx5K7jNHOTiRMZqkUKTpPsvygkGiFCSu0SggEPxouOyWwj/z3mizwo144mpK9b0tny kDCU/2iZ2tys4unMaX6RrWXocCf+eSZO05rxR7K3/Kg8MCzfCVH6DW4eaEz83J8KRP/X QqcTSixim2lE2+OW8VVDMfQBbDuhuh4T1UR1G01lydwnUkqZMBpQyUgC9uG3VH+FND5n o7ezn6yBuUmFZ67CFvB87gPxT5gD0XrZO9miudJwjR1CjUkh/5z74AlSFLfIHhZ3pDBQ oOiOcLALpLmRaQzvWm3e6kHmMPSRfdAaMSREo8B8DP4+L8W2ioLSX4oqg4+b3y29U9kT UM1A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=a7zUzYaP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id x12si41582413ill.167.2021.11.09.16.01.19; Tue, 09 Nov 2021 16:01:31 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=a7zUzYaP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236715AbhKIPcj (ORCPT + 97 others); Tue, 9 Nov 2021 10:32:39 -0500 Received: from mail.kernel.org ([198.145.29.99]:39368 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236677AbhKIPcj (ORCPT ); Tue, 9 Nov 2021 10:32:39 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id B23DE611CA; Tue, 9 Nov 2021 15:29:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1636471793; bh=eJtozRUR5h8pluy5NEdrhAqmDhEU6q84/t9GV3y8+1o=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=a7zUzYaPODFM1y4fYyQAX3RlfgrpmzTGX192L/0wnwqk9aB6vyh2QymVPvfHDdHPL jFeDvjcuV4qTmreOw3AFSF+KfJ9TtPoRgRI4Mro/O+9z1Ja79lEDwlw5Axk0Sspmde xBnJ9PFm28H6b2u0T8q0SqUA8zexRsdlvKfBRB3BAwfPBxvGbJbNrQutXL9c5QlyDp 9/DViqZAqJ9Eu7Jy8lOHyq2G9VMV0s/Ra3+S6iT2oTkTvC5kH2H1kYiO5CgzGH8J/W tZYYpozOPDVHX/eII/KW06djWDzwQuSfRJnMGBtcSmBJZJI0vEcBmfpkJHK5ssShGq CzWyqu1tBec3g== Date: Tue, 9 Nov 2021 09:29:51 -0600 From: Bjorn Helgaas To: "Bao, Joseph" Cc: Bjorn Helgaas , "linux-pci@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Stuart Hayes , Lukas Wunner Subject: Re: HW power fault defect cause system hang on kernel 5.4.y Message-ID: <20211109152951.GA1146992@bhelgaas> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 09, 2021 at 07:59:59AM +0000, Bao, Joseph wrote: > Hi Lukas/Stuart, > Want to follow up with you whether the system hang is expected when > HW has a defect keeping PCI_EXP_SLTSTA_PFD always HIGH. A system hang in response to a hardware defect like this is never the expected situation. Worst case we should be able to work around it with a quirk. Far better would be a generic fix that could recognize and deal with the situation even without a quirk. But I don't know the fix yet. I'm just responding to encourage you to keep pestering us and not give up :) In the meantime, it might be worth opening a report at https://bugzilla.kernel.org with a description of how you trigger the problem, and attaching the complete dmesg log and "sudo lspci -vv" output. Bjorn