linux-kernel - Re: d63e2e1f3df breaks sparc/T5-8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAE9FiQXw3QUCNNZj2SVhn-AYWWnggT=7JXPkGNpYFzq-qAB1aQ@mail.gmail.com>
Date:	Thu, 26 Mar 2015 13:43:43 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	David Ahern <david.ahern@...cle.com>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Cc:	"sparclinux@...r.kernel.org" <sparclinux@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: d63e2e1f3df breaks sparc/T5-8

[+bjorn, pci list]

On Thu, Mar 26, 2015 at 9:51 AM, David Ahern <david.ahern@...cle.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@...nel.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/