linux-kernel - Re: PCIe legacy interrupts blocked on Intel Apollo Lake platforms

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]

Message-ID: <CAHp75VfiE7Xi76d58adttQPnsP1OyHguhdUnQcU=Drd674qp=w@mail.gmail.com>
Date:   Wed, 18 Oct 2017 14:54:30 +0300
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Daniel Drake <drake@...lessm.com>
Cc:     Andy Shevchenko <andy@...radead.org>,
        "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
        LKML <linux-kernel@...r.kernel.org>,
        "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
        "x86@...nel.org" <x86@...nel.org>,
        QCA ath9k Development <ath9k-devel@....qualcomm.com>,
        Linux Upstreaming Team <linux@...lessm.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        AceLan Kao <acelan.kao@...onical.com>
Subject: Re: PCIe legacy interrupts blocked on Intel Apollo Lake platforms

On Wed, Oct 18, 2017 at 11:36 AM, Daniel Drake <drake@...lessm.com> wrote:
> [retitling and re-summarizing in hope of attention from Intel]
>
> Andy / Rafael,
>
> Thomas Gleixner suggested that you might be able to help with a nasty
> issue related to Intel Apollo Lake platforms - or you can put us in
> contact with another relevant person at Intel.

While Rafael is looking for a solution, can you in meantime gather the
following on the affected hardware and share it via some resource on
Internet?

1. % acpidump -o tables.dat # tables.dat is point of interest
2. % lspci -vv -nk # output of the command
3. % dmidecode # output of the command
4. % grep -H 15 /sys/bus/acpi/devices/*/status # output of the command
5. % dmesg # when kernel command line has the 'ignore_loglevel
initcall_debug' added

-- 
With Best Regards,
Andy Shevchenko