[Mesa-dev] r128 problems on G3 iMac, X server locks up
Bridgman, John
John.Bridgman at amd.com
Tue Apr 20 09:38:08 PDT 2010
There might be a clue in the dmesg output.
This is looking less like a mesa dev issue - is there a better list for this ?
> -----Original Message-----
> From: Alex Buell [mailto:alex.buell at munted.org.uk]
> Sent: Tuesday, April 20, 2010 12:29 PM
> To: Bridgman, John
> Cc: mesa-dev at lists.freedesktop.org
> Subject: RE: [Mesa-dev] r128 problems on G3 iMac, X server locks up
>
> On Mon, 2010-04-19 at 16:58 -0500, Bridgman, John wrote:
> > Looks like the driver isn't finding enough memory for the
> offscreen
> > buffer. Maybe try 16-bit pixel depth instead of 24 ?
>
> That didn't work either. Here's the relevant lines found in
> Xorg.l0.log
>
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 8, (OK)
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 8, (OK)
> drmOpenByBusid: Searching for BusID pci:0000:00:10.0
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 8, (OK)
> drmOpenByBusid: drmOpenMinor returns 8
> drmOpenByBusid: drmGetBusid reports pci:0000:00:10.0
> (II) [drm] DRM interface version 1.3
> (II) [drm] DRM open master succeeded.
> (II) R128(0): [drm] Using the DRM lock SAREA also for drawables.
> (II) R128(0): [drm] framebuffer handle = 0x94000000
> (II) R128(0): [drm] added 1 reserved context for kernel
> (II) R128(0): X context handle = 0x1
> (II) R128(0): [drm] installed DRM signal handler
> (II) R128(0): [pci] 8192 kB allocated with handle 0xe47e2000
> (II) R128(0): [pci] ring handle = 0xe47e2000
> (II) R128(0): [pci] Ring mapped at 0x49050000
> (II) R128(0): [pci] Ring contents 0x00000000
> (II) R128(0): [pci] ring read ptr handle = 0xe48e3000
> (II) R128(0): [pci] Ring read ptr mapped at 0x4802a000
> (II) R128(0): [pci] Ring read ptr contents 0x00000000
> (II) R128(0): [pci] vertex/indirect buffers handle = 0xe48e4000
> (II) R128(0): [pci] Vertex/indirect buffers mapped at 0x49151000
> (II) R128(0): [pci] Vertex/indirect buffers contents 0x00000000
> (II) R128(0): [drm] register handle = 0x90000000
> (II) R128(0): [dri] Visual configs initialized
> (II) R128(0): CCE in BM mode
> (II) R128(0): Using 8 MB AGP aperture
> (II) R128(0): Using 1 MB for the ring buffer
> (II) R128(0): Using 2 MB for vertex/indirect buffers
> (II) R128(0): Using 1 MB for AGP textures
> (II) R128(0): Memory manager initialized to (0,0) (1024,3840)
> (II) R128(0): Reserved area from (0,768) to (1024,770)
> (II) R128(0): Largest offscreen area available: 1024 x 3070
> (II) R128(0): Reserved back buffer from (0,770) to (1024,1538)
> (II) R128(0): Reserved depth buffer from (0,1538) to (1024,2307)
> (II) R128(0): Reserved depth span from (0,2306) offset 0x481000
> (II) R128(0): Reserved 8704 kb for textures at offset 0x780000
> (**) R128(0): Option "XaaNoOffscreenPixmaps"
> (II) R128(0): Using XFree86 Acceleration Architecture (XAA)
> Screen to screen bit blits
> Solid filled rectangles
> 8x8 mono pattern filled rectangles
> Indirect CPU to Screen color expansion
> Solid Lines
> Dashed Lines
> Setting up tile and stipple cache:
> 32 128x128 slots
> 14 256x256 slots
> (II) R128(0): Acceleration enabled
> (==) R128(0): Backing store disabled
> (==) R128(0): Silken mouse enabled
> (II) R128(0): Using hardware cursor (scanline 4614)
> (II) R128(0): Largest offscreen area available: 1024 x 1531
> (**) R128(0): DPMS enabled
> (II) R128(0): [DRI] installation complete
> (EE) R128(0): R128DRICloseScreen: CCE stop -22
> (II) R128(0): [drm] removed 1 reserved context for kernel
> (II) R128(0): [drm] unmapping 8192 bytes of SAREA 0xe1065000
> at 0x48028000
> (II) R128(0): [drm] Closed DRM master.
> (WW) R128(0): Direct rendering disabled
> (==) RandR enabled
>
> At this point it closes the DRM, as it get a CCE stop -22.
> What does that error means?
>
> (II) AIGLX: Screen 0 is not DRI2 capable
> (II) AIGLX: Screen 0 is not DRI capable
> (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
> (II) GLX: Initialized DRISWRAST GL provider for screen 0
> (EE) R128(0): R128CCEWaitForIdle: CCE idle -9
> (EE) R128(0): Idle timed out, resetting engine...
> (EE) R128(0): R128CCEWaitForIdle: CCE stop -9
> (EE) R128(0): R128CCEWaitForIdle: CCE start -9
> (EE) R128(0): R128CCEWaitForIdle: CCE idle -9
> (EE) R128(0): Idle timed out, resetting engine...
>
> At this point it repeats the last six lines again and again
> and again...
>
> Any ideas?
>
> --
> http://www.munted.org.uk
>
> One very high maintenance cat living here.
>
>
More information about the mesa-dev
mailing list