linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel Paubert <paubert@iram.es>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: "Greg KH" <greg@kroah.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Dave Airlie" <airlied@gmail.com>,
	linuxppc-dev@lists.ozlabs.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Revert 737a3bb9416ce2a7c7a4170852473a4fcc9c67e8 ?
Date: Mon, 11 Apr 2011 15:31:28 +0200	[thread overview]
Message-ID: <20110411133128.GA24344@iram.es> (raw)
In-Reply-To: <1302185075.24704.143.camel@thor.local>

On Thu, Apr 07, 2011 at 04:04:35PM +0200, Michel Dänzer wrote:
> On Mit, 2011-04-06 at 22:43 +0200, Gabriel Paubert wrote: 
> > 
> > The probem is that, at least on one of my machines, the new driver
> > does not work: the system hangs (apparently solid, but it's before
> > networking starts up and I've not yet hooked up a serial console), 
> > after the "radeon: ib pool ready" message.
> 
> Does radeon.agpmode=-1 radeon.no_wb=1 help?
> 
> You might be able to get more information via netconsole if you prevent
> the radeon module from loading automatically (or load it with
> radeon.modeset=0 first) and then load it e.g. via ssh with modeset=1.

Loading the module with modeset=1 results in insmod blocked in
kernel state (not consuming CPU cycles either). The last kernel 
message is always the same (ib pool ready). This seems to be 
independent of agpmode and no_wb. The kernel messages when
loading the driver are:

kernel: [drm] radeon kernel modesetting enabled.
kernel: checking generic (c0000000 140000) vs hw (c0000000 10000000)
kernel: fb: conflicting fb hw usage radeondrmfb vs OFfb vga,Displa - removing generic driver
kernel: [drm] initializing kernel modesetting (RV530 0x1002:0x71C7).
kernel: radeon 0000:f1:00.0: Using 64-bit DMA iommu bypass
kernel: [drm] register mmio base: 0xE8000000
kernel: [drm] register mmio size: 65536
kernel: radeon 0000:f1:00.0: Invalid ROM contents
kernel: ATOM BIOS: X1650PRO
kernel: [drm] Generation 2 PCI interface, using max accessible memory
kernel: radeon 0000:f1:00.0: VRAM: 512M 0x0000000000000000 - 0x000000001FFFFFFF (512M used)
kernel: radeon 0000:f1:00.0: GTT: 512M 0x0000000020000000 - 0x000000003FFFFFFF
kernel: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
kernel: [drm] Driver supports precise vblank timestamp query.
kernel: irq: irq 9 on host /mpic mapped to virtual irq 24
kernel: u3msi: allocated virq 0x18 (hw 0x9) addr 0xf8004090
kernel: radeon 0000:f1:00.0: radeon: using MSI.
kernel: [drm] radeon: irq initialized.
kernel: [drm] Detected VRAM RAM=512M, BAR=256M
kernel: [drm] RAM width 128bits DDR
kernel: [TTM] Zone  kernel: Available graphics memory: 1002914 kiB.
kernel: [TTM] Initializing pool allocator.
kernel: [drm] radeon: 512M of VRAM memory ready
kernel: [drm] radeon: 512M of GTT memory ready.
kernel: [drm] GART: num cpu pages 131072, num gpu pages 131072
kernel: [drm] radeon: 1 quad pipes, 2 z pipes initialized.
kernel: [drm] PCIE GART of 512M enabled (table at 0x00040000).
kernel: radeon 0000:f1:00.0: WB enabled
kernel: [drm] Loading R500 Microcode
kernel: [drm] radeon: ring at 0x0000000020001000
kernel: [drm] ring test succeeded in 6 usecs
kernel: [drm] radeon: ib pool ready.


For now, with modeset=0, agpmode=-1 and no_wb=1, the driver
seems to work. But it sometimes took hours to fail, so some
more wait is needed.

	Regards,
	Gabriel

  reply	other threads:[~2011-04-11 13:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 23:52 Revert 737a3bb9416ce2a7c7a4170852473a4fcc9c67e8 ? Gabriel Paubert
2011-04-05 10:39 ` Michel Dänzer
2011-04-06  8:41 ` Uwe Kleine-König
2011-04-06  8:46   ` Dave Airlie
2011-04-06 20:43     ` Gabriel Paubert
2011-04-07 14:04       ` Michel Dänzer
2011-04-11 13:31         ` Gabriel Paubert [this message]
2011-04-11 15:32           ` Michel Dänzer
2011-04-12 11:30             ` Gabriel Paubert
2011-04-12 11:46               ` Michel Dänzer
2011-04-12 12:00                 ` Gabriel Paubert
2011-04-12 17:29                   ` Michel Dänzer
2011-04-13  7:59                     ` Gabriel Paubert
2011-04-13  8:16                       ` Benjamin Herrenschmidt
2011-04-13 10:01                         ` Gabriel Paubert
2011-04-13 12:12                       ` Michel Dänzer
2011-04-13 12:27                         ` Gabriel Paubert
2011-04-13 14:15                           ` Michel Dänzer
2011-04-13 20:01                             ` Andy Furniss
2011-04-13  8:02                 ` Gabriel Paubert
2011-04-13  8:12                   ` small git lesson [Was: Re: Revert 737a3bb9416ce2a7c7a4170852473a4fcc9c67e8 ?] Uwe Kleine-König
     [not found]                   ` <20110413081246.GK18850__3180.67204575545$1302682420$gmane$org@pengutronix.de>
2011-04-13  8:59                     ` Andreas Schwab
2011-04-13 10:31                       ` Gabriel Paubert
2011-04-13 12:17                         ` Uwe Kleine-König
2011-04-07 11:25     ` Revert 737a3bb9416ce2a7c7a4170852473a4fcc9c67e8 ? Gabriel Paubert
2011-04-07 11:33     ` Gabriel Paubert

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=20110411133128.GA24344@iram.es \
    --to=paubert@iram.es \
    --cc=airlied@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=michel@daenzer.net \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).