[Kernel-packages] [Bug 1429250] Re: crash cannot find stack info on ppc64le
This bug was fixed in the package crash - 7.0.3-3ubuntu4.3 --- crash (7.0.3-3ubuntu4.3) trusty; urgency=medium * Fix-for-the-PPC64-bt-command-on-both-big-endian-and-.patch (LP: #1429250) * Remove extraneous patch: 0001-Implemented-support-for-the-ARM64-bt-l-option.patch -- Chris J Arges chris.j.ar...@canonical.com Mon, 10 Aug 2015 16:44:48 -0500 ** Changed in: crash (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1429250 Title: crash cannot find stack info on ppc64le Status in crash package in Ubuntu: Fix Released Status in crash source package in Trusty: Fix Released Bug description: SRU Justification [Impact] crash's sub-command cannot show stack frame of active tasks on ppc64le systems. [Test Case] 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied [Fix] https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 [Regression potential] This is easily testable and only affects ppc64le systems. This has already been backported to vivid without issue. -- Problem Description = crash's sub-command cannot show stack frame of active tasks on ppc64le systems. Please see https://www.redhat.com/archives/crash- utility/2015-January/msg00033.html for details. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux thymelp2.isst.aus.stglabs.ibm.com 3.10.0-221.ael7b.ppc64le #1 SMP Wed Jan 7 09:27:09 EST 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = CHRP IBM,8247-22L lpar Steps to Reproduce = 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied Userspace tool common name: crash The userspace tool has the following bit modes: 64-bit Userspace rpm: crash-7.0.9-2.ael7b.ppc64le == Comment: #5 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-06 13:18:18 == For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari == Comment: #6 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-20 00:08:46 == (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Thanks Hari == Comment: #10 - Breno Henrique Leitao bren...@br.ibm.com - 2015-03-02 15:42:05 == Canonical, Can we move Crash to versin 7.1.0 that already contains this fix? Thanks. == Comment: #11 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-03-05 23:18:17 == (In reply to comment #6) (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch
[Kernel-packages] [Bug 1429250] Re: crash cannot find stack info on ppc64le
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1429250 Title: crash cannot find stack info on ppc64le Status in crash package in Ubuntu: Fix Released Status in crash source package in Trusty: Fix Committed Bug description: SRU Justification [Impact] crash's sub-command cannot show stack frame of active tasks on ppc64le systems. [Test Case] 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied [Fix] https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 [Regression potential] This is easily testable and only affects ppc64le systems. This has already been backported to vivid without issue. -- Problem Description = crash's sub-command cannot show stack frame of active tasks on ppc64le systems. Please see https://www.redhat.com/archives/crash- utility/2015-January/msg00033.html for details. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux thymelp2.isst.aus.stglabs.ibm.com 3.10.0-221.ael7b.ppc64le #1 SMP Wed Jan 7 09:27:09 EST 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = CHRP IBM,8247-22L lpar Steps to Reproduce = 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied Userspace tool common name: crash The userspace tool has the following bit modes: 64-bit Userspace rpm: crash-7.0.9-2.ael7b.ppc64le == Comment: #5 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-06 13:18:18 == For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari == Comment: #6 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-20 00:08:46 == (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Thanks Hari == Comment: #10 - Breno Henrique Leitao bren...@br.ibm.com - 2015-03-02 15:42:05 == Canonical, Can we move Crash to versin 7.1.0 that already contains this fix? Thanks. == Comment: #11 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-03-05 23:18:17 == (In reply to comment #6) (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Further, this is more of an alternative approach for getting backtrace. So, the problem I mentioned here doesn't have any issues in terms of functionality with regard to this bug or any other for that
[Kernel-packages] [Bug 1429250] Re: crash cannot find stack info on ppc64le
Hello bugproxy, or anyone else affected, Accepted crash into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/crash/7.0.3-3ubuntu4.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: crash (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1429250 Title: crash cannot find stack info on ppc64le Status in crash package in Ubuntu: Fix Released Status in crash source package in Trusty: Fix Committed Bug description: SRU Justification [Impact] crash's sub-command cannot show stack frame of active tasks on ppc64le systems. [Test Case] 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied [Fix] https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 [Regression potential] This is easily testable and only affects ppc64le systems. This has already been backported to vivid without issue. -- Problem Description = crash's sub-command cannot show stack frame of active tasks on ppc64le systems. Please see https://www.redhat.com/archives/crash- utility/2015-January/msg00033.html for details. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux thymelp2.isst.aus.stglabs.ibm.com 3.10.0-221.ael7b.ppc64le #1 SMP Wed Jan 7 09:27:09 EST 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = CHRP IBM,8247-22L lpar Steps to Reproduce = 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied Userspace tool common name: crash The userspace tool has the following bit modes: 64-bit Userspace rpm: crash-7.0.9-2.ael7b.ppc64le == Comment: #5 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-06 13:18:18 == For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari == Comment: #6 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-20 00:08:46 == (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Thanks Hari == Comment: #10 - Breno Henrique Leitao bren...@br.ibm.com - 2015-03-02 15:42:05 == Canonical, Can we move Crash to versin 7.1.0 that already contains this fix? Thanks. == Comment: #11 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-03-05 23:18:17 == (In reply to comment #6) (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace.
[Kernel-packages] [Bug 1429250] Re: crash cannot find stack info on ppc64le
** Branch linked: lp:ubuntu/trusty-proposed/crash -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1429250 Title: crash cannot find stack info on ppc64le Status in crash package in Ubuntu: Fix Released Status in crash source package in Trusty: Fix Committed Bug description: SRU Justification [Impact] crash's sub-command cannot show stack frame of active tasks on ppc64le systems. [Test Case] 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied [Fix] https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 [Regression potential] This is easily testable and only affects ppc64le systems. This has already been backported to vivid without issue. -- Problem Description = crash's sub-command cannot show stack frame of active tasks on ppc64le systems. Please see https://www.redhat.com/archives/crash- utility/2015-January/msg00033.html for details. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux thymelp2.isst.aus.stglabs.ibm.com 3.10.0-221.ael7b.ppc64le #1 SMP Wed Jan 7 09:27:09 EST 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = CHRP IBM,8247-22L lpar Steps to Reproduce = 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied Userspace tool common name: crash The userspace tool has the following bit modes: 64-bit Userspace rpm: crash-7.0.9-2.ael7b.ppc64le == Comment: #5 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-06 13:18:18 == For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari == Comment: #6 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-20 00:08:46 == (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Thanks Hari == Comment: #10 - Breno Henrique Leitao bren...@br.ibm.com - 2015-03-02 15:42:05 == Canonical, Can we move Crash to versin 7.1.0 that already contains this fix? Thanks. == Comment: #11 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-03-05 23:18:17 == (In reply to comment #6) (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Further, this is more of an alternative approach for getting backtrace. So, the problem I mentioned here doesn't have any issues in terms of functionality with regard to this bug or any other for that matter. Since, there
[Kernel-packages] [Bug 1429250] Re: crash cannot find stack info on ppc64le
** Description changed: + SRU Justification + + [Impact] + crash's sub-command cannot show stack frame of active tasks on ppc64le systems. + + [Test Case] + 1. capturing a vmcore by kdump on ppc64le system + 2. issuing crash with this vmcore + 3. run 'bt' in crash + 4. no stack frame displaied + + [Fix] + https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 + + [Regression potential] + This is easily testable and only affects ppc64le systems. This has already been backported to vivid without issue. + + -- + + Problem Description = - crash's sub-command cannot show stack frame of active tasks on ppc64le systems. Please see + crash's sub-command cannot show stack frame of active tasks on ppc64le systems. Please see https://www.redhat.com/archives/crash-utility/2015-January/msg00033.html for details. - - Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com - + + Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail + Afanasiev/afana...@us.ibm.com + ---uname output--- Linux thymelp2.isst.aus.stglabs.ibm.com 3.10.0-221.ael7b.ppc64le #1 SMP Wed Jan 7 09:27:09 EST 2015 ppc64le ppc64le ppc64le GNU/Linux - - Machine Type = CHRP IBM,8247-22L lpar - + Machine Type = CHRP IBM,8247-22L lpar + Steps to Reproduce = 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash - 4. no stack frame displaied - - Userspace tool common name: crash - The userspace tool has the following bit modes: 64-bit - Userspace rpm: crash-7.0.9-2.ael7b.ppc64le + 4. no stack frame displaied + + Userspace tool common name: crash + The userspace tool has the following bit modes: 64-bit + Userspace rpm: crash-7.0.9-2.ael7b.ppc64le == Comment: #5 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-06 13:18:18 == For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari == Comment: #6 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-20 00:08:46 == (In reply to comment #5) (In reply to comment #4) Any update? - + For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. - + But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. - + Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Thanks Hari == Comment: #10 - Breno Henrique Leitao bren...@br.ibm.com - 2015-03-02 15:42:05 == Canonical, Can we move Crash to versin 7.1.0 that already contains this fix? Thanks. == Comment: #11 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-03-05 23:18:17 == (In reply to comment #6) (In reply to comment #5) (In reply to comment #4) Any update? - + For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. - + But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. - + Thanks Hari - + I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 - + We could track the problem with first method offline or in a separate bug if needed. Further, this is more of an alternative approach for getting backtrace. So, the
[Kernel-packages] [Bug 1429250] Re: crash cannot find stack info on ppc64le
** Also affects: crash (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: crash (Ubuntu Trusty) Assignee: (unassigned) = Chris J Arges (arges) ** Changed in: crash (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: crash (Ubuntu Trusty) Status: New = In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1429250 Title: crash cannot find stack info on ppc64le Status in crash package in Ubuntu: Fix Released Status in crash source package in Trusty: In Progress Bug description: Problem Description = crash's sub-command cannot show stack frame of active tasks on ppc64le systems. Please see https://www.redhat.com/archives/crash- utility/2015-January/msg00033.html for details. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux thymelp2.isst.aus.stglabs.ibm.com 3.10.0-221.ael7b.ppc64le #1 SMP Wed Jan 7 09:27:09 EST 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = CHRP IBM,8247-22L lpar Steps to Reproduce = 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied Userspace tool common name: crash The userspace tool has the following bit modes: 64-bit Userspace rpm: crash-7.0.9-2.ael7b.ppc64le == Comment: #5 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-06 13:18:18 == For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari == Comment: #6 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-20 00:08:46 == (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Thanks Hari == Comment: #10 - Breno Henrique Leitao bren...@br.ibm.com - 2015-03-02 15:42:05 == Canonical, Can we move Crash to versin 7.1.0 that already contains this fix? Thanks. == Comment: #11 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-03-05 23:18:17 == (In reply to comment #6) (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Further, this is more of an alternative approach for getting backtrace. So, the problem I mentioned here doesn't have any issues in terms of functionality with regard to this bug or any other for that matter. Since, there are no issues in terms of functionality, I am not sure on whether to raise a bug. It is on my TODO list and I am thinking of chasing this offline.. Thanks Hari To manage notifications about this bug go to:
[Kernel-packages] [Bug 1429250] Re: crash cannot find stack info on ppc64le
We would like to have this fix also for 14.04 branch. We requested that in bug LP #1463653 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1429250 Title: crash cannot find stack info on ppc64le Status in crash package in Ubuntu: Fix Released Bug description: Problem Description = crash's sub-command cannot show stack frame of active tasks on ppc64le systems. Please see https://www.redhat.com/archives/crash- utility/2015-January/msg00033.html for details. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux thymelp2.isst.aus.stglabs.ibm.com 3.10.0-221.ael7b.ppc64le #1 SMP Wed Jan 7 09:27:09 EST 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = CHRP IBM,8247-22L lpar Steps to Reproduce = 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied Userspace tool common name: crash The userspace tool has the following bit modes: 64-bit Userspace rpm: crash-7.0.9-2.ael7b.ppc64le == Comment: #5 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-06 13:18:18 == For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari == Comment: #6 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-20 00:08:46 == (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Thanks Hari == Comment: #10 - Breno Henrique Leitao bren...@br.ibm.com - 2015-03-02 15:42:05 == Canonical, Can we move Crash to versin 7.1.0 that already contains this fix? Thanks. == Comment: #11 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-03-05 23:18:17 == (In reply to comment #6) (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Further, this is more of an alternative approach for getting backtrace. So, the problem I mentioned here doesn't have any issues in terms of functionality with regard to this bug or any other for that matter. Since, there are no issues in terms of functionality, I am not sure on whether to raise a bug. It is on my TODO list and I am thinking of chasing this offline.. Thanks Hari To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1429250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1429250] Re: crash cannot find stack info on ppc64le
This bug was fixed in the package crash - 7.0.8-1ubuntu2 --- crash (7.0.8-1ubuntu2) vivid; urgency=medium * Fix-for-the-PPC64-bt-command-on-both-big-endian-and-.patch (LP: #1429250) -- Chris J Arges chris.j.ar...@canonical.com Tue, 07 Apr 2015 13:52:16 -0500 ** Changed in: crash (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1429250 Title: crash cannot find stack info on ppc64le Status in crash package in Ubuntu: Fix Released Bug description: Problem Description = crash's sub-command cannot show stack frame of active tasks on ppc64le systems. Please see https://www.redhat.com/archives/crash- utility/2015-January/msg00033.html for details. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux thymelp2.isst.aus.stglabs.ibm.com 3.10.0-221.ael7b.ppc64le #1 SMP Wed Jan 7 09:27:09 EST 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = CHRP IBM,8247-22L lpar Steps to Reproduce = 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied Userspace tool common name: crash The userspace tool has the following bit modes: 64-bit Userspace rpm: crash-7.0.9-2.ael7b.ppc64le == Comment: #5 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-06 13:18:18 == For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari == Comment: #6 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-20 00:08:46 == (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Thanks Hari == Comment: #10 - Breno Henrique Leitao bren...@br.ibm.com - 2015-03-02 15:42:05 == Canonical, Can we move Crash to versin 7.1.0 that already contains this fix? Thanks. == Comment: #11 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-03-05 23:18:17 == (In reply to comment #6) (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Further, this is more of an alternative approach for getting backtrace. So, the problem I mentioned here doesn't have any issues in terms of functionality with regard to this bug or any other for that matter. Since, there are no issues in terms of functionality, I am not sure on whether to raise a bug. It is on my TODO list and I am thinking of chasing this offline.. Thanks Hari To manage notifications about this bug go to:
[Kernel-packages] [Bug 1429250] Re: crash cannot find stack info on ppc64le
** Branch linked: lp:ubuntu/vivid-proposed/crash -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1429250 Title: crash cannot find stack info on ppc64le Status in crash package in Ubuntu: In Progress Bug description: Problem Description = crash's sub-command cannot show stack frame of active tasks on ppc64le systems. Please see https://www.redhat.com/archives/crash- utility/2015-January/msg00033.html for details. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux thymelp2.isst.aus.stglabs.ibm.com 3.10.0-221.ael7b.ppc64le #1 SMP Wed Jan 7 09:27:09 EST 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = CHRP IBM,8247-22L lpar Steps to Reproduce = 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied Userspace tool common name: crash The userspace tool has the following bit modes: 64-bit Userspace rpm: crash-7.0.9-2.ael7b.ppc64le == Comment: #5 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-06 13:18:18 == For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari == Comment: #6 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-20 00:08:46 == (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Thanks Hari == Comment: #10 - Breno Henrique Leitao bren...@br.ibm.com - 2015-03-02 15:42:05 == Canonical, Can we move Crash to versin 7.1.0 that already contains this fix? Thanks. == Comment: #11 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-03-05 23:18:17 == (In reply to comment #6) (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Further, this is more of an alternative approach for getting backtrace. So, the problem I mentioned here doesn't have any issues in terms of functionality with regard to this bug or any other for that matter. Since, there are no issues in terms of functionality, I am not sure on whether to raise a bug. It is on my TODO list and I am thinking of chasing this offline.. Thanks Hari To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1429250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1429250] Re: crash cannot find stack info on ppc64le
** Changed in: crash (Ubuntu) Assignee: (unassigned) = Chris J Arges (arges) ** Changed in: crash (Ubuntu) Status: New = In Progress ** Changed in: crash (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1429250 Title: crash cannot find stack info on ppc64le Status in crash package in Ubuntu: In Progress Bug description: Problem Description = crash's sub-command cannot show stack frame of active tasks on ppc64le systems. Please see https://www.redhat.com/archives/crash- utility/2015-January/msg00033.html for details. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux thymelp2.isst.aus.stglabs.ibm.com 3.10.0-221.ael7b.ppc64le #1 SMP Wed Jan 7 09:27:09 EST 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = CHRP IBM,8247-22L lpar Steps to Reproduce = 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied Userspace tool common name: crash The userspace tool has the following bit modes: 64-bit Userspace rpm: crash-7.0.9-2.ael7b.ppc64le == Comment: #5 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-06 13:18:18 == For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari == Comment: #6 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-20 00:08:46 == (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Thanks Hari == Comment: #10 - Breno Henrique Leitao bren...@br.ibm.com - 2015-03-02 15:42:05 == Canonical, Can we move Crash to versin 7.1.0 that already contains this fix? Thanks. == Comment: #11 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-03-05 23:18:17 == (In reply to comment #6) (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Further, this is more of an alternative approach for getting backtrace. So, the problem I mentioned here doesn't have any issues in terms of functionality with regard to this bug or any other for that matter. Since, there are no issues in terms of functionality, I am not sure on whether to raise a bug. It is on my TODO list and I am thinking of chasing this offline.. Thanks Hari To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1429250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1429250] Re: crash cannot find stack info on ppc64le
Uploaded patch against 7.0.8 for Vivid. Should be in 7.0.8-1ubuntu2. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1429250 Title: crash cannot find stack info on ppc64le Status in crash package in Ubuntu: In Progress Bug description: Problem Description = crash's sub-command cannot show stack frame of active tasks on ppc64le systems. Please see https://www.redhat.com/archives/crash- utility/2015-January/msg00033.html for details. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux thymelp2.isst.aus.stglabs.ibm.com 3.10.0-221.ael7b.ppc64le #1 SMP Wed Jan 7 09:27:09 EST 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = CHRP IBM,8247-22L lpar Steps to Reproduce = 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied Userspace tool common name: crash The userspace tool has the following bit modes: 64-bit Userspace rpm: crash-7.0.9-2.ael7b.ppc64le == Comment: #5 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-06 13:18:18 == For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari == Comment: #6 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-20 00:08:46 == (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Thanks Hari == Comment: #10 - Breno Henrique Leitao bren...@br.ibm.com - 2015-03-02 15:42:05 == Canonical, Can we move Crash to versin 7.1.0 that already contains this fix? Thanks. == Comment: #11 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-03-05 23:18:17 == (In reply to comment #6) (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Further, this is more of an alternative approach for getting backtrace. So, the problem I mentioned here doesn't have any issues in terms of functionality with regard to this bug or any other for that matter. Since, there are no issues in terms of functionality, I am not sure on whether to raise a bug. It is on my TODO list and I am thinking of chasing this offline.. Thanks Hari To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1429250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1429250] Re: crash cannot find stack info on ppc64le
** Package changed: ubuntu = crash (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1429250 Title: crash cannot find stack info on ppc64le Status in crash package in Ubuntu: New Bug description: Problem Description = crash's sub-command cannot show stack frame of active tasks on ppc64le systems. Please see https://www.redhat.com/archives/crash- utility/2015-January/msg00033.html for details. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux thymelp2.isst.aus.stglabs.ibm.com 3.10.0-221.ael7b.ppc64le #1 SMP Wed Jan 7 09:27:09 EST 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = CHRP IBM,8247-22L lpar Steps to Reproduce = 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied Userspace tool common name: crash The userspace tool has the following bit modes: 64-bit Userspace rpm: crash-7.0.9-2.ael7b.ppc64le == Comment: #5 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-06 13:18:18 == For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari == Comment: #6 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-20 00:08:46 == (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Thanks Hari == Comment: #10 - Breno Henrique Leitao bren...@br.ibm.com - 2015-03-02 15:42:05 == Canonical, Can we move Crash to versin 7.1.0 that already contains this fix? Thanks. == Comment: #11 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-03-05 23:18:17 == (In reply to comment #6) (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Further, this is more of an alternative approach for getting backtrace. So, the problem I mentioned here doesn't have any issues in terms of functionality with regard to this bug or any other for that matter. Since, there are no issues in terms of functionality, I am not sure on whether to raise a bug. It is on my TODO list and I am thinking of chasing this offline.. Thanks Hari To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1429250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1429250] Re: crash cannot find stack info on ppc64le
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin1504 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1429250 Title: crash cannot find stack info on ppc64le Status in crash package in Ubuntu: New Bug description: Problem Description = crash's sub-command cannot show stack frame of active tasks on ppc64le systems. Please see https://www.redhat.com/archives/crash- utility/2015-January/msg00033.html for details. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux thymelp2.isst.aus.stglabs.ibm.com 3.10.0-221.ael7b.ppc64le #1 SMP Wed Jan 7 09:27:09 EST 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = CHRP IBM,8247-22L lpar Steps to Reproduce = 1. capturing a vmcore by kdump on ppc64le system 2. issuing crash with this vmcore 3. run 'bt' in crash 4. no stack frame displaied Userspace tool common name: crash The userspace tool has the following bit modes: 64-bit Userspace rpm: crash-7.0.9-2.ael7b.ppc64le == Comment: #5 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-06 13:18:18 == For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari == Comment: #6 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-02-20 00:08:46 == (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Thanks Hari == Comment: #10 - Breno Henrique Leitao bren...@br.ibm.com - 2015-03-02 15:42:05 == Canonical, Can we move Crash to versin 7.1.0 that already contains this fix? Thanks. == Comment: #11 - Hari Krishna Bathini hbath...@in.ibm.com - 2015-03-05 23:18:17 == (In reply to comment #6) (In reply to comment #5) (In reply to comment #4) Any update? For active tasks, there are two methods to get backtrace. Firstly, using pt_note registers. If this fails, use default stack search method to get backtrace. In ppc64le, currently both methods seem to fail. The below patch resolves problem in default stack search method. https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 This effectively resolves this bug. But the problem with first method is still open. I couldn't look into the problem with first method yet. Will try to work on this next week. Thanks Hari I would suggest, we close this bug as the issue reported is resolved with the below patch https://github.com/crash-utility/crash/commit/ dc4ea682a21567dd9d093862ec54eb8529199c05 We could track the problem with first method offline or in a separate bug if needed. Further, this is more of an alternative approach for getting backtrace. So, the problem I mentioned here doesn't have any issues in terms of functionality with regard to this bug or any other for that matter. Since, there are no issues in terms of functionality, I am not sure on whether to raise a bug. It is on my TODO list and I am thinking of chasing this offline.. Thanks Hari To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1429250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp