'rmmod pmt_telemetry' panics on ADL-P IOTG
Issue
- Executing 'rmmod pmt_telemetry' on ADL-P IOTG system results in a panic.
- Boot the stock RHEL8 kernel, and then do 'rmmod pmt_telemetry', the system will panic with the following messages:
BUG: unable to handle kernel paging request at fffffffffffffff0
PGD 35c813067 P4D 35c813067 PUD 35c815067 PMD 0
Oops: 0000 [#1] SMP NOPTI
CPU: 8 PID: 2181 Comm: rmmod Kdump: loaded Not tainted 4.18.0-402.el8.x86_64 #1
Hardware name: Intel Corporation Alder Lake Client Platform/AlderLake-P DDR5 RVP, BIOS ADLPFWI1.R00.3056.B00.2201310233 01/31/2022
RIP: 0010:device_del+0x1b/0x3c0
[--]
Call Trace:
<TASK>
? __xa_erase+0x53/0xb0
device_unregister+0x13/0x50
intel_pmt_dev_destroy+0x34/0x60 [pmt_class]
pmt_telem_remove+0x40/0x50 [pmt_telemetry]
auxiliary_bus_remove+0x18/0x30
device_release_driver_internal+0xc1/0x150
driver_detach+0x44/0x90
bus_remove_driver+0x74/0xd0
auxiliary_driver_unregister+0x12/0x20
pmt_telem_exit+0xc/0xe4a [pmt_telemetry]
__x64_sys_delete_module+0x13a/0x250
? syscall_trace_enter.isra.19+0x11e/0x1a0
do_syscall_64+0x58/0x80
? syscall_exit_to_user_mode+0x12/0x30
? do_syscall_64+0x67/0x80
? syscall_exit_to_user_mode+0x12/0x30
? do_syscall_64+0x67/0x80
? syscall_exit_to_user_mode+0x12/0x30
? do_syscall_64+0x67/0x80
? exc_page_fault+0x64/0x140
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7f7e1803a05b
Environment
- RedHat Enterprise Linux 8
- ADL-P IOTG system
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.