Questions about kexec-tools (resend to list)

[Philip Prindeville]

> On Mar 10, 2017, at 5:16 PM, Baoquan He <bhe at redhat.com> wrote:
> 
> On 03/10/17 at 01:20pm, Philip Prindeville wrote:
>> 
> 
>> 
>> The above memory ranges look highly suspect.
>> 
>> Anyone have any ideas where I should start digging to figure out where things are going sideways?
>> 
>> I’m using 2.0.14 on a Linux 4.4.19 kernel, with gcc 5.3.0 and MUSL 1.1.16.
> 
> Hi,
> 
> This is user space program and using in 1st kernel. I really suggest you
> should start a gdb to track what's going on when your real /proc/iomem
> is different with the debug printing of kexec. Honestly, it won't be too
> difficult, I really like this kind of debugging. If happened in kdump
> kernel, even in user space tools like makedumpfile, you have to add
> debug printing again and again.
> 
> Thanks
> Baoquan


Actually, I have my smoking gun.  And found a clue (regrettably after I had done all the digging) to confirm that I was on the right track:

http://git.alsa-project.org/?p=alsa-lib.git;a=commitdiff;h=1d3f7975f920f47e6a8a324f547da2180e64171a

Sending a patch, separately.

-Philip