Re: xserver-xorg uses 100% CPU with Debian wheezy/sid
On Mon, Oct 24, 2011 at 05:37:39PM +0300, Timo Juhani Lindfors wrote: > Niccolo Rigacci writes: > > When I start X everything seems fine, but as I touch the screen > > the CPU usage by the X process, reaches 100%. > > This is a known issue I think. > > > X is starting on defaults, no xorg.conf file. > > How did you install the system? install.sh creates an xorg.conf that > does not use tslib. This is the origin of the problem: I installed from install.sh some months ago: several thigs went wrong and I had to manually adjust them. Following the notes by Nikolaus Schaller I wrote an xorg.conf which works nice, may be I will post it somewhere. Perhaps a note on Debian Wiki should be added too? -- Niccolo Rigacci Firenze - Italy Tel. ufficio: 055-0118525 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: xserver-xorg uses 100% CPU with Debian wheezy/sid
Niccolo Rigacci writes: > When I start X everything seems fine, but as I touch the screen > the CPU usage by the X process, reaches 100%. This is a known issue I think. > X is starting on defaults, no xorg.conf file. How did you install the system? install.sh creates an xorg.conf that does not use tslib. > I'm running Debian wheezy/sid on the OpenMoko GTA02, with the > following packages: > > linux-image-2.6.34-openmoko-gta02 20101212.git049b71de-2 > libts-0.0-0 1.0-9 > xserver-xorg-core 2:1.11.1.901-2 > xserver-xorg-input-tslib 0.0.6-7+b1 > xserver-xorg-input-evdev 1:2.6.0-2+b2 > udev 172-1 > hal 0.5.14-7 I think the problem is that both tslib and evdev drivers try to read the touchscreen. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: xserver-xorg uses 100% CPU with Debian wheezy/sid
Hi,
we recently had a similar symptom on the GTA04 with Debian/Squeeze so
I suspect the solution to be very similar.
It turned out to be a configuration problem of X in combination
with automatically mapping udev.
So we had to switch off the automatic mapping of all udev touchscreens
and mice as input devices, because the same device appears
twice. This can be traced down in the x-log.#
I do not exactly remember the details, but please look here and go into
the config files for X11:
http://download.goldelico.com/gta04/20110926-GTA04A3-HW-Tester/config.tgz
-- hns
Am 24.10.2011 um 14:43 schrieb Niccolo Rigacci:
> Hi,
>
> is someone else experiencing the same problem of mine?
>
> When I start X everything seems fine, but as I touch the screen
> the CPU usage by the X process, reaches 100%.
>
> I'm running Debian wheezy/sid on the OpenMoko GTA02, with the
> following packages:
>
> linux-image-2.6.34-openmoko-gta02 20101212.git049b71de-2
> libts-0.0-0 1.0-9
> xserver-xorg-core 2:1.11.1.901-2
> xserver-xorg-input-tslib 0.0.6-7+b1
> xserver-xorg-input-evdev 1:2.6.0-2+b2
> udev 172-1
> hal 0.5.14-7
>
> X is starting on defaults, no xorg.conf file.
>
> I tried also with any deamon stopped (the ones that I can stop),
> starting just X or startx, using fbdev or glamo driver: no
> changes.
>
> I also tried to revert libts-0.0-0 to 1.0-7, but it seems NO the
> same problem as Debian bugs #623095 or #623974.
>
> As soon I touch the screen, X emits this warning:
>
>selected device is not a touchscreen I understand
>
> but the pointer is indeed woring.
>
>
> If I strace X, I see this endless loop:
>
> select(256, [1 3 4 5 7 9 11 12], NULL, NULL, {569, 897000}) = 1 (in [12],
> left {569, 896900})
> rt_sigprocmask(SIG_BLOCK, [IO], [], 8) = 0
> rt_sigprocmask(SIG_UNBLOCK, [IO], NULL, 8) = 0
> clock_gettime(CLOCK_MONOTONIC, {1719, 218454002}) = 0
> clock_gettime(CLOCK_MONOTONIC, {1719, 219599002}) = 0
>
>
> --
> Niccolo Rigacci
> Firenze - Italy
> Tel. ufficio: 055-0118525
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
xserver-xorg uses 100% CPU with Debian wheezy/sid
Hi,
is someone else experiencing the same problem of mine?
When I start X everything seems fine, but as I touch the screen
the CPU usage by the X process, reaches 100%.
I'm running Debian wheezy/sid on the OpenMoko GTA02, with the
following packages:
linux-image-2.6.34-openmoko-gta02 20101212.git049b71de-2
libts-0.0-0 1.0-9
xserver-xorg-core 2:1.11.1.901-2
xserver-xorg-input-tslib 0.0.6-7+b1
xserver-xorg-input-evdev 1:2.6.0-2+b2
udev 172-1
hal 0.5.14-7
X is starting on defaults, no xorg.conf file.
I tried also with any deamon stopped (the ones that I can stop),
starting just X or startx, using fbdev or glamo driver: no
changes.
I also tried to revert libts-0.0-0 to 1.0-7, but it seems NO the
same problem as Debian bugs #623095 or #623974.
As soon I touch the screen, X emits this warning:
selected device is not a touchscreen I understand
but the pointer is indeed woring.
If I strace X, I see this endless loop:
select(256, [1 3 4 5 7 9 11 12], NULL, NULL, {569, 897000}) = 1 (in [12], left
{569, 896900})
rt_sigprocmask(SIG_BLOCK, [IO], [], 8) = 0
rt_sigprocmask(SIG_UNBLOCK, [IO], NULL, 8) = 0
clock_gettime(CLOCK_MONOTONIC, {1719, 218454002}) = 0
clock_gettime(CLOCK_MONOTONIC, {1719, 219599002}) = 0
--
Niccolo Rigacci
Firenze - Italy
Tel. ufficio: 055-0118525
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
