From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Bruno Goncalves <bgoncalv@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
CKI Project <cki-project@redhat.com>,
coresight@lists.linaro.org, Suzuki.Poulose@arm.com,
mathieu.poirier@linaro.org
Subject: Re: [aarch64] [coresight_etm4x] [kernel 5.19.0-rc1] coresight-etm4x: probe of ARMHC500:20 failed with error -17
Date: Wed, 8 Jun 2022 09:55:12 -0600 [thread overview]
Message-ID: <20220608155512.GA951633@p14s> (raw)
In-Reply-To: <CA+QYu4ogiTa1V20aqxFqBrMH0z927YNNN2O=CKma+=M_8E81iQ@mail.gmail.com>
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/datawarehouse-public/2022/06/07/558044095/redhat:558044095_aarch64/tests/Boot_test/12104911_aarch64_1_test_console.log
>
> 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-public/2022/06/07/558044095/redhat:558044095/redhat:558044095_aarch64/.config
>
> Thanks,
> Bruno Goncalves
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-08 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 13:20 [aarch64] [coresight_etm4x] [kernel 5.19.0-rc1] coresight-etm4x: probe of ARMHC500:20 failed with error -17 Bruno Goncalves
2022-06-08 15:55 ` Mathieu Poirier [this message]
2022-06-09 7:45 ` Suzuki K Poulose
2022-06-09 9:22 ` Bruno Goncalves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220608155512.GA951633@p14s \
--to=mathieu.poirier@linaro.org \
--cc=Suzuki.Poulose@arm.com \
--cc=bgoncalv@redhat.com \
--cc=cki-project@redhat.com \
--cc=coresight@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).