From: Ryan Cumming <bodnar42@phalynx.dhs.org>
To: Curt McCutchin <sitruc@mailandnews.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Another wonderful OOPS!
Date: Mon, 19 Nov 2001 22:03:08 -0800 [thread overview]
Message-ID: <E1663zw-0001ek-00@localhost> (raw)
In-Reply-To: <20011119224528.3fae4411.sitruc@mailandnews.com>
In-Reply-To: <20011119224528.3fae4411.sitruc@mailandnews.com>
On November 19, 2001 20:45, Curt McCutchin wrote:
> I hope this is helpful this time.
> system stats in case they matter:
>
> hardwarewise:
> -------------
...
> -hercules geforce 2 mx 32mb video card
...
> softwarewise:
> -------------
...
> -NVidia 1.0-1541 driver
...
> Nov 19 21:10:42 snotball kernel: Process XFree86 (pid: 220,
stackpage=d58f7000)
....
You're going to recieve very little help from this list for debugging an
XFree86 crash using a binary-only driver. Although this sort of driver are
almost always the source of XFree86 problems, I'm sure this list would be
more than happy to help if you are able to reproduce the problem using
official, open source Linux drivers.
-Ruan
next prev parent reply other threads:[~2001-11-20 6:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 4:45 Another wonderful OOPS! Curt McCutchin
2001-11-20 6:03 ` Ryan Cumming [this message]
2001-11-20 6:39 ` Another wonderful OOPS! (why not tainted?) andrew may
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=E1663zw-0001ek-00@localhost \
--to=bodnar42@phalynx.dhs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sitruc@mailandnews.com \
/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