From: "Marek Kordík" <kordikmarek@gmail.com>
To: Yinghai Lu <yinghai@kernel.org>, Bjorn Helgaas <bhelgaas@google.com>
Cc: Gavin Shan <gwshan@linux.vnet.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Alexey Voronkov <zermond@gmail.com>,
David Airlie <airlied@linux.ie>,
Alex Deucher <alexdeucher@gmail.com>,
Richard Yang <weiyang@linux.vnet.ibm.com>
Subject: Re: Regression: bug 85491: radeon 0000:01:00.0: Fatal error during GPU init
Date: Thu, 25 Dec 2014 16:46:02 +0100 [thread overview]
Message-ID: <549C313A.7090504@gmail.com> (raw)
In-Reply-To: <CAE9FiQUoA_vz78sEnHtDAmzTJcwL0PdUe9jwLw+H9h3+omq+WA@mail.gmail.com>
On 12/24/2014 03:29 AM, Yinghai Lu wrote:
> On Tue, Dec 23, 2014 at 1:41 PM, Bjorn Helgaas <bhelgaas@google.com> wrote:
>
>>
>> Can you do this so it clips to any upstream bridge, whether it's a host
>> bridge or a PCI-to-PCI bridge? It doesn't seem like this has to be
>> specific to host bridge windows -- any device below a PCI-to-PCI bridge has
>> to use address space forwarded by that upstream bridge.
>
> ok, please check attached v2.
>
>>
>> I wish this were in generic code. There's nothing architecture-specific
>> about the problem, but this patch only fixes things on x86. Can you make a
>> similar change in the corresponding code for other arches, as well?
>
> ok, later after x86.
>
> Thanks
>
> Yinghai
>
I checked (only) v2 of your patch on versions 3.18.0 and 3.18.1. The
result of both versions is that booting stops with kernel panic. I don't
how to get the full log (there is nothing in journalctl and dmesg after
booting some working kernel - maybe if you can give me some hint what to
google) so I will attach photo of screen to the bugzilla issue.
Marek
next prev parent reply other threads:[~2014-12-25 15:46 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 [this message]
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
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=549C313A.7090504@gmail.com \
--to=kordikmarek@gmail.com \
--cc=airlied@linux.ie \
--cc=alexdeucher@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linux-pci@vger.kernel.org \
--cc=weiyang@linux.vnet.ibm.com \
--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