From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jeroen Roovers <jer@gentoo.org>
Cc: Alexander Beregalov <a.beregalov@gmail.com>,
linux-parisc@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.31-rc1: parisc: multiple PCI BAR collisions
Date: Fri, 26 Jun 2009 11:02:04 -0500 [thread overview]
Message-ID: <1246032125.3925.45.camel@mulgrave.site> (raw)
In-Reply-To: <20090626170823.0a8730b7@epia.jer-c2.orkz.net>
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@HansenPartnership.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
next prev parent reply other threads:[~2009-06-26 16:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 8:58 Alexander Beregalov
2009-06-26 14:37 ` James Bottomley
2009-06-26 15:08 ` Jeroen Roovers
2009-06-26 16:02 ` James Bottomley [this message]
2009-06-26 17:03 ` Grant Grundler
2009-06-26 17:44 ` Matthew Wilcox
2009-06-26 20:16 ` Kyle McMartin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1246032125.3925.45.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=a.beregalov@gmail.com \
--cc=jer@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®