linux-kernel - Re: [GIT PULL] PCI changes for v4.20

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 13 Nov 2018 14:41:33 +0000
From:   "Lendacky, Thomas" <Thomas.Lendacky@....com>
To:     Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...nel.org>
CC:     Bjorn Helgaas <helgaas@...nel.org>,
        Jonathan Cameron <Jonathan.Cameron@...wei.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Bart Van Assche <bvanassche@....org>,
        Jens Axboe <axboe@...nel.dk>,
        Thomas Gleixner <tglx@...utronix.de>,
        Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [GIT PULL] PCI changes for v4.20

On 11/13/2018 04:20 AM, Borislav Petkov wrote:
> On Tue, Nov 13, 2018 at 08:17:12AM +0100, Ingo Molnar wrote:
>>
>> * Bjorn Helgaas <helgaas@...nel.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.

I'm not seeing any issues on my EPYC system.  Let me see if I can locate a
Threadripper system to test on.

It seems very strange that the commit in question would cause a hang so
early. Do you have a serial console hooked up for the earlyprintk? Is the
serial port set up in legacy mode (e.g. 0x3f8 as opposed to being an MMIO
device that would require a driver)?

Can you dump the ACPI tables / run them through iasl to see what the _PXM
values are in the DSDT table?

Thanks,
Tom

>