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:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
better logging for stack overflow, ulimit stack to small
With this PMR we were searching quite hard for the reason, why a 3rd-party-software was dying with segmentation fault in dynamic linked shared library libdb1.so
We could only see: Feb 18 09:01:56 smtcb00254 kernel: [1270273.292859] os4x_licinfo: segfault at 7fffff7fe728 ip 00007ffff509d258 sp 00007fffff7fe730 error 6 in libdb2.so.1[7ffff4aef000+23ce000] And: --- SIGSEGV (Segmentation fault) @ 0 (0) --- ==10541== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==10541== Access not within mapped region at address 0x7FE800808
But nothing, except the IBM Support with this PMR, was giving a hint, that the stacksize was a problem. Solution was at the end to increase default kernel stack size from 8MB to a bigger value. (ulimit -s)
Further information should be available in the PMR.
Request: please increase and optimze logging in this failure-situation and catch this failure, eg. like this: printk(KERN_ALERT "stack size $stack too small, increase with ulimit â€“s ... . EXIT\n");
Do not place IBM confidential, company confidential, or personal information into any field.