From: Bjorn Helgaas <helgaas@kernel.org>
To: "Bao, Joseph" <joseph.bao@intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Stuart Hayes <stuart.w.hayes@gmail.com>,
Lukas Wunner <lukas@wunner.de>
Subject: Re: HW power fault defect cause system hang on kernel 5.4.y
Date: Tue, 9 Nov 2021 09:29:51 -0600 [thread overview]
Message-ID: <20211109152951.GA1146992@bhelgaas> (raw)
In-Reply-To: <DM8PR11MB570219FE94A7983E0F61A3BA86929@DM8PR11MB5702.namprd11.prod.outlook.com>
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
next prev parent reply other threads:[~2021-11-09 15:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 3:45 HW power fault defect cause system hang on kernel 5.4.y Bao, Joseph
2021-11-02 22:34 ` Bjorn Helgaas
2021-11-09 7:59 ` Bao, Joseph
2021-11-09 15:29 ` Bjorn Helgaas [this message]
2021-11-11 2:16 ` Bao, Joseph
2021-11-12 0:44 ` Krzysztof Wilczyński
2021-11-12 1:47 ` Bao, Joseph
2021-11-12 1:49 ` Krzysztof Wilczyński
2021-11-09 15:36 ` stuart hayes
2021-11-10 9:20 ` Bao, Joseph
2021-11-10 15:56 ` stuart hayes
2021-11-11 1:03 ` Bao, Joseph
2021-11-15 19:27 ` Lukas Wunner
2021-11-16 2:42 ` Bao, Joseph
2021-11-17 8:00 ` Lukas Wunner
2021-11-17 21:43 ` Bjorn Helgaas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211109152951.GA1146992@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=joseph.bao@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=stuart.w.hayes@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).