[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170525072010.GK8541@lahna.fi.intel.com>
Date: Thu, 25 May 2017 10:20:10 +0300
From: "mika.westerberg@...ux.intel.com" <mika.westerberg@...ux.intel.com>
To: "Jamet, Michael" <michael.jamet@...el.com>
Cc: "Mario.Limonciello@...l.com" <Mario.Limonciello@...l.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"andreas.noever@...il.com" <andreas.noever@...il.com>,
"Bernat, Yehezkel" <yehezkel.bernat@...el.com>,
"lukas@...ner.de" <lukas@...ner.de>,
"Levy, Amir (Jer)" <amir.jer.levy@...el.com>,
"luto@...nel.org" <luto@...nel.org>,
"Jared.Dominguez@...l.com" <Jared.Dominguez@...l.com>,
"andriy.shevchenko@...ux.intel.com"
<andriy.shevchenko@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 00/24] Thunderbolt security levels and NVM firmware
upgrade
On Wed, May 24, 2017 at 07:32:45PM +0000, Jamet, Michael wrote:
> I talked to our BIOS expert today. Here is his advice to debugging further:
>
> It looks like something may have been wrong from system (BIOS, FW, others...) perspective.
> On reboot need to enter EFI shell and check resources of
> pci 0000:01:00.0: bridge.
> At the EFI shell, this bridge MUST be either configured or absent.
>
> I would start this way, once we have this info, we may circle back to
> him and look into next debugging step.
Thanks, I'll try this today.
Powered by blists - more mailing lists