All of 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: Tue, 07 Feb 2012 18:32:44 +0100	[thread overview]
Message-ID: <1328635964.2859.25.camel@thor.local> (raw)
In-Reply-To: <20120205003840.698a2b2a.acrux_it@libero.it>

On Son, 2012-02-05 at 00:38 +0100, acrux wrote:
> 
> unable to have a working radeon kms framebuffer with linux-3.3-rc2 on ppc
> video card: Radeon X1650PRO PCIE

Is this a regression? If yes, can you bisect?


> [drm] GART: num cpu pages 131072, num gpu pages 131072

The driver detects the CPU page size as 4K, is that correct?


> [drm] radeon: ib pool ready.
> [drm] radeon: 1 quad pipes, 2 z pipes initialized.
> Machine check in kernel mode.
> Data Write PLB Error
> Oops: Machine check, sig: 7 [#1]
> Canyonlands
> Modules linked in:
> NIP: c03a3cd8 LR: c038b380 CTR: c03a3ca0
> REGS: efff7f10 TRAP: 0214   Not tainted  (3.3.0-rc2)
> MSR: 00029000 <CE,EE,ME>  CR: 447b4628  XER: 00000000
> TASK = ef830000[1] 'swapper' THREAD: ef834000
> GPR00: f5580000 ef835d60 ef830000 ffffffea f5580004 002fb02c 002fb02c 00000000
> GPR08: 800bf41b 00020000 00040000 c06b6cd4 447b4628 8500686f 0fff9038 00000000
> GPR16: 0ffc2388 0ffc2368 0ffc2388 0ffc2368 0fff9038 00000001 c0000010 0000000f
> GPR24: 00000000 ef849060 c06a14c0 000000ff ffffffff ef849000 00000002 ef8ea000
> NIP [c03a3cd8] rv370_pcie_gart_set_page+0x38/0x48
> LR [c038b380] radeon_gart_restore+0x58/0x84
> Call Trace:
> [ef835d60] [ffffffff] 0xffffffff (unreliable)
> [ef835d70] [c03a4c54] rv370_pcie_gart_enable+0x4c/0x230
> [ef835d90] [c03ae288] r520_startup+0xc0/0x188
> [ef835da0] [c03ae5d8] r520_init+0x1d0/0x234

Not sure what exactly 'Data Write PLB Error' means, but it looks like
the problem occurs when the card's VRAM is first accessed for setting a
GART page table entry. 


-- 
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-07 17:33 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 [this message]
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
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=1328635964.2859.25.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.