From: Bjorn Helgaas <helgaas@kernel.org>
To: Meelis Roos <mroos@linux.ee>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org
Subject: Re: HH DL585 warm boot fail (old)
Date: Wed, 24 Oct 2018 08:49:47 -0500 [thread overview]
Message-ID: <20181024134946.GA214775@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <b36c537a-90ee-c474-9efa-df2ead8e0376@linux.ee>
On Wed, Oct 24, 2018 at 10:47:24AM +0300, Meelis Roos wrote:
> > Would you mind opening a report at https://bugzilla.kernel.org? I'm
> > not sure if anybody will be able to do anything about this, but it's
> > always possible.
>
> Submitted now, https://bugzilla.kernel.org/show_bug.cgi?id=201503
>
> > A complete dmesg log and "sudo lspci -vv" output from a successful
> > boot would be a good start. And if you have a screenshot of the
> > failure, that would help, too. You can use the "ignore_loglevel"
> > kernel parameter to make sure we see everything on the console.
>
> Added.
>
> > Does this machine have an iLO? If so, it may have logs that
> > could be useful if this is related to some sort of bus error.
>
> Nothing in the ILO logs.
Great, thanks!
Can you try the patch below? This is extracted from the code here:
https://github.com/joyent/illumos-joyent/blob/b6a0b04d591f5b877cfe05f45e81f0e8a5cfc2b3/usr/src/uts/intel/io/pci/pci_boot.c#L1805
I'm not sure why this would be only an intermittent problem, but at
least we can see if this is related.
diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
index 6bc27b7fd452..842f900ed194 100644
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
@@ -5113,3 +5113,15 @@ DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_MICROSEMI, 0x8575,
quirk_switchtec_ntb_dma_alias);
DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_MICROSEMI, 0x8576,
quirk_switchtec_ntb_dma_alias);
+
+static void quirk_amd_8111(struct pci_dev *pdev)
+{
+ u8 ioc;
+
+ pci_read_config_byte(pdev, 0x40, &ioc);
+ if (ioc & 0x80) {
+ pci_info(pdev, "disabling NMI on error\n");
+ pci_write_config_byte(pdev, 0x40, ioc & ~0x80);
+ }
+}
+DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x7468, quirk_amd_8111);
next prev parent reply other threads:[~2018-10-24 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 19:12 HH DL585 warm boot fail (old) Meelis Roos
2018-07-09 13:38 ` Bjorn Helgaas
2018-10-24 7:47 ` Meelis Roos
2018-10-24 13:49 ` Bjorn Helgaas [this message]
2018-10-24 14:47 ` HP " Meelis Roos
2018-10-24 16:34 ` Bjorn Helgaas
2018-10-25 14:40 ` Meelis Roos
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=20181024134946.GA214775@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mroos@linux.ee \
/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).