[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170522204836.GH8541@lahna.fi.intel.com>
Date: Mon, 22 May 2017 23:48:36 +0300
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Mario.Limonciello@...l.com
Cc: gregkh@...uxfoundation.org, andreas.noever@...il.com,
michael.jamet@...el.com, yehezkel.bernat@...el.com,
lukas@...ner.de, amir.jer.levy@...el.com, luto@...nel.org,
Jared.Dominguez@...l.com, andriy.shevchenko@...ux.intel.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/24] Thunderbolt security levels and NVM firmware
upgrade
On Mon, May 22, 2017 at 08:07:54PM +0000, Mario.Limonciello@...l.com wrote:
> I was 1 version behind, but I double checked with the latest version (1.1.15)
> and the same behavior exists on Linux (still works properly on Win10).
>
> If you have some more details about what the FW guys changed, I can check
> with my Dell FW team if they've picked up the same fix. I'm guessing it's not
> the same problem though considering it works properly on Win10?
Can you send me full dmesg preferably so that you have acpiphp.dyndbg in
the kernel command line (you also need to have CONFIG_DYNAMIC_DEBUG=y)?
It is possible that Windows does ACPI hotplug differently, for example
it could add some delay somewhere and that is enough for the firmware to
get the bridges initialized properly where as in Linux we only see the
bridge when it is in the middle of the initialization or so. When it
works properly Linux should see all the PCI bridges configured properly
by the BIOS SMI handler.
Powered by blists - more mailing lists