Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace AIX
Created by Guest
Created on Sep 22, 2015

DR CPU ADD FAILURE WITH PROBEVUE RUNNING.

Problem Description:

Customer is running probevue scripts to capture rare LPM
hang on the frames and this is causing DR CPU ADD failures.

probevue thread is sleeping holding tbm_consumer_elock
and that caused probevue DR handler to fail.

From Defect 700584
Just wanted to document the fix here and the expectations so that
if we run into DR issues later we know where to look and that to do.

The trace buffer manager and DR need to be serialized for there
situations:
1. Session start and DR and this is done by the etrc_lock.
2. trace buffer manager timer handler and DR and this is done by
the etrc_timer_lock.
3. This was the issue that was being seen in 61F ie trace consumer and DR.

To resolve the third we try to acquire all the consumer locks in the DR handler and allow DR
only if all the consumer locks are acquired and fail DR otherwise.

Idea priority Medium
  • Guest
    Reply
    |
    May 4, 2020

    IBM has evaluated the priority of this enhancement proposal relative to other future product content and determined that this RFE will not be pursued for a future product release

  • Guest
    Reply
    |
    Sep 23, 2015

    Creating a new RFE based on Community RFE #77295 in product IBM AIX.