Re: Nvidia Module Tainting Kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 02/21/18 08:23, Tim wrote:
> Allegedly, on or about 21 February 2018, Stephen Morris sent:
>> I been in the situation of compiling kernel modules in other linux 
>> distributions where you could put statements in your source to stop 
>> these messages, but I have forgotten what they were.
> A install is tainted by having certain kinds of things installed (in
> this case, binary support files that are not open-source).
>
> It will still be tainted (i.e. not suitable for providing bug reports
> to sources that need the computer to be running in a defined state),
> even if you try and pretend that it is not (faking the flags).
>
> To untaint a a kernel (e.g. for the purposes of debugging something),
> you have to stop using the modules that cause the tainting (you'd
> unload the Nvidia graphics driver and use a generic one, in this case).
>  If, after doing that, the problem still occurs, you can make a bug
> report that can be used by the debugging team.  But, if after that, the
> fault goes away, it points rather firmly at your binary blob being the
> cause of the problem.  And since nobody here can debug closed source
> software, you're stuck.
>

BTW, one can determine if their kernel is tainted by doing a "cat
/proc/sys/kernel/tainted".  Anything other than 0 means "tainted".

The values are additive from this list....(may be out of date).

1 – A module with a non-GPL license has been loaded, this includes modules with no
license. Set by modutils >= 2.4.9 and module-init-tools.
2 – A module was force loaded by insmod -f. Set by modutils >= 2.4.9 and
module-init-tools.
4 – Unsafe SMP processors: SMP with CPUs not designed for SMP.
8 – A module was forcibly unloaded from the system by rmmod -f.
16 – A hardware machine check error occurred on the system.
32 – A bad page was discovered on the system.
64 – The user has asked that the system be marked “tainted”. This could be because
they are running software that directly modifies the hardware, or for other reasons.
128 – The system has died.
256 – The ACPI DSDT has been overridden with one supplied by the user instead of
using the one provided by the hardware.
512 – A kernel warning has occurred.
1024 – A module from drivers/staging was loaded.
268435456 – Unsupported hardware
536870912 – Technology Preview code was loaded


-- 
A motto of mine is: When in doubt, try it out

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux