# print modification TSs, to verify log refers to said conf file
# stat -c %y /etc/X11/xorg.conf /var/log/Xorg.0.log
2010-05-16 11:01:33.231512534 +0300
2010-05-16 12:23:02.502995953 +0300


On 05/16/10 22:15, walt wrote:
> On 05/16/2010 01:12 AM, Amit Dor-Shifer wrote:
>>
>>
>
>> Explicitly setting Driver to "evdev" (to both mouse and keyboard 
>> sections) doesn't
> > fix the unexplained messages in Xorg.0.log. At least X manages to 
> start, though.
>
> I'm expecting that your newest Xorg log will be different from the 
> earlier ones.
> Which messages do you mean?
<Xorg.0.log>
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc104"
(**) Option "xkb_layout" "en_US,ru"
(**) Option "xkb_variant" ",winkeys"
(**) Option "xkb_options" "grp:shift_toggle,grp_led:scroll"
</Xorg.0.log>

That quite the same as those I had in the beginning.
>
>> I'm now noticing another problem: X's CPU usage sky-rockets when 
>> using input devices.
> > Especially mouse: If I move my pointer around the screen, hovering 
> over some windows
> > in the process, I get >50% CPU in 'top'.
>
> I've never seen that before.  Does hovering over xev print any messages?
>
>
Well, I'm less inclined to think now that X is responsible for the high 
CPU load. I wasn't too knowledgeable about the relationships between X 
and its clients when I made my initial assumption. It was more like "I 
startx + I move mouse + CPU shoots-up => it's X".

Looks more like kde is rocking my CPU. Indeed, xev doesn't print 
anything while I'm generating high CPU with mouse movements. Also, I had 
a notion twm didn't exhibit the phenomenon as long as I didn't execute 
any kde apps. But I'm not 100% sure about the latter experiment.

I'm runing KDE 3.5.10.

Amit