public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Riveira Fernández" <ariveira@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.28-rc7
Date: Tue, 2 Dec 2008 16:56:37 +0100	[thread overview]
Message-ID: <20081202165637.09984819@varda> (raw)
In-Reply-To: <alpine.LFD.2.00.0812020748310.3256@nehalem.linux-foundation.org>

El Tue, 2 Dec 2008 07:50:05 -0800 (PST)
Linus Torvalds <torvalds@linux-foundation.org> escribió:

> 
> 
> On Tue, 2 Dec 2008, Alejandro Riveira Fernández wrote:
> >  
> >  All of this happens without the nvidia module loaded (not even compiled) 
> 
> It's definitely loaded according to your dmesg:
> 
> > [    0.000000] Linux version 2.6.28-rc7 (alex@varda) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #2 SMP PREEMPT Tue Dec 2 12:48:19 CET 2008
> ...
> > [  101.744347] nvidia: module license 'NVIDIA' taints kernel.
> > [  102.003828] nvidia 0000:01:00.0: PCI INT A -> GSI 25 (level, low) -> IRQ 25
> > [  102.003838] nvidia 0000:01:00.0: setting latency timer to 64
> > [  102.004747] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  180.06  Sat Nov  8 17:50:38 PST 2008
> 
> Hmm?? Can you double-check?

 from my reply to pazke <pazke@ports.donpac.ru>
 "
I took the sanpshot of the dmesg after loading the module if my word is not
enough i can reboot with the module disabled but i do not see the point...
The truth is that the bug prevented me from loading/installing the nvidia
module becouse i could not use sudo. Only when i rebooted into single mode
where the problems went away i could build and install the module...
"

> 
> 		Linus

 Thanks for you time


  reply	other threads:[~2008-12-02 15:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02  4:11 Linux 2.6.28-rc7 Linus Torvalds
2008-12-02 12:14 ` Alejandro Riveira Fernández
2008-12-02 13:11   ` pazke
2008-12-02 14:48     ` Alejandro Riveira Fernández
2008-12-02 15:20       ` Alistair John Strachan
2008-12-02 15:50         ` Alejandro Riveira Fernández
2008-12-02 16:14           ` Alistair John Strachan
2008-12-02 15:54         ` Alejandro Riveira Fernández
2008-12-02 15:50   ` Linus Torvalds
2008-12-02 15:56     ` Alejandro Riveira Fernández [this message]
2008-12-02 16:13       ` Linus Torvalds
2008-12-02 16:29         ` About git-bisect (was: Linux 2.6.28-rc7) Renato S. Yamane
2008-12-02 16:55           ` Sam Ravnborg
2008-12-02 17:05             ` Linus Torvalds
2008-12-02 17:01           ` Linus Torvalds
2008-12-02 18:49         ` Linux 2.6.28-rc7 Alejandro Riveira Fernández
2008-12-02 19:22           ` Alejandro Riveira Fernández
2008-12-02 19:23           ` Linus Torvalds
2008-12-02 19:45             ` Alejandro Riveira Fernández
2008-12-02 20:40               ` Linus Torvalds
2008-12-02 20:29             ` Al Viro
     [not found] <fa.IDjfwzrT2B02+NHfmYwtICnzOOA@ifi.uio.no>
     [not found] ` <fa.J8MFTCUT8El3sK8BuYDBvaMRaB8@ifi.uio.no>
     [not found]   ` <fa.q/4H3AtoJGSJ+i8tlXR4X35LFFU@ifi.uio.no>
     [not found]     ` <fa.98CeSgxJ/GGaLLyZ97s1oHgh7hE@ifi.uio.no>
2008-12-02 17:11       ` Michael B. Trausch
2008-12-02 18:06         ` Alejandro Riveira Fernández
2008-12-02 18:56           ` Michael B. Trausch

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=20081202165637.09984819@varda \
    --to=ariveira@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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