public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Toscano <pete@research.netsol.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.x SMP blamed for Xfree 4.0 crashes
Date: Tue, 13 Feb 2001 10:36:32 -0500	[thread overview]
Message-ID: <20010213103632.R15595@tesla.admin.cto.netsol.com> (raw)
In-Reply-To: <XFMail.20010213130505.gale@syntax.dera.gov.uk>
In-Reply-To: <XFMail.20010213130505.gale@syntax.dera.gov.uk>; from gale@syntax.dera.gov.uk on Tue, Feb 13, 2001 at 01:05:05PM -0000

[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]

i have been running 4.0.2 on my smp system using the 2.4.1 kernel.  the
one thing is, i was using the xfree out of precision insite's cvs with
the g400 binary-only hal lib dri module loaded.  every-so-often,
especially when closing windows or switching virtual desktops, the
kernel would crash.  luckily, i'm also running kdb on a serial console,
so i am able to check things out and keep a log.  unfortunately, when
btp all the processes, i found no text.lock, which is as far as i know
how to "debug" a kernel crash.

of course, this could very well be something wrong with the binary-only
module from matrox, so i'm seeing if the same problem presents itself
with the original mga.o loaded (which also disables hardware dri).

pete

On Tue, 13 Feb 2001, Tony Gale wrote:

> Having experienced a number of crashes with Xfree 4.0 with 2.4
> kernels, that I wasn't getting with 2.2 kernels, a quick search on
> the xfree Xpert mailing list reveals this:

-- 
Pete Toscano         pete@research.netsol.com          703.948.3364
GPG fingerprint: D8F5 A087 9A4C 56BB 8F78  B29C 1FF0 1BA7 9008 2736

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2001-02-13 15:37 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
2001-02-13 15:08   ` Tony Gale
2001-02-13 15:36 ` Pete Toscano [this message]
     [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=20010213103632.R15595@tesla.admin.cto.netsol.com \
    --to=pete@research.netsol.com \
    --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