[Bug 1828166] Comment bridged from LTC Bugzilla

2019-10-14 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2019-10-14 07:24 EDT--- IBM Bugzilla status-> closed, Fix Released with Eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828166 Title: perf

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-08-22 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2019-08-22 09:10 EDT--- @Can: Verification done by IBM. Please work on the integration... Many thx in advance -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpa

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-08-22 Thread bugproxy
--- Comment From klaus.theur...@de.ibm.com 2019-08-22 09:02 EDT--- I talked to Thomas Richter and we agreed that his test is covering all aspects. So we can go ahead to bring this into the distros -- You received this bug notification because you are a member of Ubuntu Bugs, which is sub

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-08-19 Thread bugproxy
--- Comment From tmri...@de.ibm.com 2019-08-20 02:40 EDT--- I have installed kernel and perf tool. Now it works ok. I ran the perf top command for nearly 20 Minutes and generated a good workload. No core dump and OOM messages anymore. I could not reprodure the error and I used the same sy

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-08-11 Thread bugproxy
--- Comment From tmri...@de.ibm.com 2019-08-12 02:14 EDT--- The patches have been picked up by the perf maintainer and are now upstream in the linux kernel v5.3-rc4 b9c0a64 perf annotate: Fix s390 gap between kernel end and module start 12a6d29 perf record: Fix module size on s390 -- Yo

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-07-22 Thread bugproxy
--- Comment From tmri...@de.ibm.com 2019-07-22 05:04 EDT--- During execution of command 'perf top' the error message: Not enough memory for annotating '__irf_end' symbol!) is emitted from this call sequence: __cmd_top perf_top__mmap_read perf_top__mmap_read_idx perf_event__process_sample

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-07-19 Thread bugproxy
--- Comment From tmri...@de.ibm.com 2019-07-19 07:37 EDT--- Thanks for your help. I have installed root@s8360046:~/linux-4.15.0/tools/perf# uname -a Linux s8360046 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:54:05 UTC 2019 s390x s390x s390x GNU/Linux root@s8360046:~/linux-4.15.0/tools/

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-07-18 Thread bugproxy
--- Comment From tmri...@de.ibm.com 2019-07-18 03:46 EDT--- I have this /etc/apt/sources.list file with the following deb-src lines root@s8360046:~# fgrep bionic /etc/apt/sources.list | fgrep deb-src deb-src http://us.ports.ubuntu.com/ubuntu-ports bionic main restricted deb-src http://us.p

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-07-17 Thread bugproxy
--- Comment From mbri...@us.ibm.com 2019-07-17 11:24 EDT--- (In reply to comment #45) > How can I get the source code of the kernel tree iand the perf tool? > > I have tried this command and it did not get the sources: > > root@s8360046:~# uname -r > 4.15.0-55-generic > root@s8360046:~# apt

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-07-17 Thread bugproxy
--- Comment From tmri...@de.ibm.com 2019-07-17 11:06 EDT--- How can I get the source code of the kernel tree iand the perf tool? I have tried this command and it did not get the sources: root@s8360046:~# uname -r 4.15.0-55-generic root@s8360046:~# apt-get source linux-image-$(uname -r) Re

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-07-17 Thread bugproxy
--- Comment From klaus.theur...@de.ibm.com 2019-07-17 04:49 EDT--- from LoZ and ZaaS performance point of view we need perf for root to analyze system behavior --- Comment From tmri...@de.ibm.com 2019-07-17 04:55 EDT--- All the developer for perf on s390 I would like to investage

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-07-16 Thread bugproxy
--- Comment From klaus.theur...@de.ibm.com 2019-07-16 08:52 EDT--- ran tests on m3545035. ubuntu 18.02 with latest updates. Recreated the problem first (Not enough memory for annotating '__irf_end' symbol! and a hang) with perf top and a workload. Installed provided packages, reboot to

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-07-05 Thread bugproxy
--- Comment From tmri...@de.ibm.com 2019-07-05 07:48 EDT--- I have tried to last 2 days to find a patch series to apply the required patch which failed above. The difference between upstream linux kernel 5.2.0rc7 and the ubuntu 18.04 kernel I downloaded from url = git://kernel.ubuntu.com/

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-06-04 Thread bugproxy
--- Comment From tmri...@de.ibm.com 2019-06-04 04:14 EDT--- > Since you mentioned three patches in comment #18 I assume the 3rd one became > obsolete? Yes. > Is it correct that: > edeb0c90df3581b821a764052d185df985f8b8dc > "perf tools: Stop fallbacking to kallsyms for vdso symbols lookup"

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-06-04 Thread bugproxy
--- Comment From tmri...@de.ibm.com 2019-06-04 02:52 EDT--- Two patches are now upstream and available in Linux 5.2-rc3: commit 6738028dd57df064b969d8392c943ef3b3ae705d ("perf record: Fix s390 missing module symbol and warning for non-root users") commit ed9adb2035b5be5896d465b19040262be

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-05-24 Thread bugproxy
--- Comment From tmri...@de.ibm.com 2019-05-24 08:19 EDT--- I have debugged this issue and created three patches. Two have been accepted by the perf maintainer and the third is currently under review. Once the patches are upstream I will post the commit id's for further processing by Ubu

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-05-14 Thread bugproxy
--- Comment From tmri...@de.ibm.com 2019-05-14 08:35 EDT--- I have debugged this issue Klaus reported. I have installed the following system: root@s8360046:~/linux/tools/perf# uname -a Linux s8360046 4.18.0-17-generic #18-Ubuntu SMP Wed Mar 13 14:29:38 UTC 2019 s390x s390x s390x GNU/Linux

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-05-13 Thread bugproxy
--- Comment From klaus.theur...@de.ibm.com 2019-05-13 11:48 EDT--- thanks, now I got the perf binary back. I still see Not enough memory for annotating '__irf_end' symbol! though -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-05-10 Thread bugproxy
--- Comment From klaus.theur...@de.ibm.com 2019-05-10 03:06 EDT--- sure ... and this package does not have the perf binary included -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828166 Title:

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-05-09 Thread bugproxy
--- Comment From klaus.theur...@de.ibm.com 2019-05-09 11:05 EDT--- using perf from package recommended by Frank Heimes results in: root@m3545035:/home/theurich/people.canonical.com/~ksouza/lp1828166/bionic/tmp/usr/bin# ./perf WARNING: perf not found for kernel 4.15.0-49 You may need to in

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-05-09 Thread bugproxy
--- Comment From klaus.theur...@de.ibm.com 2019-05-09 08:59 EDT--- ok, I go the image with 18.04 and could recreate the problem. Then I installed all packages with apt install ./package-name and did a reboot to activate the new kernel. Questions: - perf (binary) is no longer available via

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-05-09 Thread bugproxy
--- Comment From klaus.theur...@de.ibm.com 2019-05-09 03:53 EDT--- Talked to Thomas Richter for a fresh Ubuntu 18.04 where we can test the provided changes, he will provide this image later today (tessia). I can't use the image where I found this issue for this test. -- You received thi

[Bug 1828166] Comment bridged from LTC Bugzilla

2019-05-08 Thread bugproxy
--- Comment From epa...@de.ibm.com 2019-05-08 03:52 EDT--- (In reply to comment #11) > Hence, this needs to land in bionic (and cosmic) - disco (and eoan) kernels > are already > 4.20 Bionic aka 18.04 LTS should be priority -- You received this bug notification because you are a member o