Bug#549335: xorg: DRI/DRM hangs machine for ati/r128 driver (squeeze;powerpc)
reassign 549335 linux-2.6 2.6.30-6
close 549335 2.6.30-7
kthxbye
On Fri, Oct 2, 2009 at 13:31:36 -0400, Jeffrey B. Green wrote:
> [ 59.363422] [drm] Initialized drm 1.1.0 20060810
> [ 59.400604] [drm] Initialized r128 2.5.0 20030725 for 0000:00:10.0 on minor 0
> [ 59.484082] agpgart-uninorth 0000:00:0b.0: putting AGP V2 device into 1x mode
> [ 59.484117] aty128fb 0000:00:10.0: putting AGP V2 device into 1x mode
> [ 59.924656] platform r128_cce.0: firmware: requesting r128/r128_cce.bin
> [ 60.042432] r128_cce: Failed to load firmware "r128/r128_cce.bin"
> [ 60.042465] [drm:r128_do_init_cce] *ERROR* Failed to load firmware!
> [ 60.042655] Unable to handle kernel paging request for data at address 0x00000094
> [ 60.042671] Faulting instruction address: 0xea0c1afc
> [ 60.042691] Oops: Kernel access of bad area, sig: 11 [#1]
> [ 60.042703] PowerMac
> [ 60.042711] Modules linked in: r128 drm nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc joydev airport wacom evdev orinoco ext3 jbd mbcache dm_mod usbhid hid aic7xxx scsi_transport_spi firewire_ohci sungem sungem_phy firewire_core crc_itu_t ide_cd_mod cdrom scsi_mod uninorth_agp agpgart i2c_powermac [last unloaded: scsi_wait_scan]
> [ 60.042855] NIP: ea0c1afc LR: ea09a228 CTR: ea0c1a54
> [ 60.042875] REGS: c1f61d20 TRAP: 0300 Not tainted (2.6.30-1-powerpc)
> [ 60.042888] MSR: 00009032 <EE,ME,IR,DR> CR: 20042444 XER: 20000000
> [ 60.042921] DAR: 00000094, DSISR: 40000000
> [ 60.042936] TASK = e7873510[2303] 'Xorg' THREAD: c1f60000
> [ 60.042947] GPR00: 00000001 c1f61dd0 e7873510 e5f40000 c1f61df8 c1e33840 e9070000 0fadc568
> [ 60.042983] GPR08: 00000000 c1e337e0 80086442 00000004 00000000 101eccc0 101adde0 101addec
> [ 60.043018] GPR16: 10070ef0 101e4d28 101e4d2c 1008bf50 1009bb50 00000001 bfc2e85c 00000000
> [ 60.043053] GPR24: 109d2e18 e5f40000 ea0c1a54 80086442 e5f40000 c1f61df8 c1e33840 00000000
> [ 60.043136] NIP [ea0c1afc] r128_cce_stop+0xa8/0x14c [r128]
> [ 60.043327] LR [ea09a228] drm_ioctl+0x250/0x36c [drm]
> [ 60.043339] Call Trace:
> [ 60.043376] [c1f61dd0] [c009cef4] generic_file_aio_write+0x74/0xf0 (unreliable)
> [ 60.043455] [c1f61df0] [ea09a228] drm_ioctl+0x250/0x36c [drm]
> [ 60.043481] [c1f61ea0] [c00d4428] vfs_ioctl+0x68/0x80
> [ 60.043501] [c1f61eb0] [c00d4a2c] do_vfs_ioctl+0x5c8/0x664
> [ 60.043522] [c1f61f10] [c00d4b20] sys_ioctl+0x58/0x88
> [ 60.043547] [c1f61f40] [c0014df8] ret_from_syscall+0x0/0x40
> [ 60.043575] --- Exception: c01 at 0xfadc568
> [ 60.043582] LR = 0xfadc4cc
> [ 60.043592] Instruction dump:
> [ 60.043606] 80e90040 38638564 38840054 54c60000 7fc8f378 7c852378 480064dd 3860ffea
> [ 60.043642] 480000a0 801d0000 2f800000 419e0038 <813f0094> 81290010 39290714 7c0004ac
> [ 60.043686] ---[ end trace 88264052174689a3 ]---
> [ 60.057198] [drm:drm_release] *ERROR* Device busy: 1
Thanks for the log.
This is likely a duplicate of bug#541630, which is fixed in the kernel
package in unstable. You'll probably also want to install the
firmware-linux package, which will provide the necessary firmware to
enable DRI on your hardware.
Cheers,
Julien
Reply to: