From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Moraga Subject: Re: crash on boot with 4.6.1 on fedora 24 Date: Mon, 9 May 2016 08:52:55 -0600 Message-ID: <5730A447.3010505@riseup.net> References: <572FC2F9.3060200@riseup.net> <57307DD402000078000E9622@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0023074343837230004==" Return-path: In-Reply-To: <57307DD402000078000E9622@prv-mh.provo.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Jan Beulich Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --===============0023074343837230004== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="PX518AJs4RXi4C15l90f9diWItpEimeRw" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --PX518AJs4RXi4C15l90f9diWItpEimeRw Content-Type: multipart/mixed; boundary="QUDsmRjpqEd33SshExGEchpSu0e77A5HX" From: Kevin Moraga To: Jan Beulich Cc: xen-devel@lists.xen.org Message-ID: <5730A447.3010505@riseup.net> Subject: Re: [Xen-devel] crash on boot with 4.6.1 on fedora 24 References: <572FC2F9.3060200@riseup.net> <57307DD402000078000E9622@prv-mh.provo.novell.com> In-Reply-To: <57307DD402000078000E9622@prv-mh.provo.novell.com> --QUDsmRjpqEd33SshExGEchpSu0e77A5HX Content-Type: multipart/alternative; boundary="------------040006070705090400080205" This is a multi-part message in MIME format. --------------040006070705090400080205 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 05/09/2016 04:08 AM, Jan Beulich wrote: >>>> On 09.05.16 at 00:51, 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?=20 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=3D0B6Ol0ob95UxXQV9HM1BWMmhCZ0E Also I compiled 4.2.28 / 4.1.X and it works fine with this processor, using i915.preliminary_hw_support, but we are experiencing problems with suspend/wakeup (but that's another story) > Or if you don't have it anymore, obtain > fresh logs for whichever binary you're going to make available? > > Jan Also there are more reports about the same crash with this kernel compiled by someone else:=20 **http://yum.qubes-os.org/r3.1/unstable/dom0/fc20/rpm/kernel-4.4.8-9.pvop= s.qubes.x86_64.rpm --------------040006070705090400080205 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 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/op= en?id=3D0B6Ol0ob95UxXQV9HM1BWMmhCZ0E

Also I compiled 4.2.28 / 4.1.X and it works fine with this processor, using i915.preliminary_hw_support, but we are experiencing problems with suspend/wakeup (but that's another story)<= br> 
Or if you don't have it anymore, obtain
fresh logs for whichever binary you're going to make available?

Jan

Also there are more reports about the same crash with this kernel compiled by someone else:=A0 http://yum.qubes-os.org/r3.1/unstable/dom0/fc= 20/rpm/kernel-4.4.8-9.pvops.qubes.x86_64.rpm
--------------040006070705090400080205-- --QUDsmRjpqEd33SshExGEchpSu0e77A5HX-- --PX518AJs4RXi4C15l90f9diWItpEimeRw Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXMKRjAAoJEIr57EYHp2ROqfMP/3kRdgiOgsn4JIy32lrVLEGU l6Qw6k8gsxJlUkJhSOgQNkUp+ebkOHAB7973RV4q2PNF3rnwoDXfg1veAWnIPfTw bV5gAkw2pbUTo04FSHbH0LHJlbxZaNErpmvHozTJaSuBsRy0g38qEth8Ekh5LQS2 /GGlxNxs7lpNP/6XBLc9X7ozm6grh01mFvgkEj6VDVZABknLbbTVosGX7kIgIm0B q00F3i3mzRjHxsHrp+25AIL9HDrdBFyASF65l4kqoY2fl/RaSno4Zxiw5rj0CGBP 4O8a4tM26TbhvoX7cmPwpC6jMNIbb3ItsaSxIVT0nGQ3+iHXE1/onfDOwy2E2rw9 pGJdRvY1ccfacosEw7aH89XSMdPqfAdr+Qwhh7b2YjUxFfvJ/g5AzoavDUofi0Ib 5FizwzZltGRvL9J94oaBjiXjtbVzxv7L/9Li6sxKJaz/ISHBvobE6aL5B0Kpm3kK gvzE5p7tkSxwmigb9FcSqTu0Tq/UI6phHQaOi3Zk9ukm8aGBqTA7kbz6eW31ayLi iyr2fqWdx86m0L5V7O0A7rBPHtreqPWvzf4SkBuTTjbhLD1VR7YwoYIo/Szbw/7H Ss8Yfofx6SCb5WiD1/Rys5fmiRH86nEoymj245BuJtKN7VId34h6NJ9pmSzMk/Jl /N9+lZ9t3Kyw14QZO4mg =Onh3 -----END PGP SIGNATURE----- --PX518AJs4RXi4C15l90f9diWItpEimeRw-- --===============0023074343837230004== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9y Zy94ZW4tZGV2ZWwK --===============0023074343837230004==--