From: Bjorn Helgaas <firstname.lastname@example.org>
To: Meelis Roos <email@example.com>
Cc: Bjorn Helgaas <firstname.lastname@example.org>,
Linux Kernel Mailing List <email@example.com>,
Subject: Re: HP DL585 warm boot fail (old)
Date: Wed, 24 Oct 2018 11:34:22 -0500 [thread overview]
Message-ID: <20181024163422.GB214775@bhelgaas-glaptop.roam.corp.google.com> (raw)
On Wed, Oct 24, 2018 at 05:47:17PM +0300, Meelis Roos wrote:
> > 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
> Thank you. Unfortunately it does not change anything noticable.
Do you see the "disabling NMI on error" message?
Can you boot with "pci=earlydump vga=0xf07" and capture the output?
Drop the "vga=0xf07" if it doesn't work or makes the screen
> > I'm not sure why this would be only an intermittent problem, but at
> > least we can see if this is related.
> It seems 4.19 and current git are 100% reproducers so far - I have
> not managed to successfully boot either of them yet. I have seen
> 4.19-rc1 era git kernel booting at least once.
> I noticed that Debian packaged 4.17 with initramfs worked fine so
> far for my test, from these I have in grub menu. My selfcompiled
> kernels do not use initramfs.
It seems like the hang happens long before we would do anything with
an initramfs, but maybe there's a timing or memory map issue. It
seems like a hassle to pursue this angle, but if we can't figure it
out otherwise, maybe we'll have to.
next prev parent reply other threads:[~2018-10-24 16:34 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
2018-10-24 14:47 ` HP " Meelis Roos
2018-10-24 16:34 ` Bjorn Helgaas [this message]
2018-10-25 14:40 ` Meelis Roos
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).