Bug 192231 - ACPI : button: The lid device is not compliant to SW_LID.
Summary: ACPI : button: The lid device is not compliant to SW_LID.
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: ACPI
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Lv Zheng
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-09 20:10 UTC by Cristian Aravena Romero
Modified: 2017-03-13 05:56 UTC (History)
2 users (show)

See Also:
Kernel Version: 4.10.0-041000rc3-generic
Subsystem:
Regression: No
Bisected commit-id:

Attachments
dmesg_4.10.0-041000rc3-generic.txt (65.39 KB, text/plain)
2017-01-09 20:10 UTC, Cristian Aravena Romero 		Details
lspci -vvnn (9.58 KB, text/plain)
2017-01-09 20:11 UTC, Cristian Aravena Romero 		Details
[PATCH] Capture lid notification calling stack (515 bytes, patch)
2017-01-16 05:15 UTC, Lv Zheng 		Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Description Cristian Aravena Romero 2017-01-09 20:10:31 UTC 
Created attachment 251001 [details]
dmesg_4.10.0-041000rc3-generic.txt

[ 3965.892266] ACPI : button: The lid device is not compliant to SW_LID.
Comment 1 Cristian Aravena Romero 2017-01-09 20:11:04 UTC 
Created attachment 251011 [details]
lspci -vvnn
Comment 2 Lv Zheng 2017-01-10 00:00:49 UTC 
Just boot it with button.lid_init_state=open.
And report the dmidecode output to systemd community.

See Documentation/acpi/acpi-lid.txt for details.

Thanks
Lv
Comment 3 Lv Zheng 2017-01-10 00:03:50 UTC 
Maybe this message is not suitable.
Let me send you a debugging patch to confirm if this need to be reported.
Comment 4 Lv Zheng 2017-01-16 05:15:30 UTC 
Created attachment 251841 [details]
[PATCH] Capture lid notification calling stack

Please apply this patch.
Build the kernel with CONFIG_ACPI_DEBUG=y.
Boot the kernel with acpi.trace_state=enable.
Trigger the warning message again and upload the dmesg output here.

Please also upload acpidump output here.

Thanks
Lv
Comment 5 Zhang Rui 2017-03-13 05:56:48 UTC 
bug closed as there is not response from the bug reporter.
Please feel free to reopen it if you can provide the information requested.
Note You need to log in before you can comment on or make changes to this bug.