From: "Jan Beulich" <JBeulich@suse.com>
To: Kevin Moraga <kmoragas@riseup.net>
Cc: xen-devel@lists.xen.org
Subject: Re: crash on boot with 4.6.1 on fedora 24
Date: Mon, 09 May 2016 09:53:02 -0600 [thread overview]
Message-ID: <5730CE7E02000078000E9A8A@prv-mh.provo.novell.com> (raw)
In-Reply-To: <5730A447.3010505@riseup.net>
>>> On 09.05.16 at 16:52, <kmoragas@riseup.net> wrote:
> On 05/09/2016 04:08 AM, Jan Beulich wrote:
>>>>> On 09.05.16 at 00:51, <kmoragas@riseup.net> 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
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-09 15:53 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 22:51 crash on boot with 4.6.1 on fedora 24 Kevin Moraga
2016-05-09 7:23 ` Andrew Cooper
2016-05-09 10:05 ` Jan Beulich
2016-05-09 10:08 ` Jan Beulich
2016-05-09 14:52 ` Kevin Moraga
2016-05-09 15:53 ` Jan Beulich [this message]
2016-05-09 16:40 ` Kevin Moraga
2016-05-09 17:15 ` Boris Ostrovsky
2016-05-09 17:22 ` Kevin Moraga
2016-05-09 18:40 ` Boris Ostrovsky
2016-05-10 7:23 ` Jan Beulich
2016-05-10 13:39 ` Boris Ostrovsky
2016-05-10 13:57 ` Jan Beulich
2016-05-10 15:19 ` Juergen Gross
2016-05-10 15:35 ` Jan Beulich
[not found] ` <57321BFA02000078000EA3C2@suse.com>
2016-05-10 15:43 ` Juergen Gross
2016-05-10 16:35 ` Boris Ostrovsky
2016-05-11 5:49 ` Juergen Gross
2016-05-11 6:35 ` Jan Beulich
[not found] ` <5732EEBF02000078000EA613@suse.com>
2016-05-11 7:00 ` Juergen Gross
2016-05-11 7:15 ` Jan Beulich
[not found] ` <5732F83D02000078000EA6A2@suse.com>
2016-05-11 9:57 ` Juergen Gross
2016-05-11 10:03 ` Jan Beulich
[not found] ` <57331FA002000078000EA831@suse.com>
2016-05-11 10:10 ` Juergen Gross
2016-05-11 12:09 ` Jan Beulich
2016-05-11 10:16 ` David Vrabel
2016-05-11 12:21 ` Jan Beulich
2016-05-11 12:48 ` David Vrabel
2016-05-11 13:13 ` Jan Beulich
2016-05-11 13:15 ` Juergen Gross
2016-05-17 15:11 ` David Vrabel
2016-05-17 20:58 ` Kevin Moraga
2016-05-26 10:24 ` David Vrabel
2016-05-26 14:05 ` Boris Ostrovsky
2016-05-26 15:24 ` David Vrabel
2016-06-01 16:12 ` Martin Cerveny
2016-06-01 16:23 ` Martin Cerveny
2016-06-01 19:32 ` Boris Ostrovsky
2016-06-01 21:01 ` Martin Cerveny
2016-06-01 22:37 ` Boris Ostrovsky
2016-06-02 6:04 ` Martin Cerveny
2016-06-02 13:15 ` Martin Cerveny
2016-06-02 9:54 ` David Vrabel
2016-05-10 16:11 ` Kevin Moraga
2016-05-10 20:11 ` Boris Ostrovsky
2016-05-12 4:52 ` Kevin Moraga
-- strict thread matches above, loose matches on Subject: below --
2016-03-28 17:00 Michael Young
2016-03-29 10:07 ` Jan Beulich
2016-03-29 17:50 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5730CE7E02000078000E9A8A@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=kmoragas@riseup.net \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).