All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
	"Liang, Kan" <kan.liang@linux.intel.com>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"hdegoede@redhat.com" <hdegoede@redhat.com>,
	"kernelorg@undead.fr" <kernelorg@undead.fr>,
	"kjhambrick@gmail.com" <kjhambrick@gmail.com>,
	"2lprbe78@duck.com" <2lprbe78@duck.com>,
	"nicholas.johnson-opensource@outlook.com.au" 
	<nicholas.johnson-opensource@outlook.com.au>,
	"benoitg@coeus.ca" <benoitg@coeus.ca>,
	"mika.westerberg@linux.intel.com"
	<mika.westerberg@linux.intel.com>,
	"wse@tuxedocomputers.com" <wse@tuxedocomputers.com>,
	"mumblingdrunkard@protonmail.com"
	<mumblingdrunkard@protonmail.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Box, David E" <david.e.box@intel.com>,
	"Sun, Yunying" <yunying.sun@intel.com>,
	"Jiang, Dave" <dave.jiang@intel.com>
Subject: Re: Bug report: the extended PCI config space is missed with 6.2-rc2
Date: Fri, 6 Jan 2023 11:33:41 -0600	[thread overview]
Message-ID: <20230106173341.GA1234930@bhelgaas> (raw)
In-Reply-To: <20230106004744.GA1186792@bhelgaas>

On Thu, Jan 05, 2023 at 06:47:44PM -0600, Bjorn Helgaas wrote:
> On Fri, Jan 06, 2023 at 12:22:09AM +0000, Luck, Tony wrote:
> > > ...and Dave, who reported that CXL enumeration was busted in -rc2, says
> > > this patch fixes that. So you can also add:
> > >
> > > Tested-by: Dave Jiang <dave.jiang@intel.com>
> > 
> > Also seems good for my Broadwell/EDAC system.
> > 
> > Boot messages mentioning MMCONFIG are:
> > 
> > $ dmesg | grep MMCONFIG
> > PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
> > PCI: not using MMCONFIG
> > PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
> > PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in ACPI motherboard resources or EFI
> 
> This part looks ok.
> 
> > PCI: MMCONFIG for 0000 [bus00-7f] at [mem 0x80000000-0x87ffffff] (base 0x80000000) (size reduced!)
> > acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended configuration space under this bridge
> > acpi PNP0A03:01: fail to add MMCONFIG information, can't access extended configuration space under this bridge
> > acpi PNP0A08:02: fail to add MMCONFIG information, can't access extended configuration space under this bridge
> > acpi PNP0A08:03: fail to add MMCONFIG information, can't access extended configuration space under this bridge
> 
> But the rest of this still looks like a regression.  From your
> previous dmesg log:
> 
>   PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
>   PNP0A03:00: host bridge to domain 0000 [bus ff]
>   PNP0A03:01: host bridge to domain 0000 [bus bf]
>   PNP0A03:02: host bridge to domain 0000 [bus 7f]
>   PNP0A03:03: host bridge to domain 0000 [bus 3f]
>   PNP0A08:00: host bridge to domain 0000 [bus 00-3e]
>   PNP0A08:01: host bridge to domain 0000 [bus 40-7e]
>   PNP0A08:02: host bridge to domain 0000 [bus 80-be]
>   PNP0A08:03: host bridge to domain 0000 [bus c0-fe]
> 
> That MMCONFIG space should cover all those buses, but something is
> going wrong.

Tony, would you mind collecting a dmesg log with "efi=debug"?  I want
to see the EFI_MEMORY_MAPPED_IO size and what we remove from E820.

Bjorn

  reply	other threads:[~2023-01-06 17:33 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 14:39 Bug report: the extended PCI config space is missed with 6.2-rc2 Liang, Kan
2023-01-04 14:50 ` Bjorn Helgaas
2023-01-04 15:45   ` Bjorn Helgaas
2023-01-05 17:42     ` Tony Luck
2023-01-05 17:51       ` Bjorn Helgaas
2023-01-05 18:04         ` Luck, Tony
2023-01-05 18:29           ` Bjorn Helgaas
2023-01-05 19:23             ` Liang, Kan
2023-01-05 19:44               ` Bjorn Helgaas
2023-01-05 19:44             ` Dan Williams
2023-01-05 19:58               ` Luck, Tony
2023-01-05 20:37                 ` Bjorn Helgaas
2023-01-05 21:49                   ` Luck, Tony
2023-01-05 22:20                     ` Bjorn Helgaas
2023-01-05 20:23               ` Bjorn Helgaas
2023-01-05 21:20                 ` Dan Williams
2023-01-05 21:35                   ` Bjorn Helgaas
2023-01-05 21:43                     ` Dan Williams
2023-01-05 21:48                       ` Bjorn Helgaas
2023-01-05 22:32 ` Bjorn Helgaas
2023-01-05 23:38   ` Dan Williams
2023-01-06  0:22     ` Luck, Tony
2023-01-06  0:47       ` Bjorn Helgaas
2023-01-06 17:33         ` Bjorn Helgaas [this message]
2023-01-06 18:03           ` Luck, Tony
2023-01-06 20:52             ` Bjorn Helgaas
2023-01-06 21:37               ` Luck, Tony
2023-01-06 22:04                 ` Bjorn Helgaas
2023-01-06 22:30                   ` Luck, Tony
2023-01-10  5:43                   ` Sun, Yunying
2023-01-10 18:12                   ` Rafael J. Wysocki
2023-01-10 19:06                     ` Bjorn Helgaas
2023-01-06  0:32     ` Bjorn Helgaas
2023-01-06  0:50   ` Liang, Kan
2023-01-09 12:27   ` Giovanni Cabiddu
2023-01-10  6:03   ` Sun, Yunying
2023-01-06  9:44 ` Linux kernel regression tracking (#adding)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230106173341.GA1234930@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=2lprbe78@duck.com \
    --cc=benoitg@coeus.ca \
    --cc=bhelgaas@google.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=david.e.box@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=kan.liang@linux.intel.com \
    --cc=kernelorg@undead.fr \
    --cc=kjhambrick@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=mumblingdrunkard@protonmail.com \
    --cc=nicholas.johnson-opensource@outlook.com.au \
    --cc=tony.luck@intel.com \
    --cc=wse@tuxedocomputers.com \
    --cc=yunying.sun@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.