linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Prakash K. Cheemplavam" <prakashpublic@gmx.de>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6-test9-mm1, nptl and nvidia issue
Date: Mon, 03 Nov 2003 18:05:24 +0100	[thread overview]
Message-ID: <3FA68AD4.6040803@gmx.de> (raw)
In-Reply-To: <200311031529.03820.bzolnier@elka.pw.edu.pl>

Bartlomiej Zolnierkiewicz wrote:
> Hi,
> 
> Please try to reproduce problem without nvidia _binary only_ module loaded.
> 
> <...>
> 
>>nvidia: no version magic, tainting kernel.
>>nvidia: module license 'NVIDIA' taints kernel.
>>0: nvidia: loading NVIDIA Linux x86 nvidia.o Kernel Module  1.0-4496
> <...>
>>  [<f9a65dc9>] nv_kern_open+0xf3/0x228 [nvidia]
> <...>
>>  [<f9a7b377>] __nvsym00568+0x1f/0x2c [nvidia]
>>  [<f9a7d496>] __nvsym00775+0x6e/0xe0 [nvidia]
>>  [<f9a7d526>] __nvsym00781+0x1e/0x190 [nvidia]
>>  [<f9a7efac>] rm_init_adapter+0xc/0x10 [nvidia]
>>  [<f9a65dc9>] nv_kern_open+0xf3/0x228 [nvidia]

The problem doesn't appear with th GPL nv driver. Strange enough again 
with the nvidia binary driver, after several recompilings of the kernel 
the trace calls don't seem to appear but following message on modprobe 
(or perhaps it came that this time I manually loaded the module):
nvidia: no version magic, tainting kernel.
nvidia: module license 'NVIDIA' taints kernel.
nvidia: Unknown symbol __might_sleep
nvidia: no version magic, tainting kernel.
nvidia: module license 'NVIDIA' taints kernel.
0: nvidia: loading NVIDIA Linux x86 nvidia.o Kernel Module  1.0-4496 
Wed Jul 16 19:03:09 PDT 2003


So should i ask nvidia to compile a new driver or is this an issue with 
current kernel?

Prakash





      parent reply	other threads:[~2003-11-03 17:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03 12:39 2.6-test9-mm1, nptl and nvidia issue Prakash K. Cheemplavam
     [not found] ` <200311031529.03820.bzolnier@elka.pw.edu.pl>
2003-11-03 17:05   ` Prakash K. Cheemplavam [this message]

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=3FA68AD4.6040803@gmx.de \
    --to=prakashpublic@gmx.de \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --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;
as well as URLs for NNTP newsgroup(s).