Re: [r300] Lockups

2006-03-14 Thread Sergio Monteiro Basto
Hi, Sorry Reading better this patch is for drm kernel On Tue, 2006-03-14 at 17:17 +, Sergio Monteiro Basto wrote: > Hi, > > https://bugs.freedesktop.org/show_bug.cgi?id=5095#c7 > > Seems this bug is the same problem. > > Let me know if you have any progress > > On Fri, 2006-03-10 at 15:

Re: [r300] Lockups

2006-03-14 Thread Sergio Monteiro Basto
Hi, https://bugs.freedesktop.org/show_bug.cgi?id=5095#c7 Seems this bug is the same problem. Let me know if you have any progress On Fri, 2006-03-10 at 15:19 +0100, Christoph Brill wrote: > > > Will give it a try if one points me out where to get the patch. -- Sérgio M.B. smime.p7s Descr

Re: [r300] Lockups

2006-03-14 Thread Benjamin Herrenschmidt
On Fri, 2006-03-10 at 10:12 +, Aapo Tahkola wrote: > On Thu, 02 Mar 2006 09:27:37 +0100 > Christoph Brill <[EMAIL PROTECTED]> wrote: > > > Hi list, > > > > I'm still seeing lots of lockups with my r300 (Radeon 9700Pro) with > > current drm/mesa/xf86-video-ati cvs. I think I found a reproduca

Re: [r300] Lockups

2006-03-10 Thread Christoph Brill
Jerome Glisse schrieb: In the meantime, if you use lastet Benh patch and set agp speed to 1 and no fastwrite or other fency options you should have something a bit more stable at least which doesn't lockup in the minute... Will give it a try if one points me out where to get the patch. ---

Re: [r300] Lockups

2006-03-10 Thread Jerome Glisse
On 3/10/06, Adam K Kirchhoff <[EMAIL PROTECTED]> wrote: > Aapo Tahkola wrote: > > > >As long as it gets solved by initializing the card with fglrx, I don't see > >any point in investigating. > > > > At the risk of becoming quite unpopular around here, I have to question > that reasoning. Saying t

Re: [r300] Lockups

2006-03-10 Thread Adam K Kirchhoff
Aapo Tahkola wrote: On Thu, 02 Mar 2006 09:27:37 +0100 Christoph Brill <[EMAIL PROTECTED]> wrote: Hi list, I'm still seeing lots of lockups with my r300 (Radeon 9700Pro) with current drm/mesa/xf86-video-ati cvs. I think I found a reproducable lockup. It happens when I use Wings3d[1] (a f

Re: [r300] Lockups

2006-03-10 Thread Christoph Brill
Aapo Tahkola schrieb: On Thu, 02 Mar 2006 09:27:37 +0100 Christoph Brill <[EMAIL PROTECTED]> wrote: Hi list, I'm still seeing lots of lockups with my r300 (Radeon 9700Pro) with current drm/mesa/xf86-video-ati cvs. I think I found a reproducable lockup. It happens when I use Wings3d[1] (a

Re: [r300] Lockups

2006-03-10 Thread Aapo Tahkola
On Thu, 02 Mar 2006 09:27:37 +0100 Christoph Brill <[EMAIL PROTECTED]> wrote: > Hi list, > > I'm still seeing lots of lockups with my r300 (Radeon 9700Pro) with > current drm/mesa/xf86-video-ati cvs. I think I found a reproducable > lockup. It happens when I use Wings3d[1] (a free modeller). Wi

Re: R300 lockups...

2005-03-04 Thread Adam K Kirchhoff
Nicolai Haehnle wrote: On Tuesday 22 February 2005 21:57, Adam K Kirchhoff wrote: No luck. I setup my xorg.conf file to limit X to 640x480, and used xrandr to drop the refresh rate to 60... Launched neverputt at 640x480, fullscreen. Lockup was nearly instantaneous... The music continues, a

Re: R300 lockups...

2005-02-22 Thread Nicolai Haehnle
On Tuesday 22 February 2005 21:57, Adam K Kirchhoff wrote: > No luck. I setup my xorg.conf file to limit X to 640x480, and used > xrandr to drop the refresh rate to 60... Launched neverputt at 640x480, > fullscreen. Lockup was nearly instantaneous... The music continues, at > least till neve

Re: R300 lockups...

2005-02-22 Thread Adam K Kirchhoff
Vladimir Dergachev wrote: On Mon, 21 Feb 2005, Adam K Kirchhoff wrote: FYI, I've now tried neverputt in a window, instead of fullscreen, and I'm getting the same lockups as I was previously getting (full lockups, including mouse, requiring me to ssh in a reboot). It finally occurred to me to ch

Re: R300 lockups...

2005-02-21 Thread Vladimir Dergachev
On Mon, 21 Feb 2005, Adam K Kirchhoff wrote: FYI, I've now tried neverputt in a window, instead of fullscreen, and I'm getting the same lockups as I was previously getting (full lockups, including mouse, requiring me to ssh in a reboot). It finally occurred to me to check dmesg: [drm:radeon_cp