Summary: | ati driver sleeps for 1 second every 6 seconds with LCD display panel | ||
---|---|---|---|
Product: | xorg | Reporter: | registering on bugzilla vs greylisting steeeeeenks <stuff> |
Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> |
Status: | RESOLVED NOTOURBUG | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | normal | ||
Priority: | medium | CC: | stuff, tjaalton |
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
registering on bugzilla vs greylisting steeeeeenks
2008-03-04 11:33:51 UTC
(In reply to comment #0) > I have Dell Latitude C640 with an ATI display card and a LCD display (a normal > feature for a laptop, if you ask me). With the ATI driver for xorg that ships > with ubuntu as xserver-xorg-video-ati_6.7.195-1ubuntu2_i386.deb, I got > stop-start behaviour. Every 6 seconds, there was a small delay. > > In my Xorg.0.log I get this every 6 seconds too: > > enable montype: 2 > enable montype: 2 > enable montype: 2 > enable montype: 2 > enable montype: 2 > enable montype: 2 The driver doesn't do this by default. It sounds like ubuntu must have process running that does something every 6 seconds. > I suspect that the "usleep" was put there for a reason, but it was not > anticipated that it would get called every time the x server > checks whether a new monitor has been attached. (Conceivably > radeon_output->PanelPwrDly = 0 ; could work better) The usleep is required to to bring the panel up reliably. Tell more about your setup; -what desktop environment do you use (GNOME, KDE, ?) -can you see the same with a vanilla installation (livecd should be close enough) and please attach the output of 'ps auxwww' from a normal session. The laptop in question has suffered decelleration trauma, and my installation has gone to hard disk heaven. I'll see if I can produce the behaviour on a new installation and hard disk on the same system and try to pin down which process causes it - but it will take a while. The system was set up with KDE, and the one strange thing I did was to enable XAA for transparency .. briefly - before discovering that I don't really have memory to handle things like this. While diagnosing the fault, I did kill every non-essential process (e.g. hal-storage, KDE power saving, etc), which had no effect. please re-open if this is still an issue. I suspect kde is polling for monitors. |
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.