linux-kernel - acer-wmi broken in latest git kernel on TravelMate 6492 (Insufficient arguments

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 2 Aug 2008 17:50:54 +0200 (CEST)
From:	Sven Wegener <sven.wegener@...aler.net>
To:	Carlos Corbacho <carlos@...angeworlds.co.uk>
cc:	Bob Moore <robert.moore@...el.com>,
	Andi Kleen <ak@...ux.intel.com>,
	Lin Ming <ming.m.lin@...el.com>, linux-acpi@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: acer-wmi broken in latest git kernel on TravelMate 6492 (Insufficient
 arguments - method [WQAA])

Hi all,

running Linus' latest (2b12a4c) git kernel, acer-wmi triggers the 
following ACPI Error on my Acer TravelMate 6492:

acer-wmi: Acer Laptop ACPI-WMI Extras
ACPI Error (nseval-0159): Insufficient arguments - method [WQAA] needs 1, found 0 [20080609]
acer-wmi: Unable to detect available WMID devices

Reverting commit f3454ae8104efb2dbf0d08ec42c6f5d0fe9225bc (ACPICA: Add 
argument count checking to control method invocation via 
acpi_evaluate_object) makes acer_wmi work as before.

Doing a little debugging the call trace starting at acer_wmi_init() is:

WMID_set_capabilities() (called from drivers/misc/acer-wmi.c:1192)
wmi_query_block(WMID_GUID2, 1, &out) (called from drivers/misc/acer-wmi.c:747)
acpi_evaluate_object(handle, method, NULL, out) (called from drivers/acpi/wmi.c:350)
acpi_ns_evaluate(info) (called from drivers/acpi/namespace/nsxfeval.c:258)

Is it a bug in acer-wmi or in Acer's ACPI implementation? I can provide 
more information as necessary.

Sven
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/