From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756184AbdESSB0 (ORCPT ); Fri, 19 May 2017 14:01:26 -0400 Received: from mga03.intel.com ([134.134.136.65]:35260 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755847AbdESSBV (ORCPT ); Fri, 19 May 2017 14:01:21 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.38,365,1491289200"; d="scan'208";a="859129571" Date: Fri, 19 May 2017 21:00:21 +0300 From: Mika Westerberg To: Mario.Limonciello@dell.com Cc: gregkh@linuxfoundation.org, andreas.noever@gmail.com, michael.jamet@intel.com, yehezkel.bernat@intel.com, lukas@wunner.de, amir.jer.levy@intel.com, luto@kernel.org, Jared.Dominguez@dell.com, andriy.shevchenko@linux.intel.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH 00/24] Thunderbolt security levels and NVM firmware upgrade Message-ID: <20170519180021.GH8541@lahna.fi.intel.com> References: <20170518143914.60902-1-mika.westerberg@linux.intel.com> <799e3a9d4d394d1eb9b9e742d81bd044@ausx13mpc120.AMER.DELL.COM> <20170519171948.GG8541@lahna.fi.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170519171948.GG8541@lahna.fi.intel.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 19, 2017 at 08:19:48PM +0300, Mika Westerberg wrote: > These two I've seen before. > > > [ 7.428503] pcieport 0000:02:02.0: PCI bridge to [bus 39] > > [ 7.428512] pcieport 0000:02:02.0: bridge window [mem 0xd9f00000-0xd9ffffff] > > [ 7.428519] pci_bus 0000:39: [bus 39] partially hidden behind bridge 0000:02 [bus 02-05] > > And this. > > It happens occasionally when you reboot the machine when a device is > connected but seems to be dependent on the BIOS version. Since it is the > BIOS who is supposed to enumerated these devices, I suspect that it is > either problem in BIOS or our PCI enumeration code does something wrong. I tried on Intel Skull Canyon NUC so that I downgraded the NVM firmware from 25 to 18. With that I see the exactly same issue. Upgrading it back to 25 seems to fix it. Even with version 18 if I plug devices after boot or if the machine is completely shut down from power button with devices connected, it works. The problem happens only when the machine is warn booted. However, since I'm able to reproduce this - I'll try to investigate what might be the root cause.