linux-kernel - Re: Woke up to a crashed kernet this morning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <898083.40014.qm@web52507.mail.re2.yahoo.com>
Date:	Thu, 2 Aug 2007 07:46:49 -0700 (PDT)
From:	Marc Perkel <mperkel@...oo.com>
To:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Woke up to a crashed kernet this morning - nVidia is crap

OK - so the driver I downloaded from nVidia to fix
their problem I was having with the video installed
drivers for everything? I'm really getting to dislike
nVidia.


--- Michal Piotrowski
<michal.k.k.piotrowski@...il.com> wrote:

> 
> Nvidia binary crap
> 
> "    When you are using a binary driver, the kernel
> is "tainted",
> which means that the source
> of possible problems may be unrelated to the kernel
> code (see
> https://secure-support.
>
novell.com/KanisaPlatform/Publishing/250/3582750_f.SAL_Public.html
> for more de-
> tails). You can check whether or not the kernel was
> tainted when the
> problem occurred by
> looking at the corresponding error message. If can
> you see something
> similar to the following
> line:
> EIP:       0060:[<c046c7c3>]        Tainted: P     
> VLI
> (the word Tainted is crucial here), the kernel was
> tainted and most
> probably the kernel
> developers will not be able to help you. In that
> case you should try
> to reproduce the problem
> without the binary driver loaded. Moreover, if the
> problem does not
> occur without it, you
> should send a bug report to the creators of the
> binary driver and ask
> them to ï¬x it.
>     In the ï¬le Documentation/oops-tracing.txt,
> included in the kernel
> sources, there is a
> list of reasons why the kernel can be considered as
> tainted. As
> follows from this document,
> the presence of a binary module is not the only
> possible reason of
> tainting the kernel, but
> in practice it turns out to be the most frequent
> one. Generally, you
> should avoid reporting
> problems in tainted kernels to the LKML (or to the
> kernel developers
> in general) and the
> problems related to binary drivers should be
> reported to their providers."
> 
> -- Linux Kernel Tester's Guide
> 
> Regards,
> Michal
> 
> -- 
> LOG
> http://www.stardust.webpages.pl/log/
> 



       
____________________________________________________________________________________
Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games.
http://sims.yahoo.com/  
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/