On Sat, Jan 22, 2022 at 10:05:24PM +0300, Alexander Sergeyev wrote: > I'm not sure about kernel log buffering or maybe the device support for > pipelining, but is it okay that alc_update_coefex_idx() seem to overlap? Given that the CPU number is the same in alc_update_coefex_idx(), it seems these calls execution is interrupted and interleaved on the same core. And, actually, there are two LEDs to set (mute and micmute). Am I onto something here? [4.043235] alc_update_coefex_idx(codec, nid, coef_idx=0xb, mask=0x8, bits_set=0x0): entering [4.043237] CPU: 0 PID: 18 Comm: kworker/0:1 Tainted: G T 5.16.0-rc1-00001-g5c38c8c84e47-dirty #18 [4.043910] Hardware name: HP HP EliteBook 855 G8 Notebook PC/8895, BIOS T82 Ver. 01.06.03 09/17/2021 [4.044559] Workqueue: events set_brightness_delayed [4.044559] Call Trace: [4.044559] <TASK> [4.046289] dump_stack_lvl+0x34/0x4c [4.046289] alc_update_coefex_idx+0x34/0x7a [4.046289] coef_mute_led_set+0x48/0x56 [4.046289] set_brightness_delayed+0x6f/0xb0 [4.046289] process_one_work+0x1e1/0x380 [4.046289] worker_thread+0x4e/0x3b0 [4.046289] ? rescuer_thread+0x370/0x370 [4.046289] kthread+0x145/0x170 [4.046289] ? set_kthread_struct+0x50/0x50 [4.046289] ret_from_fork+0x22/0x30 [4.046289] </TASK> [4.052793] alc_update_coefex_idx(codec, nid, coef_idx=0x19, mask=0x2000, bits_set=0x0): entering [4.052794] CPU: 0 PID: 171 Comm: kworker/0:2 Tainted: G T 5.16.0-rc1-00001-g5c38c8c84e47-dirty #18 [4.053363] Hardware name: HP HP EliteBook 855 G8 Notebook PC/8895, BIOS T82 Ver. 01.06.03 09/17/2021 [4.053364] Workqueue: events set_brightness_delayed [4.053366] Call Trace: [4.053366] <TASK> [4.053367] dump_stack_lvl+0x34/0x4c [4.053790] alc_update_coefex_idx+0x34/0x7a [4.053790] coef_micmute_led_set+0x48/0x56 [4.053790] set_brightness_delayed+0x6f/0xb0 [4.053790] process_one_work+0x1e1/0x380 [4.053790] worker_thread+0x4e/0x3b0 [4.053790] ? rescuer_thread+0x370/0x370 [4.053790] kthread+0x145/0x170 [4.053790] ? set_kthread_struct+0x50/0x50 [4.053790] ret_from_fork+0x22/0x30 [4.053790] </TASK>
