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]

Message-ID: <20090626170823.0a8730b7@epia.jer-c2.orkz.net>
Date:	Fri, 26 Jun 2009 17:08:23 +0200
From:	Jeroen Roovers <jer@...too.org>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
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, 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.


Kind regards,
     jer
Download attachment "minicom.cap.bz2" of type "application/x-bzip" (5195 bytes)