All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Markus Hästbacka" <midian@ihme.org>
To: Lukas Postupa <postupa@gmx.de>
Cc: Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: Nvidia kernel module and kernel 2.6
Date: Mon, 15 Dec 2003 22:39:17 +0200	[thread overview]
Message-ID: <1071520756.20738.5.camel@midux> (raw)
In-Reply-To: <1071519127.770.12.camel@linux>

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

On Mon, 2003-12-15 at 22:12, Lukas Postupa wrote:
> Hello,
> 
Hi!
> i'm using linux 2.6.0-test11-bk11 on Intel architecture (Celeron
> Coppermine) and nvidia kernel module 1.0-4620 for Nvidia GF FX 5200.
> Mttr registers are enabled.
> I applied appropriate patches from www.minion.de.
> After loading and using nvidia kernel module, dmesg shows this output:
> [...snip...]
I get these messages all the time with nvidia module, you can disable
these messages from the kernel configuration: "make menuconfig -> kernel
hacking -> sleep-inside-spinlock checking"
> 
> This always is happening on loading this module.
> I get same trouble with nvidia kernel module 1.0-4496.
> I never had such problems with kernel 2.4 before.
> 
You pribably didn't have that option enabled in the 2.4 kernel.
I don't know about the danger of this message, but it haven't caused me
any problems

Regards,
Markus
-- 
"Software is like sex, it's better when it's free."
Markus Hästbacka <midian at ihme dot org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-12-15 20:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-15 20:12 Nvidia kernel module and kernel 2.6 Lukas Postupa
2003-12-15 20:39 ` Markus Hästbacka [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=1071520756.20738.5.camel@midux \
    --to=midian@ihme.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=postupa@gmx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.