[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#906728: marked as done (linux-perf-4.17: "perf report" fails with "failed to process sample")



Your message dated Sat, 26 Nov 2022 20:53:12 +0100 (CET)
with message-id <20221126195312.87C3EBE2DE0@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #906728,
regarding linux-perf-4.17: "perf report" fails with "failed to process sample"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
906728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906728
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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

--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---

Reply to: