From: Bjorn Helgaas <bhelgaas@google.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Alexey Voronkov" <zermond@gmail.com>,
"David Airlie" <airlied@linux.ie>,
"Saifi Khan" <saifi.khan@datasynergy.org>,
"Alex Deucher" <alexdeucher@gmail.com>,
"Marek Kordík" <kordikmarek@gmail.com>
Subject: Re: Regression: bug 85491: radeon 0000:01:00.0: Fatal error during GPU init
Date: Thu, 4 Dec 2014 09:37:41 -0700 [thread overview]
Message-ID: <20141204163741.GD3168@google.com> (raw)
In-Reply-To: <CAE9FiQXqqg-KYi3aEVvCm=hfjN3mx_7J8uQ61hVJFVLNe+U=Zg@mail.gmail.com>
On Wed, Dec 03, 2014 at 06:01:33PM -0800, Yinghai Lu wrote:
> On Wed, Dec 3, 2014 at 2:15 PM, Bjorn Helgaas <bhelgaas@google.com> wrote:
> > In v3.16 (which does contain 5b28541552ef), when pbus_size_mem() sizes
> > the 64-bit prefetchable window, it only looks for downstream 64-bit
> > resources. Since the radeon at 01:00.0 has none, we size the window
> > to 0 + 0x200000 (the 0x200000 part is pci_hotplug_mem_size, to
> > accommodate future hot-added devices).
> >
> > But that's not big enough to hold the radeon BAR 0 [mem
> > 0xc0000000-0xcfffffff pref], so BAR 0 remains unassigned, so
> > pci_enable_device() should fail, and radeon doesn't work.
> >
> > I don't know what the best fix is, but I think it's probably too
> > aggressive to *never* use a 64-bit prefetchable window for downstream
> > 32-bit prefetchable resources. This configuration from BIOS should
> > just work without us changing anything (although we probably should
> > trim the window to start at 0xc0000000, which would still work).
>
> pci=realloc should workaround the problem, as it would take control of
> the bridge mmio BAR, and allocate more range for mmio pref under it.
I don't think pci=realloc is the answer because
1) It's a poor user experience. We should be able to handle this
automatically, without asking the user to do anything.
2) It puts the radeon framebuffer in the non-prefetchable window, and we
should be able to keep it in the prefetchable window.
Bjorn
next prev parent reply other threads:[~2014-12-04 16:37 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
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 [this message]
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=20141204163741.GD3168@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox