FS#35320 - [linux] 3.9.x - 3.10.x asus-nb-wmi kernel module fails

Attached to Project: Arch Linux
Opened by Lachlan (padfoot) - Thursday, 16 May 2013, 08:29 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 17 September 2013, 09:36 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description: With the upgrade from linux-3.8.11 to linux-3.9.2 the kernel module asus-nb-wmi fails on boot with the following error:

May 14 17:22:01 Ethan kernel: ACPI Error: [IIA0] Namespace lookup failure, AE_ALREADY_EXISTS (20130117/dsfield-211)
May 14 17:22:01 Ethan kernel: ACPI Error: Method parse/execution failed [\_SB_.ATKD.WMNB] (Node ffff8804088b6a78), AE_ALREADY_EXISTS (20130117/psparse-537)
May 14 17:22:01 Ethan kernel: ACPI Error: [IIA0] Namespace lookup failure, AE_ALREADY_EXISTS (20130117/dsfield-211)
May 14 17:22:01 Ethan kernel: ACPI Error: Method parse/execution failed [\_SB_.ATKD.WMNB] (Node ffff8804088b6a78), AE_ALREADY_EXISTS (20130117/psparse-537)
May 14 17:22:01 Ethan kernel: ACPI: Marking method WMNB as Serialized because of AE_ALREADY_EXISTS error
May 14 17:22:01 Ethan kernel: asus-nb-wmi: probe of asus-nb-wmi failed with error -5

After boot the module can be manually started with:
# modprobe asus-nb-wmi
This starts without error, resulting in backlight functionality returning, but wmi keys do not work.

Downgrading to linux-3.8.11 resolves the issue returning wmi key finctionality.

Uncertain if this is a packaging bug with the Arch build or an upstream regression.

Cheers.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Tuesday, 17 September 2013, 09:36 GMT
Reason for closing:  Fixed
Additional comments about closing:  3.11.1
Comment by Lachlan (padfoot) - Thursday, 16 May 2013, 08:31 GMT
Machine details follow:
Asus G75V laptop
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1c.3 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 4 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM77 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: NVIDIA Corporation Device 0fd4 (rev a1)
01:00.1 Audio device: NVIDIA Corporation GK107 HDMI Audio Controller (rev a1)
03:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)
04:00.0 Ethernet controller: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet (rev c0)

Using stock Arch install and nouveau video driver.

Cheers.
Comment by Lachlan (padfoot) - Thursday, 16 May 2013, 11:03 GMT
An update for you:

adding asus-nb-wmi to the modules array in mkinitcpio.conf and running mkinitcpio -p linux still gives the same module error on boot, however, this time the module stays loaded and all wmi keys now work.

Cheers.
Comment by Alfonso (euoar) - Sunday, 19 May 2013, 01:51 GMT
Thanks for the info, Lachlan, keys working again for me -asus k55v- using your tip...

(https://bugs.archlinux.org/task/35253)
Comment by salvo (mcpalls) - Wednesday, 22 May 2013, 13:55 GMT
i'have this problem and is present also with linux-3.9.3 :
dmesg | grep asus
[ 3.316702] asus_wmi: ASUS WMI generic driver loaded
[ 3.316975] asus_wmi: Initialization: 0x1
[ 3.317019] asus_wmi: BIOS WMI version: 7.9
[ 3.317084] asus_wmi: SFUN value: 0x4a2877
[ 3.317982] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input6
[ 3.395250] asus-nb-wmi: probe of asus-nb-wmi failed with error -5

the fn key don't work
if i adding asus-nb-wmi to the modules array in mkinitcpio.conf and running mkinitcpio -p linux
the fn key work except fn+f5 fn+f6
Comment by Boohbah (Boohbah) - Thursday, 01 August 2013, 21:27 GMT

Loading...