2048 is TAINT_FIRMWARE_WORKAROUND. That seems to be set when linux thinks there is something wrong with ACPI tables:
arch/x86/pci/fixup.c: add_taint(TAINT_FIRMWARE_WORKAROUND, LOCKDEP_STILL_OK); drivers/acpi/arm64/iort.c: if (WARN_TAINT(iort_node >= iort_end, TAINT_FIRMWARE_WORKAROUND, drivers/dma/ioat/dca.c: add_taint(TAINT_FIRMWARE_WORKAROUND, LOCKDEP_STILL_OK); drivers/firmware/efi/runtime-wrappers.c: add_taint(TAINT_FIRMWARE_WORKAROUND, LOCKDEP_NOW_UNRELIABLE); drivers/iommu/intel/dmar.c: add_taint(TAINT_FIRMWARE_WORKAROUND, LOCKDEP_STILL_OK);
That would make sense to be happening on some systems where the tests were not running before.
Cascardo.
2048 is TAINT_FIRMWARE_ WORKAROUND. That seems to be set when linux thinks there is something wrong with ACPI tables:
arch/x86/ pci/fixup. c: add_taint( TAINT_FIRMWARE_ WORKAROUND, LOCKDEP_STILL_OK); acpi/arm64/ iort.c: if (WARN_TAINT( iort_node >= iort_end, TAINT_FIRMWARE_ WORKAROUND, dma/ioat/ dca.c: add_taint( TAINT_FIRMWARE_ WORKAROUND, LOCKDEP_STILL_OK); firmware/ efi/runtime- wrappers. c: add_taint( TAINT_FIRMWARE_ WORKAROUND, LOCKDEP_ NOW_UNRELIABLE) ; iommu/intel/ dmar.c: add_taint( TAINT_FIRMWARE_ WORKAROUND, LOCKDEP_STILL_OK);
drivers/
drivers/
drivers/
drivers/
That would make sense to be happening on some systems where the tests were not running before.
Cascardo.