linux-kernel - Re: 4.3-rc3 BAR allocation problems on multiple machines

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: <CAE9FiQXM9YxRwcbG577Pcqmj7YbOa0yk6hYELb2FpTtct5u2jg@mail.gmail.com>
Date:	Wed, 7 Oct 2015 15:49:42 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Meelis Roos <mroos@...ux.ee>
Cc:	Linux Kernel list <linux-kernel@...r.kernel.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Subject: Re: 4.3-rc3 BAR allocation problems on multiple machines

On Wed, Oct 7, 2015 at 2:25 AM, Meelis Roos <mroos@...ux.ee> wrote:
> First I noticed that on Sun Netra t1-150 (sparc64 CPU), PCI allocation
> was failing for qla1280 scsi driver. Reading dmesg uncovered "can't
> claim BAR" errors. Looking for this in my other test machines I see more
> of them - on many sparc64 machines and some on x86.
>
> In another thread for "Resource allocation cleanup for v4.4", Yinghai Lu
> asked for full dmesg to solve another similar case. So to help
> understanding this one, here are the dmesgs of my machines:
>
> sparc64 machines:
>
> http://kodu.ut.ee/~mroos/dm/dm.t1-105
> http://kodu.ut.ee/~mroos/dm/dm.t1-200
> http://kodu.ut.ee/~mroos/dm/dm.v120
> http://kodu.ut.ee/~mroos/dm/dm.v210
> http://kodu.ut.ee/~mroos/dm/dm.v240
> http://kodu.ut.ee/~mroos/dm/dm.sb100

Please try

git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git
for-pci-v4.4-next

It should fix some "no compatible bridge window"

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/