* [linux-linus test] 104684: regressions - FAIL
@ 2017-01-26 13:23 osstest service owner
2017-01-26 15:03 ` Boris Ostrovsky
0 siblings, 1 reply; 12+ messages in thread
From: osstest service owner @ 2017-01-26 13:23 UTC (permalink / raw)
To: xen-devel, osstest-admin
flight 104684 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/104684/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 6 xen-boot fail REGR. vs. 59254
test-armhf-armhf-libvirt-xsm 6 xen-boot fail REGR. vs. 59254
test-armhf-armhf-libvirt 6 xen-boot fail REGR. vs. 59254
test-armhf-armhf-xl-arndale 6 xen-boot fail REGR. vs. 59254
test-armhf-armhf-xl-credit2 6 xen-boot fail REGR. vs. 59254
test-amd64-amd64-xl-qemut-debianhvm-amd64 13 guest-localmigrate fail REGR. vs. 59254
test-armhf-armhf-xl-xsm 6 xen-boot fail REGR. vs. 59254
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-rtds 6 xen-boot fail REGR. vs. 59254
test-armhf-armhf-libvirt-raw 6 xen-boot fail baseline untested
test-armhf-armhf-xl-vhd 6 xen-boot fail baseline untested
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 59254
test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail like 59254
test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop fail like 59254
test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop fail like 59254
Tests which did not succeed, but are not blocking:
test-arm64-arm64-libvirt-xsm 1 build-check(1) blocked n/a
test-arm64-arm64-xl 1 build-check(1) blocked n/a
build-arm64-libvirt 1 build-check(1) blocked n/a
test-arm64-arm64-libvirt-qcow2 1 build-check(1) blocked n/a
test-arm64-arm64-libvirt 1 build-check(1) blocked n/a
test-arm64-arm64-xl-credit2 1 build-check(1) blocked n/a
test-arm64-arm64-xl-rtds 1 build-check(1) blocked n/a
test-arm64-arm64-xl-multivcpu 1 build-check(1) blocked n/a
test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a
build-arm64 5 xen-build fail never pass
test-amd64-amd64-xl-pvh-amd 11 guest-start fail never pass
test-amd64-amd64-libvirt 12 migrate-support-check fail never pass
test-amd64-amd64-xl-pvh-intel 14 guest-saverestore fail never pass
test-amd64-amd64-libvirt-xsm 12 migrate-support-check fail never pass
test-amd64-i386-libvirt 12 migrate-support-check fail never pass
test-amd64-i386-libvirt-xsm 12 migrate-support-check fail never pass
build-arm64-xsm 5 xen-build fail never pass
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass
test-amd64-amd64-libvirt-vhd 11 migrate-support-check fail never pass
test-amd64-amd64-qemuu-nested-amd 16 debian-hvm-install/l1/l2 fail never pass
test-armhf-armhf-xl-multivcpu 12 migrate-support-check fail never pass
test-armhf-armhf-xl-multivcpu 13 saverestore-support-check fail never pass
test-armhf-armhf-xl-cubietruck 12 migrate-support-check fail never pass
test-armhf-armhf-xl-cubietruck 13 saverestore-support-check fail never pass
test-armhf-armhf-xl-rtds 12 migrate-support-check fail never pass
test-armhf-armhf-xl-rtds 13 saverestore-support-check fail never pass
version targeted for testing:
linux 49e555a932de57611eb27edf2d1ad03d9a267bdd
baseline version:
linux 45820c294fe1b1a9df495d57f40585ef2d069a39
Last test of basis 59254 2015-07-09 04:20:48 Z 567 days
Failing since 59348 2015-07-10 04:24:05 Z 566 days 225 attempts
Testing same since 104684 2017-01-26 04:21:40 Z 0 days 1 attempts
------------------------------------------------------------
7518 people touched revisions under test,
not listing them all
jobs:
build-amd64-xsm pass
build-arm64-xsm fail
build-armhf-xsm pass
build-i386-xsm pass
build-amd64 pass
build-arm64 fail
build-armhf pass
build-i386 pass
build-amd64-libvirt pass
build-arm64-libvirt blocked
build-armhf-libvirt pass
build-i386-libvirt pass
build-amd64-pvops pass
build-arm64-pvops pass
build-armhf-pvops pass
build-i386-pvops pass
build-amd64-rumprun pass
build-i386-rumprun pass
test-amd64-amd64-xl pass
test-arm64-arm64-xl blocked
test-armhf-armhf-xl fail
test-amd64-i386-xl pass
test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm pass
test-amd64-i386-xl-qemut-debianhvm-amd64-xsm pass
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm pass
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm pass
test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm pass
test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm pass
test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm pass
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm pass
test-amd64-amd64-libvirt-xsm pass
test-arm64-arm64-libvirt-xsm blocked
test-armhf-armhf-libvirt-xsm fail
test-amd64-i386-libvirt-xsm pass
test-amd64-amd64-xl-xsm pass
test-arm64-arm64-xl-xsm blocked
test-armhf-armhf-xl-xsm fail
test-amd64-i386-xl-xsm pass
test-amd64-amd64-qemuu-nested-amd fail
test-amd64-amd64-xl-pvh-amd fail
test-amd64-i386-qemut-rhel6hvm-amd pass
test-amd64-i386-qemuu-rhel6hvm-amd pass
test-amd64-amd64-xl-qemut-debianhvm-amd64 fail
test-amd64-i386-xl-qemut-debianhvm-amd64 pass
test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass
test-amd64-i386-xl-qemuu-debianhvm-amd64 pass
test-amd64-i386-freebsd10-amd64 pass
test-amd64-amd64-xl-qemuu-ovmf-amd64 pass
test-amd64-i386-xl-qemuu-ovmf-amd64 pass
test-amd64-amd64-rumprun-amd64 pass
test-amd64-amd64-xl-qemut-win7-amd64 fail
test-amd64-i386-xl-qemut-win7-amd64 fail
test-amd64-amd64-xl-qemuu-win7-amd64 fail
test-amd64-i386-xl-qemuu-win7-amd64 fail
test-armhf-armhf-xl-arndale fail
test-amd64-amd64-xl-credit2 pass
test-arm64-arm64-xl-credit2 blocked
test-armhf-armhf-xl-credit2 fail
test-armhf-armhf-xl-cubietruck pass
test-amd64-i386-freebsd10-i386 pass
test-amd64-i386-rumprun-i386 pass
test-amd64-amd64-qemuu-nested-intel pass
test-amd64-amd64-xl-pvh-intel fail
test-amd64-i386-qemut-rhel6hvm-intel pass
test-amd64-i386-qemuu-rhel6hvm-intel pass
test-amd64-amd64-libvirt pass
test-arm64-arm64-libvirt blocked
test-armhf-armhf-libvirt fail
test-amd64-i386-libvirt pass
test-amd64-amd64-xl-multivcpu pass
test-arm64-arm64-xl-multivcpu blocked
test-armhf-armhf-xl-multivcpu pass
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-amd64-amd64-libvirt-pair pass
test-amd64-i386-libvirt-pair pass
test-amd64-amd64-amd64-pvgrub pass
test-amd64-amd64-i386-pvgrub pass
test-amd64-amd64-pygrub pass
test-arm64-arm64-libvirt-qcow2 blocked
test-amd64-amd64-xl-qcow2 pass
test-armhf-armhf-libvirt-raw fail
test-amd64-i386-xl-raw pass
test-amd64-amd64-xl-rtds fail
test-arm64-arm64-xl-rtds blocked
test-armhf-armhf-xl-rtds pass
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 pass
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 pass
test-amd64-amd64-libvirt-vhd pass
test-armhf-armhf-xl-vhd fail
test-amd64-amd64-xl-qemut-winxpsp3 pass
test-amd64-i386-xl-qemut-winxpsp3 pass
test-amd64-amd64-xl-qemuu-winxpsp3 pass
test-amd64-i386-xl-qemuu-winxpsp3 pass
------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images
Logs, config files, etc. are available at
http://logs.test-lab.xenproject.org/osstest/logs
Explanation of these reports, and of osstest in general, is at
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
Not pushing.
(No revision log; it would be 2192223 lines long.)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [linux-linus test] 104684: regressions - FAIL
2017-01-26 13:23 [linux-linus test] 104684: regressions - FAIL osstest service owner
@ 2017-01-26 15:03 ` Boris Ostrovsky
2017-01-26 17:18 ` Ian Jackson
0 siblings, 1 reply; 12+ messages in thread
From: Boris Ostrovsky @ 2017-01-26 15:03 UTC (permalink / raw)
To: osstest service owner, xen-devel
On 01/26/2017 08:23 AM, osstest service owner wrote:
> flight 104684 linux-linus real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/104684/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-armhf-armhf-xl 6 xen-boot fail REGR. vs. 59254
> test-armhf-armhf-libvirt-xsm 6 xen-boot fail REGR. vs. 59254
> test-armhf-armhf-libvirt 6 xen-boot fail REGR. vs. 59254
> test-armhf-armhf-xl-arndale 6 xen-boot fail REGR. vs. 59254
> test-armhf-armhf-xl-credit2 6 xen-boot fail REGR. vs. 59254
I don't see why AMR tests fail. But then I also don't see (in the serial
log) the output of 4.10.0-rc5 being booted. There is U-Boot loading it
but there it nothing coming to the console from it.
There is output from 3.16 kernels though.
> test-amd64-amd64-xl-qemut-debianhvm-amd64 13 guest-localmigrate fail REGR. vs. 59254
This one fails in xc_domain_populate_physmap_exact during restore:
xc: detail: Failed allocation for dom 4: 1024 extents of order 0
-boris
> test-armhf-armhf-xl-xsm 6 xen-boot fail REGR. vs. 59254
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [linux-linus test] 104684: regressions - FAIL
2017-01-26 15:03 ` Boris Ostrovsky
@ 2017-01-26 17:18 ` Ian Jackson
2017-01-26 19:01 ` Boris Ostrovsky
0 siblings, 1 reply; 12+ messages in thread
From: Ian Jackson @ 2017-01-26 17:18 UTC (permalink / raw)
To: Boris Ostrovsky, Julien Grall, Stefano Stabellini; +Cc: xen-devel
Boris Ostrovsky writes ("Re: [Xen-devel] [linux-linus test] 104684: regressions - FAIL"):
> On 01/26/2017 08:23 AM, osstest service owner wrote:
> > flight 104684 linux-linus real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/104684/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > test-armhf-armhf-xl 6 xen-boot fail REGR. vs. 59254
...
> I don't see why ARM tests fail. But then I also don't see (in the serial
> log) the output of 4.10.0-rc5 being booted. There is U-Boot loading it
> but there it nothing coming to the console from it.
Yes.
Unfortunately the osstest bisector is having some trouble with this
because the basis revision combination includes Xen f3a7ca02400d which
is ancient and doesn't build now on armhf, although it built before.
(I think the difference is that the compiler has been updated by
Debian.)
Since there is no output from Xen, I think this must be a problem with
the Xen image, not anything to do with Linux.
The history for this test is here:
http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/linux-linus
In xen-unstable, there is what looks like a different failure:
http://logs.test-lab.xenproject.org/osstest/logs/104681/test-armhf-armhf-xl/serial-arndale-westfield.log
The machine in 104684 is cubietruck-metzinger which seems fine:
http://logs.test-lab.xenproject.org/osstest/results/host/cubietruck-metzinger.html
Here are the histories on the linux-linus and xen-unstable branches:
http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/linux-linus
http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/xen-unstable
I think there may be a host-specific bug in ARM in xen-unstable ?
> There is output from 3.16 kernels though.
I think the 3.16 tests you are refrring to are running with a
different version of Xen and on different hardware.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [linux-linus test] 104684: regressions - FAIL
2017-01-26 17:18 ` Ian Jackson
@ 2017-01-26 19:01 ` Boris Ostrovsky
2017-01-26 21:11 ` Julien Grall
0 siblings, 1 reply; 12+ messages in thread
From: Boris Ostrovsky @ 2017-01-26 19:01 UTC (permalink / raw)
To: Ian Jackson, Julien Grall, Stefano Stabellini; +Cc: xen-devel
On 01/26/2017 12:18 PM, Ian Jackson wrote:
> Boris Ostrovsky writes ("Re: [Xen-devel] [linux-linus test] 104684: regressions - FAIL"):
>> On 01/26/2017 08:23 AM, osstest service owner wrote:
>>> flight 104684 linux-linus real [real]
>>> http://logs.test-lab.xenproject.org/osstest/logs/104684/
>>>
>>> Regressions :-(
>>>
>>> Tests which did not succeed and are blocking,
>>> including tests which could not be run:
>>> test-armhf-armhf-xl 6 xen-boot fail REGR. vs. 59254
> ...
>> I don't see why ARM tests fail. But then I also don't see (in the serial
>> log) the output of 4.10.0-rc5 being booted. There is U-Boot loading it
>> but there it nothing coming to the console from it.
> Yes.
>
> Unfortunately the osstest bisector is having some trouble with this
> because the basis revision combination includes Xen f3a7ca02400d which
> is ancient and doesn't build now on armhf, although it built before.
> (I think the difference is that the compiler has been updated by
> Debian.)
>
> Since there is no output from Xen, I think this must be a problem with
> the Xen image, not anything to do with Linux.
>
> The history for this test is here:
> http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/linux-linus
>
> In xen-unstable, there is what looks like a different failure:
> http://logs.test-lab.xenproject.org/osstest/logs/104681/test-armhf-armhf-xl/serial-arndale-westfield.log
>
> The machine in 104684 is cubietruck-metzinger which seems fine:
> http://logs.test-lab.xenproject.org/osstest/results/host/cubietruck-metzinger.html
I am probably not interpreting results correctly but 104684 looks like
failed to me:
http://logs.test-lab.xenproject.org/osstest/logs/104684/test-armhf-armhf-xl/info.html
And 104681's failure looks exactly like 104684.
>
> Here are the histories on the linux-linus and xen-unstable branches:
> http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/linux-linus
> http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/xen-unstable
>
> I think there may be a host-specific bug in ARM in xen-unstable ?
I am not aware of any but I wouldn't know anyway.
-boris
>
>> There is output from 3.16 kernels though.
> I think the 3.16 tests you are refrring to are running with a
> different version of Xen and on different hardware.
>
> Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [linux-linus test] 104684: regressions - FAIL
2017-01-26 19:01 ` Boris Ostrovsky
@ 2017-01-26 21:11 ` Julien Grall
2017-02-14 14:57 ` Julien Grall
0 siblings, 1 reply; 12+ messages in thread
From: Julien Grall @ 2017-01-26 21:11 UTC (permalink / raw)
To: Boris Ostrovsky, Ian Jackson, Stefano Stabellini; +Cc: xen-devel
Hi,
On 26/01/2017 19:01, Boris Ostrovsky wrote:
> On 01/26/2017 12:18 PM, Ian Jackson wrote:
>> Boris Ostrovsky writes ("Re: [Xen-devel] [linux-linus test] 104684: regressions - FAIL"):
>>> On 01/26/2017 08:23 AM, osstest service owner wrote:
>>>> flight 104684 linux-linus real [real]
>>>> http://logs.test-lab.xenproject.org/osstest/logs/104684/
>>>>
>>>> Regressions :-(
>>>>
>>>> Tests which did not succeed and are blocking,
>>>> including tests which could not be run:
>>>> test-armhf-armhf-xl 6 xen-boot fail REGR. vs. 59254
>> ...
>>> I don't see why ARM tests fail. But then I also don't see (in the serial
>>> log) the output of 4.10.0-rc5 being booted. There is U-Boot loading it
>>> but there it nothing coming to the console from it.
>> Yes.
>>
>> Unfortunately the osstest bisector is having some trouble with this
>> because the basis revision combination includes Xen f3a7ca02400d which
>> is ancient and doesn't build now on armhf, although it built before.
>> (I think the difference is that the compiler has been updated by
>> Debian.)
>>
>> Since there is no output from Xen, I think this must be a problem with
>> the Xen image, not anything to do with Linux.
>>
>> The history for this test is here:
>> http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/linux-linus
>>
>> In xen-unstable, there is what looks like a different failure:
>> http://logs.test-lab.xenproject.org/osstest/logs/104681/test-armhf-armhf-xl/serial-arndale-westfield.log
>>
>> The machine in 104684 is cubietruck-metzinger which seems fine:
>> http://logs.test-lab.xenproject.org/osstest/results/host/cubietruck-metzinger.html
>
> I am probably not interpreting results correctly but 104684 looks like
> failed to me:
>
> http://logs.test-lab.xenproject.org/osstest/logs/104684/test-armhf-armhf-xl/info.html
>
> And 104681's failure looks exactly like 104684.
I agree here. I think Ian got confused because the cubietruck is used to
build Xen.
>>
>> Here are the histories on the linux-linus and xen-unstable branches:
>> http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/linux-linus
>> http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/xen-unstable
>>
>> I think there may be a host-specific bug in ARM in xen-unstable ?
So the problem with linux-linus is the path in the DeviceTree for the
serial has been changed by commit 5d99cc5 "ARM: dts: exynos: Move
Exynos5250 and Exynos5420 nodes under soc". Before the path was
/serial@12C20000, now it is /soc/serial@12C20000.
From my understanding, osstest is testing 3.18 and onwards. Correct?
If so, all the device tree we care have the same alias name to the
serial node. I would use it to get avoid specific command line option
depending on the kernel.
Replacing on xen command line "dtuart=/serial@12C20000" by
"dtuart=serial0" will allow Xen to be able to use again the console.
Regarding xen-unstable, I spot in the log a lot of "asix 2-3.2.4:1.0
eth0: link down". So this looks like an ethernet issue. IIRC the network
dongle on the Arndale has always been unreliable. So I would not worry
too much here and wait the next flight.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [linux-linus test] 104684: regressions - FAIL
2017-01-26 21:11 ` Julien Grall
@ 2017-02-14 14:57 ` Julien Grall
2017-02-14 17:42 ` Wei Liu
0 siblings, 1 reply; 12+ messages in thread
From: Julien Grall @ 2017-02-14 14:57 UTC (permalink / raw)
To: Boris Ostrovsky, Ian Jackson, Stefano Stabellini; +Cc: nd, xen-devel, Wei Liu
Hi,
On 01/26/2017 09:11 PM, Julien Grall wrote:
> Hi,
>
> On 26/01/2017 19:01, Boris Ostrovsky wrote:
>> On 01/26/2017 12:18 PM, Ian Jackson wrote:
>>> Boris Ostrovsky writes ("Re: [Xen-devel] [linux-linus test] 104684:
>>> regressions - FAIL"):
>>>> On 01/26/2017 08:23 AM, osstest service owner wrote:
>>>>> flight 104684 linux-linus real [real]
>>>>> http://logs.test-lab.xenproject.org/osstest/logs/104684/
>>>>>
>>>>> Regressions :-(
>>>>>
>>>>> Tests which did not succeed and are blocking,
>>>>> including tests which could not be run:
>>>>> test-armhf-armhf-xl 6 xen-boot fail REGR. vs.
>>>>> 59254
>>> ...
>>>> I don't see why ARM tests fail. But then I also don't see (in the
>>>> serial
>>>> log) the output of 4.10.0-rc5 being booted. There is U-Boot loading it
>>>> but there it nothing coming to the console from it.
>>> Yes.
>>>
>>> Unfortunately the osstest bisector is having some trouble with this
>>> because the basis revision combination includes Xen f3a7ca02400d which
>>> is ancient and doesn't build now on armhf, although it built before.
>>> (I think the difference is that the compiler has been updated by
>>> Debian.)
>>>
>>> Since there is no output from Xen, I think this must be a problem with
>>> the Xen image, not anything to do with Linux.
>>>
>>> The history for this test is here:
>>>
>>> http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/linux-linus
>>>
>>>
>>> In xen-unstable, there is what looks like a different failure:
>>>
>>> http://logs.test-lab.xenproject.org/osstest/logs/104681/test-armhf-armhf-xl/serial-arndale-westfield.log
>>>
>>>
>>> The machine in 104684 is cubietruck-metzinger which seems fine:
>>>
>>> http://logs.test-lab.xenproject.org/osstest/results/host/cubietruck-metzinger.html
>>>
>>
>> I am probably not interpreting results correctly but 104684 looks like
>> failed to me:
>>
>> http://logs.test-lab.xenproject.org/osstest/logs/104684/test-armhf-armhf-xl/info.html
>>
>>
>> And 104681's failure looks exactly like 104684.
>
> I agree here. I think Ian got confused because the cubietruck is used to
> build Xen.
>
>>>
>>> Here are the histories on the linux-linus and xen-unstable branches:
>>>
>>> http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/linux-linus
>>>
>>>
>>> http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/xen-unstable
>>>
>>>
>>> I think there may be a host-specific bug in ARM in xen-unstable ?
>
> So the problem with linux-linus is the path in the DeviceTree for the
> serial has been changed by commit 5d99cc5 "ARM: dts: exynos: Move
> Exynos5250 and Exynos5420 nodes under soc". Before the path was
> /serial@12C20000, now it is /soc/serial@12C20000.
>
> From my understanding, osstest is testing 3.18 and onwards. Correct?
>
> If so, all the device tree we care have the same alias name to the
> serial node. I would use it to get avoid specific command line option
> depending on the kernel.
>
> Replacing on xen command line "dtuart=/serial@12C20000" by
> "dtuart=serial0" will allow Xen to be able to use again the console.
I have looked at osstest git [1] and was not able to find where the
configuration for the Arndale.
Can someone knowing Osstest look at it? This would unblock linux-linus
test on ARM.
>
> Regarding xen-unstable, I spot in the log a lot of "asix 2-3.2.4:1.0
> eth0: link down". So this looks like an ethernet issue. IIRC the network
> dongle on the Arndale has always been unreliable. So I would not worry
> too much here and wait the next flight.
Cheers,
[1] http://xenbits.xen.org/gitweb/?p=osstest.git;a=summary
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [linux-linus test] 104684: regressions - FAIL
2017-02-14 14:57 ` Julien Grall
@ 2017-02-14 17:42 ` Wei Liu
2017-02-16 14:54 ` Julien Grall
0 siblings, 1 reply; 12+ messages in thread
From: Wei Liu @ 2017-02-14 17:42 UTC (permalink / raw)
To: Julien Grall
Cc: Stefano Stabellini, Wei Liu, Ian Jackson, xen-devel, Boris Ostrovsky, nd
On Tue, Feb 14, 2017 at 02:57:42PM +0000, Julien Grall wrote:
> Hi,
>
> On 01/26/2017 09:11 PM, Julien Grall wrote:
> > Hi,
> >
> > On 26/01/2017 19:01, Boris Ostrovsky wrote:
> > > On 01/26/2017 12:18 PM, Ian Jackson wrote:
> > > > Boris Ostrovsky writes ("Re: [Xen-devel] [linux-linus test] 104684:
> > > > regressions - FAIL"):
> > > > > On 01/26/2017 08:23 AM, osstest service owner wrote:
> > > > > > flight 104684 linux-linus real [real]
> > > > > > http://logs.test-lab.xenproject.org/osstest/logs/104684/
> > > > > >
> > > > > > Regressions :-(
> > > > > >
> > > > > > Tests which did not succeed and are blocking,
> > > > > > including tests which could not be run:
> > > > > > test-armhf-armhf-xl 6 xen-boot fail REGR. vs.
> > > > > > 59254
> > > > ...
> > > > > I don't see why ARM tests fail. But then I also don't see (in the
> > > > > serial
> > > > > log) the output of 4.10.0-rc5 being booted. There is U-Boot loading it
> > > > > but there it nothing coming to the console from it.
> > > > Yes.
> > > >
> > > > Unfortunately the osstest bisector is having some trouble with this
> > > > because the basis revision combination includes Xen f3a7ca02400d which
> > > > is ancient and doesn't build now on armhf, although it built before.
> > > > (I think the difference is that the compiler has been updated by
> > > > Debian.)
> > > >
> > > > Since there is no output from Xen, I think this must be a problem with
> > > > the Xen image, not anything to do with Linux.
> > > >
> > > > The history for this test is here:
> > > >
> > > > http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/linux-linus
> > > >
> > > >
> > > > In xen-unstable, there is what looks like a different failure:
> > > >
> > > > http://logs.test-lab.xenproject.org/osstest/logs/104681/test-armhf-armhf-xl/serial-arndale-westfield.log
> > > >
> > > >
> > > > The machine in 104684 is cubietruck-metzinger which seems fine:
> > > >
> > > > http://logs.test-lab.xenproject.org/osstest/results/host/cubietruck-metzinger.html
> > > >
> > >
> > > I am probably not interpreting results correctly but 104684 looks like
> > > failed to me:
> > >
> > > http://logs.test-lab.xenproject.org/osstest/logs/104684/test-armhf-armhf-xl/info.html
> > >
> > >
> > > And 104681's failure looks exactly like 104684.
> >
> > I agree here. I think Ian got confused because the cubietruck is used to
> > build Xen.
> >
> > > >
> > > > Here are the histories on the linux-linus and xen-unstable branches:
> > > >
> > > > http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/linux-linus
> > > >
> > > >
> > > > http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/xen-unstable
> > > >
> > > >
> > > > I think there may be a host-specific bug in ARM in xen-unstable ?
> >
> > So the problem with linux-linus is the path in the DeviceTree for the
> > serial has been changed by commit 5d99cc5 "ARM: dts: exynos: Move
> > Exynos5250 and Exynos5420 nodes under soc". Before the path was
> > /serial@12C20000, now it is /soc/serial@12C20000.
> >
> > From my understanding, osstest is testing 3.18 and onwards. Correct?
> >
> > If so, all the device tree we care have the same alias name to the
> > serial node. I would use it to get avoid specific command line option
> > depending on the kernel.
> >
> > Replacing on xen command line "dtuart=/serial@12C20000" by
> > "dtuart=serial0" will allow Xen to be able to use again the console.
>
> I have looked at osstest git [1] and was not able to find where the
> configuration for the Arndale.
>
> Can someone knowing Osstest look at it? This would unblock linux-linus test
> on ARM.
>
(test-lab)liuw@osstest:~/testing.git$ ./mg-hosts showprops | grep DTUART | grep arndale
arndale-bluewater XenDTUARTPath /serial@12C20000
arndale-lakeside XenDTUARTPath /serial@12C20000
arndale-metrocentre XenDTUARTPath /serial@12C20000
arndale-westfield XenDTUARTPath /serial@12C20000
That's a property of this kind of hosts in osstest. It needs to be
updated by the administrator (Ian).
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [linux-linus test] 104684: regressions - FAIL
2017-02-14 17:42 ` Wei Liu
@ 2017-02-16 14:54 ` Julien Grall
2017-02-22 13:19 ` Ian Jackson
0 siblings, 1 reply; 12+ messages in thread
From: Julien Grall @ 2017-02-16 14:54 UTC (permalink / raw)
To: Wei Liu, Ian Jackson; +Cc: xen-devel, Boris Ostrovsky, nd, Stefano Stabellini
Hi,
On 14/02/17 17:42, Wei Liu wrote:
> (test-lab)liuw@osstest:~/testing.git$ ./mg-hosts showprops | grep DTUART | grep arndale
> arndale-bluewater XenDTUARTPath /serial@12C20000
> arndale-lakeside XenDTUARTPath /serial@12C20000
> arndale-metrocentre XenDTUARTPath /serial@12C20000
> arndale-westfield XenDTUARTPath /serial@12C20000
>
> That's a property of this kind of hosts in osstest. It needs to be
> updated by the administrator (Ian).
Ian, could you change the XenDTUARTPath property for the arndale from
"/serial@12C20000" to "serial0"?
This should hopefully fix boot of Linux upstream on the board and keep
compatibility with the previous version of Linux.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [linux-linus test] 104684: regressions - FAIL
2017-02-16 14:54 ` Julien Grall
@ 2017-02-22 13:19 ` Ian Jackson
2017-02-22 14:11 ` Julien Grall
0 siblings, 1 reply; 12+ messages in thread
From: Ian Jackson @ 2017-02-22 13:19 UTC (permalink / raw)
To: Julien Grall; +Cc: xen-devel, Boris Ostrovsky, nd, Wei Liu, Stefano Stabellini
Julien Grall writes ("Re: [Xen-devel] [linux-linus test] 104684: regressions - FAIL"):
> On 14/02/17 17:42, Wei Liu wrote:
> > (test-lab)liuw@osstest:~/testing.git$ ./mg-hosts showprops | grep DTUART | grep arndale
> > arndale-bluewater XenDTUARTPath /serial@12C20000
> > arndale-lakeside XenDTUARTPath /serial@12C20000
> > arndale-metrocentre XenDTUARTPath /serial@12C20000
> > arndale-westfield XenDTUARTPath /serial@12C20000
> >
> > That's a property of this kind of hosts in osstest. It needs to be
> > updated by the administrator (Ian).
>
> Ian, could you change the XenDTUARTPath property for the arndale from
> "/serial@12C20000" to "serial0"?
Done.
> This should hopefully fix boot of Linux upstream on the board and keep
> compatibility with the previous version of Linux.
Let's hope it doesn't break anything :-).
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [linux-linus test] 104684: regressions - FAIL
2017-02-22 13:19 ` Ian Jackson
@ 2017-02-22 14:11 ` Julien Grall
2017-02-24 10:40 ` Julien Grall
0 siblings, 1 reply; 12+ messages in thread
From: Julien Grall @ 2017-02-22 14:11 UTC (permalink / raw)
To: Ian Jackson; +Cc: xen-devel, Boris Ostrovsky, nd, Wei Liu, Stefano Stabellini
Hi Ian,
On 22/02/17 13:19, Ian Jackson wrote:
> Julien Grall writes ("Re: [Xen-devel] [linux-linus test] 104684: regressions - FAIL"):
>> On 14/02/17 17:42, Wei Liu wrote:
>>> (test-lab)liuw@osstest:~/testing.git$ ./mg-hosts showprops | grep DTUART | grep arndale
>>> arndale-bluewater XenDTUARTPath /serial@12C20000
>>> arndale-lakeside XenDTUARTPath /serial@12C20000
>>> arndale-metrocentre XenDTUARTPath /serial@12C20000
>>> arndale-westfield XenDTUARTPath /serial@12C20000
>>>
>>> That's a property of this kind of hosts in osstest. It needs to be
>>> updated by the administrator (Ian).
>>
>> Ian, could you change the XenDTUARTPath property for the arndale from
>> "/serial@12C20000" to "serial0"?
>
> Done.
>
>> This should hopefully fix boot of Linux upstream on the board and keep
>> compatibility with the previous version of Linux.
>
> Let's hope it doesn't break anything :-).
Thank you! I will watch next flights on osstest.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [linux-linus test] 104684: regressions - FAIL
2017-02-22 14:11 ` Julien Grall
@ 2017-02-24 10:40 ` Julien Grall
2017-02-24 11:14 ` Ian Jackson
0 siblings, 1 reply; 12+ messages in thread
From: Julien Grall @ 2017-02-24 10:40 UTC (permalink / raw)
To: Ian Jackson; +Cc: xen-devel, Boris Ostrovsky, nd, Wei Liu, Stefano Stabellini
Hi,
On 02/22/2017 02:11 PM, Julien Grall wrote:
> On 22/02/17 13:19, Ian Jackson wrote:
>> Julien Grall writes ("Re: [Xen-devel] [linux-linus test] 104684:
>> regressions - FAIL"):
>>> On 14/02/17 17:42, Wei Liu wrote:
>>>> (test-lab)liuw@osstest:~/testing.git$ ./mg-hosts showprops | grep
>>>> DTUART | grep arndale
>>>> arndale-bluewater XenDTUARTPath /serial@12C20000
>>>> arndale-lakeside XenDTUARTPath /serial@12C20000
>>>> arndale-metrocentre XenDTUARTPath /serial@12C20000
>>>> arndale-westfield XenDTUARTPath /serial@12C20000
>>>>
>>>> That's a property of this kind of hosts in osstest. It needs to be
>>>> updated by the administrator (Ian).
>>>
>>> Ian, could you change the XenDTUARTPath property for the arndale from
>>> "/serial@12C20000" to "serial0"?
>>
>> Done.
>>
>>> This should hopefully fix boot of Linux upstream on the board and keep
>>> compatibility with the previous version of Linux.
>>
>> Let's hope it doesn't break anything :-).
>
> Thank you! I will watch next flights on osstest.
Sounds like this trick didn't work ([1]) and we also lost xen log for
the other the flights (see xen-unstable-smoke [2]) thought they are
still passing.
Looking at the device-tree again, I thought the serial aliases were
existing in 3.16.7-ctk one but it seems that I looked at the wrong DT.
Sorry for that.
This means that the path to the serial is different between 3.16 and
4.10 and we have no common one. For now, I would revert it.
A per-flight override sounds quite ugly, so I am not sure how to solve
this in the future. Any opinions?
Regardless that I gave the wrong alias on the previous e-mail for 4.10.
Below the list of serial alias:
serial0 = "/soc/serial@12C00000";
serial1 = "/soc/serial@12C10000";
serial2 = "/soc/serial@12C20000";
serial3 = "/soc/serial@12C30000";
So for the alias should be serial2.
Cheers,
[1] http://logs.test-lab.xenproject.org/osstest/logs/106009/test-armhf-
armhf-xl/info.html
[2]
http://logs.test-lab.xenproject.org/osstest/logs/106021/test-armhf-armhf-xl/info.html
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [linux-linus test] 104684: regressions - FAIL
2017-02-24 10:40 ` Julien Grall
@ 2017-02-24 11:14 ` Ian Jackson
0 siblings, 0 replies; 12+ messages in thread
From: Ian Jackson @ 2017-02-24 11:14 UTC (permalink / raw)
To: Julien Grall; +Cc: xen-devel, Boris Ostrovsky, nd, Wei Liu, Stefano Stabellini
Julien Grall writes ("Re: [Xen-devel] [linux-linus test] 104684: regressions - FAIL"):
> This means that the path to the serial is different between 3.16 and
> 4.10 and we have no common one. For now, I would revert it.
Done.
> A per-flight override sounds quite ugly, so I am not sure how to solve
> this in the future. Any opinions?
I'll look at the code and think of something.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2017-02-24 11:14 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-01-26 13:23 [linux-linus test] 104684: regressions - FAIL osstest service owner
2017-01-26 15:03 ` Boris Ostrovsky
2017-01-26 17:18 ` Ian Jackson
2017-01-26 19:01 ` Boris Ostrovsky
2017-01-26 21:11 ` Julien Grall
2017-02-14 14:57 ` Julien Grall
2017-02-14 17:42 ` Wei Liu
2017-02-16 14:54 ` Julien Grall
2017-02-22 13:19 ` Ian Jackson
2017-02-22 14:11 ` Julien Grall
2017-02-24 10:40 ` Julien Grall
2017-02-24 11:14 ` Ian Jackson
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.