[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: regression in recent pvops kernels, dom0 crashes early
- To: Olaf Hering <olaf@xxxxxxxxx>
- From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
- Date: Thu, 13 May 2021 13:29:32 +0100
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ohf7UPG1S3BPgYS665xHfBXuDMNUeU7vCuoEhzzTtkI=; b=MwKigK3UxN77xZ9VW8Vkng0Nibrs2Fus9Hmkodjcc2TqKw8EZ/qmfgbRTdjkRx0e/Zaor28WeUTc59vH7Z+Ft4ZehNGOqxlXHftlguxFpd0syuI7txdWhY6BhnZ4v663k2g/IYijief6TNwnnhfpWO9XxusyrTwVWfjLkP0zmnqk5y0z0zZN6EUjIqUSKX0OiX1R2gkTV1SVGWmFS1GpnJ3AHQEKTKVjGz0h3z/r7R5UQO3HS/oPLuqCnM3v2PJUPbljG9sbSzWBYJdfFJUzEyZijNt6l4K1yDRZpjLaCXO3XLCqi73H8qtMQdpBuJNy04zYnXE9urPMtplwVS0nFg==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Yj1xG/IaZc3WGZBEK/U0+sELdXf1JuhhtHyMN2kLvAgPt3DG0QWEHf5fR55om5ia9SKRAYeXOLHV2xgiuVIiJXuu3K4BWCQnBoNVfzZYv73U0MBGCTh8A+oY25gCdZ0LYx8VvC/fIyKFsI6VssymTYRpqmmF1/n0+K08xR6T7Yb2v3MWPr20/izUaZB1rxZqtQA9tM7kC2/+Glr2rd5NoNVh7r8LTLJGkIwTPqJKcs2fAYd/UStjBXWbt+rYtYzfnSoR0ot1I6lDzFO7aJ1aZAewFmhPX5BrAnGw6kr4LUZ289au9InMyDVWTvokYdD8kZ4Bl3NkDH3Qm1F0uvzkFg==
- Authentication-results: esa4.hc3370-68.iphmx.com; dkim=pass (signature verified) header.i=@citrix.onmicrosoft.com
- Cc: <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- Delivery-date: Thu, 13 May 2021 12:29:47 +0000
- Ironport-hdrordr: A9a23:ZWQX76nNVAUtHk7yNlt3Z2bgKhjpDfMpimdD5ihNYBxZY6Wkfp +V88jzhCWZtN9OYhwdcLC7WZVpQRvnhPtICPoqTMiftW7dyReVxeBZnPbfKljbdREWmdQtrZ uIH5IOb+EYSGIK9/oSgzPIYOrIouP3iZxA7N22pxwGLXAIGtRdBkVCe2Km+yVNNXl77PECZf yhD6R81lidkDgsH7+G7i5vZZmzmzSHruOrXfZobCRXpzWmvHeN0vrXAhKY1hARX3dk2rE561 XIlAT/++GKr+y74gW07R6S071m3P/ajvdTDs2FjcYYbh/2jByzWYhnU7qe+BgoveCU7kowmt WkmWZgAy1K0QKSQoiJm2qp5+G5uwxer0MKiGXoz0cLmPaJBw7TUKF69MVkmnKz0TtTgDl+uJ g7lF5x+aAnSy8opx6NkOQgYSsa3nZckUBS5dL7sEYvJ7f2SIUh57D3r3klXavpIkrBmcka+b 5Vfb/hDbBtAAqnU0w=
- Ironport-sdr: GpRorewRqtZcOLksbPnldzKs1Pqmxxw6RL9wXSCQ9ItNxYZQ69qLHHL8cSKhBZF0Gz1cjTwxC7 oH/224HspcV0JUlefJEdH4eFI5psDR42B4eVKkEO8nLTO/RA+la/Gc7oyhGnAkyCyKjSKoSuC0 pSnHb2+QJJCK73jt58WD2B6Dviuzf1wIK21hUw5XSXC9CoDHZst4N95OUfBFL2x2jb3ACZRxRp FYx7S1qLnNVwqpZNuRSVtSTl5gWnK0IG95c3PLJLKf66WHdnckm8mXtYxlHlF8GNQVcvAvW7tS YE4=
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 13/05/2021 13:22, Olaf Hering wrote:
> Am Thu, 13 May 2021 13:11:10 +0100
> schrieb Andrew Cooper <andrew.cooper3@xxxxxxxxxx>:
>
>> If I'm counting bits correctly, that is Xen rejecting the use of the NX
>> bit, which is suspicious. Do you have the full Xen boot log on this
>> box? I wonder if we've some problem clobbing the XD-disable bit.
>
> Yes, it was attached.
> Is there any other Xen cmdline knob to enable more debug?
Urgh sorry - I've not had enough coffee yet today.
Warning: NX (Execute Disable) protection not active
And this is an AMD box not an Intel box, so no XD-disable nonsense (that
I'm aware of).
So, the two options are:
1) This box legitimately doesn't have NX, and the dom0 kernel is buggy
for trying to use it.
2) This box does actually have NX, Xen has failed to turn it on, and
dom0 (through non CPUID means) thinks that NX is usable.
Can we first establish whether this box really does, or does not, have NX ?
~Andrew
|
