still got the other call trace after re-loading mtk_mdp3 module:
[   61.478615] sysfs: cannot create duplicate filename '/class/hdmirxswitch'
[   61.478619] CPU: 4 PID: 1282 Comm: modprobe Not tainted 5.15.0-1036-mtk 
#43-Ubuntu
[   61.478624] Hardware name: Unknown Unknown Product/Unknown Product, BIOS 
2022.10-gcab6fe6708 10/01/2022
[   61.478626] Call trace:
[   61.478627]  dump_backtrace+0x0/0x200
[   61.478635]  show_stack+0x20/0x30
[   61.478638]  dump_stack_lvl+0x68/0x84
[   61.478647]  dump_stack+0x18/0x34
[   61.478651]  sysfs_warn_dup+0x6c/0x90
[   61.478656]  sysfs_create_dir_ns+0xf0/0x110
[   61.478659]  create_dir+0x30/0x1a0
[   61.478666]  kobject_add_internal+0x8c/0x200
[   61.478669]  kset_register+0x60/0xa4
[   61.478672]  __class_register+0xd0/0x190
[   61.478678]  __class_create+0x5c/0xa4
[   61.478682]  uevent_dev_register.constprop.0.isra.0+0x68/0x1f0 [mtk_hdmirx]
[   61.478698]  hdmirx_probe+0xd4/0x5ec [mtk_hdmirx]
[   61.478709]  platform_probe+0x70/0x110
[   61.478711]  really_probe+0xd0/0x490
[   61.478715]  __driver_probe_device+0x148/0x190
[   61.478719]  driver_probe_device+0x48/0x180
[   61.478722]  __driver_attach+0x104/0x240
[   61.478726]  bus_for_each_dev+0x78/0xd0
[   61.478729]  driver_attach+0x2c/0x40
[   61.478732]  bus_add_driver+0x154/0x270
[   61.478736]  driver_register+0x80/0x13c
[   61.478739]  __platform_driver_register+0x30/0x40
[   61.478742]  hdmirx_driver_init+0x2c/0x1000 [mtk_hdmirx]
[   61.478753]  do_one_initcall+0x4c/0x2bc
[   61.478756]  do_init_module+0x50/0x270
[   61.478760]  load_module+0xa4c/0xbf0
[   61.478762]  __do_sys_finit_module+0xa8/0x114
[   61.478764]  __arm64_sys_finit_module+0x28/0x3c
[   61.478767]  invoke_syscall+0x78/0x100
[   61.478772]  el0_svc_common.constprop.0+0x54/0x184
[   61.478776]  do_el0_svc+0x30/0xac
[   61.478778]  el0_svc+0x48/0x160
[   61.478783]  el0t_64_sync_handler+0xa4/0x12c
[   61.478787]  el0t_64_sync+0x1a4/0x1a8
[   61.478790] kobject_add_internal failed for hdmirxswitch with -EEXIST, don't 
try to register things with the same name in the same directory.
[   61.480441] [RX]create_switch_class fail
[   61.480442] [RX]aud_uevent_dev_register, 0xffff0000c9800140
[   61.480450] sysfs: cannot create duplicate filename '/class/hdmirxaud'
[   61.480452] CPU: 4 PID: 1282 Comm: modprobe Not tainted 5.15.0-1036-mtk 
#43-Ubuntu
[   61.480454] Hardware name: Unknown Unknown Product/Unknown Product, BIOS 
2022.10-gcab6fe6708 10/01/2022
[   61.480456] Call trace:
[   61.480457]  dump_backtrace+0x0/0x200
[   61.480459]  show_stack+0x20/0x30
[   61.480461]  dump_stack_lvl+0x68/0x84
[   61.480465]  dump_stack+0x18/0x34
[   61.480469]  sysfs_warn_dup+0x6c/0x90
[   61.480471]  sysfs_create_dir_ns+0xf0/0x110
[   61.480473]  create_dir+0x30/0x1a0
[   61.480475]  kobject_add_internal+0x8c/0x200
[   61.480478]  kset_register+0x60/0xa4
[   61.480480]  __class_register+0xd0/0x190
[   61.480484]  __class_create+0x5c/0xa4
[   61.480488]  aud_uevent_dev_register.constprop.0.isra.0+0x68/0x294 
[mtk_hdmirx]
[   61.480498]  hdmirx_probe+0xf4/0x5ec [mtk_hdmirx]
[   61.480507]  platform_probe+0x70/0x110
[   61.480509]  really_probe+0xd0/0x490
[   61.480512]  __driver_probe_device+0x148/0x190
[   61.480515]  driver_probe_device+0x48/0x180
[   61.480519]  __driver_attach+0x104/0x240
[   61.480522]  bus_for_each_dev+0x78/0xd0
[   61.480524]  driver_attach+0x2c/0x40
[   61.480527]  bus_add_driver+0x154/0x270
[   61.480531]  driver_register+0x80/0x13c
[   61.480534]  __platform_driver_register+0x30/0x40
[   61.480536]  hdmirx_driver_init+0x2c/0x1000 [mtk_hdmirx]
[   61.480545]  do_one_initcall+0x4c/0x2bc
[   61.480548]  do_init_module+0x50/0x270
[   61.480550]  load_module+0xa4c/0xbf0
[   61.480552]  __do_sys_finit_module+0xa8/0x114
[   61.480554]  __arm64_sys_finit_module+0x28/0x3c
[   61.480556]  invoke_syscall+0x78/0x100
[   61.480560]  el0_svc_common.constprop.0+0x54/0x184
[   61.480564]  do_el0_svc+0x30/0xac
[   61.480565]  el0_svc+0x48/0x160
[   61.480568]  el0t_64_sync_handler+0xa4/0x12c
[   61.480571]  el0t_64_sync+0x1a4/0x1a8
[   61.480574] kobject_add_internal failed for hdmirxaud with -EEXIST, don't 
try to register things with the same name in the same directory.
[   61.482153] [RX]create_aud_switch_class fail
[   61.482162] sysfs: cannot create duplicate filename '/class/hdmirx'
[   61.482164] CPU: 4 PID: 1282 Comm: modprobe Not tainted 5.15.0-1036-mtk 
#43-Ubuntu
[   61.482166] Hardware name: Unknown Unknown Product/Unknown Product, BIOS 
2022.10-gcab6fe6708 10/01/2022
[   61.482167] Call trace:
[   61.482168]  dump_backtrace+0x0/0x200
[   61.482170]  show_stack+0x20/0x30
[   61.482172]  dump_stack_lvl+0x68/0x84
[   61.482175]  dump_stack+0x18/0x34
[   61.482179]  sysfs_warn_dup+0x6c/0x90
[   61.482181]  sysfs_create_dir_ns+0xf0/0x110
[   61.482183]  create_dir+0x30/0x1a0
[   61.482185]  kobject_add_internal+0x8c/0x200
[   61.482187]  kset_register+0x60/0xa4
[   61.482190]  __class_register+0xd0/0x190
[   61.482193]  __class_create+0x5c/0xa4
[   61.482196]  hdmirx_probe+0x168/0x5ec [mtk_hdmirx]
[   61.482206]  platform_probe+0x70/0x110
[   61.482208]  really_probe+0xd0/0x490
[   61.482211]  __driver_probe_device+0x148/0x190
[   61.482214]  driver_probe_device+0x48/0x180
[   61.482217]  __driver_attach+0x104/0x240
[   61.482220]  bus_for_each_dev+0x78/0xd0
[   61.482223]  driver_attach+0x2c/0x40
[   61.482226]  bus_add_driver+0x154/0x270
[   61.482229]  driver_register+0x80/0x13c
[   61.482232]  __platform_driver_register+0x30/0x40
[   61.482234]  hdmirx_driver_init+0x2c/0x1000 [mtk_hdmirx]
[   61.482243]  do_one_initcall+0x4c/0x2bc
[   61.482245]  do_init_module+0x50/0x270
[   61.482247]  load_module+0xa4c/0xbf0
[   61.482249]  __do_sys_finit_module+0xa8/0x114
[   61.482251]  __arm64_sys_finit_module+0x28/0x3c
[   61.482253]  invoke_syscall+0x78/0x100
[   61.482257]  el0_svc_common.constprop.0+0x54/0x184
[   61.482260]  do_el0_svc+0x30/0xac
[   61.482262]  el0_svc+0x48/0x160
[   61.482265]  el0t_64_sync_handler+0xa4/0x12c
[   61.482268]  el0t_64_sync+0x1a4/0x1a8
[   61.482270] kobject_add_internal failed for hdmirx with -EEXIST, don't try 
to register things with the same name in the same directory.

** Tags removed: verification-needed-jammy-linux-mtk
** Tags added: verification-failed-jammy-linux-mtk

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2090981

Title:
  [g1200-evk] Call trace appeared when reload mtk_mdp3 module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2090981/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to