Bug#216933: Workaround for the CMS bug

[Emmanuel Fleury <emmanuel.fleury@labri.fr>]

Hi,

I did investigate a bit further the problem.

When starting X on the laptop, the LCD display blank and stay in this
state. The network access allowed me to see what was happening. The
Xorg server is using 80-90% of the CPU power:

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 4298 root      25   0 29152 4896 3108 R 98.8  1.4   0:23.53 Xorg

The Xorg process is un-killable even with SIGKILL signal (9). So, I
obviously conclude that Xorg is waiting for something in the kernel.

I tried to downgrade from kernel 2.6.15 back to 2.6.14.5 (which was
previously working with the old Xorg) but it still behave the same.

When the system is asked to shutdown, the Xorg process seems to be the
last one to be killed (confirmation of the un-killable process).

I can't attach gdb to the Xorg process as it does not reply. I have to
try to strace it on my next attempt.

xserver-xorg   6.9.0.dfsg.1-4 the X.Org X server

Does somebody have the same behaviour or is just me ?

To be continued...
-- 
Emmanuel Fleury

The great difficulty in debugging: You have to divorce yourself
from preconceptions, make your mind blank, unlinked, unchanneld,
the Zen state ...
  -- Ellen Ullman (The Bug)