Sebastien Roy wrote: >>> Is there a CR filed against Xorg that I can look at? >> I wonder, is this a regression? With Xorg, did powertop report 100% highest >> p-state residency on b121 and previous version? > > That's a yes for build 121, but powertop didn't work at all in the other > builds I had running on this laptop (something about missing dtrace > probes). I don't remember noticing this until recently, so it's > possible that this was introduced at some point after build 118 (the > build I had running before 121). > >> If this is a regression, we need to ask Xorg guys what they did to hurt >> idle power, :) > > Or at least some help root-causing this. We don't know if the cause is > the X server or a client issuing X requests for no reason (I suspect > it's the latter)... I wrote a little dtrace script that dumps X > requests, and on an idle system, I see hundreds of X requests every > second from X client ID 43. Now how do I map that to a process ID?
My first question would be have you installed the run-away GNOME program fix that Ghee posted last week? http://mail.opensolaris.org/pipermail/opensolaris-discuss/2009-September/050070.html Otherwise, the only way to turn an X client id into a process id is to either be tracing when it connects, or walk the server internal structures in a debugger. Unfortunately, we don't deliver with the -g information in the X server, and aren't allowed to ship CTF data, so you'd have to rebuild the X server from source to get the data structure info. -- -Alan Coopersmith- alan.coopersmith at sun.com Sun Microsystems, Inc. - X Window System Engineering
