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: <5516BF4B.9030901@oracle.com>
Date:	Sat, 28 Mar 2015 08:48:43 -0600
From:	David Ahern <david.ahern@...cle.com>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	Bjorn Helgaas <bhelgaas@...gle.com>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	"sparclinux@...r.kernel.org" <sparclinux@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: d63e2e1f3df breaks sparc/T5-8

On 3/27/15 11:26 PM, Yinghai Lu wrote:
> On Fri, Mar 27, 2015 at 8:45 PM, David Ahern <david.ahern@...cle.com> wrote:
>> On 3/27/15 9:19 PM, Yinghai Lu wrote:
>>>
>>> Good. But we still have annoying warning about "no compatible window".
>>>
>>> Please try attached patch that support 64bit pci mem space for sparc.
>>>
>>> BTW, looks like you still do not have   CONFIG_PCI_DEBUG=y in your
>>> .config.
>>> otherwise we should more verbose print out.
>>> Or did you have DYNAMIC_DEBUG enabled ?
>>> If it is that case, can you remove that?
>>>
>>
>> done. attached.
>>
>
> ok, we are almost there.
>
> [99510.956337] pci_sun4v f02dbcfc: PCI host bridge to bus 0000:00
> [99511.025812] pci_bus 0000:00: root bus resource [io
> 0x804000000000-0x80400fffffff] (bus address [0x0000-0xfffffff])
> [99511.151039] pci_bus 0000:00: root bus resource [mem
> 0x800000000000-0x80007effffff] (bus address [0x00000000-0x7effffff])
> [99511.282693] pci_bus 0000:00: root bus resource [mem
> 0x800100000000-0x8007ffffffff] (bus address [0x00000000-0x6ffffffff])
> [99511.414878] pci_bus 0000:00: root bus resource [bus 00-77]
>
>
> looks like the offset for mem64 is not right.
>
> Please try attached v2.




View attachment "dmesg" of type "text/plain" (69125 bytes)