[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] crash on boot with 4.6.1 on fedora 24

On 05/09/2016 09:53 AM, Jan Beulich wrote:
>>>> On 09.05.16 at 16:52, <kmoragas@xxxxxxxxxx> wrote:
>> On 05/09/2016 04:08 AM, Jan Beulich wrote:
>>>>>> On 09.05.16 at 00:51, <kmoragas@xxxxxxxxxx> wrote:
>>>> I'm try to compile kernel 4.4.8 (using fedora 23) to run with Xen 4.6.0
>>>> and Intel Skylake processor (Intel Core i7-6600U)
>>>> This kernel is crashing almost in the same way as explained in this
>>>> thread... But my problem is mainly with Skylake. Because the same
>>>> configuration works within another machine but with another processor
>>>> (Intel Core i5-3340M). Attached are the boot logs.
>>> The address the fault occurs on (ffff8000006bdee0) is bogus, so
>>> from the register and stack dump alone I don't think we can derive
>>> much. What we'd need is access to the kernel binary used (or
>>> really the vmlinux accompanying the vmlinuz that was used), in
>>> order to see where exactly the kernel died, and hence where this
>>> bogus address originates from. As I understand it this is a kernel
>>> you built yourself - can you make said binary from exactly that
>>> build available somewhere? 
>> Yes I have it. But I get the same crash on various 4.4.X and also with
>> 4.5.3.
>> **https://drive.google.com/open?id=0B6Ol0ob95UxXQV9HM1BWMmhCZ0E 
> Well, this doesn't contain the file I'm after (vmlinux), and taking
> apart vmlinuz would be quite cumbersome.
> Jan

Oh sorry, here is the link to vmlinux


Kevin Moraga
Fingerprint: 3915 A5A9 959C D18F 0A89 B47E FB4B 55F5 F258 EDCB

Attachment: signature.asc
Description: OpenPGP digital signature

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.