** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792195
Title:
Signal 7 error when running GPFS tracing in cluster
To manage notifications about this bug go to:
** Changed in: ubuntu-power-systems
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792195
Title:
Signal 7 error when running GPFS tracing in cluster
To
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792195
Title:
Signal 7 error when running GPFS tracing in cluster
To manage
** Changed in: ubuntu-power-systems
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792195
Title:
Signal 7 error when running GPFS tracing in cluster
To
This bug was fixed in the package linux - 4.18.0-11.12
---
linux (4.18.0-11.12) cosmic; urgency=medium
* linux: 4.18.0-11.12 -proposed tracker (LP: #1799445)
* arm64: snapdragon: WARNING: CPU: 0 PID: 1 arch/arm64/kernel/setup.c:271
reserve_memblock_reserved_regions (LP:
This bug was fixed in the package linux - 4.18.0-11.12
---
linux (4.18.0-11.12) cosmic; urgency=medium
* linux: 4.18.0-11.12 -proposed tracker (LP: #1799445)
* arm64: snapdragon: WARNING: CPU: 0 PID: 1 arch/arm64/kernel/setup.c:271
reserve_memblock_reserved_regions (LP:
This bug was fixed in the package linux - 4.15.0-39.42
---
linux (4.15.0-39.42) bionic; urgency=medium
* linux: 4.15.0-39.42 -proposed tracker (LP: #1799411)
* Linux: insufficient shootdown for paging-structure caches (LP: #1798897)
- mm: move tlb_table_flush to
** Changed in: ubuntu-power-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792195
Title:
Signal 7 error when running GPFS tracing in cluster
To
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792195
Title:
Signal 7 error when running GPFS tracing in cluster
To
I tested this bug against the -proposed kernel and it looks good - the
problem looks fixed.
user@deb3qwsp1:~/gdrcopy$ cat /proc/version
Linux version 4.15.0-39-generic (buildd@bos02-ppc64el-016) (gcc version 7.3.0
(Ubuntu 7.3.0-16ubuntu3)) #42-Ubuntu SMP Tue Oct 23 15:41:45 UTC 2018
** Tags
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792195
Title:
Signal 7 error when running GPFS tracing in cluster
To
** Description changed:
-
== SRU Justification ==
IBM is requesting these commits in bionic and cosmic. These commits
- also rely on commit 7acf50e4efa6, which was SRU'd in bug 1792102. The
- first patch, commit 2bf1071a8d50, was backported by IBM themself.
+ also rely on commit
I built another test kernel, without commit 2bf1071a8d5. This test
kernel has the three commit:
7acf50e4efa6 ("Revert "powerpc/powernv: Increase memory block size to 1GB on
radix"")
f08d08f3db55 ("powerpc/mm/radix: Only need the Nest MMU workaround for R -> RW
transition")
bd0dbb73e013
In regards to commit 2bf1071a8d509:
The SRU team would not like to see such a large portion of code getting
removed after release. One never knows whether there really was nothing
that did not still make use of some parts.
I believe 2bf1071a8d5 is needed as a prereq for f08d08f3db5545. Do you
Thanks for the update. I'm also building a Launchpad PPA with these
changes. That will allow anyone else that wants to test that way. I'll
post a link when the PPA is ready.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The PPA is available here:
https://launchpad.net/~jsalisbury/+archive/ubuntu/1792195
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792195
Title:
Signal 7 error when running GPFS tracing in cluster
SRU request submitted for Bionic and Cosmic:
https://lists.ubuntu.com/archives/kernel-team/2018-October/095977.html
** Also affects: linux (Ubuntu Cosmic)
Importance: Critical
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
** Description changed:
+
+ == SRU
Sorry, it looks like my copy failed. The files should be there now.
http://kernel.ubuntu.com/~jsalisbury/lp1792195
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792195
Title:
Signal 7 error when
I built a v2 test kernel. This test kernel now has the following four
commits:
f08d08f3db55 ("powerpc/mm/radix: Only need the Nest MMU workaround for R -> RW
transition")
bd0dbb73e013 ("powerpc/mm/books3s: Add new pte bit to mark pte temporarily
invalid.")
2bf1071a8d50 ("powerpc/64s: Remove
You are correct, commit bd0dbb73e01306a1060e56f81e5fe287be936477 was not
in that test kernel. It looks like it needs some backporing as well.
I'll do that and build a v2 test kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the backport!
I built a test kernel with commits f08d08f3db5545 and your backport of
2bf1071a8d50928. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1792195
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
** Changed in: linux (Ubuntu)
Importance: Medium => Critical
** Changed in: linux (Ubuntu Bionic)
Importance: Medium => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792195
Title:
** Changed in: ubuntu-power-systems
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792195
Title:
Signal 7 error when running GPFS tracing in cluster
To manage
** Changed in: ubuntu-power-systems
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792195
Title:
Signal 7 error when running GPFS tracing in cluster
To
** Changed in: ubuntu-power-systems
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792195
Title:
Signal 7 error when running GPFS tracing in cluster
To manage
I tried to apply 2bf1071a8d50928a4ae366bb3108833166c2b70c to Bionic, but
it looks like a backport is needed.
It appears 2bf1071a8d5 is needed as a prereq for f08d08f3db5545. Do you
happen to already have a backport of 2bf1071a8d5 already done for
Bionic?
** Changed in: linux (Ubuntu)
** Changed in: ubuntu-power-systems
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792195
Title:
Signal 7 error when running GPFS tracing in cluster
To manage
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph
Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Canonical Kernel Team
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792195
Title:
Signal 7 error when running GPFS tracing in cluster
To manage notifications about this bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
** Tags added: architecture-ppc64le bugnameltc-171273 severity-high
targetmilestone-inin1804
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792195
Title:
Signal 7 error when running GPFS tracing in
35 matches
Mail list logo
