Radeon driver: 6.12.1 - Ubuntu Jaunty version Using powertop to measure wakeups. During normal mode, cpu enters c3-c4 states to save power. Approx. 10 wakeups/s. During screenblank this increases to approx 60/s. running 'xset dpms force off' Thus not letting the cpu enter c3-c4 states ! Hardware: Thinkpad T42, radeon 7500.
Please attach your xorg log and config. Also, what kernel and drm modules are you using?
Created attachment 25001 [details] Xorg.log with thinkpad attached to port replicator
Created attachment 25002 [details] xorg.conf
Kernel: Ubuntu Jaunty's Linux 2.6.28-11.42 DRM version (from 'dmesg | grep drm'): [ 20.392854] [drm] Initialized drm 1.1.0 20060810 [ 20.418107] [drm] Initialized radeon 1.29.0 20080528 on minor 0 [ 21.055228] [drm] Setting GART location based on new memory map [ 21.055238] [drm] Loading R100 Microcode [ 21.055294] [drm] writeback test succeeded in 2 usecs
I noticed it has been discussed on the mailinglist: http://www.mail-archive.com/dri-devel@lists.sourceforge.net/msg37843.html Did you ever find a solution?
Is this a bug in the xorg radeon driver, or in the drm module ? Any options I could try to workaround this ? Any other informations I should provide you ?
Drm version! Is it the libdrm package you mean? My libdrm version: 2.4.5 Is this fixed in later versions ?
(In reply to comment #6) > Is this a bug in the xorg radeon driver, or in the drm module ? The X driver I think, apparently it considers the CRTC disabled but it's still generating vertical blank interrupts. > Any options I could try to workaround this ? None that I know of unfortunately.
(In reply to comment #8) > The X driver I think, apparently it considers the CRTC disabled but it's still > generating vertical blank interrupts. Is this only a bug on specific hardware models or a generel bug? I think the 6.9.0 driver did properly disable my hardware (radeon 7500), but now it doesn't! I will be glad to help test any solution provided? This could give me approx. ½ hour more battery-time in my work conditions! Because I 'dpms off' as often as posible to save power.
(In reply to comment #9) > (In reply to comment #8) > > The X driver I think, apparently it considers the CRTC disabled but it's still > > generating vertical blank interrupts. > > Is this only a bug on specific hardware models or a generel bug? Not sure but I suspect it affects all Radeons, at least all pre-AVIVO ones. > I think the 6.9.0 driver did properly disable my hardware (radeon 7500), but > now it doesn't! Interesting, sounds like the old driver really disabled the CRTC while the current one leaves it somewhat enabled. Alex, does this give you any ideas?
(In reply to comment #10) > > Interesting, sounds like the old driver really disabled the CRTC while the > current one leaves it somewhat enabled. Alex, does this give you any ideas? > We never actually disabled the crtcs, just blank them it looks like. Same thing even with older versions of the driver, so I don't know how this ever worked in the past. I've just pushed a fix: 7d9f643ae3d07e51e644a5979ca90bc2c102bc89
(In reply to comment #11) > (In reply to comment #10) > > > > Interesting, sounds like the old driver really disabled the CRTC while the > > current one leaves it somewhat enabled. Alex, does this give you any ideas? > > > > We never actually disabled the crtcs, just blank them it looks like. Same > thing even with older versions of the driver, so I don't know how this ever > worked in the past. I've just pushed a fix: > 7d9f643ae3d07e51e644a5979ca90bc2c102bc89 > How do I compile a version to test with my ubuntu 9.04 setup?
(In reply to comment #12) > > How do I compile a version to test with my ubuntu 9.04 setup? > basic instructions here: http://www.botchco.com/agd5f/?page_id=2
Tormod Volden was so kind to put latest git in his launchpad ppa. https://launchpad.net/~tormodvolden/+archive/ppa I have testet your fix. WORKS GREAT! ;-) Power usage has dropped during dpms off. My hardware now uses approx 6.5 W when dpms off, thats 2 W less than before. Thank you for your great work.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.