From: Bjorn Helgaas <bhelgaas@google.com>
To: Dave Airlie <airlied@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jiang Liu <jiang.liu@linux.intel.com>,
Rafael Wysocki <rjw@rjwysocki.net>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Lv Zheng <lv.zheng@intel.com>
Subject: Re: regression in 4.0.0-rc1 with r8169 ethernet
Date: Wed, 25 Feb 2015 01:10:56 -0600 [thread overview]
Message-ID: <CAErSpo4kG_RrpFtZ6QyRFkMO51Zx62q94L+r60-HfSZY3VHD1g@mail.gmail.com> (raw)
In-Reply-To: <CAPM=9tz8HQAZbdfgE15++i++NkArjxqiY3-BjANqDBTo1g-pOw@mail.gmail.com>
[+cc Jiang, Thomas, Lv, Rafael, linux-pci, linux-acpi]
On Tue, Feb 24, 2015 at 9:47 PM, Dave Airlie <airlied@gmail.com> wrote:
> Hey,
>
> just booted an old AMD rs780 box with new kernel and my ethernet
> failed to come up!
>
> Looks like the MAC addr is all ff's because the PCI bridge windows are
> messed up.
>
> I've attached two dmesg one from a 3.19.0-rc6 I had on it, and one
> failing from the 4.0.0-rc1 time.
>
> b24e2bdde4af656bb0679a101265ebb8f8735d3c is latest Linus commit in
> that tree (I have some radeon patches on top).
>
> motherboard is a Gigabyte GA-MA78GM-S2H, lspci also attached.
Here's the dmesg diff that looks relevant to me:
-pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
-pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
-pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
-pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff]
-pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed44fff]
-pci_bus 0000:00: root bus resource [mem 0x7ff00000-0xfebfffff]
+pci_bus 0000:00: root bus resource [io 0x0cf8-0x0cff]
+pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window]
+pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window]
+pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
+pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff window]
+pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed44fff window]
What's interesting is:
* v3.19 ignored [io 0x0cf8-0x0cff], but v4.0 includes it. I think
it's wrong to include it because that's the configuration space
address/data registers, so it's consumed by the host bridge and not
produced on the downstream side.
* v3.19 includes [mem 0x7ff00000-0xfebfffff], but v4.0 does not. This
is what's screwing up the devices.
I think all the windows should be marked as ACPI_PRODUCER in _CRS
since the space is "produced" on the downstream side of the bridge.
The [io 0x0cf8-0x0cff] region should probably be marked
ACPI_CONSUMER, and maybe that accounts for why v3.19 ignores it. But
I haven't found the code that does that yet.
I suspect this is all related to the ACPI resource parsing rework. I
looked through that briefly, but no issues jumped out at me, so this
is just a heads-up in case it is obvious to you guys.
Dave, it'd be useful if you could collect an acpidump so we can look
at the _CRS data in more detail.
Bjorn
next parent reply other threads:[~2015-02-25 7:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPM=9tz8HQAZbdfgE15++i++NkArjxqiY3-BjANqDBTo1g-pOw@mail.gmail.com>
2015-02-25 7:10 ` Bjorn Helgaas [this message]
2015-02-25 8:03 ` regression in 4.0.0-rc1 with r8169 ethernet Dave Airlie
2015-02-25 22:42 ` Rafael J. Wysocki
2015-02-27 14:50 ` Thomas Voegtle
2015-02-27 22:24 ` Rafael J. Wysocki
2015-02-28 8:06 ` Jiang Liu
2015-02-28 8:36 ` Marcel Holtmann
2015-02-28 8:45 ` Jiang Liu
2015-02-28 10:03 ` Thomas Voegtle
2015-03-02 4:33 ` [Debug 0/2] Debug PCI root resource parsing failure Jiang Liu
2015-03-02 4:33 ` [Debug 1/2] x86/PCI/ACPI: Ignore resources consumed by host bridge itself Jiang Liu
2015-03-02 4:33 ` [Debug 2/2] x86/PCI/ACPI: Gather debug info Jiang Liu
2015-03-02 8:35 ` [Debug 0/2] Debug PCI root resource parsing failure Thomas Voegtle
2015-03-02 9:51 ` [Debug 0/2] Debug ACPI " Jiang Liu
2015-03-02 9:51 ` [Debug 1/2] x86/PCI/ACPI: Ignore resources consumed by host bridge itself Jiang Liu
2015-03-02 9:51 ` [Debug 2/2] x86/PCI/ACPI: Gather debug info Jiang Liu
2015-03-02 11:52 ` [Debug 0/2] Debug ACPI resource parsing failure Thomas Voegtle
2015-02-28 8:43 ` regression in 4.0.0-rc1 with r8169 ethernet Jiang Liu
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=CAErSpo4kG_RrpFtZ6QyRFkMO51Zx62q94L+r60-HfSZY3VHD1g@mail.gmail.com \
--to=bhelgaas@google.com \
--cc=airlied@gmail.com \
--cc=jiang.liu@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).