dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: acrux <acrux_it@libero.it>
Cc: 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 08:50:16 +0100	[thread overview]
Message-ID: <1329378616.2859.395.camel@thor.local> (raw)
In-Reply-To: <20120216010549.321bf6b6.acrux_it@libero.it>

On Don, 2012-02-16 at 01:05 +0000, acrux wrote: 
> On Thu, 16 Feb 2012 07:28:10 +1100
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> 
> > On Wed, 2012-02-15 at 08:39 +0100, Michel Dänzer wrote:
> > 
> > > > > Btw, to sum up the list of Power Architecture machines with
> > > > > PCIE  that aim to be a desktop/workstation: Apple iMac G5
> > > > > (iSight), Apple PowerMac Quad G5, YDL Powerstation 2x970MP and
> > > > > Acube Sam460ex . And the last two, on present evidence (my
> > > > > attempts), aren't able to boot up if bootkernel has kms enabled.
> > > > 
> > > > Which radeon card, kernel log please ?
> > > 
> > > See
> > > http://lists.freedesktop.org/archives/dri-devel/2012-February/018792.html
> > > (start of this thread) and
> > > http://lists.freedesktop.org/archives/dri-devel/2012-February/018791.html .
> > 
> > Ok, so for the 460EX, I am not surprised things aren't working with
> > KMS & DRI2... the 460 is not cache coherent, and this is not handled
> > by TTM as far as I can tell.
> > 
> > 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.


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

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

  reply	other threads:[~2012-02-16  7:50 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 [this message]
2012-02-16  8:02                     ` Benjamin Herrenschmidt
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=1329378616.2859.395.camel@thor.local \
    --to=michel@daenzer.net \
    --cc=acrux_it@libero.it \
    --cc=dri-devel@lists.freedesktop.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