From: "Alexandre P. Nunes" <alex@PolesApart.wox.org>
To: linux-kernel@vger.kernel.org
Subject: NVidia proprietary driver problem? Read this.
Date: Tue, 25 Jun 2002 10:35:45 -0300 [thread overview]
Message-ID: <3D1871B1.2000002@PolesApart.wox.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 314 bytes --]
Hi all,
I'm forwarding an email i've got from nvidia. All linux users having
problems with the NVdriver and that are able to supply the information
Christian is asking me in this forwarded email, are encouraged to sent
this information directly to him.
Please read the forwarded message.
Cheers,
Alexandre
[-- Attachment #2: Re: NVidia + kernel panic discussion at linux kernel list. --]
[-- Type: message/rfc822, Size: 3543 bytes --]
From: Christian Zander <CZander@nvidia.com>
To: "Alexandre P. Nunes" <alex@polesapart.dhs.org>
Cc: linux-bugs@nvidia.com
Subject: Re: NVidia + kernel panic discussion at linux kernel list.
Date: Mon, 24 Jun 2002 13:43:41 -0700
Message-ID: <20020624204341.GI10204@goblin>
On Mon, Jun 24, 2002 at 11:38:34AM -0300, Alexandre P. Nunes wrote:
>
> Someone please read the thread:
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=102479554629270&w=2
>
> Including the replies.
>
Please provide me with the following pieces of information:
- your system's hardware configuration
- a list of the loaded modules
- the kernel version
- your current kernel's configuration file
- the development tools used to build it (gcc, binutils, etc)
- the shortest way to reproduce the problem
- the exact BUG message, if possible a ksymoops decoded trace
- any relevant log files
- whatever else you can think of that might help
The more information you can provide, the better; I can't currently
reproduce the problem, however I have had reports from other users
experiencing it. If you know other users with this problem and have
a way to contact them, please ask them to send me these bits of
information as well. One user reported that he could not reproduce
the problem with 2.5 series kernels; I do not encourage you to use
2.5 at this point, but if you feel adventurous, it would be helpful
to know how 2.5 works for you.
Thanks,
--
christian zander
czander@nvidia.com
reply other threads:[~2002-06-25 13:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3D1871B1.2000002@PolesApart.wox.org \
--to=alex@polesapart.wox.org \
--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