[Bug 25799] New: (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI. with xf86-video-ati-6.12.4

2009-12-26 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=25799 Summary: (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI. with xf86-video-ati-6.12.4 Product: DRI Version: XOrg CVS Platform: x86 (IA32) OS/Version: Linux (All

Re: drm/radeon/kms: pm: single frame corruptions on reclocking

2009-12-26 Thread Rafał Miłecki
W dniu 26 grudnia 2009 02:46 użytkownik Rafał Miłecki napisał: > There are some my experiments with engine. Reclocking between: > 1) 110MHz and 680MHz - 1 corrupted frame on every reclock > 2) 200MHz and 680MHz - 1 corrupted frame on almost every reclock > 3) 250MHz and 680MHz - no corruptions > 4

[Bug 25799] (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI. with xf86-video-ati-6.12.4

2009-12-26 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=25799 Michel Dänzer changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

Re: drm/radeon/kms: pm: single frame corruptions on reclocking

2009-12-26 Thread Jerome Glisse
On Sat, Dec 26, 2009 at 02:46:29AM +0100, Rafał Miłecki wrote: > W dniu 24 grudnia 2009 08:19 użytkownik Michel Dänzer > napisał: > > I suspect the delay is more likely due to the workqueue than the > > interrupt itself. Way back when I implemented DRI1 tear-free buffer > > swaps for i945, I had t

Re: drm/radeon/kms: pm: single frame corruptions on reclocking

2009-12-26 Thread Rafał Miłecki
2009/12/26 Jerome Glisse : > What is the screen resolution ? It's 1600x900 panel driven by INTERNAL_KLDSCP_LVTMA. I guess you think about minimum clocks needed to drive my display, am I right? It could make sense if I would see general corruptions and not only at reclocking time. -- Rafał

Re: [PATCH] drm/radeon/kms: add dynamic engine reclocking (V9)

2009-12-26 Thread Luca Tettamanti
2009/12/25 Rafał Miłecki : > W dniu 24 grudnia 2009 23:19 użytkownik Luca Tettamanti > napisał: >> 2009/12/24 Rafał Miłecki : >>> W dniu 24 grudnia 2009 17:32 użytkownik Luca Tettamanti >>> napisał: I think it would be safer to execute that code in the IH (or in a tasklet, which is guar

[Bug 25490] kernel crash with 2.6.32, drm and kms enabled.

2009-12-26 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=25490 che...@kalri.org changed: What|Removed |Added CC||che...@kalri.org --- Comment #7 fro

[Bug 25490] kernel crash with 2.6.32, drm and kms enabled.

2009-12-26 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=25490 --- Comment #8 from dagg 2009-12-26 09:50:35 PST --- if you disable kms, your system will probably not freeze. since I've disabled it (kernel wise) the system didn't froze even once. -- Configure bugmail: http://bugs.freedesktop.org/userpr

[Bug 25776] [regression] crash on loading radeon module on 2.6.33-rc1 vanilla

2009-12-26 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=25776 --- Comment #3 from Alex Deucher 2009-12-26 10:55:19 PST --- (In reply to comment #2) > OK that's nice > but from 2.6.32.2 after init gfx i have black screen and on 2.6.32-rc8 not. > 2.6.32.2 is another issue. that's fixed with this patch

Re: drm/radeon/kms: pm: single frame corruptions on reclocking

2009-12-26 Thread Alex Deucher
2009/12/26 Rafał Miłecki : > W dniu 26 grudnia 2009 02:46 użytkownik Rafał Miłecki > napisał: >> There are some my experiments with engine. Reclocking between: >> 1) 110MHz and 680MHz - 1 corrupted frame on every reclock >> 2) 200MHz and 680MHz - 1 corrupted frame on almost every reclock >> 3) 250

Re: drm/radeon/kms: pm: single frame corruptions on reclocking

2009-12-26 Thread Rafał Miłecki
W dniu 26 grudnia 2009 20:08 użytkownik Alex Deucher napisał: > It may be that the engine doesn't like to be reclocked while it's > running.  Perhaps we should use the GUI idle interrupt rather than > vblanks to reclock the engine. Could you say something more about GUI idle interrupt, please? Wh