1. Please describe the problem: perf stat -ddd <some program e.g. ls> outputs Error: No supported events found. 2. What is the Version-Release number of the kernel: 6.19.9-200.fc43.x86_64 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : The following tests all use the latest official kernel 6.19.9-200.fc43.x86_64, only with different perf packages: Last known fully working version was perf 6.18.16-200.fc43: perf stat -ddd fortune [...} Performance counter stats for 'fortune': 20.804.185 task-clock:u # 0,712 CPUs utilized 0 context-switches:u # 0,000 /sec 0 cpu-migrations:u # 0,000 /sec 392 page-faults:u # 18,842 K/sec [...} 0,029238758 seconds time elapsed 0,018675000 seconds user 0,003119000 seconds sys Last working with some stats missing version was perf 6.19.5-200.fc43: perf stat -ddd fortune [...] Performance counter stats for 'fortune': 0 context-switches:u # 0,0 cs/sec cs_per_second 0 cpu-migrations:u # 0,0 migrations/sec migrations_per_second 388 page-faults:u # 19573,2 faults/sec page_faults_per_second 19,82 msec task-clock:u # 0,6 CPUs [...] 0,028560534 seconds time elapsed 0,019307000 seconds user 0,002041000 seconds sys First known broken version is perf 6.19.6-200.fc43: perf stat -ddd fortune Error: No supported events found. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Open a terminal and execute perf stat -ddd <program-name e.g. ls> 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: Now testing with both kernel and perf 7.0.0-0.rc5.260325gbbeb83d3182ab.44.fc45.x86_64 perf stat is fixed and works as expected. 6. Are you running any modules that not shipped with directly Fedora's kernel?: no 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. see attached dmesg.txt Reproducible: Always
Created attachment 2135053 [details] kernel journal