Description of problem: perf report complains that it cannot find tips.txt Version-Release number of selected component (if applicable): perf-4.10.13-200.fc25.x86_64 Steps to Reproduce: 1. perf record "ls" 2. perf report 2>&1 | cat Actual results: At the end of the output, it says # # (Cannot load tips.txt file, please install perf!) # Expected results: Given that I installed the `perf` package, running `perf` should not complain that `perf` is not installed. Additional info: 1. Google finds a patch which lets users run `perf` from its build directory, and have it find the corresponding tips.txt. I think that explains the purpose of the message (before that patch). 2. Strangely, `strace -f -e open perf report 2>&1 | grep tips.txt` does not show an attempt to open any file called tips.txt. 3. `rpm -q --dump perf| grep tips.txt` doesn't show a tips.txt file either.
Oops, it doesn't use open, because it already found the file did not exist. Here's what it's looking for: $ strace -f -e file perf report 2>&1 | grep tips.txt access("/usr/share/doc/perf-tip/tips.txt", F_OK) = -1 ENOENT (No such file or directory) access("/builddir/build/BUILD/kernel-4.10.fc25/linux-4.10.13-200.fc25.x86_64/tools/perf/Documentation/tips.txt", F_OK) = -1 ENOENT (No such file or directory) # (Cannot load tips.txt file, please install perf!)
This is a weird edge case of how perf gets packaged. We intentionally delete the tips documentation because we don't package the docs (it creates more work than benefit). Unfortunately, perf seems to think that means it isn't installed at all(?) and generates a confusing message as you've discovered. I'm torn if upstream would accept a patch to fix this or just grumble that we should package it properly.
*** Bug 1498436 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug is still happening on Fedora 27.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Yep, still happening with perf-4.15.0-300.fc27.x86_64
Still happening with perf-4.16.0-302.fc28.x86_64
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs. Fedora 27 has now been rebased to 4.17.7-100.fc27. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 28, and are still experiencing this issue, please change the version to Fedora 28. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 5 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still happening with perf-4.19.3-300.fc29.x86_64 & kernel-4.19.4-300.fc29.x86_64.
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs. Fedora 29 has now been rebased to 4.19.5-300.fc29. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
tips.txt is still missing even with kernel-4.19.6-300.fc29.x86_64
Still a problem in perf-4.19.10-300.fc29.x86_64
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs. Fedora 29 has now been rebased to 4.20.5-200.fc29. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
Still a problem with kernel-4.20.5-200.fc29.x86_64 & perf-4.20.5-200.fc29.x86_64.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs. Fedora 29 has now been rebased to 5.2.9-100.fc29. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 30, and are still experiencing this issue, please change the version to Fedora 30. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
$ strace -f -e file perf report 2>&1 | grep tips.txt access("/usr/share/doc/perf-tip/tips.txt", F_OK) = -1 ENOENT (No such file or directory) access("/builddir/build/BUILD/kernel-4.10.fc25/linux-4.10.13-200.fc25.x86_64/tools/perf/Documentation/tips.txt", F_OK) = -1 ENOENT (No such file or directory) # (Cannot load tips.txt file, please install perf!) Shows that the file is not in the rpm. Where do we find the tips.txt file that should be installed in the rpm or is there a perf-docs.rpm package?
$ strace -f -e file perf report -i perf.data.fc30 2>&1 | grep tips.txt access("/usr/share/doc/perf-tip/tips.txt", F_OK) = -1 ENOENT (No such file or directory) access("/builddir/build/BUILD/kernel-5.3.fc30/linux-5.3/tools/perf/Documentation/tips.txt", F_OK) = -1 ENOENT (No such file or directory)
The file is: For a higher level overview, try: perf report --sort comm,dso Sample related events with: perf record -e '{cycles,instructions}:S' Compare performance results with: perf diff [<old file> <new file>] Boolean options have negative forms, e.g.: perf report --no-children Customize output of perf script with: perf script -F event,ip,sym Generate a script for your data: perf script -g <lang> Save output of perf stat using: perf stat record <target workload> Create an archive with symtabs to analyse on other machine: perf archive Search options using a keyword: perf report -h <keyword> Use parent filter to see specific call path: perf report -p <regex> List events using substring match: perf list <keyword> To see list of saved events and attributes: perf evlist -v Use --symfs <dir> if your symbol files are in non-standard locations To see callchains in a more compact form: perf report -g folded Show individual samples with: perf script Limit to show entries above 5% only: perf report --percent-limit 5 Profiling branch (mis)predictions with: perf record -b / perf report Treat branches as callchains: perf report --branch-history To count events in every 1000 msec: perf stat -I 1000 Print event counts in CSV format with: perf stat -x, If you have debuginfo enabled, try: perf report -s sym,srcline For memory address profiling, try: perf mem record / perf mem report For tracepoint events, try: perf report -s trace_fields To record callchains for each sample: perf record -g To record every process run by a user: perf record -u <user> Skip collecting build-id when recording: perf record -B To change sampling frequency to 100 Hz: perf record -F 100 See assembly instructions with percentage: perf annotate <symbol> If you prefer Intel style assembly, try: perf annotate -M intel For hierarchical output, try: perf report --hierarchy Order by the overhead of source file name and line number: perf report -s srcline System-wide collection from all CPUs: perf record -a Show current config key-value pairs: perf config --list Show user configuration overrides: perf config --user --list To add Node.js USDT(User-Level Statically Defined Tracing): perf buildid-cache --add `which node` To report cacheline events from previous recording: perf c2c report I downloaded the kernel from kernel.org and copyied the file from out of the package and put it in the right spot.
Created attachment 1641702 [details] The file that should be included in either perf.rpm or kernel.rpm This file should be included in the perf rpm package or kernel package.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs. Fedora 30 has now been rebased to 5.5.7-100.fc30. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31. If you experience different issues, please open a new bug report for those.
Fixed in Fedora 32 by perf-5.5.0-0.rc6.git0.1.fc32.x86_64 which provides /usr/share/doc/perf-tip/tips.txt
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days