Description: Xorg goes crazy tapping my cpu usage when I compile via makepkg on my Arch x86_64 box inside a 32-bit chroot. For example, >60 % of the total CPU is going to Xorg rather than to gcc (running Gnome if that matters). The htop screenshot below shows X and gdm using it. I know that if I start gnome from init 3 without gdm the same problem occurs except htop just shows X as the culprit.

Further, packages fail to build when I run makepkg through X (again in the 32-bit chroot). If I run makepkg when I'm in init 3 without X at all, the very same package successfully builds. If I leave myself logged into Gnome and open tty1 and enter the 32-bit chroot there, it builds just fine.

Any thoughts why? That has to be a bug in Xorg given the conditions I explained above, but what I don't know if it's something unique to the Arch pacakges or if it's in upstream.

Screenshot of htop:
http://img440.imageshack.us/img440/4202/wtfwh.jpg

I entered the 32-bit chroot via: linux32 chroot /opt/arch32 /bin/bash

Additional info:
* package version(s) --> xorg-server-1.9
* config and/or log files etc. --> Xorg.0.log contains nothing relevant but I can post it upon request. Nothing in dmesg either.


Steps to reproduce:

*Setup a 32-bit chroot on Arch 86_64 in Gnome as described above.
*From within the chroot, attempt to build the kernel26-ck package from the AUR.
*Look at your htop readings to see if X is taking up the CPU cycles and wait as the build fails.
*You may repeat from a tty outside of X and will see that it builds successfully.