From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Patrick Finnegan <pat@computer-refuge.org>
Cc: paulus@samba.org,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Problem with Infiniband adapter on IBM p550
Date: Fri, 08 Oct 2010 16:45:49 +1100 [thread overview]
Message-ID: <1286516749.2463.408.camel@pasglop> (raw)
In-Reply-To: <1286516470.2463.403.camel@pasglop>
> Ok, so from what I can tell, the driver is unhappy because either BAR 0
> hasn't been assigned a memory resource or the size doesn't match what
> the driver expects.
>
Ooops, accidentally sent too quickly...
>From your OF log I see:
reg 00c10000 00000000 00000000 00000000 00000000
03c10010 00000000 00000000 00000000 00100000
43c10018 00000000 00000000 00000000 00800000
43c10020 00000000 00000000 00000000 08000000
assigned-addresses 83c10020 00000000 e8000000 00000000 08000000
Now, I think this is the problem.
The "assigned-addresses" property seems to indicate that the firmware only
assigned BAR 4 and didn't assign anything to the other ones.
I don't know why, but it definitely looks like a firmware bug to me. On those
machines, PCI resource assignment is under hypervisor control and so Linux
cannot re-assign missing resources itself.
I'll see if I can find a FW person to shed some light on this.
Can you provide me (privately maybe) with the FW version on the machine ?
Cheers,
Ben.
next prev parent reply other threads:[~2010-10-08 5:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 3:24 Problem with Infiniband adapter on IBM p550 Patrick Finnegan
2010-10-08 5:41 ` Benjamin Herrenschmidt
2010-10-08 5:45 ` Benjamin Herrenschmidt [this message]
2010-11-03 3:15 ` Patrick Finnegan
2010-11-03 13:34 ` Anton Blanchard
2010-11-03 14:43 ` Patrick Finnegan
2010-11-03 13:46 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2010-10-08 2:57 Patrick Finnegan
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=1286516749.2463.408.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=pat@computer-refuge.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).