Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #61864 > unrolled thread
| Started by | Ralf Jung <post@ralfj.de> |
|---|---|
| First post | 2018-08-20 11:10 +0200 |
| Last post | 2019-05-24 17:30 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.kernel
Bug#906728: linux-perf-4.17: "perf report" fails with "failed to process sample" Ralf Jung <post@ralfj.de> - 2018-08-20 11:10 +0200
Bug#906728: linux-perf-4.17: "perf report" fails with "failed to process sample" Ben Hutchings <ben@decadent.org.uk> - 2019-05-24 17:30 +0200
| From | Ralf Jung <post@ralfj.de> |
|---|---|
| Date | 2018-08-20 11:10 +0200 |
| Subject | Bug#906728: linux-perf-4.17: "perf report" fails with "failed to process sample" |
| Message-ID | <woOmd-4mG-9@gated-at.bofh.it> |
Package: linux-perf-4.17 Version: 4.17.14-1 Severity: important Dear Maintainer, fairly frequently, after recording perf data with perf record -F99 --call-graph dwarf [...] when I then immediately do perf report I get an error message saying failed to process sample 0x44098e [0x8]: failed to process type: 68 making the recorded data unusable (at least so far I found no way to use it). All I can do is record again, maybe with lower frequency, and hope that this time the problematic event does not happen... I have rebooted the machine since the last kernel upgrade, so the perf tool and the running kernel should match exactly. Kind regards, Ralf -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-perf-4.17 depends on: ii libbabeltrace1 1.5.6-1 ii libc6 2.27-5 ii libdw1 0.170-0.5 ii libelf1 0.170-0.5 ii liblzma5 5.2.2-1.3 ii libnuma1 2.0.11-2.2 ii libperl5.26 5.26.2-7 ii libpython2.7 2.7.15-3 ii libslang2 2.3.2-1+b1 ii libunwind8 1.2.1-8 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages linux-perf-4.17 recommends: ii linux-base 4.5 Versions of packages linux-perf-4.17 suggests: pn linux-doc-4.17 <none> -- no debconf information
[toc] | [next] | [standalone]
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Date | 2019-05-24 17:30 +0200 |
| Message-ID | <y1kiR-7HX-3@gated-at.bofh.it> |
| In reply to | #61864 |
[Multipart message — attachments visible in raw view] — view raw
On Fri, 2019-05-24 at 14:57 +0200, Vladimír Čunát wrote: > Hello! For others who stumble on this... > > I got this message when my perf version didn't match the running kernel, > and it disappeared when I fixed that. (It was on a different distro > than Debian - NixOS, but I don't expect distro is really relevant for > this problem.) Debian doesn't have that problem, because it uses a wrapper script to select the right version for the running kernel. Ben. -- Ben Hutchings This sentence contradicts itself - no actually it doesn't.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web