Messages in this thread | | | Date | Fri, 16 Dec 2011 10:27:24 +0100 | From | "Arend van Spriel" <> | Subject | unexpected taint message |
| |
To whoever may know,
Upon loading our driver module I get the following message:
kernel: [ 344.805106] Disabling lock debugging due to kernel taint
What exactly are the criteria for tainting? Our driver locking strategy is something we want to refactor and having lock debugging during that transition may be a life safer.
Gr. AvS
| |