| 2019-05-08 06:49:20 |
bugproxy |
bug |
|
|
added bug |
| 2019-05-08 06:49:22 |
bugproxy |
tags |
|
architecture-s39064 bugnameltc-177443 severity-high targetmilestone-inin18041 |
|
| 2019-05-08 06:49:24 |
bugproxy |
attachment added |
|
example screenshot https://bugs.launchpad.net/bugs/1828166/+attachment/5262259/+files/Screenshot_from_2019-05-07_14-56-17.png |
|
| 2019-05-08 06:49:25 |
bugproxy |
ubuntu: assignee |
|
Skipper Bug Screeners (skipper-screen-team) |
|
| 2019-05-08 06:49:30 |
bugproxy |
affects |
ubuntu |
linux (Ubuntu) |
|
| 2019-05-08 06:51:14 |
Frank Heimes |
bug task added |
|
ubuntu-z-systems |
|
| 2019-05-08 06:51:24 |
Frank Heimes |
ubuntu-z-systems: status |
New |
Triaged |
|
| 2019-05-08 06:51:26 |
Frank Heimes |
ubuntu-z-systems: importance |
Undecided |
High |
|
| 2019-05-08 06:51:41 |
Frank Heimes |
ubuntu-z-systems: assignee |
|
Canonical Kernel Team (canonical-kernel-team) |
|
| 2019-05-08 06:53:48 |
Frank Heimes |
bug |
|
|
added subscriber Terry Rudd |
| 2019-05-08 13:37:38 |
Frank Heimes |
description |
perf top hangs and shows error messages
---uname output---
Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux
---Steps to Reproduce---
I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore
Following analyse took place:
No problem with current kernel .
Bi-Secting of perf tool took place and following commit was found:
commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad)
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date: Tue Oct 16 17:08:29 2018 -0300
perf tools: Stop fallbacking to kallsyms for vdso symbols lookup
When you apply this patch the issue is gone, however it is contained in these versions:
git tag --contains edeb0c90df3581b821
v4.19
v4.20
....
The level I was debugging was kernel 4.15 which does not contain this patch. |
SRU Justification:
==================
[Impact]
* The perf top tool hangs and shows error messages, like 'Not enough memory for annotating'
[Fix]
* edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop fallbacking to kallsyms for vdso symbols lookup"
[Test Case]
* start a benchmark (mem_alloc, but it doesn't really matter what)
* execute perf top in a second terminal
* the output of perf top is correct
* now stop the benchmark
* and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)"
* and perf top can't be exited anymore
[Regression Potential]
* The regression potential can be considered as low since this happens only while using the perf top tool
* and it is known that the commit (above) fixes the problem
* and the fix is upstream since 4.19
[Other Info]
* current disco and eoan kernels don't show that problem
* bisecting result points to above commit
* applies cleanly on cosmic, but has a little conflict on bionic (both master-next)
_________________________
perf top hangs and shows error messages
---uname output---
Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux
---Steps to Reproduce---
I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore
Following analyse took place:
No problem with current kernel .
Bi-Secting of perf tool took place and following commit was found:
commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad)
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date: Tue Oct 16 17:08:29 2018 -0300
perf tools: Stop fallbacking to kallsyms for vdso symbols lookup
When you apply this patch the issue is gone, however it is contained in these versions:
git tag --contains edeb0c90df3581b821
v4.19
v4.20
....
The level I was debugging was kernel 4.15 which does not contain this patch. |
|
| 2019-05-08 13:38:15 |
Kleber Sacilotto de Souza |
nominated for series |
|
Ubuntu Cosmic |
|
| 2019-05-08 13:38:15 |
Kleber Sacilotto de Souza |
bug task added |
|
linux (Ubuntu Cosmic) |
|
| 2019-05-08 13:38:15 |
Kleber Sacilotto de Souza |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-05-08 13:38:15 |
Kleber Sacilotto de Souza |
bug task added |
|
linux (Ubuntu Bionic) |
|
| 2019-05-08 13:39:34 |
Kleber Sacilotto de Souza |
linux (Ubuntu): status |
New |
Fix Released |
|
| 2019-05-08 15:41:03 |
Kleber Sacilotto de Souza |
linux (Ubuntu Bionic): status |
New |
In Progress |
|
| 2019-05-08 15:41:05 |
Kleber Sacilotto de Souza |
linux (Ubuntu Cosmic): status |
New |
In Progress |
|
| 2019-05-08 16:09:58 |
Frank Heimes |
ubuntu-z-systems: status |
Triaged |
In Progress |
|
| 2019-05-24 11:52:23 |
Frank Heimes |
ubuntu-z-systems: status |
In Progress |
Incomplete |
|
| 2019-06-04 07:23:33 |
Frank Heimes |
ubuntu-z-systems: status |
Incomplete |
Triaged |
|
| 2019-06-04 08:32:43 |
Frank Heimes |
ubuntu-z-systems: status |
Triaged |
Confirmed |
|
| 2019-06-17 14:30:58 |
Manoj Iyer |
linux (Ubuntu): status |
Fix Released |
Confirmed |
|
| 2019-07-11 12:25:18 |
Kleber Sacilotto de Souza |
linux (Ubuntu Cosmic): status |
In Progress |
Invalid |
|
| 2019-07-22 09:52:36 |
Frank Heimes |
ubuntu-z-systems: status |
Confirmed |
Incomplete |
|
| 2019-08-12 07:01:13 |
Frank Heimes |
ubuntu-z-systems: status |
Incomplete |
Triaged |
|
| 2019-08-13 10:38:01 |
Frank Heimes |
description |
SRU Justification:
==================
[Impact]
* The perf top tool hangs and shows error messages, like 'Not enough memory for annotating'
[Fix]
* edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop fallbacking to kallsyms for vdso symbols lookup"
[Test Case]
* start a benchmark (mem_alloc, but it doesn't really matter what)
* execute perf top in a second terminal
* the output of perf top is correct
* now stop the benchmark
* and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)"
* and perf top can't be exited anymore
[Regression Potential]
* The regression potential can be considered as low since this happens only while using the perf top tool
* and it is known that the commit (above) fixes the problem
* and the fix is upstream since 4.19
[Other Info]
* current disco and eoan kernels don't show that problem
* bisecting result points to above commit
* applies cleanly on cosmic, but has a little conflict on bionic (both master-next)
_________________________
perf top hangs and shows error messages
---uname output---
Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux
---Steps to Reproduce---
I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore
Following analyse took place:
No problem with current kernel .
Bi-Secting of perf tool took place and following commit was found:
commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad)
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date: Tue Oct 16 17:08:29 2018 -0300
perf tools: Stop fallbacking to kallsyms for vdso symbols lookup
When you apply this patch the issue is gone, however it is contained in these versions:
git tag --contains edeb0c90df3581b821
v4.19
v4.20
....
The level I was debugging was kernel 4.15 which does not contain this patch. |
SRU Justification:
==================
[Impact]
* The perf top tool hangs and shows error messages, like 'Not enough memory for annotating'
[Fix]
* b9c0a64901d5bdec6eafd38d1dc8fa0e2974fccb b9c0a64 "perf annotate: Fix s390 gap between kernel end and module start"
* 12a6d2940b5f02b4b9f71ce098e3bb02bc24a9ea 12a6d29 "perf record: Fix module size on s390"
[Test Case]
* start a benchmark (mem_alloc, but it doesn't really matter what)
* execute perf top in a second terminal
* the output of perf top is correct
* now stop the benchmark
* and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)"
* and perf top can't be exited anymore
[Regression Potential]
* The regression potential can be considered as medium since this happens only while using the perf top tool
* and just 3 files are changed, and one of them is arch/s390/util/machine.c
* but symbol and machine header in /tools/perf/util modified and several loc added
[Other Info]
* cherry-pick was possible to bionic-master-next and to disco-master-next (but used '--strategy=recursive -X theirs' for disco)
* adding the patches to disco is to avoid regressions
_________________________
perf top hangs and shows error messages
---uname output---
Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux
---Steps to Reproduce---
I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore
Following analyse took place:
No problem with current kernel .
Bi-Secting of perf tool took place and following commit was found:
commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad)
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date: Tue Oct 16 17:08:29 2018 -0300
perf tools: Stop fallbacking to kallsyms for vdso symbols lookup
When you apply this patch the issue is gone, however it is contained in these versions:
git tag --contains edeb0c90df3581b821
v4.19
v4.20
....
The level I was debugging was kernel 4.15 which does not contain this patch. |
|
| 2019-08-16 15:23:14 |
Kleber Sacilotto de Souza |
nominated for series |
|
Ubuntu Disco |
|
| 2019-08-16 15:23:14 |
Kleber Sacilotto de Souza |
bug task added |
|
linux (Ubuntu Disco) |
|
| 2019-08-16 15:23:22 |
Kleber Sacilotto de Souza |
linux (Ubuntu Disco): status |
New |
In Progress |
|
| 2019-08-16 15:23:45 |
Kleber Sacilotto de Souza |
linux (Ubuntu Bionic): importance |
Undecided |
High |
|
| 2019-08-16 15:23:47 |
Kleber Sacilotto de Souza |
linux (Ubuntu Disco): importance |
Undecided |
High |
|
| 2019-08-16 15:49:06 |
Frank Heimes |
ubuntu-z-systems: status |
Triaged |
In Progress |
|
| 2019-08-23 10:58:40 |
Kleber Sacilotto de Souza |
description |
SRU Justification:
==================
[Impact]
* The perf top tool hangs and shows error messages, like 'Not enough memory for annotating'
[Fix]
* b9c0a64901d5bdec6eafd38d1dc8fa0e2974fccb b9c0a64 "perf annotate: Fix s390 gap between kernel end and module start"
* 12a6d2940b5f02b4b9f71ce098e3bb02bc24a9ea 12a6d29 "perf record: Fix module size on s390"
[Test Case]
* start a benchmark (mem_alloc, but it doesn't really matter what)
* execute perf top in a second terminal
* the output of perf top is correct
* now stop the benchmark
* and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)"
* and perf top can't be exited anymore
[Regression Potential]
* The regression potential can be considered as medium since this happens only while using the perf top tool
* and just 3 files are changed, and one of them is arch/s390/util/machine.c
* but symbol and machine header in /tools/perf/util modified and several loc added
[Other Info]
* cherry-pick was possible to bionic-master-next and to disco-master-next (but used '--strategy=recursive -X theirs' for disco)
* adding the patches to disco is to avoid regressions
_________________________
perf top hangs and shows error messages
---uname output---
Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux
---Steps to Reproduce---
I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore
Following analyse took place:
No problem with current kernel .
Bi-Secting of perf tool took place and following commit was found:
commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad)
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date: Tue Oct 16 17:08:29 2018 -0300
perf tools: Stop fallbacking to kallsyms for vdso symbols lookup
When you apply this patch the issue is gone, however it is contained in these versions:
git tag --contains edeb0c90df3581b821
v4.19
v4.20
....
The level I was debugging was kernel 4.15 which does not contain this patch. |
SRU Justification:
==================
[Impact]
* The perf top tool hangs and shows error messages, like 'Not enough memory for annotating'
[Fix]
* b9c0a64901d5bdec6eafd38d1dc8fa0e2974fccb b9c0a64 "perf annotate: Fix s390 gap between kernel end and module start"
* 12a6d2940b5f02b4b9f71ce098e3bb02bc24a9ea 12a6d29 "perf record: Fix module size on s390"
Disco needs also as prereq:
* 6738028dd57df064b969d8392c943ef3b3ae705d 6738028 perf record: Fix s390 missing module symbol and warning for non-root users
[Test Case]
* start a benchmark (mem_alloc, but it doesn't really matter what)
* execute perf top in a second terminal
* the output of perf top is correct
* now stop the benchmark
* and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)"
* and perf top can't be exited anymore
[Regression Potential]
* The regression potential can be considered as medium since this happens only while using the perf top tool
* and just 3 files are changed, and one of them is arch/s390/util/machine.c
* but symbol and machine header in /tools/perf/util modified and several loc added
[Other Info]
* cherry-pick was possible to bionic-master-next and to disco-master-next (but used '--strategy=recursive -X theirs' for disco)
* adding the patches to disco is to avoid regressions
_________________________
perf top hangs and shows error messages
---uname output---
Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux
---Steps to Reproduce---
I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore
Following analyse took place:
No problem with current kernel .
Bi-Secting of perf tool took place and following commit was found:
commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad)
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date: Tue Oct 16 17:08:29 2018 -0300
perf tools: Stop fallbacking to kallsyms for vdso symbols lookup
When you apply this patch the issue is gone, however it is contained in these versions:
git tag --contains edeb0c90df3581b821
v4.19
v4.20
....
The level I was debugging was kernel 4.15 which does not contain this patch. |
|
| 2019-08-23 11:13:06 |
Kleber Sacilotto de Souza |
linux (Ubuntu): status |
Confirmed |
Fix Committed |
|
| 2019-09-04 02:33:09 |
Khaled El Mously |
linux (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2019-09-04 02:33:11 |
Khaled El Mously |
linux (Ubuntu Disco): status |
In Progress |
Fix Committed |
|
| 2019-09-04 06:26:43 |
Andrew Cloke |
ubuntu-z-systems: status |
In Progress |
Fix Committed |
|
| 2019-10-08 13:02:15 |
Frank Heimes |
description |
SRU Justification:
==================
[Impact]
* The perf top tool hangs and shows error messages, like 'Not enough memory for annotating'
[Fix]
* b9c0a64901d5bdec6eafd38d1dc8fa0e2974fccb b9c0a64 "perf annotate: Fix s390 gap between kernel end and module start"
* 12a6d2940b5f02b4b9f71ce098e3bb02bc24a9ea 12a6d29 "perf record: Fix module size on s390"
Disco needs also as prereq:
* 6738028dd57df064b969d8392c943ef3b3ae705d 6738028 perf record: Fix s390 missing module symbol and warning for non-root users
[Test Case]
* start a benchmark (mem_alloc, but it doesn't really matter what)
* execute perf top in a second terminal
* the output of perf top is correct
* now stop the benchmark
* and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)"
* and perf top can't be exited anymore
[Regression Potential]
* The regression potential can be considered as medium since this happens only while using the perf top tool
* and just 3 files are changed, and one of them is arch/s390/util/machine.c
* but symbol and machine header in /tools/perf/util modified and several loc added
[Other Info]
* cherry-pick was possible to bionic-master-next and to disco-master-next (but used '--strategy=recursive -X theirs' for disco)
* adding the patches to disco is to avoid regressions
_________________________
perf top hangs and shows error messages
---uname output---
Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux
---Steps to Reproduce---
I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore
Following analyse took place:
No problem with current kernel .
Bi-Secting of perf tool took place and following commit was found:
commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad)
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date: Tue Oct 16 17:08:29 2018 -0300
perf tools: Stop fallbacking to kallsyms for vdso symbols lookup
When you apply this patch the issue is gone, however it is contained in these versions:
git tag --contains edeb0c90df3581b821
v4.19
v4.20
....
The level I was debugging was kernel 4.15 which does not contain this patch. |
SRU Justification:
==================
[Impact]
* The perf top tool hangs and shows error messages, like 'Not enough memory for annotating'
[Fix]
* b9c0a64901d5bdec6eafd38d1dc8fa0e2974fccb b9c0a64 "perf annotate: Fix s390 gap between kernel end and module start"
* 12a6d2940b5f02b4b9f71ce098e3bb02bc24a9ea 12a6d29 "perf record: Fix module size on s390"
Disco needs also as prereq:
* 6738028dd57df064b969d8392c943ef3b3ae705d 6738028 "perf record: Fix s390 missing module symbol and warning for non-root users"
[Test Case]
* start a benchmark (mem_alloc, but it doesn't really matter what)
* execute perf top in a second terminal
* the output of perf top is correct
* now stop the benchmark
* and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)"
* and perf top can't be exited anymore
[Regression Potential]
* The regression potential can be considered as medium since this happens only while using the perf top tool
* and just 3 files are changed, and one of them is arch/s390/util/machine.c
* but symbol and machine header in /tools/perf/util modified and several loc added
[Other Info]
* cherry-pick was possible to bionic-master-next and to disco-master-next (but used '--strategy=recursive -X theirs' for disco)
* adding the patches to disco is to avoid regressions
_________________________
perf top hangs and shows error messages
---uname output---
Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux
---Steps to Reproduce---
I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore
Following analyse took place:
No problem with current kernel .
Bi-Secting of perf tool took place and following commit was found:
commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad)
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date: Tue Oct 16 17:08:29 2018 -0300
perf tools: Stop fallbacking to kallsyms for vdso symbols lookup
When you apply this patch the issue is gone, however it is contained in these versions:
git tag --contains edeb0c90df3581b821
v4.19
v4.20
....
The level I was debugging was kernel 4.15 which does not contain this patch. |
|
| 2019-10-14 10:08:24 |
Kleber Sacilotto de Souza |
linux (Ubuntu Disco): status |
Fix Committed |
Fix Released |
|
| 2019-10-14 10:08:38 |
Kleber Sacilotto de Souza |
linux (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-10-14 10:22:19 |
Frank Heimes |
linux (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2019-10-14 10:22:26 |
Frank Heimes |
ubuntu-z-systems: status |
Fix Committed |
Fix Released |
|
