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

Date:	Fri, 26 Jun 2009 11:02:04 -0500
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Jeroen Roovers <jer@...too.org>
Cc:	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, 2009-06-26 at 17:08 +0200, Jeroen Roovers wrote:
> On Fri, 26 Jun 2009 14:37:40 +0000
> James Bottomley <James.Bottomley@...senPartnership.com> wrote:
> 
> > On Fri, 2009-06-26 at 12:58 +0400, Alexander Beregalov 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.
> > 
> > This tends to indicate a problem with resource parenting ... could you
> > post the full boot output?  That might indicate why.
> 
> Here goes.

It looks like there's some sort of screw up in the LBA resource
allocation on 32 bits.  The slight problem with this is that I don't
have an LBA 32 bit system to debug this; I've only got a C360.

How recent is the failure? Could you bisect it back to the failing
commit?

Thanks,

James


--
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/