archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <>
To: Meelis Roos <>
Cc: Linux Kernel Mailing List <>,
Subject: Re: HH DL585 warm boot fail (old)
Date: Mon, 9 Jul 2018 08:38:07 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Jul 6, 2018 at 2:13 PM Meelis Roos <> wrote:
> I have a first gen HP Proliant DL585 ("G1" but the name was not used
> back then) that boots up fine from poweron but usually fails bootup from
> warm reboot, somewhere in PCI detection (will try to photographs the
> screen some time).
> I just stumbled upon an old OpenSolaris thead about the same DL585 and
> same symptoms:
> Their conclusion was the wfollowing and they seem to have found a fix
> (although I have not tested any version of Solaris on this DL585
> myself):
> "The hang is caused when, during PCI enumeration, a PCI-PCI bridge is
> partially disabled when the PCI command register bits which enable IO
> and memory windows are cleared."
> Is this information useful in some way for debugging it?
> What else besides screenshot of the can be useful in debugging?

Would you mind opening a report at  I'm
not sure if anybody will be able to do anything about this, but it's
always possible.

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.  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.


  reply	other threads:[~2018-07-09 13:38 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 [this message]
2018-10-24  7:47   ` Meelis Roos
2018-10-24 13:49     ` Bjorn Helgaas
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).