Re: [Xen-devel] Xen 4.7.0 boot PANIC on kernel 4.7.0-4 + UEFI ?

[Andrew Cooper <andrew.cooper3@xxxxxxxxxx>]

On 27/07/16 17:54, lists@xxxxxxxxxxxx wrote:
>
> On Wed, Jul 27, 2016, at 09:34 AM, Andrew Cooper wrote:
>> This looks suspiciously like the issue which was fixed by c/s
>> d6b186c1e2d852a92c43f090d0d8fad4704d51ef "x86/xen: avoid m2p lookup when
>> setting early page table entries", but that fix is present in Linux 4.7.0
>>
>> Can you check to see whether the commit is included in your kernel?
> This
>
>  
> https://kernel.googlesource.com/pub/scm/linux/kernel/git/stable/linux-stable.git/+/d6b186c1e2d852a92c43f090d0d8fad4704d51ef
>
> looks like the Suse team was involved,
>
>   Reviewed-by: Juergen Gross <jgross@xxxxxxxx>
>
> But checking this kernel
>
>  rpm -q kernel-source
>   kernel-source-4.7.0-4.1.g89a2ada.noarch
>  rpm -q --changelog kernel-source | egrep -i "m2p|d6b186c1"
>   - guarantee M2P to be invisible to user mode.
>
> it doesn't look like it's in here.

Juergen: Any ideas?

>
>> Failing that, can you find out exactly where the kernel crashed?  You
>> need to manually decode ffffffff81f6374c with the debug symbols.
> Sure can try.  I'm gonna have to read-up on how .  Atm no clue.

addr2line -e /path/to/linux/debug/symbols ffffffff81f6374c

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel