root@host1:~/fio# uname -a Linux host1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:20:17 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux
root@host1:~/fio# dpkg -S $(which perf) linux-tools-common: /usr/bin/perf root@host1:~/fio# dpkg --get-selections | grep linux-tools linux-tools-4.10.0-11 install linux-tools-4.10.0-13 install linux-tools-4.10.0-13-generic install linux-tools-4.10.0-14 install linux-tools-4.10.0-14-generic install linux-tools-4.10.0-9 install linux-tools-4.10.0-9-generic install linux-tools-common install linux-tools-generic install Running perf like: perf record -F 99 -g -- sleep 10 also has the same issue I've been running: perf record -a -- sleep 10 Annotation works on kernel modules and user code, but non-module kernel code has the issue where annotation doesn't work on it. After running record, run perf report, select one of the kernel symbols, hit enter, select Annotate <symbol> and hit enter again. Thanks, Ali -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675949 Title: perf report can't annotate kernel and dbgsym package has wrong addresses Status in linux package in Ubuntu: Incomplete Bug description: Running zesty 4.10.0-13-generic kernel and running: $ perf record followed by $ perf report results in output that can't be annotated (even when run as root). The following message appears: Couldn't annotate do_io_submit: No vmlinux file with build id 81ba79d482fa9e3ea58486de8f119b27fe6db55e was found in the path. Note that annotation using /proc/kcore requires CAP_SYS_RAWIO capability. Please use: perf buildid-cache -vu vmlinux Note this is being run as root and /proc/kcore is accessible with dd from the same shell: $ dd if=/proc/kcore bs=8 count=16 | hexdump 0000000 457f 464c 0102 0001 0000 0000 0000 0000 0000010 0004 00b7 0001 0000 0000 0000 0000 0000 0000020 0040 0000 0000 0000 0000 0000 0000 0000 0000030 0000 0000 0040 0038 0003 0000 0000 0000 0000040 0004 0000 0000 0000 00e8 0000 0000 0000 Additionally, installing the linux-image-4.10.0-13-generic-dbgsym actually hurts the situation because the symbol addresses in the dbgsym don't match the kernel addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
