Re: xdm locks up keyboard and hogs cpu
--- Donald Spoon <dspoon@astcomm.net> wrote:
>
> problems, as you point out. I would "suspect" it is
> a configuration
> issue, since some installs work OK (at least one I
> know about..mine :)
>
> I am talking here about that portion of XDM/GDM/KDM
> that allows you to
> display remote computer"s on your screen
> (multi-user, multi-computer).
> If you are having problems with just getting XDM
> /GDM / KDM to run as a
> Display Manager in a multi-user/single-computer
> mode, the I would even
> more strongly suspect a config problem. However,
> since I am running
> "testing" here for X, I cannot absolutely rule out a
> bug in your
> software....
>
> From the above, the initial possible "differences"
> I see are the following:
>
> 1. I am using a mix of testing/unstable. X is from
> the "testing' tree.
> 2. I always use "dpkg-reconfigure xserver-xfree86"
> to set up my X
> installs instead of xf86cfg (??).
> 3. My use is not full-time, but somewhat
> intermittant. Definately not
> a "production" environment like you would see in a
> University computer
> lab for example.
> 4. Hardware?? (particular video cards, etc.)
>
> I would be happy to work with you, either on-list or
> off-list, by
> comparing systems and setup proceedures to detect
> any differences. That
> might help isolate the "problem" area. I am not a
> "guru", especially on
> X, but I do have a "working" system! Even IF it
> ultimately is a config
> problem, I believe the XDM/KDM/GDM setup docs are
> quite confusing and
> could use some work.
> Cheers,
> -Don Spoon-
My video card is a NVIDIA Riva TNT2. I should try
using the dpkg way of reconfiguring X, but I think all
that does is launch xf86config to do the
configuration. xf86cfg is just a more user friendly
config program that gives you a usable X configuration
in most cases. I think you might be right in that,
the problem is a configuration issue. More
specifically, I think it might be an xdm config issue
rather than an X issue. Also, I do not think its a
bug in X in unstable, I had the same luck with
earlier versions of X too. I did get xdm to work on a
NetBSD box just fine. One thing I noticed that was
different between xdm on NetBSD and Debian was that
NetBSD stored all its xdm configs in
/usr/X11R6/lib/X11/xdm, but Debian stores it both in
/usr/X11R6/lib/X11/xdm and /etc/X11/xdm (they refer to
each other and its a mess in debian). Could this be a
possible cause?
I did an strace on the process when it was locked up
and taking about 95% CPU and I found that it was stuck
in some kind of select loop. Here is an excerpt from
the output.
gettimeofday({1041297960, 882864}, NULL) = 0
select(256, [1 3 9 10 11], NULL, NULL, {292, 114000})
= 1 (in [3], left {292, 120000})
read(3, "", 64) = 0
gettimeofday({1041297960, 883119}, NULL) = 0
select(256, [1 3 9 10 11], NULL, NULL, {292, 113000})
= 1 (in [3], left {292, 120000})
read(3, "", 64) = 0
--- SIGALRM (Alarm clock) ---
setitimer(ITIMER_REAL, {it_interval={0, 0},
it_value={0, 0}}, NULL) = 0
sigreturn() = ? (mask now
[])
setitimer(ITIMER_REAL, {it_interval={0, 20000},
it_value={0, 20000}}, NULL) = 0
gettimeofday({1041297960, 883974}, NULL) = 0
select(256, [1 3 9 10 11], NULL, NULL, {292, 113000})
= 1 (in [3], left {292, 120000})
read(3, "", 64) = 0
gettimeofday({1041297960, 884240}, NULL) = 0
select(256, [1 3 9 10 11], NULL, NULL, {292, 112000})
= 1 (in [3], left {292, 120000})
read(3, "", 64) = 0
gettimeofday({1041297960, 884495}, NULL) = 0
select(256, [1 3 9 10 11], NULL, NULL, {292, 112000})
= 1 (in [3], left {292, 120000})
read(3, "", 64) = 0
gettimeofday({1041297960, 884750}, NULL) = 0
select(256, [1 3 9 10 11], NULL, NULL, {292, 112000})
= 1 (in [3], left {292, 120000})
read(3, "", 64) = 0
Donald: I don't mind working offline, would you be on
OPN by any chance?
Thank you,
Aravind.
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
Reply to: