Re: [aarch64] [coresight_etm4x] [kernel 5.19.0-rc1] coresight-etm4x: probe of ARMHC500:20 failed with error -17
CC'ing the coresight mailing list and maintainers.
On Wed, Jun 08, 2022 at 03:20:12PM +0200, Bruno Goncalves wrote:
Hello,
We recently started to hit this call trace when loading the coresight-etm4x module.
[ 78.683475] coresight etm103: CPU103: etm v4.1 initialized [ 78.683645] sysfs: cannot create duplicate filename '/devices/system/container/ACPI0004:00/ARMHC9FE:00/funnel0/connections/in:0' [ 78.683650] CPU: 17 PID: 2522 Comm: systemd-udevd Not tainted 5.19.0-rc1 #1 [ 78.683653] Hardware name: HPE Apollo 70 /C01_APACHE_MB , BIOS L50_5.13_1.16 07/29/2020 [ 78.683655] Call trace: [ 78.683657] dump_backtrace+0xc4/0x130 [ 78.683665] show_stack+0x24/0x70 [ 78.683668] dump_stack_lvl+0x64/0x80 [ 78.683673] dump_stack+0x18/0x34 [ 78.683676] sysfs_warn_dup+0x70/0x90 [ 78.683681] sysfs_do_create_link_sd+0x13c/0x144 [ 78.683683] sysfs_create_link_sd+0x20/0x30 [ 78.683685] sysfs_add_link_to_group+0x48/0x74 [ 78.683688] coresight_add_sysfs_link+0xa4/0x114 [coresight] [ 78.683705] coresight_make_links+0x98/0xdc [coresight] [ 78.683714] coresight_register+0x1d4/0x3cc [coresight] [ 78.683721] etm4_probe+0x1e0/0x334 [coresight_etm4x] [ 78.683729] etm4_probe_amba+0x44/0xa0 [coresight_etm4x] [ 78.683735] amba_probe+0x11c/0x1b0 [ 78.683741] really_probe+0x19c/0x3f0 [ 78.683747] __driver_probe_device+0x11c/0x190 [ 78.683749] driver_probe_device+0x44/0xf4 [ 78.683753] __driver_attach+0xd8/0x1b4 [ 78.683756] bus_for_each_dev+0x6c/0xb0 [ 78.683758] driver_attach+0x30/0x40 [ 78.683761] bus_add_driver+0x154/0x240 [ 78.683763] driver_register+0x84/0x140 [ 78.683765] amba_driver_register+0x30/0x44 [ 78.683768] etm4x_init+0xd8/0x1000 [coresight_etm4x] [ 78.683775] do_one_initcall+0x40/0x220 [ 78.683778] do_init_module+0x50/0x1f4 [ 78.683782] load_module+0x940/0xaf0 [ 78.683783] __do_sys_finit_module+0x9c/0xfc [ 78.683785] __arm64_sys_finit_module+0x2c/0x40 [ 78.683787] invoke_syscall+0x50/0x120 [ 78.683790] el0_svc_common.constprop.0+0xd4/0xf4 [ 78.683792] do_el0_svc+0x38/0x4c [ 78.683794] el0_svc+0x34/0xd0 [ 78.683797] el0t_64_sync_handler+0x11c/0x150 [ 78.683799] el0t_64_sync+0x190/0x194 [ 78.725063] coresight-etm4x: probe of ARMHC500:20 failed with error -17
console log: https://s3.us-east-1.amazonaws.com/arr-cki-prod-datawarehouse-public/datawar...
more logs: https://datawarehouse.cki-project.org/kcidb/tests/3797753 cki issue tracker: https://datawarehouse.cki-project.org/issue/1261
kernel config: http://s3.amazonaws.com/arr-cki-prod-datawarehouse-public/datawarehouse-publ...
Thanks, Bruno Goncalves
linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Hi Bruno
On 08/06/2022 16:55, Mathieu Poirier wrote:
CC'ing the coresight mailing list and maintainers.
On Wed, Jun 08, 2022 at 03:20:12PM +0200, Bruno Goncalves wrote:
Hello,
We recently started to hit this call trace when loading the coresight-etm4x module.
[ 78.683475] coresight etm103: CPU103: etm v4.1 initialized [ 78.683645] sysfs: cannot create duplicate filename '/devices/system/container/ACPI0004:00/ARMHC9FE:00/funnel0/connections/in:0' [ 78.683650] CPU: 17 PID: 2522 Comm: systemd-udevd Not tainted 5.19.0-rc1 #1 [ 78.683653] Hardware name: HPE Apollo 70 /C01_APACHE_MB , BIOS L50_5.13_1.16 07/29/2020 [ 78.683655] Call trace:
Please could you confirm that there are no duplicate entries for the Graph connection for funnel0 (ARMHC9FE:00) input port 0 ?
This looks like an issue in the ACPI table. The failing ETM ACPI table describes the output port connection to the funnel0 inport 0 which I believe is connected to a different ETM that has been already probed. Does the system boot fine with the warning ? If yes, please could you check the existing link for "funnel0, in:0" ?
Suzuki
[ 78.683657] dump_backtrace+0xc4/0x130 [ 78.683665] show_stack+0x24/0x70 [ 78.683668] dump_stack_lvl+0x64/0x80 [ 78.683673] dump_stack+0x18/0x34 [ 78.683676] sysfs_warn_dup+0x70/0x90 [ 78.683681] sysfs_do_create_link_sd+0x13c/0x144 [ 78.683683] sysfs_create_link_sd+0x20/0x30 [ 78.683685] sysfs_add_link_to_group+0x48/0x74 [ 78.683688] coresight_add_sysfs_link+0xa4/0x114 [coresight] [ 78.683705] coresight_make_links+0x98/0xdc [coresight] [ 78.683714] coresight_register+0x1d4/0x3cc [coresight] [ 78.683721] etm4_probe+0x1e0/0x334 [coresight_etm4x] [ 78.683729] etm4_probe_amba+0x44/0xa0 [coresight_etm4x] [ 78.683735] amba_probe+0x11c/0x1b0 [ 78.683741] really_probe+0x19c/0x3f0 [ 78.683747] __driver_probe_device+0x11c/0x190 [ 78.683749] driver_probe_device+0x44/0xf4 [ 78.683753] __driver_attach+0xd8/0x1b4 [ 78.683756] bus_for_each_dev+0x6c/0xb0 [ 78.683758] driver_attach+0x30/0x40 [ 78.683761] bus_add_driver+0x154/0x240 [ 78.683763] driver_register+0x84/0x140 [ 78.683765] amba_driver_register+0x30/0x44 [ 78.683768] etm4x_init+0xd8/0x1000 [coresight_etm4x] [ 78.683775] do_one_initcall+0x40/0x220 [ 78.683778] do_init_module+0x50/0x1f4 [ 78.683782] load_module+0x940/0xaf0 [ 78.683783] __do_sys_finit_module+0x9c/0xfc [ 78.683785] __arm64_sys_finit_module+0x2c/0x40 [ 78.683787] invoke_syscall+0x50/0x120 [ 78.683790] el0_svc_common.constprop.0+0xd4/0xf4 [ 78.683792] do_el0_svc+0x38/0x4c [ 78.683794] el0_svc+0x34/0xd0 [ 78.683797] el0t_64_sync_handler+0x11c/0x150 [ 78.683799] el0t_64_sync+0x190/0x194 [ 78.725063] coresight-etm4x: probe of ARMHC500:20 failed with error -17
console log: https://s3.us-east-1.amazonaws.com/arr-cki-prod-datawarehouse-public/datawar...
more logs: https://datawarehouse.cki-project.org/kcidb/tests/3797753 cki issue tracker: https://datawarehouse.cki-project.org/issue/1261
kernel config: http://s3.amazonaws.com/arr-cki-prod-datawarehouse-public/datawarehouse-publ...
Thanks, Bruno Goncalves
linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
-
Mathieu Poirier -
Suzuki K Poulose