[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFxCSWCG7ZvHW3AkLPzMPMAuG1BhL8fNgC0-JPYU4LZVow@mail.gmail.com>
Date: Fri, 5 Jan 2018 16:00:25 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Aaro Koskinen <aaro.koskinen@....fi>
Cc: Christian König <christian.koenig@....com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [BISECTED] v4.15-rc: Boot regression on x86_64/AMD
On Fri, Jan 5, 2018 at 2:04 PM, Aaro Koskinen <aaro.koskinen@....fi> wrote:
>
> After v4.14, I've been unable to boot my AMD compilation box with the
> v4.15-rc mainline Linux. It just ends up in a silent reboot loop.
>
> I bisected this to:
>
> commit fa564ad9636651fd11ec2c79c48dee844066f73a
> Author: Christian König <christian.koenig@....com>
> Date: Tue Oct 24 14:40:29 2017 -0500
>
> x86/PCI: Enable a 64bit BAR on AMD Family 15h (Models 00-1f, 30-3f, 60-7f)
Hmm. That was reported to break boot earlier already.
The breakage was supposedly fixed by three patches from Christian:
a19e2696135e: "x86/PCI: Only enable a 64bit BAR on single-socket AMD
Family 15h"
470195f82e4e: "x86/PCI: Fix infinite loop in search for 64bit BAR placement"
and a third one that was apparently never applied.
I'm not sure why that third patch was never applied, I'm including it here.
Does the system work for you if you apply that patch (instead of
reverting all of them)?
I wonder why that patch wasn't applied, but if it doesn't fix things,
I think we do need to revert it all.
Christian? Bjorn?
Linus
View attachment "0003-x86-PCI-limit-the-size-of-the-64bit-BAR-to-256GB.patch" of type "text/x-patch" (1192 bytes)
Powered by blists - more mailing lists