I think this is a bug in your device tree because the KASSERT was
intentional:
- In the ACPI case, we probe for CPU PMU support before calling
armv8_pmu_init.
- In the FDT case, the PMU attaches to a node described in the device
tree.
So if you hit this KASSERT, AFAICT it means your device tree is describing
a device that is not there. Unless I'm missing something here.
Take care,
Jared
On Wed, 9 Nov 2022, Ryo Shimizu wrote:
Module Name: src
Committed By: ryo
Date: Wed Nov 9 19:06:46 UTC 2022
Modified Files:
src/sys/dev/tprof: tprof_armv8.c
Log Message:
If the hardware does not support PMU, return an error instead of KASSERT.
To generate a diff of this commit:
cvs rdiff -u -r1.14 -r1.15 src/sys/dev/tprof/tprof_armv8.c
Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.
