这意味着什么,我该如何纠正呢?
# cat /var/log/messages | grep -a 'lid'
Mar 22 00:36:00 debian kernel: [ 1039.517767] ACPI: button: The lid device is not compliant to SW_LID.系统:
# uname -a
Linux debian 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26) x86_64 GNU/Linux发布于 2020-03-22 13:07:06
此消息来自drivers/acpi/button.c,它是Linux内核中ACPI_BUTTON模块的一部分。
例如,在linux-source-4.19/drivers/acpi/button.c after行171下可以找到它:
194 /* Complain the buggy firmware */
195 pr_warn_once("The lid device is not compliant to SW_LID.\n");如您所见,当检测到buggy固件时,将打印此消息。该评论继续说:
196 /*
197 * Send the unreliable complement switch event:
. *
. * On most platforms, the lid device is reliable. However
. * there are exceptions:
. * 1. Platforms returning initial lid state as "close" by
. * default after booting/resuming:
. * https://bugzilla.kernel.org/show_bug.cgi?id=89211
. * https://bugzilla.kernel.org/show_bug.cgi?id=106151
. * 2. Platforms never reporting "open" events:
. * https://bugzilla.kernel.org/show_bug.cgi?id=106941
. * On these buggy platforms, the usage model of the ACPI
. * lid device actually is:
. * 1. The initial returning value of _LID may not be
. * reliable.
. * 2. The open event may not be reliable.
. * 3. The close event is reliable.
. *
. * But SW_LID is typed as input switch event, the input
. * layer checks if the event is redundant. Hence if the
. * state is not switched, the userspace cannot see this
. * platform triggered reliable event. By inserting a
. * complement switch event, it then is guaranteed that the
. * platform triggered reliable one can always be seen by
. * the userspace.
222 */如何解决它-这只是一个诊断信息,如果一切都好,你可以忽略它。如果有些东西不起作用,您应该访问上面发布的链接,为您所拥有的特定硬件寻找可能的解决方案,或者尝试升级计算机的固件,但不幸的是,Linux并不总是能够实现的。
https://unix.stackexchange.com/questions/574250
复制相似问题