From: Yinghai Lu <yinghai@kernel.org>
To: David Ahern <david.ahern@oracle.com>,
Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Cc: "sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: d63e2e1f3df breaks sparc/T5-8
Date: Thu, 26 Mar 2015 13:43:43 -0700 [thread overview]
Message-ID: <CAE9FiQXw3QUCNNZj2SVhn-AYWWnggT=7JXPkGNpYFzq-qAB1aQ@mail.gmail.com> (raw)
In-Reply-To: <5514391F.2030300@oracle.com>
[+bjorn, pci list]
On Thu, Mar 26, 2015 at 9:51 AM, David Ahern <david.ahern@oracle.com> wrote:
> Hi:
>
> Boot of an 8-socket T5 sparc system fails on top of tree. git bisect points
> to this commit:
>
> commit 904bf6bd150bdafb42ddbb3257ea8
> Author: Yinghai Lu <yinghai@kernel.org>
> Date: Thu Jan 15 16:21:51 2015 -0600
>
> sparc/PCI: Clip bridge windows to fit in upstream windows
>
> Every PCI-PCI bridge window should fit inside an upstream bridge window
> because orphaned address space is unreachable from the primary side of the
> upstream bridge. If we inherit invalid bridge windows that overlap an
> upstream window from firmware, clip them to fit and update the bridge
> accordingly.
>
>
> Sure enough if I revert it on top of tree the system boots fine.
Can you send out boot log with "debug ignore_loglevel"?
Thanks
Yinghai
next prev parent reply other threads:[~2015-03-26 20:43 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 16:51 d63e2e1f3df breaks sparc/T5-8 David Ahern
2015-03-26 20:43 ` Yinghai Lu [this message]
2015-03-26 23:27 ` David Ahern
2015-03-27 21:01 ` Yinghai Lu
2015-03-27 21:50 ` David Miller
2015-03-27 22:51 ` Yinghai Lu
[not found] ` <CABhMZUVqgsYdT4wn2H8hsrh4f=6hT0G+sg=wwYSt33+jtvBS9A@mail.gmail.com>
2015-03-29 18:32 ` David Miller
2015-04-03 15:45 ` Bjorn Helgaas
2015-04-03 16:48 ` David Miller
2015-03-27 23:57 ` Yinghai Lu
2015-03-28 0:32 ` David Ahern
2015-03-28 0:36 ` David Ahern
2015-03-28 3:19 ` Yinghai Lu
2015-03-28 3:22 ` David Ahern
2015-03-28 3:27 ` Yinghai Lu
2015-03-28 3:45 ` David Ahern
2015-03-28 5:26 ` Yinghai Lu
2015-03-28 14:48 ` David Ahern
2015-03-28 20:24 ` Yinghai Lu
2015-03-29 14:47 ` David Ahern
2015-03-29 20:07 ` Yinghai Lu
2015-03-30 22:54 ` David Ahern
2015-03-31 1:06 ` Yinghai Lu
2015-03-31 4:10 ` David Ahern
2015-03-31 16:53 ` Yinghai Lu
2015-03-31 17:04 ` David Ahern
2015-03-31 20:28 ` Yinghai Lu
2015-03-31 22:29 ` David Ahern
2015-03-31 22:38 ` Yinghai Lu
2015-03-31 22:42 ` David Ahern
2015-03-31 15:06 ` David Miller
2015-03-31 18:16 ` Yinghai Lu
2015-03-31 18:19 ` David Miller
2015-03-31 18:25 ` Yinghai Lu
2015-03-28 1:05 ` Sam Ravnborg
2015-03-28 2:07 ` Yinghai Lu
2015-03-28 8:18 ` Sam Ravnborg
2015-03-28 18:16 ` David Miller
2015-03-28 20:19 ` 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='CAE9FiQXw3QUCNNZj2SVhn-AYWWnggT=7JXPkGNpYFzq-qAB1aQ@mail.gmail.com' \
--to=yinghai@kernel.org \
--cc=bhelgaas@google.com \
--cc=david.ahern@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
/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).