public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Tony Gale <gale@syntax.dera.gov.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.x SMP blamed for Xfree 4.0 crashes
Date: Tue, 13 Feb 2001 14:43:40 +0000	[thread overview]
Message-ID: <21887.982075420@redhat.com> (raw)
In-Reply-To: <XFMail.20010213130505.gale@syntax.dera.gov.uk>
In-Reply-To: <XFMail.20010213130505.gale@syntax.dera.gov.uk>


gale@syntax.dera.gov.uk said:
> 
>    This is a long-standing problem with 2.3 and 2.4 SMP kernels.  I
> believe it is a kernel bug and isn't the XFree86 project's problem.
> The problem does not exist on 2.2 SMP kernels nor on 2.3/4 UP kernels.
>  The symptoms are random segfaults in perfectly fine XFree86 code.

> Anyone looking into this?

I had an XFree86 setup which was perfectly stable in RH6.2, and had been 
for some months. Upon upgrading to RH7 - with glibc-2.2 and new 
screensavers, it started falling over almost every night.

The crashes got less frequent when I started running X against glibc-2.1
(note _running_ against glibc-2.1, not just compiling against it and running
against glibc-2.2). But they were still happening. 

In the week or so since killing xscreensaver, neither of the boxen on which
I was seeing this have fallen over. Another box on which I killed 
xscreensaver but didn't run X against glibc-2.1 is still suffering, albeit 
less frequently. 

Looks like two separate bugs - I see no reason to expect that there's only 
one such bug causing X to fall over :)

If others can try these remedies and confirm that they really do help, and
it's not just the statistics playing silly buggers with my brain, that'd 
hopefully give us some lead on getting it fixed.


passion /etc/X11 $ cat X
#!/bin/sh

logger "X restarting"
free | logger
cp /var/log/XFree86.0.log /var/log/XFree86.0.log-old
sync
sync
sync

exec /usr/i386-glibc21-linux/lib/ld-linux.so.2 --library-path /usr/i386-glibc21-linux/lib /usr/X11R6/bin/XFree86-4.0.2-glibc2.1 -modulepath /usr/X11R6/lib/modules-4.0.2-glibc2.1/ "$@"


--
dwmw2



  parent reply	other threads:[~2001-02-13 14:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-13 13:05 2.4.x SMP blamed for Xfree 4.0 crashes Tony Gale
2001-02-13 13:17 ` Alan Cox
2001-02-13 14:11   ` Tony Gale
2001-02-13 14:38   ` Zdenek Kabelac
2001-02-13 19:55   ` Rogerio Brito
2001-02-13 20:17     ` Aaron Dewell
2001-02-13 13:20 ` Richard B. Johnson
2001-02-13 17:01   ` David Howells
2001-02-13 14:43 ` David Woodhouse [this message]
2001-02-13 15:08   ` Tony Gale
2001-02-13 15:36 ` Pete Toscano
     [not found] <20010214085015.A29267@linuxcare.com>
     [not found] ` <Pine.GSO.4.10.10102131503190.3929-100000@spruce.woods.net>
2001-02-13 22:06   ` Anton Blanchard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21887.982075420@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=gale@syntax.dera.gov.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox