From Bugzilla Helper:
User-Agent: Mozilla/4.75 [en] (Windows NT 5.0; U)
Description of problem:
On large memory configurations (12-16GB) we are seeing server-timeouts when dumping memory resulting in dump that is
then physical memory. Most dumps are less that 4GB is size. It may not be important that the entire memory is dumped as long as
we can reliably get a dump that large enough to analysis root cause of the crash.
These are typical errors we are seeing:
Jul 8 14:28:13 dse-rac1-db netdump: Got too many timeouts waiting for memory page for client 0x1e061886, ignoring it
Jul 8 14:28:17 dse-rac1-db netdump: Got too many timeouts waiting for SHOW_STATUS for client 0x1e061886, rebooting it
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Actual Results: Small dump, server timeouts
Expected Results: Same size dump each time. No timeouts.
We are working on a reduced-memory tuneable, in which case netdump
will be configurable to *not* send free pages, user pages, and page