PPC64 - DRM - Radeon module causes Kernel Oops

[Michel Dänzer]

On Tue, 2008-05-13 at 18:53 -0400, Hans J. Harff wrote:
> 
> I am trying to get drm/dri to work on my box (see specs below), but
> I am not having much success.

dri-devel at lists.sf.net would be the list for this, btw.


> [  722.854646] [drm] Initialized drm 1.1.0 20060810
> [  722.871013] [drm] Initialized radeon 1.28.0 20060524 on minor 0
> 
> However, as soon as /dev/dri/card0 is being accessed (e.g. start X,
> or simply do 'cat /dev/dri/card0') the console will display:
> 
> Bus error
> 
> and dmesg will provide the following:

[...]

> [  740.147969] Call Trace:
> [  740.147972] [c0000002243d79b0] [0000000000000001] 0x1 (unreliable)
> [  740.147978] [c0000002243d7a40] [d00000000061ba48] .radeon_driver_lastclose+0x48/0x90 [radeon]
> [  740.147992] [c0000002243d7ac0] [d0000000005d4c48] .drm_lastclose+0x78/0x510 [drm]
> [  740.148016] [c0000002243d7b80] [d0000000005d6278] .drm_release+0x528/0x6f0 [drm]
> [  740.148037] [c0000002243d7c50] [c0000000000c6eb8] .__fput+0xf8/0x230
> [  740.148047] [c0000002243d7d00] [c0000000000c2dc0] .filp_close+0xa0/0x100
> [  740.148054] [c0000002243d7d90] [c0000000000c4cfc] .sys_close+0xbc/0x170
> [  740.148061] [c0000002243d7e30] [c0000000000086ac] syscall_exit+0x0/0x40

It would be interesting to know where exactly in
radeon_driver_lastclose() it's tripping over. Can you add some debugging
output, e.g. with DRM_INFO()? Also, writing 1
to /sys/module/drm/parameters/debug before reproducing the problem might
provide additional information.


-- 
Earthling Michel Dänzer           |          http://tungstengraphics.com
Libre software enthusiast         |          Debian, X and DRI developer