[Dri-devel] Re: DRM+ATI-Radeon-Mobility

2004-02-10 Thread Greg Wilkins
Using the radeon.o driver from 2.4.22 with 2.4.24 avoids the problem. Looking at the diffs between the radeon code in 22 and 24 I see: + some new CP microcode + changes to the initialization of the scratch register pointer + changes to the radeon_do_init_pageflip method + changes to the radeon_

Re: [Dri-devel] Re: DRM+ATI-Radeon-Mobility

2004-02-10 Thread Michel Dänzer
On Tue, 2004-02-10 at 13:36, Greg Wilkins wrote: > I can confirm that doing a warm reboot from 4.2.22 to 4.2.24 > "solves" the problem and that glxgears works. Some random ideas to try and further track down the problem: * make a diff of drivers/char/drm between kernels 2.4.22 and 2

[Dri-devel] Re: DRM+ATI-Radeon-Mobility

2004-02-10 Thread Greg Wilkins
I can confirm that doing a warm reboot from 4.2.22 to 4.2.24 "solves" the problem and that glxgears works. Greg Wilkins wrote: I think I'm having a similar problem on my IBM a30p. I just upgraded the kernel from 2.4.22 to 2.4.24 and now DRI applications (eg glxgears) lock the machine up. I have no