From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: Tony Breeds <tbreeds@au1.ibm.com>, acrux <acrux_it@libero.it>,
dri-devel@lists.freedesktop.org
Subject: Re: linux-3.3-rc2 and radeon kms failure on ppc32 with Radeon X1650PRO pcie
Date: Thu, 16 Feb 2012 19:02:51 +1100 [thread overview]
Message-ID: <1329379371.2892.7.camel@pasglop> (raw)
In-Reply-To: <1329378616.2859.395.camel@thor.local>
On Thu, 2012-02-16 at 08:50 +0100, Michel Dänzer wrote:
> > > The second case with no firmware is a bit more surprising, looks like
> > > something bad happened on the PCI express bus or the kernel tried to
> > > access something that the card rejected (target abort or PCIe
> > > equivalent most likely), thus triggering a PLB error . That could be
> > > investigated a bit more.
>
> AFAICT in both cases the immediate problem is the PLB error on first
> access to VRAM, indicating some kind of problem with ioremap_wc() or
> generally PCIe device memory access.
I think the problem here is more along the lines of >32-bit physical
memory and ttm screwing up the physical addresses before mapping the
vram object.
Tony (CC) has some patches to address that part (for use with a 476
which is cache coherent, we got evergreen working on that).
I think he hasn't yet "polished" the patches enough (ie fixed all the
drivers for the change in types) but basically, quite a few places in
there need to store physical addresses in resource_size_t instead of
long's.
> > Anyway after nearly ten years, due a lack in resources, i'm sadly going
> > to suspend the CRUX PPC project and my activism pro free
> > software thus i'm unable to follow these debug. I'll hold on to me
> > the only YDL Powerstation then from the next weeks i'll can only follow
> > trying to help in debug [1] on this specific machine.
> >
> > [1]http://lists.freedesktop.org/archives/dri-devel/2012-January/018575.html
>
> For that one, I'd try adding some more debugging output to
> radeon_get_bios() to find out which method it ends up using to retrieve
> the ROM contents, and why it doesn't look like it's an ATOM BIOS.
Is it an Apple card or an x86 card ? Apple cards don't have the BIOS in
the right place unfortunately.
Cheers,
Ben.
> Does the same card work in an x86 machine?
>
>
> --
> Earthling Michel Dänzer | http://www.amd.com
> Libre software enthusiast | Debian, X and DRI developer
>
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2012-02-16 8:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 1:56 linux-3.2.2 and radeon kms failure on ppc32 with Radeon X1650PRO pcie acrux
2012-02-04 23:38 ` linux-3.3-rc2 " acrux
2012-02-07 17:32 ` Michel Dänzer
2012-02-11 20:00 ` acrux
2012-02-12 10:00 ` Michel Dänzer
2012-02-12 10:14 ` Michel Dänzer
2012-02-15 2:23 ` acrux
2012-02-15 2:50 ` Benjamin Herrenschmidt
2012-02-15 7:39 ` Michel Dänzer
2012-02-15 20:28 ` Benjamin Herrenschmidt
2012-02-16 1:05 ` acrux
2012-02-16 7:50 ` Michel Dänzer
2012-02-16 8:02 ` Benjamin Herrenschmidt [this message]
2012-02-16 8:26 ` Michel Dänzer
2012-02-16 8:52 ` Benjamin Herrenschmidt
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=1329379371.2892.7.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=acrux_it@libero.it \
--cc=dri-devel@lists.freedesktop.org \
--cc=michel@daenzer.net \
--cc=tbreeds@au1.ibm.com \
/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