From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Bader Subject: (XEN) traps.c:3071: GPF (0000): ffff82d0801d76b2 -> ffff82d080222806 Date: Mon, 03 Nov 2014 10:45:04 +0100 Message-ID: <54574EA0.5070101@canonical.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2832209043405747859==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --===============2832209043405747859== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="cQ69W14HbP5Lg69N41p23H5UMufnN6rre" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --cQ69W14HbP5Lg69N41p23H5UMufnN6rre Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: quoted-printable I see the message from the subject on my Intel box whenever a guest (iirc= even dom0) starts up. It is not fatal and everything seems ok. I am just curio= us about what might trigger this. The addresses look to be inside the hyperv= isor code. I was wondering whether there is a simple way to figure out what th= is relates to (likely need to look at the objdump of the unstripped hv modul= e). Or has someone already looked into this and knows what likely is the caus= e? -Stefan --cQ69W14HbP5Lg69N41p23H5UMufnN6rre Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJUV06gAAoJEOhnXe7L7s6jR+gP/RKx76b6HSxJhfoY5bopinh2 Ey4C63qcHT7vf40c6FwfVU4RhMR1Rykws3vhOYYy0BqNAl/DYb+EJ1vdVVt7gFac rQ/JafbvUkuWgZLlsnmuluGnV5HLxbKXqO+0VcUD4A+mRE94bHqYnhaUQLKhkuoN /djM+8Hw3ycdamW69W2aShvGNoGfQ4cl5fFGLgTJHarTDiW/HuiHnthmy2kOVTsU fdVKrzncUGX5lIIaRCkPvP2n9qz1mVNQqmUhbAfKYtu9VyQvBhJX7M6mWUfS6brt baiBtuN91ooitSqlgBKKxRiT0WJL8Pd4Am1AzdURINyYAo8mj4knvcEhWwOrIHwy iO3Jyl1EvrNlXsfQmU08EUupFMIObh7OCGZK2FeBKMObdmiK6Y0KBE/fQrT6g+WA qfETcL7LgVRASogiXJV+c2460+2El0sqZcD2z0GEQfwghxfkCt5U2KABQmh2Oj/L EWvYKM614jmKj15B6sPJEDrsKAEkmd1Jq1fNdMGmYxVRBofpkWJl0sKLuwkDzWgO 64nE/bYo4m/bG8q/nzVr01+r1j3pn1KK+abddZZZlvqGBFa76fAiWlCMr7WJTIde e08Mq5ufOBOZAYxOs4YBJjoriug3nxq9ozZkj+0d4xgfvAxNWRgAEdhXz1nGcdz7 3ZOshwcXi4RHyyAYJg6u =J3r/ -----END PGP SIGNATURE----- --cQ69W14HbP5Lg69N41p23H5UMufnN6rre-- --===============2832209043405747859== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============2832209043405747859==--