[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: kernel regression from stable to testing (acpi lid / EEEpc 1215p)



Hi,

On Fri, 4 Jan 2019 20:11:53 +0100
Andrea Borgia <andrea@borgia.bo.it> wrote:

(...)
> 
> dmesg has this interesting warning:
> ACPI: button: The lid device is not compliant to SW_LID.

oddly, here with my Lenovo Ideapad 100s the lid switch stopped working,
too. However, this is totally different hardware and I do not get the above
error message, but instead dmesg says after booting:

   ACPI Error: Method parse/execution failed \_SB.LID0._LID, AE_NOT_EXIST (20180810/psparse-516)

And when I close and re-open the lid dmesg|tail says:

 ACPI Error: No handler for Region [ECRE] (00000000cad769b9) [GenericSerialBus] (20180810/evregion-132)
 ACPI Error: Region GenericSerialBus (ID=9) has no handler (20180810/exfldio-265)
 ACPI Error: Result stack is empty! State=000000005069dd47 (20180810/dswstate-65)
 ACPI Error: Method parse/execution failed \_SB.LID0._LID, AE_NOT_EXIST (20180810/psparse-516)
 ACPI Error: No handler for Region [ECRE] (00000000cad769b9) [GenericSerialBus] (20180810/evregion-132)
 ACPI Error: Region GenericSerialBus (ID=9) has no handler (20180810/exfldio-265)
 ACPI Error: Result stack is empty! State=00000000fdc80083 (20180810/dswstate-65)
 ACPI Error: Method parse/execution failed \_SB.LID0._LID, AE_NOT_EXIST (20180810/psparse-516)

Since the error message looks different from yours I guess that this is
probably a completely different issue, though. 


> What's the best way to handle this? IMHO it's quite likely a kernel 
> issue, most likely upstream.
> Should I file a bug on linux-image-amd64 or directly on
> bugzilla.kernel.org?

I believe reporting to debian is the best so long as you use a debian kernel.
If you want to report to kernel.org probably they'll expect that you
compile and try their kernel first.

Regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Schshschshchsch.
		-- The Gorn, "Arena", stardate 3046.2


Reply to: