Re: thinkpad_acpi: unhandled HKEY event , kernel NULL pointer dereference

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 02 Dec 2019, Jenny wrote:
> Whenever I reattach the keyboard cover, the tablet becomes unresponsive
> to inputs shortly after and has to be rebooted forcefully.

...

> [  157.064177] int3403 thermal INT3403:01: Unsupported event [0x91]
> [  157.064181] int3403 thermal INT3403:00: Unsupported event [0x91]
> [  159.581940] thinkpad_acpi: unhandled HKEY event 0x4012
> [  159.581942] thinkpad_acpi: please report the conditions when this
> event happened to ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx
> [  159.583681] int3403 thermal INT3403:01: Unsupported event [0x91]
> [  159.583684] int3403 thermal INT3403:00: Unsupported event [0x91]

The above are Red Herrings, but...

> [  173.851420] usb 1-7: USB disconnect, device number 4
> [  173.897429] hid-rmi 0003:17EF:6085.0009: failed to write hid report
> (-19)
> [  173.897438] hid-rmi 0003:17EF:6085.0009: rmi_set_page: set page
> failed: -19.
> [  173.897444] rmi4_physical rmi4-01: rmi_driver_clear_irq_bits: Failed
> to change enabled interrupts!
> [  173.921419] BUG: kernel NULL pointer dereference, address:
> 0000000000000040
> [  173.921432] #PF: supervisor read access in kernel mode
> [  173.921440] #PF: error_code(0x0000) - not-present page
> [  173.921445] PGD 0 P4D 0 
> [  173.921460] Oops: 0000 [#1] SMP NOPTI
> [  173.921473] CPU: 3 PID: 27 Comm: kworker/3:0 Not tainted 5.3.12-
> 300.fc31.x86_64 #1
> [  173.921480] Hardware name: LENOVO 20GHS1UK00/20GHS1UK00, BIOS
> N1LET86W (1.86 ) 06/26/2019
> [  173.921500] Workqueue: usb_hub_wq hub_event
> [  173.921517] RIP: 0010:__irq_domain_deactivate_irq+0x14/0x40
> [  173.921527] Code: 05 e9 c0 28 ab 00 c3 66 66 2e 0f 1f 84 00 00 00 00
> 00 0f 1f 40 00 0f 1f 44 00 00 48 85 ff 74 2f 53 48 89 fb eb 1e 48 8b 47
> 18 <48> 8b 40 40 48 85 c0 74 08 48 89 de e8 8b 28 ab 00 48 8b 5b 28 48
> [  173.921536] RSP: 0018:ffffbbf6801638b8 EFLAGS: 00010082
> [  173.921545] RAX: 0000000000000000 RBX: ffff9f8251818c28 RCX:
> 0000000000000085
> [  173.921552] RDX: 0000000000000001 RSI: 0000000000000246 RDI:
> ffff9f8288891b40
> [  173.921559] RBP: ffff9f8251818ca4 R08: 0000000000000000 R09:
> ffff9f828def3280
> [  173.921564] R10: 0000000000000000 R11: ffffffffbd4554c8 R12:
> ffff9f8251bf4c00
> [  173.921570] R13: ffff9f8251818d60 R14: 0000000000000246 R15:
> ffff9f8251818c28
> [  173.921579] FS:  0000000000000000(0000) GS:ffff9f8291380000(0000)
> knlGS:0000000000000000
> [  173.921587] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [  173.921594] CR2: 0000000000000040 CR3: 0000000407012006 CR4:
> 00000000003606e0
> [  173.921601] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
> 0000000000000000
> [  173.921607] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
> 0000000000000400
> [  173.921613] Call Trace:
> [  173.921632]  irq_domain_deactivate_irq+0x1a/0x30
> [  173.921646]  __free_irq+0x242/0x300
> [  173.921658]  free_irq+0x37/0x60
> [  173.921670]  release_nodes+0x239/0x280
> [  173.921691]  device_release_driver_internal+0xe8/0x1b0
> [  173.921703]  bus_remove_device+0xdb/0x140
> [  173.921718]  device_del+0x163/0x360
> [  173.921740]  rmi_unregister_function+0x30/0x70 [rmi_core]
> [  173.921762]  rmi_free_function_list+0x96/0x110 [rmi_core]
> [  173.921784]  rmi_driver_remove+0x48/0x50 [rmi_core]
> [  173.921798]  device_release_driver_internal+0xd8/0x1b0
> [  173.921809]  bus_remove_device+0xdb/0x140
> [  173.921823]  device_del+0x163/0x360
> [  173.921842]  rmi_unregister_transport_device+0x12/0x20 [rmi_core]
> [  173.921857]  rmi_remove+0x41/0x50 [hid_rmi]
> [  173.921874]  hid_device_remove+0x4c/0xb0
> [  173.921887]  device_release_driver_internal+0xd8/0x1b0
> [  173.921898]  bus_remove_device+0xdb/0x140
> [  173.921911]  device_del+0x163/0x360
> [  173.921926]  hid_destroy_device+0x42/0x60
> [  173.921940]  usbhid_disconnect+0x4a/0x60
> [  173.921953]  usb_unbind_interface+0x84/0x250
> [  173.921967]  device_release_driver_internal+0xd8/0x1b0
> [  173.921978]  bus_remove_device+0xdb/0x140
> [  173.921991]  device_del+0x163/0x360
> [  173.922004]  usb_disable_device+0x93/0x240
> [  173.922018]  usb_disconnect+0xba/0x260
> [  173.922032]  hub_event+0xd23/0x1490
> [  173.922048]  process_one_work+0x19d/0x340
> [  173.922057]  worker_thread+0x50/0x3b0
> [  173.922071]  kthread+0xfb/0x130
> [  173.922081]  ? process_one_work+0x340/0x340
> [  173.922093]  ? kthread_park+0x80/0x80
> [  173.922104]  ret_from_fork+0x1f/0x40

This one isn't.  It shows the RMI driver blowing up in flames because of
some bug either in the RMI driver itself, or somewhere else in the USB
stack.

I don't think thinkpad-acpi can help much on this one, it would be
better to file a bug against the RMI driver or ask for help in LKML.

-- 
  Henrique Holschuh


_______________________________________________
ibm-acpi-devel mailing list
ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel



[Index of Archives]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Photo]     [Yosemite Photos]     [Yosemite Advice]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]

  Powered by Linux