Disabling lock debugging due to kernel taint

Amir Lee

Intellectual 280 points

When I load driver module with the command "insmod",I get the following message:

root@am335x-evm:/usr# insmod am335x_gpio.ko
Disabling lock debugging due to kernel taint

The Linux version I am using is Linux 3.2 and My driver is GPL licensed? What is the kernel taint?

Is it unsafe?

over 13 years ago

0 Chase Maupin over 13 years ago

TI__Expert 5450 points

John,

Where did the am335x_gpio module come from? If this as an out-of-tree module then it will be seen as tainted. It does not mean it is unsafe, just that the kernel was not aware of this module when it was built.

Chase

0 Amir Lee over 13 years ago in reply to Chase Maupin

Intellectual 280 points

HI,Chase

As you known,It is an out-of-tree module that I build.

Is it a bug of kernel?Do you have a manner to fix the problem?

Thanks!

0 Chase Maupin over 13 years ago in reply to Amir Lee

TI__Expert 5450 points

It is not a kernel bug, but expected behavior. I think if you were to merge that driver into the kernel (i.e. add the sources and update the kernel Makefiles) and build it as part of the kernel build then this message would go away.

Chase

0 Gururaja Hebbar over 13 years ago in reply to Amir Lee

TI__Intellectual 2725 points

Is this driver GPL licensed?

whats is the output of "cat /proc/sys/kernel/tainted"

0 Sim Nikolov over 12 years ago in reply to Gururaja Hebbar

Prodigy 70 points

Hi Gururaja,

Hi Community,

I'm new in the LKM and i have the same problem whit my out of tree module when i do insmod on my target board - "Disabling lock debugging due to kernel taint".

The output of "cat /proc/sys/kernel/tainted" is 4096, but i have no idea what that means?

It is generally possible to build out of tree module without kernel taint???

Processors

Processors forum

Disabling lock debugging due to kernel taint