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

[Andrew Cooper <andrew.cooper3@citrix.com>]

On 27/07/16 19:22, lists@ssl-mail.com wrote:
>
> On Wed, Jul 27, 2016, at 09:56 AM, Andrew Cooper wrote:
>>>> 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
> Thanks.
>
> For whatever reason it the dev debug symbols aren't available for the official Kernel:Stable branch,
>
> 	http://software.opensuse.org/package/kernel-default-debuginfo?search_term=kernel-default-debuginfo
>
> unlike for the release 4.1.x kernel.
>
> But there is this from an unofficial repo
>
> 	https://build.opensuse.org/package/binaries/hardware:nvdimm/kernel-default?repository=openSUSE_Leap_42.1
>
> I'm not sure if that's good enough.

Sadly not.  The debug symbols need to be specific to the exact binary
you booted.

Any change in the compilation will result in the translation being
useless.  What addr2line is doing is saying "which specific bit of
source code did the compiler/linker end up putting at $X".

I wouldn't worry too much - I expect (the lack of) the aforementioned
changeset is the cause of your issues.

~Andrew

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