From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?0K7RgNGW0Lkg0JrQvtC90L7QstCw0LvQtdC90LrQvg==?= Subject: Re: Frequent reports about Xen unstable hanging on ARM boots Date: Fri, 18 Mar 2016 19:36:59 +0200 Message-ID: References: <5BFA3B79-F43D-4E3D-97A7-D7A8427544C7@gmail.com> <56E85677.2050604@arm.com> <65B31D07-F41F-4213-B4D5-1A41262369FF@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3130329749504297853==" Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1agyKb-0001uT-8c for xen-devel@lists.xenproject.org; Fri, 18 Mar 2016 17:37:01 +0000 Received: by mail-wm0-f43.google.com with SMTP id p65so78633017wmp.1 for ; Fri, 18 Mar 2016 10:36:59 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Paul Sujkov Cc: WeiLiu , Lars Kurth , Doug Goldstein , Julien Grall , Stefano Stabellini , xen-devel , baozich@gmail.com List-Id: xen-devel@lists.xenproject.org --===============3130329749504297853== Content-Type: multipart/alternative; boundary=001a114b2d46b04ae6052e563106 --001a114b2d46b04ae6052e563106 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, Lars! We've just verified current master (Xen 4.7-unstable) on our DRA7 setup. Everything works fine, issue is not reproduced. There are a lot of strange things in this setup: 1. It seems like there are problems with UART driver detection in Xen. It is because of incorrect command line: (XEN) Command line: sync_console console=3Duart dtuart=3Duart1 According to wiki must be "sync_console console=3Ddtuart dtuart=3Dserial2". I see setuping it in u-boot: U-Boot# setenv xen_bootargs 'sync_console console=3Ddtuart dtuart=3Dserial2= ' U-Boot# fdt set /chosen xen,xen-bootargs \"$xen_bootargs\" But as you can see it doesn't work. 2. We have for our DRA7 setup console on serial0, not serial2. Is it right to use serial2 for that setup? 3. Xen starts not in Hypervisor mode, nad switches to this mode: - NOT HYP, setting it ... - - Xen starting in Hyp mode - As far as I know, this functionality is moved to u-boot, I can't see this code in master branch. So, are there any additional patches over mainline? 18 =D0=BC=D0=B0=D1=80=D1=82=D0=B0 2016 =D0=B3. 19:21 =D0=BF=D0=BE=D0=BB=D1= =8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C "Paul Sujkov" =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB: > Hi, > > linking in Iurii, who did an investigation of this issue from our side. > --001a114b2d46b04ae6052e563106 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hi, Lars!

We've just verified current master (Xen 4.7-unstable) on= our DRA7 setup. Everything works fine, issue is not reproduced.

There are a lot of strange things in this setup:
1. It seems like there are problems with UART driver detection in Xen. It i= s because of incorrect command line:
(XEN) Command line: sync_console console=3Duart dtuart=3Duart1
According to wiki must be "sync_console console=3Ddtuart dtuart=3Dseri= al2".
I see setuping it in u-boot:
U-Boot# setenv xen_bootargs 'sync_console console=3Ddtuart dtuart=3Dser= ial2'
U-Boot# fdt set /chosen xen,xen-bootargs \"$xen_bootargs\"
But as you can see it doesn't work.
2. We have for our DRA7 setup console on serial0, not serial2. Is it right = to use serial2 for that setup?
3. Xen starts not in Hypervisor mode, nad switches to this mode:
- NOT HYP, setting it ... -
- Xen starting in Hyp mode -
As far as I know, this functionality is moved to u-boot, I can't see th= is code in master branch.
So, are there any additional patches over mainline?

18 =D0=BC=D0=B0=D1=80=D1=82=D0=B0 2016 =D0=B3. 1= 9:21 =D0=BF=D0=BE=D0=BB=D1=8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1= =8C "Paul Sujkov" <psujko= v@gmail.com> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB:
Hi,

linking in Iurii, who did an investigation of thi= s issue from our side.
--001a114b2d46b04ae6052e563106-- --===============3130329749504297853== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9y Zy94ZW4tZGV2ZWwK --===============3130329749504297853==--