* ❌ FAIL (MISSED 2 of 87): Test report for for-kernelci (6.9.0-rc4, arm-next, 6a71d290)
@ 2024-04-19 20:30 cki-project
2024-04-22 17:08 ` Will Deacon
0 siblings, 1 reply; 8+ messages in thread
From: cki-project @ 2024-04-19 20:30 UTC (permalink / raw
To: catalin.marinas, will, linux-arm-kernel, bgoncalv
Hi, we tested your kernel and here are the results:
Overall result: FAILED
Merge: OK
Compile: OK
Test: FAILED
Kernel information:
Commit message: Merge branch 'for-next/core' into for-kernelci
You can find all the details about the test run at
https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:1260423326
One or more kernel tests failed:
Unrecognized or new issues:
Boot test
aarch64
Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1260423326-aarch64-kernel_upt_4
Non-passing ran subtests:
❌ FAIL distribution/kpkginstall/journalctl-check
Reboot test
aarch64
Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1260423326-aarch64-kernel_upt_10
Non-passing ran subtests:
❌ FAIL misc/reboot-test/journalctl-check
We also see the following known issues which are not related to your changes:
Issue: [upstream] blktests tests/zbd/010 failed (WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51)
URL: https://lore.kernel.org/linux-block/CAHj4cs-kfojYC9i0G73PRkYzcxCTex=-vugRFeP40g_URGvnfQ@mail.gmail.com/T/#u
Affected tests:
Storage - blktests - blk - upstream [aarch64]
Issue: [Rawhide] avc: denied { getattr } for pid=79656 comm="selinux-autorel" path="/etc/passwd" dev="dm-0" ino=17705170 scontext=system_u:system_r:selinux_autorelabel_generator_t:s0 tcontext=system_u:object_r:passwd_file_t:s0 tclass=file permissive=1
URL: https://bugzilla.redhat.com/show_bug.cgi?id=2275266
Affected tests:
Filesystem - Loopdev Sanity [aarch64]
Networking cki netfilter test [aarch64]
Networking vnic: ipvlan/basic [aarch64]
POSIX pjd-fstest suites [aarch64]
Storage - blktests - blk - upstream [aarch64]
stress: stress-ng - cpu-cache [aarch64]
stress: stress-ng - memory [aarch64]
xfstests - btrfs [aarch64]
xfstests - ext4 [aarch64]
xfstests - xfs [aarch64]
Issue: [upstream] stress-ng: avc denial on secretmemory
URL: https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/1752
Affected tests:
stress: stress-ng - memory [aarch64]
Tests that were not ran because of internal issues:
Memory function: memfd_create [aarch64]
If you find a failure unrelated to your changes, please ask the test maintainer to review it.
This will prevent the failures from being incorrectly reported in the future.
Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: ❌ FAIL (MISSED 2 of 87): Test report for for-kernelci (6.9.0-rc4, arm-next, 6a71d290)
2024-04-19 20:30 ❌ FAIL (MISSED 2 of 87): Test report for for-kernelci (6.9.0-rc4, arm-next, 6a71d290) cki-project
@ 2024-04-22 17:08 ` Will Deacon
2024-04-23 11:06 ` Suzuki K Poulose
2024-04-23 11:14 ` James Clark
0 siblings, 2 replies; 8+ messages in thread
From: Will Deacon @ 2024-04-22 17:08 UTC (permalink / raw
To: cki-project, suzuki.poulose, mike.leach, james.clark
Cc: catalin.marinas, linux-arm-kernel, bgoncalv, Jonathan.Cameron
[+Suzuki, Mike and James]
On Fri, Apr 19, 2024 at 08:30:09PM -0000, cki-project@redhat.com wrote:
> Hi, we tested your kernel and here are the results:
>
> Overall result: FAILED
> Merge: OK
> Compile: OK
> Test: FAILED
>
>
> Kernel information:
> Commit message: Merge branch 'for-next/core' into for-kernelci
>
> You can find all the details about the test run at
> https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:1260423326
>
> One or more kernel tests failed:
> Unrecognized or new issues:
> Boot test
> aarch64
> Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1260423326-aarch64-kernel_upt_4
> Non-passing ran subtests:
> ❌ FAIL distribution/kpkginstall/journalctl-check
I'm not sure if it's the root cause, but the logs here have a tonne of
coresight ETM splats (I included one at the end of the mail).
https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/trusted-artifacts/1260423326/test_aarch64/6670265232/artifacts/run.done.01/job.01/recipes/15985953/tasks/5/results/1713555252/logs/journalctl.log
Jonathan has recently done a bunch of work fixing up the ->parent
pointers for PMU devices, but I don't see anything going near the
coresight drivers so this is probably unrelated.
Will
--->8
Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: CSCFG registered etm103
Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: coresight etm103: CPU103: etm v4.1 initialized
Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: sysfs: cannot create duplicate filename '/devices/system/container/ACPI0004:00/ARMHC9FE:00/funnel0/connections/in:0'
Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: mlx5_core 0000:0b:00.0: Adding to iommu group 1
Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: CPU: 42 PID: 2528 Comm: (udev-worker) Not tainted 6.9.0-rc4 #1
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: mlx5_core 0000:0b:00.0: firmware version: 14.21.1000
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: Hardware name: HPE Apollo 70 /C01_APACHE_MB , BIOS L50_5.13_1.16 07/29/2020
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: Call trace:
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: dump_backtrace+0xdc/0x140
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: mlx5_core 0000:0b:00.0: 63.008 Gb/s available PCIe bandwidth (8.0 GT/s PCIe x8 link)
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: show_stack+0x20/0x40
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: dump_stack_lvl+0x60/0x80
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: dump_stack+0x18/0x28
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: sysfs_warn_dup+0x6c/0x90
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: sysfs_do_create_link_sd+0xf8/0x108
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: sysfs_create_link_sd+0x1c/0x30
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: sysfs_add_link_to_group+0x44/0x80
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: coresight_add_sysfs_link+0xa0/0x118 [coresight]
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: coresight_make_links+0xa0/0x108 [coresight]
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: coresight_orphan_match+0xf4/0x138 [coresight]
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: bus_for_each_dev+0x84/0x100
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: coresight_register+0x178/0x270 [coresight]
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: ipmi_ssif i2c-IPI0001:06: IPMI message handler: Found new BMC (man_id: 0x00b3d1, prod_id: 0x0202, dev_id: 0x20)
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: etm4_add_coresight_dev.isra.0+0x14c/0x270 [coresight_etm4x]
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: etm4_probe+0x108/0x188 [coresight_etm4x]
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: etm4_probe_platform_dev+0xd8/0x188 [coresight_etm4x]
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: platform_probe+0x70/0xe8
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: really_probe+0xc8/0x3a0
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: __driver_probe_device+0x84/0x160
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: driver_probe_device+0x44/0x130
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: __driver_attach+0xcc/0x208
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: bus_for_each_dev+0x84/0x100
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: driver_attach+0x2c/0x40
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: bus_add_driver+0x11c/0x238
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: driver_register+0x70/0x138
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: __platform_driver_register+0x30/0x48
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: etm4x_init+0xec/0xff8 [coresight_etm4x]
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: do_one_initcall+0x60/0x318
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: do_init_module+0x68/0x260
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: load_module+0x62c/0x760
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: init_module_from_file+0x90/0xe0
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: idempotent_init_module+0x18c/0x2b8
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: __arm64_sys_finit_module+0x6c/0xe0
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: invoke_syscall+0x74/0x100
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: el0_svc_common.constprop.0+0xc8/0xf0
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: do_el0_svc+0x24/0x38
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: el0_svc+0x3c/0x158
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: el0t_64_sync_handler+0x120/0x138
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: el0t_64_sync+0x194/0x198
Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: coresight-etm4x ARMHC500:20: probe with driver coresight-etm4x failed with error -17
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: ❌ FAIL (MISSED 2 of 87): Test report for for-kernelci (6.9.0-rc4, arm-next, 6a71d290)
2024-04-22 17:08 ` Will Deacon
@ 2024-04-23 11:06 ` Suzuki K Poulose
2024-04-23 11:14 ` James Clark
1 sibling, 0 replies; 8+ messages in thread
From: Suzuki K Poulose @ 2024-04-23 11:06 UTC (permalink / raw
To: Will Deacon, cki-project, mike.leach, james.clark
Cc: catalin.marinas, linux-arm-kernel, bgoncalv, Jonathan.Cameron
Hi Will
On 22/04/2024 18:08, Will Deacon wrote:
> [+Suzuki, Mike and James]
Thanks for looping us in.
>
> On Fri, Apr 19, 2024 at 08:30:09PM -0000, cki-project@redhat.com wrote:
>> Hi, we tested your kernel and here are the results:
>>
>> Overall result: FAILED
>> Merge: OK
>> Compile: OK
>> Test: FAILED
>>
>>
>> Kernel information:
>> Commit message: Merge branch 'for-next/core' into for-kernelci
>>
>> You can find all the details about the test run at
>> https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:1260423326
>>
>> One or more kernel tests failed:
>> Unrecognized or new issues:
>> Boot test
>> aarch64
>> Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1260423326-aarch64-kernel_upt_4
>> Non-passing ran subtests:
>> ❌ FAIL distribution/kpkginstall/journalctl-check
>
> I'm not sure if it's the root cause, but the logs here have a tonne of
> coresight ETM splats (I included one at the end of the mail).
>
> https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/trusted-artifacts/1260423326/test_aarch64/6670265232/artifacts/run.done.01/job.01/recipes/15985953/tasks/5/results/1713555252/logs/journalctl.log
>
> Jonathan has recently done a bunch of work fixing up the ->parent
> pointers for PMU devices, but I don't see anything going near the
> coresight drivers so this is probably unrelated.
>
> Will
>
> --->8
>
> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: CSCFG registered etm103
> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: coresight etm103: CPU103: etm v4.1 initialized
> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: sysfs: cannot create duplicate filename '/devices/system/container/ACPI0004:00/ARMHC9FE:00/funnel0/connections/in:0'
That looks like a buggy ACPI table to me. We don't reach anywhwere near
the PMU part yet. This is during the initial probe, the driver finds the
connections and exposes them in sysfs. I have, in the past seen a
similar splat (from a similar Cavium/Marvell).
Looks like one of the funnels have got duplicate "input port0"
connections. Most likely two different "ETMs" have described
their output port is connected to the same input port (0), of a
funnel.
Has this platform ever run CoreSight with ACPI tables in the past ?
Suzuki
> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: mlx5_core 0000:0b:00.0: Adding to iommu group 1
> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: CPU: 42 PID: 2528 Comm: (udev-worker) Not tainted 6.9.0-rc4 #1
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: mlx5_core 0000:0b:00.0: firmware version: 14.21.1000
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: Hardware name: HPE Apollo 70 /C01_APACHE_MB , BIOS L50_5.13_1.16 07/29/2020
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: Call trace:
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: dump_backtrace+0xdc/0x140
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: mlx5_core 0000:0b:00.0: 63.008 Gb/s available PCIe bandwidth (8.0 GT/s PCIe x8 link)
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: show_stack+0x20/0x40
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: dump_stack_lvl+0x60/0x80
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: dump_stack+0x18/0x28
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: sysfs_warn_dup+0x6c/0x90
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: sysfs_do_create_link_sd+0xf8/0x108
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: sysfs_create_link_sd+0x1c/0x30
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: sysfs_add_link_to_group+0x44/0x80
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: coresight_add_sysfs_link+0xa0/0x118 [coresight]
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: coresight_make_links+0xa0/0x108 [coresight]
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: coresight_orphan_match+0xf4/0x138 [coresight]
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: bus_for_each_dev+0x84/0x100
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: coresight_register+0x178/0x270 [coresight]
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: ipmi_ssif i2c-IPI0001:06: IPMI message handler: Found new BMC (man_id: 0x00b3d1, prod_id: 0x0202, dev_id: 0x20)
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: etm4_add_coresight_dev.isra.0+0x14c/0x270 [coresight_etm4x]
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: etm4_probe+0x108/0x188 [coresight_etm4x]
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: etm4_probe_platform_dev+0xd8/0x188 [coresight_etm4x]
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: platform_probe+0x70/0xe8
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: really_probe+0xc8/0x3a0
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: __driver_probe_device+0x84/0x160
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: driver_probe_device+0x44/0x130
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: __driver_attach+0xcc/0x208
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: bus_for_each_dev+0x84/0x100
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: driver_attach+0x2c/0x40
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: bus_add_driver+0x11c/0x238
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: driver_register+0x70/0x138
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: __platform_driver_register+0x30/0x48
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: etm4x_init+0xec/0xff8 [coresight_etm4x]
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: do_one_initcall+0x60/0x318
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: do_init_module+0x68/0x260
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: load_module+0x62c/0x760
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: init_module_from_file+0x90/0xe0
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: idempotent_init_module+0x18c/0x2b8
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: __arm64_sys_finit_module+0x6c/0xe0
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: invoke_syscall+0x74/0x100
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: el0_svc_common.constprop.0+0xc8/0xf0
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: do_el0_svc+0x24/0x38
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: el0_svc+0x3c/0x158
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: el0t_64_sync_handler+0x120/0x138
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: el0t_64_sync+0x194/0x198
> Apr 19 15:33:39 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: coresight-etm4x ARMHC500:20: probe with driver coresight-etm4x failed with error -17
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: ❌ FAIL (MISSED 2 of 87): Test report for for-kernelci (6.9.0-rc4, arm-next, 6a71d290)
2024-04-22 17:08 ` Will Deacon
2024-04-23 11:06 ` Suzuki K Poulose
@ 2024-04-23 11:14 ` James Clark
2024-04-23 11:17 ` James Clark
1 sibling, 1 reply; 8+ messages in thread
From: James Clark @ 2024-04-23 11:14 UTC (permalink / raw
To: Will Deacon, cki-project, suzuki.poulose, mike.leach
Cc: catalin.marinas, linux-arm-kernel, bgoncalv, Jonathan.Cameron
On 22/04/2024 18:08, Will Deacon wrote:
> [+Suzuki, Mike and James]
>
> On Fri, Apr 19, 2024 at 08:30:09PM -0000, cki-project@redhat.com wrote:
>> Hi, we tested your kernel and here are the results:
>>
>> Overall result: FAILED
>> Merge: OK
>> Compile: OK
>> Test: FAILED
>>
>>
>> Kernel information:
>> Commit message: Merge branch 'for-next/core' into for-kernelci
>>
>> You can find all the details about the test run at
>> https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:1260423326
>>
>> One or more kernel tests failed:
>> Unrecognized or new issues:
>> Boot test
>> aarch64
>> Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1260423326-aarch64-kernel_upt_4
>> Non-passing ran subtests:
>> ❌ FAIL distribution/kpkginstall/journalctl-check
>
> I'm not sure if it's the root cause, but the logs here have a tonne of
> coresight ETM splats (I included one at the end of the mail).
>
> https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/trusted-artifacts/1260423326/test_aarch64/6670265232/artifacts/run.done.01/job.01/recipes/15985953/tasks/5/results/1713555252/logs/journalctl.log
>
> Jonathan has recently done a bunch of work fixing up the ->parent
> pointers for PMU devices, but I don't see anything going near the
> coresight drivers so this is probably unrelated.
>
> Will
>
> --->8
>
> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: CSCFG registered etm103
> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: coresight etm103: CPU103: etm v4.1 initialized
> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: sysfs: cannot create duplicate filename '/devices/system/container/ACPI0004:00/ARMHC9FE:00/funnel0/connections/in:0'
Hi Will,
It looks like multiple ETMs are described as being connected to the same
port on a funnel. Those connections to build the filename string all
come from the firmware. I don't think there are any changes since 6.8 in
Coresight that would affect device registration.
I did try to find some previous runs on that machine and I found this
message
(https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/trusted-artifacts/1260423326/test_aarch64/6670265232/artifacts/run.done.01/job.01/recipes/15985953/tasks/5/results/1713555252/logs/journalctl.log):
"ETM4 disabled due to firmware bug"
Although I couldn't find where that string comes from. It seems to me
like there has been a firmware change on that machine recently, or this
is the first time it's been booted with Coresight enabled.
Also possible is that we removed the kernel part that disabled it due to
whatever that flag is, but I don't think that's happened. Maybe Suzuki
knows about that message and could comment?
Thanks
James
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: ❌ FAIL (MISSED 2 of 87): Test report for for-kernelci (6.9.0-rc4, arm-next, 6a71d290)
2024-04-23 11:14 ` James Clark
@ 2024-04-23 11:17 ` James Clark
2024-04-23 11:49 ` Suzuki K Poulose
0 siblings, 1 reply; 8+ messages in thread
From: James Clark @ 2024-04-23 11:17 UTC (permalink / raw
To: Will Deacon, cki-project, suzuki.poulose, mike.leach
Cc: catalin.marinas, linux-arm-kernel, bgoncalv, Jonathan.Cameron
On 23/04/2024 12:14, James Clark wrote:
>
>
> On 22/04/2024 18:08, Will Deacon wrote:
>> [+Suzuki, Mike and James]
>>
>> On Fri, Apr 19, 2024 at 08:30:09PM -0000, cki-project@redhat.com wrote:
>>> Hi, we tested your kernel and here are the results:
>>>
>>> Overall result: FAILED
>>> Merge: OK
>>> Compile: OK
>>> Test: FAILED
>>>
>>>
>>> Kernel information:
>>> Commit message: Merge branch 'for-next/core' into for-kernelci
>>>
>>> You can find all the details about the test run at
>>> https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:1260423326
>>>
>>> One or more kernel tests failed:
>>> Unrecognized or new issues:
>>> Boot test
>>> aarch64
>>> Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1260423326-aarch64-kernel_upt_4
>>> Non-passing ran subtests:
>>> ❌ FAIL distribution/kpkginstall/journalctl-check
>>
>> I'm not sure if it's the root cause, but the logs here have a tonne of
>> coresight ETM splats (I included one at the end of the mail).
>>
>> https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/trusted-artifacts/1260423326/test_aarch64/6670265232/artifacts/run.done.01/job.01/recipes/15985953/tasks/5/results/1713555252/logs/journalctl.log
>>
>> Jonathan has recently done a bunch of work fixing up the ->parent
>> pointers for PMU devices, but I don't see anything going near the
>> coresight drivers so this is probably unrelated.
>>
>> Will
>>
>> --->8
>>
>> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: CSCFG registered etm103
>> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: coresight etm103: CPU103: etm v4.1 initialized
>> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: sysfs: cannot create duplicate filename '/devices/system/container/ACPI0004:00/ARMHC9FE:00/funnel0/connections/in:0'
>
> Hi Will,
>
> It looks like multiple ETMs are described as being connected to the same
> port on a funnel. Those connections to build the filename string all
> come from the firmware. I don't think there are any changes since 6.8 in
> Coresight that would affect device registration.
>
> I did try to find some previous runs on that machine and I found this
> message
> (https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/trusted-artifacts/1260423326/test_aarch64/6670265232/artifacts/run.done.01/job.01/recipes/15985953/tasks/5/results/1713555252/logs/journalctl.log):
>
> "ETM4 disabled due to firmware bug"
>
> Although I couldn't find where that string comes from. It seems to me
> like there has been a firmware change on that machine recently, or this
> is the first time it's been booted with Coresight enabled.
>
> Also possible is that we removed the kernel part that disabled it due to
> whatever that flag is, but I don't think that's happened. Maybe Suzuki
> knows about that message and could comment?
>
> Thanks
>
> James
Ok I found the string, it's from an out of tree patch:
https://src.fedoraproject.org/rpms/kernel/c/2db8df88f66eacaa9bec1995431388fb3a044566.patch
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: ❌ FAIL (MISSED 2 of 87): Test report for for-kernelci (6.9.0-rc4, arm-next, 6a71d290)
2024-04-23 11:17 ` James Clark
@ 2024-04-23 11:49 ` Suzuki K Poulose
[not found] ` <2d319f18-c279-48de-88cd-add456fe731en@redhat.com>
0 siblings, 1 reply; 8+ messages in thread
From: Suzuki K Poulose @ 2024-04-23 11:49 UTC (permalink / raw
To: James Clark, Will Deacon, cki-project, mike.leach
Cc: catalin.marinas, linux-arm-kernel, bgoncalv, Jonathan.Cameron
On 23/04/2024 12:17, James Clark wrote:
>
>
> On 23/04/2024 12:14, James Clark wrote:
>>
>>
>> On 22/04/2024 18:08, Will Deacon wrote:
>>> [+Suzuki, Mike and James]
>>>
>>> On Fri, Apr 19, 2024 at 08:30:09PM -0000, cki-project@redhat.com wrote:
>>>> Hi, we tested your kernel and here are the results:
>>>>
>>>> Overall result: FAILED
>>>> Merge: OK
>>>> Compile: OK
>>>> Test: FAILED
>>>>
>>>>
>>>> Kernel information:
>>>> Commit message: Merge branch 'for-next/core' into for-kernelci
>>>>
>>>> You can find all the details about the test run at
>>>> https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:1260423326
>>>>
>>>> One or more kernel tests failed:
>>>> Unrecognized or new issues:
>>>> Boot test
>>>> aarch64
>>>> Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1260423326-aarch64-kernel_upt_4
>>>> Non-passing ran subtests:
>>>> ❌ FAIL distribution/kpkginstall/journalctl-check
>>>
>>> I'm not sure if it's the root cause, but the logs here have a tonne of
>>> coresight ETM splats (I included one at the end of the mail).
>>>
>>> https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/trusted-artifacts/1260423326/test_aarch64/6670265232/artifacts/run.done.01/job.01/recipes/15985953/tasks/5/results/1713555252/logs/journalctl.log
>>>
>>> Jonathan has recently done a bunch of work fixing up the ->parent
>>> pointers for PMU devices, but I don't see anything going near the
>>> coresight drivers so this is probably unrelated.
>>>
>>> Will
>>>
>>> --->8
>>>
>>> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: CSCFG registered etm103
>>> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: coresight etm103: CPU103: etm v4.1 initialized
>>> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel: sysfs: cannot create duplicate filename '/devices/system/container/ACPI0004:00/ARMHC9FE:00/funnel0/connections/in:0'
>>
>> Hi Will,
>>
>> It looks like multiple ETMs are described as being connected to the same
>> port on a funnel. Those connections to build the filename string all
>> come from the firmware. I don't think there are any changes since 6.8 in
>> Coresight that would affect device registration.
>>
>> I did try to find some previous runs on that machine and I found this
>> message
>> (https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/trusted-artifacts/1260423326/test_aarch64/6670265232/artifacts/run.done.01/job.01/recipes/15985953/tasks/5/results/1713555252/logs/journalctl.log):
>>
>> "ETM4 disabled due to firmware bug"
>>
>> Although I couldn't find where that string comes from. It seems to me
>> like there has been a firmware change on that machine recently, or this
>> is the first time it's been booted with Coresight enabled.
>>
>> Also possible is that we removed the kernel part that disabled it due to
>> whatever that flag is, but I don't think that's happened. Maybe Suzuki
>> knows about that message and could comment?
>>
>> Thanks
>>
>> James
>
> Ok I found the string, it's from an out of tree patch:
>
> https://src.fedoraproject.org/rpms/kernel/c/2db8df88f66eacaa9bec1995431388fb3a044566.patch
>
>
Could they not black list the coresight* modules on the system ?
Suzuki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: ❌ FAIL (MISSED 2 of 87): Test report for for-kernelci (6.9.0-rc4, arm-next, 6a71d290)
[not found] ` <2d319f18-c279-48de-88cd-add456fe731en@redhat.com>
@ 2024-04-23 15:23 ` Jeremy Linton
2024-04-23 15:36 ` Jeremy Linton
0 siblings, 1 reply; 8+ messages in thread
From: Jeremy Linton @ 2024-04-23 15:23 UTC (permalink / raw
To: Donald Zickus, cki-project
Cc: Suzuki K Poulose, catalin.marinas@arm.com,
linux-arm-kernel@lists.infradead.org, Bruno Goncalves,
Jonathan.Cameron@huawei.com, James Clark, Will Deacon,
mike.leach@linaro.org
Hi,
On 4/23/24 09:42, Donald Zickus wrote:
> (adding Jeremy Linton as the author of the out of tree patch)
>
> Hi Jeremy,
>
>
> On Tuesday, April 23, 2024 at 7:49:26 AM UTC-4 Suzuki K Poulose wrote:
>
> On 23/04/2024 12:17, James Clark wrote:
>>
>>
>> On 23/04/2024 12:14, James Clark wrote:
>>>
>>>
>>> On 22/04/2024 18:08, Will Deacon wrote:
>>>> [+Suzuki, Mike and James]
>>>>
>>>> On Fri, Apr 19, 2024 at 08:30:09PM -0000, cki-project@redhat.com wrote:
>>>>> Hi, we tested your kernel and here are the results:
>>>>>
>>>>> Overall result: FAILED
>>>>> Merge: OK
>>>>> Compile: OK
>>>>> Test: FAILED
>>>>>
>>>>>
>>>>> Kernel information:
>>>>> Commit message: Merge branch 'for-next/core' into for-kernelci
>>>>>
>>>>> You can find all the details about the test run at
>>>>> https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:1260423326
>>>>>
>>>>> One or more kernel tests failed:
>>>>> Unrecognized or new issues:
>>>>> Boot test
>>>>> aarch64
>>>>> Logs: https://datawarehouse.cki-project.org/kcidb/tests/
> redhat:1260423326-aarch64-kernel_upt_4
>>>>> Non-passing ran subtests:
>>>>> ❌ FAIL distribution/kpkginstall/journalctl-check
>>>>
>>>> I'm not sure if it's the root cause, but the logs here have a tonne of
>>>> coresight ETM splats (I included one at the end of the mail).
>>>>
>>>> https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/
> trusted-artifacts/1260423326/test_aarch64/6670265232/
> artifacts/run.done.01/job.01/recipes/15985953/tasks/5/
> results/1713555252/logs/journalctl.log
>>>>
>>>> Jonathan has recently done a bunch of work fixing up the ->parent
>>>> pointers for PMU devices, but I don't see anything going near the
>>>> coresight drivers so this is probably unrelated.
>>>>
>>>> Will
>>>>
>>>> --->8
>>>>
>>>> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel:
> CSCFG registered etm103
>>>> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel:
> coresight etm103: CPU103: etm v4.1 initialized
>>>> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com kernel:
> sysfs: cannot create duplicate filename '/devices/system/container/
> ACPI0004:00/ARMHC9FE:00/funnel0/connections/in:0'
>>>
>>> Hi Will,
>>>
>>> It looks like multiple ETMs are described as being connected to the same
>>> port on a funnel. Those connections to build the filename string all
>>> come from the firmware. I don't think there are any changes since 6.8 in
>>> Coresight that would affect device registration.
>>>
>>> I did try to find some previous runs on that machine and I found this
>>> message
>>> (https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/
> trusted-artifacts/1260423326/test_aarch64/6670265232/
> artifacts/run.done.01/job.01/recipes/15985953/tasks/5/
> results/1713555252/logs/journalctl.log):
>>>
>>> "ETM4 disabled due to firmware bug"
>>>
>>> Although I couldn't find where that string comes from. It seems to me
>>> like there has been a firmware change on that machine recently, or this
>>> is the first time it's been booted with Coresight enabled.
>>>
>>> Also possible is that we removed the kernel part that disabled it due to
>>> whatever that flag is, but I don't think that's happened. Maybe Suzuki
>>> knows about that message and could comment?
>>>
>>> Thanks
>>>
>>> James
>>
>> Ok I found the string, it's from an out of tree patch:
>>
>> https://src.fedoraproject.org/rpms/kernel/c/2db8df88f66eacaa9bec1995431388
> fb3a044566.patch
>
>
> Is your patch [1] still relevant in light of the current splat?
Yes. because the firmware doesn't appear to be updated on the test machine.
The downstream patch is quirking/disabling coresight on the machine in
question because the table is just fundamentally broken. So, yes the
module could be blacklisted if the test harness could do that on a
machine by machine basis, or for that matter a corrected table could
also be injected.
>
> Cheers,
> Don
>
> [1]
> - https://gitlab.com/cki-project/kernel-ark/-/commit/ea9bdc9a2dd2fe5aa2de58dcbfa14f64bdd4d716
>
>
>>
>>
>
>
> Could they not black list the coresight* modules on the system ?
>
> Suzuki
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: ❌ FAIL (MISSED 2 of 87): Test report for for-kernelci (6.9.0-rc4, arm-next, 6a71d290)
2024-04-23 15:23 ` Jeremy Linton
@ 2024-04-23 15:36 ` Jeremy Linton
0 siblings, 0 replies; 8+ messages in thread
From: Jeremy Linton @ 2024-04-23 15:36 UTC (permalink / raw
To: Donald Zickus, cki-project
Cc: Suzuki K Poulose, catalin.marinas@arm.com,
linux-arm-kernel@lists.infradead.org, Bruno Goncalves,
Jonathan.Cameron@huawei.com, James Clark, Will Deacon,
mike.leach@linaro.org
Hi,
I'm fairly certain I had a conversation about whether that patch should
be upstream and there wasn't a big desire to carry it upstream for
$REASONS. But google/etc can't seem to find the conversation so maybe it
didn't happen in public.
So, I will post it there is a willingness to carry it.
Thanks,
On 4/23/24 10:23, Jeremy Linton wrote:
> Hi,
>
> On 4/23/24 09:42, Donald Zickus wrote:
>> (adding Jeremy Linton as the author of the out of tree patch)
>>
>> Hi Jeremy,
>>
>>
>> On Tuesday, April 23, 2024 at 7:49:26 AM UTC-4 Suzuki K Poulose wrote:
>>
>> On 23/04/2024 12:17, James Clark wrote:
>>>
>>>
>>> On 23/04/2024 12:14, James Clark wrote:
>>>>
>>>>
>>>> On 22/04/2024 18:08, Will Deacon wrote:
>>>>> [+Suzuki, Mike and James]
>>>>>
>>>>> On Fri, Apr 19, 2024 at 08:30:09PM -0000, cki-project@redhat.com
>>>>> wrote:
>>>>>> Hi, we tested your kernel and here are the results:
>>>>>>
>>>>>> Overall result: FAILED
>>>>>> Merge: OK
>>>>>> Compile: OK
>>>>>> Test: FAILED
>>>>>>
>>>>>>
>>>>>> Kernel information:
>>>>>> Commit message: Merge branch 'for-next/core' into for-kernelci
>>>>>>
>>>>>> You can find all the details about the test run at
>>>>>> https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:1260423326
>>>>>>
>>>>>> One or more kernel tests failed:
>>>>>> Unrecognized or new issues:
>>>>>> Boot test
>>>>>> aarch64
>>>>>> Logs: https://datawarehouse.cki-project.org/kcidb/tests/
>> redhat:1260423326-aarch64-kernel_upt_4
>>>>>> Non-passing ran subtests:
>>>>>> ❌ FAIL distribution/kpkginstall/journalctl-check
>>>>>
>>>>> I'm not sure if it's the root cause, but the logs here have a tonne of
>>>>> coresight ETM splats (I included one at the end of the mail).
>>>>>
>>>>> https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/
>> trusted-artifacts/1260423326/test_aarch64/6670265232/
>> artifacts/run.done.01/job.01/recipes/15985953/tasks/5/
>> results/1713555252/logs/journalctl.log
>>>>>
>>>>> Jonathan has recently done a bunch of work fixing up the ->parent
>>>>> pointers for PMU devices, but I don't see anything going near the
>>>>> coresight drivers so this is probably unrelated.
>>>>>
>>>>> Will
>>>>>
>>>>> --->8
>>>>>
>>>>> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com
>>>>> kernel:
>> CSCFG registered etm103
>>>>> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com
>>>>> kernel:
>> coresight etm103: CPU103: etm v4.1 initialized
>>>>> Apr 19 15:33:38 hpe-apollo-cn99xx-03.khw.eng.rdu2.dc.redhat.com
>>>>> kernel:
>> sysfs: cannot create duplicate filename '/devices/system/container/
>> ACPI0004:00/ARMHC9FE:00/funnel0/connections/in:0'
>>>>
>>>> Hi Will,
>>>>
>>>> It looks like multiple ETMs are described as being connected to the
>>>> same
>>>> port on a funnel. Those connections to build the filename string all
>>>> come from the firmware. I don't think there are any changes since
>>>> 6.8 in
>>>> Coresight that would affect device registration.
>>>>
>>>> I did try to find some previous runs on that machine and I found this
>>>> message
>>>> (https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/
>> trusted-artifacts/1260423326/test_aarch64/6670265232/
>> artifacts/run.done.01/job.01/recipes/15985953/tasks/5/
>> results/1713555252/logs/journalctl.log):
>>>>
>>>> "ETM4 disabled due to firmware bug"
>>>>
>>>> Although I couldn't find where that string comes from. It seems to me
>>>> like there has been a firmware change on that machine recently, or this
>>>> is the first time it's been booted with Coresight enabled.
>>>>
>>>> Also possible is that we removed the kernel part that disabled it
>>>> due to
>>>> whatever that flag is, but I don't think that's happened. Maybe Suzuki
>>>> knows about that message and could comment?
>>>>
>>>> Thanks
>>>>
>>>> James
>>>
>>> Ok I found the string, it's from an out of tree patch:
>>>
>>> https://src.fedoraproject.org/rpms/kernel/c/2db8df88f66eacaa9bec1995431388
>> fb3a044566.patch
>>
>>
>> Is your patch [1] still relevant in light of the current splat?
>
> Yes. because the firmware doesn't appear to be updated on the test machine.
>
> The downstream patch is quirking/disabling coresight on the machine in
> question because the table is just fundamentally broken. So, yes the
> module could be blacklisted if the test harness could do that on a
> machine by machine basis, or for that matter a corrected table could
> also be injected.
>
>
>
>
>>
>> Cheers,
>> Don
>>
>> [1]
>> -
>> https://gitlab.com/cki-project/kernel-ark/-/commit/ea9bdc9a2dd2fe5aa2de58dcbfa14f64bdd4d716
>>
>>
>>>
>>>
>>
>>
>> Could they not black list the coresight* modules on the system ?
>>
>> Suzuki
>>
>>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2024-04-23 15:37 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-04-19 20:30 ❌ FAIL (MISSED 2 of 87): Test report for for-kernelci (6.9.0-rc4, arm-next, 6a71d290) cki-project
2024-04-22 17:08 ` Will Deacon
2024-04-23 11:06 ` Suzuki K Poulose
2024-04-23 11:14 ` James Clark
2024-04-23 11:17 ` James Clark
2024-04-23 11:49 ` Suzuki K Poulose
[not found] ` <2d319f18-c279-48de-88cd-add456fe731en@redhat.com>
2024-04-23 15:23 ` Jeremy Linton
2024-04-23 15:36 ` Jeremy Linton
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.