Hi All, So this is a rebased resend of an old patch of mine, which back then was rejected because all the ugly ACPI errors scaring the user during boot would need to be resolved in either the ACPICA code or in the BIOS / firmware in question. It is a year later now and as all the people commenting on: https://bugzilla.kernel.org/show_bug.cgi?id=198167 show (33 comments and counting in a short time), people experience these kinda errors as a real problem. Note this bug is (mostly) about a new bunch of ACPI error messages which are not fixed by this patch actually, but it does nicely illustrate that people experience these errors as a real problem / a real nuisance and I agree with them. https://bugzilla.kernel.org/show_bug.cgi?id=198167#c33 also shows that the chances of ever getting these errors fixed in the case where the problem is in the DSDT is very close to 0, so rejecting this patch with an "ask your vendor to fix the firmware" is really not a useful answer, people have tried and this is simply not going to happen. Given all the effort distros have done with splash-screens to give users a nice clean boot experience, we really want dmesg --level=err to not print anything unless there is a real problem with either the hardware or the kernel. And in this case neither is not true and these unfixable and therefor useless errors only lead to a very jarring boot experience (hence all the users complaining in bug 198167). Note this patch does not silence or removes the messages about these problems in the ACPI tables, it merely lowers their log level from error to warning so that the messages do not show on the console, they will still show in dmesg and other logs. Regards, Hans -- 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
