Bug 202661 - Failed to detect touch pad, ACPI Namespace lookup failure, AE_NOT_FOUND
Summary: Failed to detect touch pad, ACPI Namespace lookup failure, AE_NOT_FOUND
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: ACPI
Classification: Unclassified
Component: Config-Hotplug (show other bugs)
Hardware: Intel Linux
: P1 high
Assignee: Zhang Rui
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-24 07:10 UTC by NotUsuallyMyJob
Modified: 2019-09-29 07:51 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.15.0-45-generic
Tree: Mainline
Regression: No


Attachments
acpidump (1.31 MB, text/plain)
2019-02-24 07:10 UTC, NotUsuallyMyJob
Details
dmesg (63.89 KB, text/plain)
2019-02-24 07:11 UTC, NotUsuallyMyJob
Details
dmidecode (26.20 KB, text/plain)
2019-02-24 07:11 UTC, NotUsuallyMyJob
Details
dmesg output of kernel version 4.19 (63.34 KB, text/plain)
2019-04-16 12:18 UTC, NotUsuallyMyJob
Details

Description NotUsuallyMyJob 2019-02-24 07:10:47 UTC
Created attachment 281309 [details]
acpidump

Distro: Ubuntu 18.04.2 LTS (Bionic Beaver)
I have tried different kernel versions up to 5.0. Still not recognizing my touch pad. (I am using a PS/2 mouse to use my laptop to file this bug report)
There are no bios upgrades from OEM at the time I am writing this and I have tried using several grub boot flags but it was no use.
Comment 1 NotUsuallyMyJob 2019-02-24 07:11:07 UTC
Created attachment 281311 [details]
dmesg
Comment 2 NotUsuallyMyJob 2019-02-24 07:11:30 UTC
Created attachment 281313 [details]
dmidecode
Comment 3 Zhang Rui 2019-03-26 13:57:07 UTC
[    0.076002] ACPI Error: [_SB_.PCI0.RP05.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload2-191)
[    0.076002] No Local Variables are initialized for Method [PXSX]
[    0.076002] No Arguments are initialized for method [PXSX]
[    0.076002] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
[    0.076002] ACPI Error: Method parse/execution failed \_SB.PCI0.RP04.PXSX, AE_NOT_FOUND (20170831/psparse-550)
[    0.076002] ACPI Error: [_SB_.PCI0.RP09.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload2-191)
[    0.076002] No Local Variables are initialized for Method [PXSX]
[    0.076002] No Arguments are initialized for method [PXSX]
[    0.076002] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
[    0.076002] ACPI Error: Method parse/execution failed \_SB.PCI0.RP08.PXSX, AE_NOT_FOUND (20170831/psparse-550)
[    0.081412] ACPI Error: [_SB_.PCI0.RP13.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload2-191)
[    0.081420] No Local Variables are initialized for Method [PXSX]
[    0.081421] No Arguments are initialized for method [PXSX]
[    0.081422] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
[    0.081426] ACPI Error: Method parse/execution failed \_SB.PCI0.RP12.PXSX, AE_NOT_FOUND (20170831/psparse-550)
[    0.085639] ACPI: Executed 57 blocks of module-level executable AML code

I'm not sure what they are complaining about.
Erik, can you please take a look?


[    0.100315] ACPI Error: Field [SAC1] at bit offset/length 64/64 exceeds size of target Buffer (64 bits) (20170831/dsopcode-235)
[    0.100323] Executing subtree for Buffer/Package/Region
[    0.100325] ACPI Exception: AE_AML_BUFFER_LIMIT, Could not execute arguments for [SAC1] (BufferField) (20170831/nsinit-426)
            Name (AC00, Buffer (0x08)
            {
                 0x00, 0x00, 0x00, 0x00, 0x01, 0x01, 0x01, 0x01   // ........
            })
            CreateQWordField (AC00, Zero, SAC0)
            CreateQWordField (AC00, 0x08, SAC1)
Comment 4 Erik Kaneda 2019-04-15 17:22:40 UTC
Hi, Sorry I've been away for a bit. Your dmesg shows this:

Linux version 4.15.0-45-generic

Please post a dmesg of a kernel older than 4.17 as well.
Thanks
Comment 5 NotUsuallyMyJob 2019-04-16 12:18:22 UTC
Created attachment 282349 [details]
dmesg output of kernel version 4.19
Comment 6 Erik Kaneda 2019-04-16 18:35:06 UTC
So there are far fewer ACPI errors in the 4.19 version of the kernel. Just out of curiosity, could you try booting the latest upstream rc? We've made several changes in the EC driver and this might affect the behavior of the touchpad.. 

Are you able to use a USB keyboard on this machine?
Also, what is the model name of this system?

In the 4.19 output, all PSXS errors go away but the SAC1 error remains. This SAC1 error is a legitimate bug in the ASL as Rui has show in comment 3. However, this particular SAC1 is not used so this error is not harmful.

@Rui, I don't think this is an AML interpreter issue. I'm thinking that this could be an issue with the EC or maybe USB... I'm going to re-assign this to you because you might know the appropriate people to contact. Feel free to contact me for any further questions.
Comment 7 Zhang Rui 2019-07-01 08:45:00 UTC
please attach the dmesg output with the latest upstream kernel.
Comment 8 Zhang Rui 2019-09-03 07:07:32 UTC
bug closed as there is no response from the bug reporter.
Please feel free to reopen it if the problem still exists in the latest upstream kernel and you can attach the full dmesg output after boot.

Note You need to log in before you can comment on or make changes to this bug.