Discussion:
[Bug 194833] New: Error: Needed [Buffer/String/Package], found [Integer] ffff880414af1dc8 (20160930/exresop-594)
b***@bugzilla.kernel.org
2017-03-09 20:48:29 UTC
Permalink
https://bugzilla.kernel.org/show_bug.cgi?id=194833

Bug ID: 194833
Summary: Error: Needed [Buffer/String/Package], found [Integer]
ffff880414af1dc8 (20160930/exresop-594)
Product: ACPI
Version: 2.5
Kernel Version: 4.10.1
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: ***@kernel-bugs.osdl.org
Reporter: ***@archlinux.org
Regression: No

My pretty new HP Probook 430 G4 notebook is affected by Bug 191561 and later
shows these errors in the logs. I'm not sure to what component they belong if
they can be ignored or should be fixed:

[ 5.193114] Bluetooth: BNEP socket layer initialized
[ 5.243658] (NULL device *): hwmon_device_register() is deprecated. Please
convert the driver to use hwmon_device_register_with_info().
[ 5.325603] ACPI Error: Needed [Buffer/String/Package], found [Integer]
ffff880414af1dc8 (20160930/exresop-594)
[ 5.325615] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands
for [OpcodeName unavailable] (20160930/dswexec-461)
[ 5.325625] ACPI Error: Method parse/execution failed [\_SB.WMIV.WVPO] (Node
ffff88041f8b2438), AE_AML_OPERAND_TYPE (20160930/psparse-543)
[ 5.325637] ACPI Error: Method parse/execution failed [\_SB.WMIV.WMPV] (Node
ffff88041f8b2550), AE_AML_OPERAND_TYPE (20160930/psparse-543)
[ 5.326933] ACPI Error: Needed [Buffer/String/Package], found [Integer]
ffff88041a129ca8 (20160930/exresop-594)
[ 5.326943] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands
for [OpcodeName unavailable] (20160930/dswexec-461)
[ 5.326952] ACPI Error: Method parse/execution failed [\_SB.WMIV.WVPO] (Node
ffff88041f8b2438), AE_AML_OPERAND_TYPE (20160930/psparse-543)
[ 5.326964] ACPI Error: Method parse/execution failed [\_SB.WMIV.WMPV] (Node
ffff88041f8b2550), AE_AML_OPERAND_TYPE (20160930/psparse-543)
[ 5.327956] ACPI Error: Needed [Buffer/String/Package], found [Integer]
ffff88041a1293a8 (20160930/exresop-594)
[ 5.327965] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands
for [OpcodeName unavailable] (20160930/dswexec-461)
[ 5.327974] ACPI Error: Method parse/execution failed [\_SB.WMIV.WVPO] (Node
ffff88041f8b2438), AE_AML_OPERAND_TYPE (20160930/psparse-543)
[ 5.327985] ACPI Error: Method parse/execution failed [\_SB.WMIV.WMPV] (Node
ffff88041f8b2550), AE_AML_OPERAND_TYPE (20160930/psparse-543)
[ 5.328050] input: HP WMI hotkeys as /devices/virtual/input/input15
[ 5.331265] ACPI Error: Attempt to CreateField of length zero
(20160930/dsopcode-168)
[ 5.331274] ACPI Error: Method parse/execution failed [\_SB.WMIV.WVPI] (Node
ffff88041f8b2f00), AE_AML_OPERAND_VALUE (20160930/psparse-543)
[ 5.331287] ACPI Error: Method parse/execution failed [\_SB.WMIV.WMPV] (Node
ffff88041f8b2550), AE_AML_OPERAND_VALUE (20160930/psparse-543)
[ 5.369565] thermal LNXTHERM:00: registered as thermal_zone2
[ 5.369567] ACPI: Thermal Zone [CPUZ] (46 C)
[ 5.519984] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
[ 5.633606] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 5.634273] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 5.701178] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 5.701740] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 5.727371] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 5.737254] psmouse serio3: synaptics: queried max coordinates: x [..5654],
y [..4702]
[ 5.768307] psmouse serio3: synaptics: queried min coordinates: x [1288..],
y [1150..]
[ 5.826305] psmouse serio3: synaptics: Touchpad model: 1, fw: 8.2, id:
0x1e2b1, caps: 0xf00123/0x840300/0x12e800/0x0, board id: 3245, fw id: 2368862
[ 5.863412] input: SynPS/2 Synaptics TouchPad as
/devices/platform/i8042/serio3/input/input14
[ 5.888540] thermal LNXTHERM:01: registered as thermal_zone3
[ 5.888544] ACPI: Thermal Zone [GFXZ] (0 C)
[ 6.247933] thermal LNXTHERM:02: registered as thermal_zone4
[ 6.247940] ACPI: Thermal Zone [EXTZ] (40 C)
[ 6.255157] thermal LNXTHERM:03: registered as thermal_zone5
[ 6.255159] ACPI: Thermal Zone [LOCZ] (40 C)
[ 6.262152] thermal LNXTHERM:04: registered as thermal_zone6
[ 6.262154] ACPI: Thermal Zone [BATZ] (31 C)
[ 6.262549] thermal LNXTHERM:05: registered as thermal_zone7
[ 6.262550] ACPI: Thermal Zone [PCHZ] (127 C)
[ 6.280207] input: ST LIS3LV02DL Accelerometer as
/devices/platform/lis3lv02d/input/input17
[ 6.287149] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)


I'm using pci=noaer to avoid this error but this is probably a different one:
Feb 21 16:09:01 laptop64 kernel: pcieport 0000:00:1d.0: PCIe Bus Error:
severity=Corrected, type=Physical Layer, id=00e8(Receiver ID)
Feb 21 16:09:01 laptop64 kernel: pcieport 0000:00:1d.0: device [8086:9d18]
error status/mask=00000001/00002000
Feb 21 16:09:01 laptop64 kernel: pcieport 0000:00:1d.0: [ 0] Receiver Error
(First)
--
You are receiving this mail because:
You are watching the assignee of the bug.
b***@bugzilla.kernel.org
2017-03-10 03:54:06 UTC
Permalink
https://bugzilla.kernel.org/show_bug.cgi?id=194833

Robert Moore (***@intel.com) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@intel.com

--- Comment #1 from Robert Moore (***@intel.com) ---
Please post the acpidump for this machine, thanks.
--
You are receiving this mail because:
You are watching the assignee of the bug.
b***@bugzilla.kernel.org
2017-03-10 15:34:45 UTC
Permalink
https://bugzilla.kernel.org/show_bug.cgi?id=194833

--- Comment #2 from Andreas Radke (***@archlinux.org) ---
Created attachment 255169
--> https://bugzilla.kernel.org/attachment.cgi?id=255169&action=edit
acpidump
--
You are receiving this mail because:
You are watching the assignee of the bug.
b***@bugzilla.kernel.org
2017-03-10 17:57:21 UTC
Permalink
https://bugzilla.kernel.org/show_bug.cgi?id=194833

--- Comment #3 from Robert Moore (***@intel.com) ---
I don't see where WMPV is being called from anywhere within the static ACPI
tables, nor is it called from Linux.

Perhaps it is in a dynamically loaded SSDT (via Load operator).

$ grep -n WMPV *.dsl
dsdt.dsl:3728: Method (WMPV, 3, Serialized)

$ grep -n Load *.dsl
ssdt13.dsl:266: Load (CST0, HC0) /* \_PR_.CPU0.HC0_ */
ssdt13.dsl:274: Load (IST0, HI0) /* \_PR_.CPU0.HI0_ */
ssdt13.dsl:285: Load (HWP0, HW0) /* \_PR_.CPU0.HW0_ */
ssdt13.dsl:289: Load (HWPL, HW2) /* \_PR_.CPU0.HW2_
*/
ssdt13.dsl:376: Load (CST1, HC1) /* \_PR_.CPU1.HC1_ */
ssdt13.dsl:386: Load (IST1, HI1) /* \_PR_.CPU1.HI1_ */
ssdt13.dsl:398: Load (HWP1, HW1) /* \_PR_.CPU1.HW1_ */

I think there is a way to grab the dynamically loaded SSDTs on Linux, but I
don't know how to do it.
--
You are receiving this mail because:
You are watching the assignee of the bug.
b***@bugzilla.kernel.org
2017-03-10 21:47:13 UTC
Permalink
https://bugzilla.kernel.org/show_bug.cgi?id=194833

--- Comment #4 from Robert Moore (***@intel.com) ---
Anyway, it looks like somewhere, WMPV is being called with an incorrect
argument, and the runtime typechecking is catching it.
--
You are receiving this mail because:
You are watching the assignee of the bug.
b***@bugzilla.kernel.org
2017-03-14 03:49:57 UTC
Permalink
https://bugzilla.kernel.org/show_bug.cgi?id=194833

Lv Zheng (***@intel.com) changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Post by b***@bugzilla.kernel.org
I don't see where WMPV is being called from anywhere within the static ACPI
tables, nor is it called from Linux.
WMPV should have been invoked by OS WMI driver.
Post by b***@bugzilla.kernel.org
Anyway, it looks like somewhere, WMPV is being called with an incorrect
argument, and the runtime typechecking is catching it.
Is the typechecking wrong?
Is the OS invocation itself wrong?
--
You are receiving this mail because:
You are watching the assignee of the bug.
b***@bugzilla.kernel.org
2017-03-14 05:07:15 UTC
Permalink
https://bugzilla.kernel.org/show_bug.cgi?id=194833

Lv Zheng (***@intel.com) changed:

What |Removed |Added
----------------------------------------------------------------------------
Summary|Error: Needed |Error: Needed
|[Buffer/String/Package], |[Buffer/String/Package],
|found [Integer] |found [Integer]
|ffff880414af1dc8 |ffff880414af1dc8
|(20160930/exresop-594) |(20160930/exresop-594) - HP
| |Probook 430 G4
--
You are receiving this mail because:
You are watching the assignee of the bug.
b***@bugzilla.kernel.org
2017-03-14 05:08:11 UTC
Permalink
https://bugzilla.kernel.org/show_bug.cgi?id=194833

Lv Zheng (***@intel.com) changed:

What |Removed |Added
----------------------------------------------------------------------------
Component|Other |x86-64
Assignee|***@kernel-bugs.osdl |***@kernel-bugs
|.org |.osdl.org
Product|ACPI |Platform Specific/Hardware
--
You are receiving this mail because:
You are watching the assignee of the bug.
b***@bugzilla.kernel.org
2017-03-16 08:26:17 UTC
Permalink
https://bugzilla.kernel.org/show_bug.cgi?id=194833

Lv Zheng (***@intel.com) changed:

What |Removed |Added
----------------------------------------------------------------------------
Component|x86-64 |BIOS
Assignee|***@kernel-bugs |***@kernel-bugs.osdl.
|.osdl.org |org
Product|Platform Specific/Hardware |ACPI
--
You are receiving this mail because:
You are watching the assignee of the bug.
b***@bugzilla.kernel.org
2017-03-16 14:52:25 UTC
Permalink
https://bugzilla.kernel.org/show_bug.cgi?id=194833

--- Comment #11 from Robert Moore (***@intel.com) ---
Yes, a BIOS bug.

Could be exposed due to some hardware issue that forces a different code path
through the ASL.
--
You are receiving this mail because:
You are watching the assignee of the bug.
b***@bugzilla.kernel.org
2017-06-22 21:51:30 UTC
Permalink
https://bugzilla.kernel.org/show_bug.cgi?id=194833

Kamil Iskra (***@iskra.name) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@iskra.name

--- Comment #12 from Kamil Iskra (***@iskra.name) ---
I'm seeing the same error messages with HP EliteBook 820 G4. I tracked them
down to CONFIG_HP_WMI (drivers/platform/x86/hp-wmi.c).

So fair enough, the driver may be triggering a BIOS bug, but I guess it's
really an indication that HP has changed their APIs and the driver needs to be
updated. For all intents and purposes, the driver does not work *at all* on
these new HP laptops right now (kernel 4.11).

Andreas, which special keys [do not] work on your system? I'm particularly
interested to hear about Wifi, Volume mute, and Microphone mute (both keys and
lights).
--
You are receiving this mail because:
You are watching the assignee of the bug.
b***@bugzilla.kernel.org
2017-06-23 18:13:38 UTC
Permalink
https://bugzilla.kernel.org/show_bug.cgi?id=194833

--- Comment #13 from Andreas Radke (***@archlinux.org) ---
Microphone mute (Fn+f10) doens't work here. Volume mute and Wifi/BT hardware
switch (two extra keys above keyboard) seem to work well. Nothing in the log
when hitting "Mute" or "Mic mute" but Wifi switch gives:


Jun 23 20:08:03 laptop64 kernel: atkbd serio0: Unknown key pressed (translated
set 2, code 0xf8 on isa0060/serio0).
Jun 23 20:08:03 laptop64 kernel: atkbd serio0: Use 'setkeycodes e078 <keycode>'
to make it known.
Jun 23 20:08:03 laptop64 systemd[1]: Starting Load/Save RF Kill Switch
Status...
Jun 23 20:08:03 laptop64 systemd[1]: Started Load/Save RF Kill Switch Status.
Jun 23 20:08:03 laptop64 kernel: wlp2s0: deauthenticating from
c4:6e:1f:ea:da:f9 by local choice (Reason: 3=DEAUTH_LEAVING)
Jun 23 20:08:03 laptop64 kernel: iwlwifi 0000:02:00.0: Failed to find station
Jun 23 20:08:03 laptop64 kernel: wlp2s0: failed to remove key (1,
ff:ff:ff:ff:ff:ff) from hardware (-22)
Jun 23 20:08:03 laptop64 avahi-daemon[268]: Interface wlp2s0.IPv6 no longer
relevant for mDNS.
Jun 23 20:08:03 laptop64 avahi-daemon[268]: Leaving mDNS multicast group on
interface wlp2s0.IPv6 with address 2a02:8109:953f:ed90:7eb0:c2ff:fe33:946f.
Jun 23 20:08:03 laptop64 avahi-daemon[268]: Interface wlp2s0.IPv4 no longer
relevant for mDNS.
Jun 23 20:08:03 laptop64 avahi-daemon[268]: Leaving mDNS multicast group on
interface wlp2s0.IPv4 with address 192.168.1.110.
Jun 23 20:08:03 laptop64 avahi-daemon[268]: Withdrawing address record for
2a02:8109:953f:ed90:7eb0:c2ff:fe33:946f on wlp2s0.
Jun 23 20:08:03 laptop64 avahi-daemon[268]: Withdrawing address record for
192.168.1.110 on wlp2s0.
Jun 23 20:08:04 laptop64 kernel: atkbd serio0: Unknown key released (translated
set 2, code 0xf8 on isa0060/serio0).
Jun 23 20:08:04 laptop64 kernel: atkbd serio0: Use 'setkeycodes e078 <keycode>'
to make it known.

Its functionality seems to work though. I hope this helps.
--
You are receiving this mail because:
You are watching the assignee of the bug.
b***@bugzilla.kernel.org
2017-06-26 02:15:19 UTC
Permalink
https://bugzilla.kernel.org/show_bug.cgi?id=194833

Lv Zheng (***@intel.com) changed:

What |Removed |Added
----------------------------------------------------------------------------
Component|BIOS |x86-64
Assignee|***@kernel-bugs.osdl. |***@kernel-bugs
|org |.osdl.org
Product|ACPI |Platform Specific/Hardware

--- Comment #14 from Lv Zheng (***@intel.com) ---
Let's re-assign this bug to hp-wmi maintainers.
Feel free to re-open it under platform specific hardware.
--
You are receiving this mail because:
You are watching the assignee of the bug.
Loading...