On Fri, Jul 06, Jan Beulich wrote: > > Could it be that some code tweaks the stack content used by decompress() > > in some odd way? But that would most likely lead to a crash, not to > > unexpected uncompressing results. > > Especially if the old and new kernel are using the exact same > image, how about the decompression writing over the shared > info page causing all this? As the decompressor wouldn't > expect Xen to possibly write stuff there itself, it could easily be > that some repeat count gets altered, thus breaking the > decompressed data without the decompression code necessarily > noticing. In my case the gfn of the shared info page is 1f54. Is it possible to move the page at runtime? It looks like it can be done because the hvm loader configures fffff initially. Perhaps the PVonHVM code has to give up the shared pages or move them to some dedicated unused page during the process of booting into the new kernel. Konrad, any idea how that could be done? > If that's the case, there would be a more general problem here > (for kdump at least), as granted pages could also still get written > to when the new kernel already is in the process of launching. Maybe you meant to say kexec instead of kdump? kdump runs in its own memory area, so I think the worst thing is that some pages of the crashed kernel get modified. Olaf
