On 5/31/22 08:18, David Hildenbrand wrote:
On 26.05.22 15:39, Sourabh Jain wrote:
Hello Eric,
On 26/05/22 18:46, Eric DeVolder wrote:
On 5/25/22 10:13, Sourabh Jain wrote:
Hello Eric,
On 06/05/22 00:15, Eric DeVolder wrote:
When the kdump service is loaded, if a CPU or memory is hot
On 26.05.22 15:39, Sourabh Jain wrote:
> Hello Eric,
>
> On 26/05/22 18:46, Eric DeVolder wrote:
>>
>>
>> On 5/25/22 10:13, Sourabh Jain wrote:
>>> Hello Eric,
>>>
>>> On 06/05/22 00:15, Eric DeVolder wrote:
When the kdump service is loaded, if a CPU or memory is hot
un/plugged, the
Hello Eric,
On 26/05/22 18:46, Eric DeVolder wrote:
On 5/25/22 10:13, Sourabh Jain wrote:
Hello Eric,
On 06/05/22 00:15, Eric DeVolder wrote:
When the kdump service is loaded, if a CPU or memory is hot
un/plugged, the crash elfcorehdr (for x86), which describes the CPUs
and memory in the
On 5/26/22 08:39, Sourabh Jain wrote:
Hello Eric,
On 26/05/22 18:46, Eric DeVolder wrote:
On 5/25/22 10:13, Sourabh Jain wrote:
Hello Eric,
On 06/05/22 00:15, Eric DeVolder wrote:
When the kdump service is loaded, if a CPU or memory is hot
un/plugged, the crash elfcorehdr (for x86),
On 5/25/22 10:13, Sourabh Jain wrote:
Hello Eric,
On 06/05/22 00:15, Eric DeVolder wrote:
When the kdump service is loaded, if a CPU or memory is hot
un/plugged, the crash elfcorehdr (for x86), which describes the CPUs
and memory in the system, must also be updated, else the resulting
vmcore
Hello Eric,
On 06/05/22 00:15, Eric DeVolder wrote:
When the kdump service is loaded, if a CPU or memory is hot
un/plugged, the crash elfcorehdr (for x86), which describes the CPUs
and memory in the system, must also be updated, else the resulting
vmcore is inaccurate (eg. missing either CPU
When the kdump service is loaded, if a CPU or memory is hot
un/plugged, the crash elfcorehdr (for x86), which describes the CPUs
and memory in the system, must also be updated, else the resulting
vmcore is inaccurate (eg. missing either CPU context or memory
regions).
The current solution
