I think we have a problem with both ACPI_DEBUG_PRINT and ACPI_WARNING and how these ACPI core macros work on Linux. ACPI_WARNING is an improvement over the past where all the ACPI_DEBUG_PRINT messages went away on a production kernel. ACPI_DEBUG_PRINT is very handy in that via acpi_ut_print() you can turn them on and off on your debug kernel depending on the level and section of code. But both funnel through osl.c where there is no native Linux print level associated with the message, and thus if it gets that far, it unconditionaly gets printed to the screen and log buffer, no mater how the system has been administered to handle messages of different levels. ie. the kernel.h levels are not used: #define KERN_EMERG "<0>" /* system is unusable */ #define KERN_ALERT "<1>" /* action must be taken immediately */ #define KERN_CRIT "<2>" /* critical conditions */ #define KERN_ERR "<3>" /* error conditions */ #define KERN_WARNING "<4>" /* warning conditions */ #define KERN_NOTICE "<5>" /* normal but significant condition */ #define KERN_INFO "<6>" /* informational */ #define KERN_DEBUG "<7>" /* debug-level messages */ thoughts? -Len - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
