Hmm, apparently /usr/bin/perf is only a wrapper script that runs the
"right" version of the perf executable for the current kernel. But the
perf executable (typically inside /usr/lib/linux-tools-VERSION) is part
of the "linux-tools-VERSION" package.
So if I do:
$ sudo apt install linux-tools-4.15
I've installed linux-tools-common 4.15.0-47.50 from bionic-proposed and
checked that the new /usr/bin/perf binary still doesn't demangle C++
symbols (even when "perf report --demangle" is passed explicitly).
** Tags removed: verification-needed-bionic
** Tags added: verification-failed-bionic
--
Note that `perf` can crash when demangling. The (trivial) patch shown below
fixes the issue for me:
http://lkml.iu.edu/hypermail/linux/kernel/1810.2/02663.html
Related libbfd issue for incorrect demangling:
https://sourceware.org/bugzilla/show_bug.cgi?id=23715
** Bug watch added: Sourceware.or
@Weasel that's a different problem, that doesn't necessarily occur with
the same CPUs. This specific bug entry is about lockups that (to quote
the original message) "typically occur when the load is low".
For example, I've had several low-load lockups on my Ryzen 1700, I
haven't had a single high
Unfortunately, setting the governor to performance doesn't fix the issue
here (Ryzen 7 1700, ASRock Fatal1ty X370 Gaming X).
--
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/1690085
Title:
As #18 pointed out, this still affects 18.04. Could the fix be ported
there?
--
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/1396654
Title:
C++ demangling support missing from perf
Stat
@Paul I understand this. I'm also monitoring the corresponding Ubuntu
issue. Still, I was asking whether there was a specific reason to
believe this bug was fixed upstream (as opposed to the fact that a
single person doesn't experience the issue anymore).
--
You received this bug notification be
(In reply to Michaël Colignon from comment #400)
>
> Hi Antoine, i checked the manual of your Asrock motherboard quickly.
> For your machine the "typical idle current" is named "c6 mode"
> Disable it and you get the "typical idle current", i think.
> While keeping the boost monothread.
Hi Michaël
I don't think there is any reason to think that the "c6 mode" option had
anything to do with "typical idle current". Its name implied that it
disabled C6 states, which it actually didn't (according to the Zenstates
script).
--
You received this bug notification because you are a member of Kernel
@Daniel what makes you think this bug is fixed? It certainly isn't for
me. I have a ASRock Fatal1ty X370 Gaming X motherboard, a Ryzen 7 1700
CPU, have updated the motherboard BIOS to its latest version (4.80 with
PinnaclePI-AM4_1.0.0.2 Patch A) and am still getting idle lockups with
kernel 4.15.
This bug still occurs for me with 4.15.0-32-generic (Ubuntu 18.04.1) if
I don't disable C6 states.
--
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/1690085
Title:
Ryzen 1800X freeze - rcu_
According at least to http://blog.programster.org/stabilizing-
ubuntu-16-04-on-ryzen, 18.04 is supposed to be ok. I haven't upgraded
yet myself.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
I got this issue after trying to install the nvidia-352 driver on my laptop (an
optimus setup with both an Intel iGPU and a NVidia GPU).
I then uninstalled the NVidia driver, but it still doesn't fix the problem,
which is mysterious.
--
You received this bug notification because you are a membe
13 matches
Mail list logo
