l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2003 Jan 24 13:03

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] xdm died unprovokedly
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] xdm died unprovokedly

> Date: Fri, 24 Jan 2003 04:39:14 +0000
> From: "Karsten M. Self" <kmself@ix.netcom.com>
> To: vox-tech@lists.lugod.org
> Subject: Re: [vox-tech] xdm died unprovokedly
> Reply-To: vox-tech@lists.lugod.org
> on Thu, Jan 23, 2003 at 08:00:46PM -0800, Ken Bloom (kabloom@ucdavis.edu) wrote:
> > I left my computer for an hour and a half to eat dinner and attend an 
> > important meeting and while I was gone XDM died without a trace, except 
> > for the contents of /var/log/xdm.log, and I had to go root to restart 
> > XDM. This has happened to me once before that I am aware of.
> > 
> > I have enclosed /var/log/xdm.log. Does anybody have any idea what my 
> > problem might be? 
> > 
> > (Come to think of it, I'm about to upgrade to -4 from unstable, which 
> > says it "fixes server crash when a screen fails to initialise". I wonder 
> > if this is what's happening.)
> > 
> <...>
> > GetModeLine - hdsp: 1280 hbeg: 1328 hend: 1440 httl: 1688
> >               vdsp: 1024 vbeg: 1025 vend: 1028 vttl: 1066 flags: 5
> > xdm error (pid 295): Server for display :0 terminated unexpectedly: 0
> > xdm error (pid 295): Unknown session exit code 2816 from process 4200
> A few suggestions:
>   - Is this a reproduceable error?  If it doesn't happen again, ignore
>     it.  There are occasional app failures which can bring down X.
>   - How long have you been using this configuration?  Any prior errors?
>   - I've had bad luck with XF86v4 on some older video cards.  In
>     particular, one box would run (the other doesn't, at least not for
>     display results that qualify), but would crash the X server when
>     XDMCP screen blanking cut in.  The solution was to disable this
>     (both in XF86Config-4 and xscreensaver's config).  Note that this
>     blanking generally occurs after 10-15 minutes of inactivity.
>   - What app was it that crashed?  What was running on your X session at
>     the time?
>   - You might also investigate switching to XF86v3.
> Peace.

This time that I asked about it here was the second time it occurred. 
(The other time was two weeks ago) It only seems to happen when I'm
nowhere near the computer (so my only information about what happened
was the log I attached), and so far it has only happened while the
XServer has been showing the xdm login screen. I've been using the
configuration since August, at least. Unless you can use more
information to help troubleshoot it, I'll hope that updating from
4.2.1-3 to 4.2.1-5 out of unstable fixed the problem.

PGP/GPG Fingerprint: D5E2 8839 6ED3 3305 805C  941F 9476 A9BD E2B2 CAD1
Import with `gpg --keyserver pgp.mit.edu --recv-key E2B2CAD1`
Also on www: http://wwwcsif.cs.ucdavis.edu/~bloom/kabloom.asc
For more information about PGP and GPG, see http://www.gnupg.org/

Attachment: pgp00010.pgp
Description: PGP signature

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
O'Reilly and Associates
For numerous book donations.