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

Re: [Xen-devel] Linux 4.19.5 fails to boot as Xen dom0


  • To: Greg KH <greg@xxxxxxxxx>
  • From: Juergen Gross <jgross@xxxxxxxx>
  • Date: Fri, 11 Jan 2019 09:54:31 +0100
  • Autocrypt: addr=jgross@xxxxxxxx; prefer-encrypt=mutual; keydata= xsBNBFOMcBYBCACgGjqjoGvbEouQZw/ToiBg9W98AlM2QHV+iNHsEs7kxWhKMjrioyspZKOB ycWxw3ie3j9uvg9EOB3aN4xiTv4qbnGiTr3oJhkB1gsb6ToJQZ8uxGq2kaV2KL9650I1SJve dYm8Of8Zd621lSmoKOwlNClALZNew72NjJLEzTalU1OdT7/i1TXkH09XSSI8mEQ/ouNcMvIJ NwQpd369y9bfIhWUiVXEK7MlRgUG6MvIj6Y3Am/BBLUVbDa4+gmzDC9ezlZkTZG2t14zWPvx XP3FAp2pkW0xqG7/377qptDmrk42GlSKN4z76ELnLxussxc7I2hx18NUcbP8+uty4bMxABEB AAHNHkp1ZXJnZW4gR3Jvc3MgPGpncm9zc0BzdXNlLmRlPsLAeQQTAQIAIwUCU4xw6wIbAwcL CQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJELDendYovxMvi4UH/Ri+OXlObzqMANruTd4N zmVBAZgx1VW6jLc8JZjQuJPSsd/a+bNr3BZeLV6lu4Pf1Yl2Log129EX1KWYiFFvPbIiq5M5 kOXTO8Eas4CaScCvAZ9jCMQCgK3pFqYgirwTgfwnPtxFxO/F3ZcS8jovza5khkSKL9JGq8Nk czDTruQ/oy0WUHdUr9uwEfiD9yPFOGqp4S6cISuzBMvaAiC5YGdUGXuPZKXLpnGSjkZswUzY d9BVSitRL5ldsQCg6GhDoEAeIhUC4SQnT9SOWkoDOSFRXZ+7+WIBGLiWMd+yKDdRG5RyP/8f 3tgGiB6cyuYfPDRGsELGjUaTUq3H2xZgIPfOwE0EU4xwFgEIAMsx+gDjgzAY4H1hPVXgoLK8 B93sTQFN9oC6tsb46VpxyLPfJ3T1A6Z6MVkLoCejKTJ3K9MUsBZhxIJ0hIyvzwI6aYJsnOew cCiCN7FeKJ/oA1RSUemPGUcIJwQuZlTOiY0OcQ5PFkV5YxMUX1F/aTYXROXgTmSaw0aC1Jpo w7Ss1mg4SIP/tR88/d1+HwkJDVW1RSxC1PWzGizwRv8eauImGdpNnseneO2BNWRXTJumAWDD pYxpGSsGHXuZXTPZqOOZpsHtInFyi5KRHSFyk2Xigzvh3b9WqhbgHHHE4PUVw0I5sIQt8hJq 5nH5dPqz4ITtCL9zjiJsExHuHKN3NZsAEQEAAcLAXwQYAQIACQUCU4xwFgIbDAAKCRCw3p3W KL8TL0P4B/9YWver5uD/y/m0KScK2f3Z3mXJhME23vGBbMNlfwbr+meDMrJZ950CuWWnQ+d+ Ahe0w1X7e3wuLVODzjcReQ/v7b4JD3wwHxe+88tgB9byc0NXzlPJWBaWV01yB2/uefVKryAf AHYEd0gCRhx7eESgNBe3+YqWAQawunMlycsqKa09dBDL1PFRosF708ic9346GLHRc6Vj5SRA UTHnQqLetIOXZm3a2eQ1gpQK9MmruO86Vo93p39bS1mqnLLspVrL4rhoyhsOyh0Hd28QCzpJ wKeHTd0MAWAirmewHXWPco8p1Wg+V+5xfZzuQY0f4tQxvOpXpt4gQ1817GQ5/Ed/wsDtBBgB CAAgFiEEhRJncuj2BJSl0Jf3sN6d1ii/Ey8FAlrd8NACGwIAgQkQsN6d1ii/Ey92IAQZFggA HRYhBFMtsHpB9jjzHji4HoBcYbtP2GO+BQJa3fDQAAoJEIBcYbtP2GO+TYsA/30H/0V6cr/W V+J/FCayg6uNtm3MJLo4rE+o4sdpjjsGAQCooqffpgA+luTT13YZNV62hAnCLKXH9n3+ZAgJ RtAyDWk1B/0SMDVs1wxufMkKC3Q/1D3BYIvBlrTVKdBYXPxngcRoqV2J77lscEvkLNUGsu/z W2pf7+P3mWWlrPMJdlbax00vevyBeqtqNKjHstHatgMZ2W0CFC4hJ3YEetuRBURYPiGzuJXU pAd7a7BdsqWC4o+GTm5tnGrCyD+4gfDSpkOT53S/GNO07YkPkm/8J4OBoFfgSaCnQ1izwgJQ jIpcG2fPCI2/hxf2oqXPYbKr1v4Z1wthmoyUgGN0LPTIm+B5vdY82wI5qe9uN6UOGyTH2B3p hRQUWqCwu2sqkI3LLbTdrnyDZaixT2T0f4tyF5Lfs+Ha8xVMhIyzNb1byDI5FKCb
  • Cc: Hans van Kranenburg <hans@xxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx, "Kirill A. Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>, stable <stable@xxxxxxxxxxxxxxx>
  • Delivery-date: Fri, 11 Jan 2019 08:54:42 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Openpgp: preference=signencrypt

On 11/01/2019 09:46, Greg KH wrote:
> On Fri, Jan 11, 2019 at 08:59:52AM +0100, Juergen Gross wrote:
>> On 22/12/2018 12:14, Juergen Gross wrote:
>>> On 06/12/2018 12:46, Greg KH wrote:
>>>> On Thu, Dec 06, 2018 at 12:31:15PM +0100, Juergen Gross wrote:
>>>>> On 06/12/2018 12:13, Greg KH wrote:
>>>>>> On Thu, Nov 29, 2018 at 02:35:17PM +0100, Juergen Gross wrote:
>>>>>>> On 29/11/2018 14:26, Kirill A. Shutemov wrote:
>>>>>>>> On Thu, Nov 29, 2018 at 09:41:25AM +0000, Juergen Gross wrote:
>>>>>>>>> On 29/11/2018 02:22, Hans van Kranenburg wrote:
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> As also seen at:
>>>>>>>>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914951
>>>>>>>>>>
>>>>>>>>>> Attached there are two serial console output logs. One is starting 
>>>>>>>>>> with
>>>>>>>>>> Xen 4.11 (from debian unstable) as dom0, and the other one without 
>>>>>>>>>> Xen.
>>>>>>>>>>
>>>>>>>>>> [    2.085543] BUG: unable to handle kernel paging request at
>>>>>>>>>> ffff888d9fffc000
>>>>>>>>>> [    2.085610] PGD 200c067 P4D 200c067 PUD 0
>>>>>>>>>> [    2.085674] Oops: 0000 [#1] SMP NOPTI
>>>>>>>>>> [    2.085736] CPU: 1 PID: 1 Comm: swapper/0 Not tainted
>>>>>>>>>> 4.19.0-trunk-amd64 #1 Debian 4.19.5-1~exp1+pvh1
>>>>>>>>>> [    2.085823] Hardware name: HP ProLiant DL360 G7, BIOS P68 
>>>>>>>>>> 05/21/2018
>>>>>>>>>> [    2.085895] RIP: e030:ptdump_walk_pgd_level_core+0x1fd/0x490
>>>>>>>>>> [...]
>>>>>>>>>
>>>>>>>>> The offending stable commit is 
>>>>>>>>> 4074ca7d8a1832921c865d250bbd08f3441b3657
>>>>>>>>> ("x86/mm: Move LDT remap out of KASLR region on 5-level paging"), this
>>>>>>>>> is commit d52888aa2753e3063a9d3a0c9f72f94aa9809c15 upstream.
>>>>>>>>>
>>>>>>>>> Current upstream kernel is booting fine under Xen, so in general the
>>>>>>>>> patch should be fine. Using an upstream kernel built from above commit
>>>>>>>>> (with the then needed Xen fixup patch 1457d8cf7664f34c4ba534) is fine,
>>>>>>>>> too.
>>>>>>>>>
>>>>>>>>> Kirill, are you aware of any prerequisite patch from 4.20 which could 
>>>>>>>>> be
>>>>>>>>> missing in 4.19.5?
>>>>>>>>
>>>>>>>> I'm not.
>>>>>>>>
>>>>>>>> Let me look into this.
>>>>>>>>
>>>>>>>
>>>>>>> What is making me suspicious is the failure happening just after
>>>>>>> releasing the init memory. Maybe there is an access to .init.data
>>>>>>> segment or similar? The native kernel booting could be related to the
>>>>>>> usage of 2M mappings not being available in a PV-domain.
>>>>>>
>>>>>> Did this ever get fixed anywhere that I can properly backport it to the
>>>>>> 4.19.y tree?
>>>>>
>>>>> https://lore.kernel.org/lkml/20181130202328.65359-2-kirill.shutemov@xxxxxxxxxxxxxxx/
>>>>>
>>>>> Still pending upstream. Just pinged tglx.
>>>>
>>>> Thanks, it should have gotten a cc: stable@ tag, but I can watch out for
>>>> it...
>>>
>>> It's upstream now: commit 16877a5570e0c5f4270d5b17f9bab427bcae9514
>>
>> Any reason you didn't include this patch in 4.19.14?
> 
> I was catching up on pending patches and got to this yesterday. It
> should now be queued up already for the next releases, right?

Okay, thanks for confirmation.


Juergen

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

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