https://bugzilla.kernel.org/show_bug.cgi?id=215588

--- Comment #2 from Erhard F. (erhar...@mailbox.org) ---
Created attachment 300772
  --> https://bugzilla.kernel.org/attachment.cgi?id=300772&action=edit
dmesg (kernel 5.17-rc3, AMD Ryzen 9 5950X)

5.18-rc3 still affected.
[...]
UBSAN: invalid-load in drivers/mailbox/pcc.c:684:22
load of value 107 is not a valid value for type 'bool' (aka '_Bool')
CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.18.0-rc3-Zen3 #1
Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B450M Steel
Legend, BIOS P4.20 08/03/2021
Call Trace:
 <TASK>
 dump_stack_lvl+0xe5/0x154
 __ubsan_handle_load_invalid_value+0xd2/0x110
 pcc_mbox_probe+0x20c3/0x2610
 platform_probe+0xdc/0x150
 really_probe+0x3fb/0x820
 __driver_probe_device+0x147/0x240
 driver_probe_device+0x4b/0x320
 __driver_attach+0x263/0x4f0
 ? driver_attach+0x40/0x40
 bus_for_each_dev+0xff/0x140
 bus_add_driver+0x2b7/0x480
 driver_register+0x1f5/0x330
 __platform_driver_probe+0x101/0x300
 __platform_create_bundle+0x1d8/0x210
 ? pcc_chan_reg_write+0xe0/0xe0
 pcc_init+0x59/0x88
 ? pmc_atom_init+0x4e5/0x4e5
 do_one_initcall+0x12b/0x2d0
 ? pmc_atom_init+0x4e5/0x4e5
 do_initcall_level+0x136/0x1bf
 ? kernel_init+0x14/0x1d0
 do_initcalls+0x46/0x76
 kernel_init_freeable+0x334/0x456
 ? rest_init+0x240/0x240
 kernel_init+0x14/0x1d0
 ? rest_init+0x240/0x240
 ret_from_fork+0x22/0x30
 </TASK>
================================================================================
Detected 1 PCC Subspaces
Registering PCC driver as Mailbox controller
================================================================================
UBSAN: invalid-load in drivers/mailbox/mailbox.c:486:12
load of value 107 is not a valid value for type 'bool' (aka '_Bool')
CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.18.0-rc3-Zen3 #1
Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B450M Steel
Legend, BIOS P4.20 08/03/2021
Call Trace:
 <TASK>
 dump_stack_lvl+0xe5/0x154
 __ubsan_handle_load_invalid_value+0xd2/0x110
 ? _printk+0x74/0x94
 mbox_controller_register+0x4e5/0x520
 pcc_mbox_probe+0x238f/0x2610
 platform_probe+0xdc/0x150
 really_probe+0x3fb/0x820
 __driver_probe_device+0x147/0x240
 driver_probe_device+0x4b/0x320
 __driver_attach+0x263/0x4f0
 ? driver_attach+0x40/0x40
 bus_for_each_dev+0xff/0x140
 bus_add_driver+0x2b7/0x480
 driver_register+0x1f5/0x330
 __platform_driver_probe+0x101/0x300
 __platform_create_bundle+0x1d8/0x210
 ? pcc_chan_reg_write+0xe0/0xe0
 pcc_init+0x59/0x88
 ? pmc_atom_init+0x4e5/0x4e5
 do_one_initcall+0x12b/0x2d0
 ? pmc_atom_init+0x4e5/0x4e5
 do_initcall_level+0x136/0x1bf
 ? kernel_init+0x14/0x1d0
 do_initcalls+0x46/0x76
 kernel_init_freeable+0x334/0x456
 ? rest_init+0x240/0x240
 kernel_init+0x14/0x1d0
 ? rest_init+0x240/0x240
 ret_from_fork+0x22/0x30
 </TASK>

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to