linux-kernel - Re: 2.6.31-rc1: parisc: multiple PCI BAR collisions

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] [day] [month] [year] [list]

Message-ID: <20090626201602.GA9862@bombadil.infradead.org>
Date:	Fri, 26 Jun 2009 16:16:02 -0400
From:	Kyle McMartin <kyle@...artin.ca>
To:	Matthew Wilcox <matthew@....cx>
Cc:	Grant Grundler <grundler@...isc-linux.org>,
	Alexander Beregalov <a.beregalov@...il.com>,
	linux-parisc@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.31-rc1: parisc: multiple PCI BAR collisions

On Fri, Jun 26, 2009 at 11:44:18AM -0600, Matthew Wilcox wrote:
> > > Hardware is HP j6000.
> > > It cannot initialize many PCI devices (sym53c8xx, tulip, STI,
> > > usb(onci)) and cannot boot (no root device).
> > > Messages like this:
> > > sym53c8xx 0:0:0f.0: device not available because of BAR 1 [0xf4005000
> > > - 0xf40053ff] collisions.
> > 
> > I'm pretty sure this is a problem of the root bus resources not getting
> > setup correctly. I'm not clear on what's wrong. jejb and willy are looking
> > at it now as well.
> 
> This patch fixes it for me.
> 

obviously correct, applied and pushed out.

thanks, kyle
--
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/