From: Bjorn Helgaas <bhelgaas@google.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
zermond@gmail.com, David Airlie <airlied@linux.ie>,
saifi.khan@datasynergy.org, Alex Deucher <alexdeucher@gmail.com>,
kordikmarek@gmail.com
Subject: Re: Regression: bug 85491: radeon 0000:01:00.0: Fatal error during GPU init
Date: Thu, 4 Dec 2014 09:15:06 -0700 [thread overview]
Message-ID: <20141204161506.GA2501@google.com> (raw)
In-Reply-To: <CAE9FiQUP6v=bGxkTXuyYf6mO1reQcD2gLjrr2nDHNYDBQ8ubug@mail.gmail.com>
On Wed, Dec 03, 2014 at 05:41:32PM -0800, Yinghai Lu wrote:
> On Wed, Dec 3, 2014 at 5:38 PM, Yinghai Lu <yinghai@kernel.org> wrote:
> > On Wed, Dec 3, 2014 at 2:15 PM, Bjorn Helgaas <bhelgaas@google.com> wrote:
> >> There's a bugzilla for this, so this email is to make the bugzilla
> >> more discoverable and to have a more public discussion about it.
> >>
> >> https://bugzilla.kernel.org/show_bug.cgi?id=85491
> >>
> >> I think this regression is caused by 5b28541552ef ("PCI: Restrict
> >> 64-bit prefetchable bridge windows to 64-bit resources"). These dmesg
> >> fragments are from v3.16, which doesn't work:
> >>
> >> pci_bus 0000:00: root bus resource [mem 0xc0000000-0xffffffff]
> >>
> >> pci 0000:00:01.0: PCI bridge to [bus 01]
> >> pci 0000:00:01.0: bridge window [io 0x8000-0xafff]
> >> pci 0000:00:01.0: bridge window [mem 0xfdf00000-0xfdffffff]
> >> pci 0000:00:01.0: bridge window [mem 0xbdf00000-0xddefffff 64bit
> >> pref] <-- outside host bridge window
> >>
> >> pci 0000:01:00.0: reg 0x10: [mem 0xc0000000-0xcfffffff pref]
> >> pci 0000:01:00.0: reg 0x14: [io 0xa000-0xa0ff]
> >> pci 0000:01:00.0: reg 0x18: [mem 0xfdff0000-0xfdffffff]
> >> pci 0000:01:00.0: reg 0x30: [mem 0xfdfc0000-0xfdfdffff pref]
> >>
> >> pci 0000:00:01.0: can't claim BAR 15 [mem 0xbdf00000-0xddefffff
> >> 64bit pref]: no compatible bridge window
> >> pci 0000:01:00.0: can't claim BAR 0 [mem 0xc0000000-0xcfffffff
> >> pref]: no compatible bridge window
> >
> > Looks like we wrong type checking from parent resource searching.
I don't understand what you're trying to say, but I don't think the "no
compatible bridge window" problem is related to resource types. I think
it's because the 00:01.0 window at [mem 0xbdf00000-0xddefffff] starts
before the [mem 0xc0000000-0xffffffff] host bridge window.
> oh, no, the BIOS is crazy...
>
> [ 0.158601] pci 0000:00:01.0: address space collision: [mem
> 0xbdf00000-0xddefffff 64bit pref] conflicts with System RAM [mem
> 0x00100000-0xbff9ffff]
>
> mmio is overlapping with ram range....
I agree, it certainly looks like the BIOS programmed the 00:01.0 window
incorrectly. But I think we should just clip it so it starts at 0xc0000000
instead of 0xbdf00000.
There's no reason we should depend on correct PCI configuration from the
BIOS.
Bjorn
next prev parent reply other threads:[~2014-12-04 16:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 22:15 Regression: bug 85491: radeon 0000:01:00.0: Fatal error during GPU init Bjorn Helgaas
2014-12-04 0:51 ` Bjorn Helgaas
2014-12-04 1:44 ` Yinghai Lu
2014-12-04 17:34 ` Bjorn Helgaas
2014-12-04 22:06 ` Yinghai Lu
2014-12-05 10:59 ` Benjamin Herrenschmidt
2014-12-08 0:47 ` Gavin Shan
2014-12-08 21:04 ` Bjorn Helgaas
2014-12-08 21:38 ` Benjamin Herrenschmidt
2014-12-08 21:46 ` Bjorn Helgaas
2014-12-08 23:38 ` Gavin Shan
2014-12-09 0:21 ` Yinghai Lu
2014-12-19 22:17 ` Bjorn Helgaas
2014-12-20 0:23 ` Bjorn Helgaas
2014-12-20 0:34 ` Yinghai Lu
2014-12-20 0:56 ` Bjorn Helgaas
2014-12-20 1:33 ` Yinghai Lu
2014-12-23 1:53 ` Yinghai Lu
2014-12-23 21:41 ` Bjorn Helgaas
2014-12-24 2:29 ` Yinghai Lu
2014-12-24 17:26 ` Bjorn Helgaas
2014-12-24 20:29 ` Yinghai Lu
2014-12-25 15:46 ` Marek Kordík
2014-12-25 21:12 ` Yinghai Lu
2015-01-09 18:45 ` Bjorn Helgaas
2015-01-09 20:38 ` Yinghai Lu
2014-12-22 8:17 ` Wei Yang
2014-12-22 19:50 ` Bjorn Helgaas
2014-12-04 1:38 ` Yinghai Lu
2014-12-04 1:41 ` Yinghai Lu
2014-12-04 16:15 ` Bjorn Helgaas [this message]
2014-12-04 22:15 ` Yinghai Lu
2014-12-04 22:25 ` Bjorn Helgaas
2014-12-04 2:01 ` Yinghai Lu
2014-12-04 16:37 ` Bjorn Helgaas
2014-12-04 22:24 ` Yinghai Lu
2014-12-05 0:24 ` Yinghai Lu
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=20141204161506.GA2501@google.com \
--to=bhelgaas@google.com \
--cc=airlied@linux.ie \
--cc=alexdeucher@gmail.com \
--cc=kordikmarek@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=saifi.khan@datasynergy.org \
--cc=yinghai@kernel.org \
--cc=zermond@gmail.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.