On 11/19/25 1:09 PM, lijiang wrote:
> On Wed, Nov 19, 2025 at 12:50 PM HAGIO KAZUHITO(萩尾 一仁) <k-hagio-ab@nec.com>
> wrote:
>
>> On 2025/11/18 17:55, Lianbo Jiang wrote:
>>> The "runq -g" option may fail on some vmcores from customers, and report
>>> the following error:
>>>
>>> crash> runq -g
>>> ...
>>> malloc_bp[1998]: 11592c20
>>> malloc_bp[1999]: 11662490
>>> ...
>>> average size: 11922
>>> runq: cannot allocate any more memory!
>>>
>>> This is because the maximum number of malloc() was reached through
>>> GETBUF(), currently which is limited to MAX_MALLOC_BUFS(2000).
>>> Furthermore, the error messages is not very clear.
>>>
>>> Given that, let's expand the limitation of MAX_MALLOC_BUFS and make the
>>> error message clear and concise.
Hi Lijiang,
I would like to propose another method to go about this problem.
What if we keep the default value as 2000, and introduce a command line
option
to `recommend` user to increase the max limit.
Thanks for sharing your idea, Shivang.
More code changes are required, and probably many users do not know what values are appropriate, they have to try it, again and again. E.g: need to exit, and then loading crash with a parameter...
Lianbo
Regards.
~Shivang.