From: Borislav Petkov <bp@alien8.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bart Van Assche <bvanassche@acm.org>,
Jens Axboe <axboe@kernel.dk>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [GIT PULL] PCI changes for v4.20
Date: Tue, 13 Nov 2018 11:20:04 +0100 [thread overview]
Message-ID: <20181113102004.GC10502@zn.tnic> (raw)
In-Reply-To: <20181113071712.GA2353@gmail.com>
On Tue, Nov 13, 2018 at 08:17:12AM +0100, Ingo Molnar wrote:
>
> * Bjorn Helgaas <helgaas@kernel.org> wrote:
>
> > PCI changes:
> >
> > - Pay attention to device-specific _PXM node values (Jonathan Cameron)
>
> There's a new boot regression, my AMD ThreadRipper system (MSI X399 SLI
> PLUS (MS-7B09)) hangs during early bootup, and I have bisected it down to
> this commit:
>
> bad7dcd94f39: ACPI/PCI: Pay attention to device-specific _PXM node values
>
> Reverting it solves the hang.
>
> Unfortunately there's no console output when it hangs, even with
> earlyprintk. It just hangs after the "loading initrd" line.
>
> Config is an Ubuntu-ish config with PROVE_LOCKING=y and a few other debug
> options.
>
> All my other testsystems boot fine with similar configs, so it's probably
> something specific to this system.
Lemme add Tom, he might have an idea.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-11-13 10:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 17:39 [GIT PULL] PCI changes for v4.20 Bjorn Helgaas
2018-10-25 13:55 ` Linus Torvalds
2018-11-13 7:17 ` Ingo Molnar
2018-11-13 10:20 ` Borislav Petkov [this message]
2018-11-13 14:41 ` Lendacky, Thomas
2018-11-13 19:47 ` Lendacky, Thomas
2018-11-13 14:47 ` Bjorn Helgaas
2018-11-14 10:21 ` Ingo Molnar
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=20181113102004.GC10502@zn.tnic \
--to=bp@alien8.de \
--cc=Jonathan.Cameron@huawei.com \
--cc=a.p.zijlstra@chello.nl \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.