https://bugzilla.kernel.org/show_bug.cgi?id=198145
Edward Shin ([email protected]) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #5 from Edward Shin ([email protected]) --- I've also been investigating this issue. Acpidump and dsdt.dat are identical to Steve's, as expected. Attached are my logs for extra info, as well as the decompiled DSDT. The DSDT is clearly being loaded, and other HIDs, such as the lid (PNP0C0D), are detected. I'm digging through the ACPI code to see what triggers loading of the drivers, but I don't have much experience with the kernel, unfortunately. Anybody have any pointers on where to start looking? A few lines of note from dmesg: Dec 04 18:23:11 gjbu kernel: ACPI Error: [_SB_.PCI0] Namespace lookup failure, AE_NOT_FOUND (20170728/dswload2-191) Dec 04 18:23:11 gjbu kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170728/psobject-252) Dec 04 18:23:11 gjbu kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.UA02, AE_NOT_FOUND (20170728/psparse-550) Dec 04 18:23:11 gjbu kernel: ACPI: Executed 26 blocks of module-level executable AML code Dec 04 18:23:11 gjbu kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored I don't see how this would be directly related to the ACPI battery, however. -- You are receiving this mail because: You are watching the assignee of the bug. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ acpi-bugzilla mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
