[xen-unstable-smoke test] 85178: regressions - FAIL

[xen-unstable-smoke test] 85178: regressions - FAIL

[osstest service owner]

flight 85178 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/85178/

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. 85080

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-libvirt     12 migrate-support-check        fail   never pass

version targeted for testing:
 xen                  03720ea541382a3ca80eaaec2aa11932b03aacaf
baseline version:
 xen                  7ba900efe5f526c941b1ca055e5347947bb7eb4b

Last test of basis    85080  2016-03-02 16:00:54 Z    0 days
Testing same since    85178  2016-03-03 09:20:13 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@citrix.com>
  Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
  Boris Ostrovsky <boris.ostrovsky@oracle.com>
  Dario Faggioli <dario.faggioli@citrix.com>
  Hanjun Guo <hanjun.guo@linaro.org>
  Jan Beulich <jbeulich@suse.com>
  Juergen Gross <jgross@suse.com>
  Naresh Bhat <naresh.bhat@linaro.org>
  Parth Dixit <parth.dixit@linaro.org>
  Shannon Zhao <shannon.zhao@linaro.org>
  Shannon Zhao <zhaoshenglong@huawei.com>
  Stefano Stabellini <stefano.stabellini@eu.citrix.com>
  Tomasz Nowicki <tomasz.nowicki@linaro.org>

jobs:
 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-amd64-libvirt                                          pass    
 test-armhf-armhf-xl                                          fail    
 test-amd64-amd64-xl-qemuu-debianhvm-i386                     pass    
 test-amd64-amd64-libvirt                                     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 323 lines long.)

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [xen-unstable-smoke test] 85178: regressions - FAIL

[Jan Beulich]

>>> On 03.03.16 at 12:18, <osstest-admin@xenproject.org> wrote:
> flight 85178 xen-unstable-smoke real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/85178/ 
> 
> 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. 85080

Unless this is a spurious failure, would one of you please look into
this? The complete lack of Xen messages in the log after the most
recent host install may suggest that a boot attempt failed very
early.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [xen-unstable-smoke test] 85178: regressions - FAIL

[Shannon Zhao]

On 2016/3/3 20:53, Jan Beulich wrote:
>>>> On 03.03.16 at 12:18, <osstest-admin@xenproject.org> wrote:
>> > flight 85178 xen-unstable-smoke real [real]
>> > http://logs.test-lab.xenproject.org/osstest/logs/85178/ 
>> > 
>> > 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. 85080
> Unless this is a spurious failure, would one of you please look into
> this? The complete lack of Xen messages in the log after the most
> recent host install may suggest that a boot attempt failed very
> early.
Ah, sorry for this. I'm looking at this and have reproduced this.

It fails with below log:

(XEN) Xen call trace:
(XEN)    [<0000000000204f08>] dt_irq_translate+0x14/0x58 (PC)
(XEN)    [<0000000000205244>] dt_device_get_irq+0x2c/0x38 (LR)
(XEN)    [<0000000000205244>] dt_device_get_irq+0x2c/0x38
(XEN)    [<000000000024ab54>] platform_get_irq+0x14/0x44
(XEN)    [<000000000028f088>] preinit_xen_time+0x8c/0x120
(XEN)    [<000000000028ddc0>] start_xen+0x554/0xc8c
(XEN)    [<000000000020061c>] arm64/head.o#paging+0x84/0xbc
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Assertion 'dt_irq_xlate != NULL' failed at device_tree.c:1452

I'm fixing this.

BTW, if I fix this problem, do I need to update the original patch or
send a new one?

Thanks,
-- 
Shannon


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [xen-unstable-smoke test] 85178: regressions - FAIL

[Andrew Cooper]

On 03/03/16 13:38, Shannon Zhao wrote:
>
> On 2016/3/3 20:53, Jan Beulich wrote:
>>>>> On 03.03.16 at 12:18, <osstest-admin@xenproject.org> wrote:
>>>> flight 85178 xen-unstable-smoke real [real]
>>>> http://logs.test-lab.xenproject.org/osstest/logs/85178/ 
>>>>
>>>> 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. 85080
>> Unless this is a spurious failure, would one of you please look into
>> this? The complete lack of Xen messages in the log after the most
>> recent host install may suggest that a boot attempt failed very
>> early.
> Ah, sorry for this. I'm looking at this and have reproduced this.
>
> It fails with below log:
>
> (XEN) Xen call trace:
> (XEN)    [<0000000000204f08>] dt_irq_translate+0x14/0x58 (PC)
> (XEN)    [<0000000000205244>] dt_device_get_irq+0x2c/0x38 (LR)
> (XEN)    [<0000000000205244>] dt_device_get_irq+0x2c/0x38
> (XEN)    [<000000000024ab54>] platform_get_irq+0x14/0x44
> (XEN)    [<000000000028f088>] preinit_xen_time+0x8c/0x120
> (XEN)    [<000000000028ddc0>] start_xen+0x554/0xc8c
> (XEN)    [<000000000020061c>] arm64/head.o#paging+0x84/0xbc
> (XEN)
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Assertion 'dt_irq_xlate != NULL' failed at device_tree.c:1452
>
> I'm fixing this.
>
> BTW, if I fix this problem, do I need to update the original patch or
> send a new one?

Smoke tests are run on top of what is already committed into staging. 
Please submit a new patch.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [xen-unstable-smoke test] 85178: regressions - FAIL

[Shannon Zhao]

On 2016/3/3 21:54, Andrew Cooper wrote:
> On 03/03/16 13:38, Shannon Zhao wrote:
>> >
>> > On 2016/3/3 20:53, Jan Beulich wrote:
>>>>>> >>>>> On 03.03.16 at 12:18, <osstest-admin@xenproject.org> wrote:
>>>>> >>>> flight 85178 xen-unstable-smoke real [real]
>>>>> >>>> http://logs.test-lab.xenproject.org/osstest/logs/85178/ 
>>>>> >>>>
>>>>> >>>> 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. 85080
>>> >> Unless this is a spurious failure, would one of you please look into
>>> >> this? The complete lack of Xen messages in the log after the most
>>> >> recent host install may suggest that a boot attempt failed very
>>> >> early.
>> > Ah, sorry for this. I'm looking at this and have reproduced this.
>> >
>> > It fails with below log:
>> >
>> > (XEN) Xen call trace:
>> > (XEN)    [<0000000000204f08>] dt_irq_translate+0x14/0x58 (PC)
>> > (XEN)    [<0000000000205244>] dt_device_get_irq+0x2c/0x38 (LR)
>> > (XEN)    [<0000000000205244>] dt_device_get_irq+0x2c/0x38
>> > (XEN)    [<000000000024ab54>] platform_get_irq+0x14/0x44
>> > (XEN)    [<000000000028f088>] preinit_xen_time+0x8c/0x120
>> > (XEN)    [<000000000028ddc0>] start_xen+0x554/0xc8c
>> > (XEN)    [<000000000020061c>] arm64/head.o#paging+0x84/0xbc
>> > (XEN)
>> > (XEN)
>> > (XEN) ****************************************
>> > (XEN) Panic on CPU 0:
>> > (XEN) Assertion 'dt_irq_xlate != NULL' failed at device_tree.c:1452
>> >
>> > I'm fixing this.
>> >
>> > BTW, if I fix this problem, do I need to update the original patch or
>> > send a new one?
> Smoke tests are run on top of what is already committed into staging. 
> Please submit a new patch.
Ok, thanks a lot.

-- 
Shannon


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [xen-unstable-smoke test] 85178: regressions - FAIL

[Shannon Zhao]

[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]



On 2016/3/3 21:38, Shannon Zhao wrote:
> 
> 
> On 2016/3/3 20:53, Jan Beulich wrote:
>>>>> On 03.03.16 at 12:18, <osstest-admin@xenproject.org> wrote:
>>>> flight 85178 xen-unstable-smoke real [real]
>>>> http://logs.test-lab.xenproject.org/osstest/logs/85178/ 
>>>>
>>>> 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. 85080
>> Unless this is a spurious failure, would one of you please look into
>> this? The complete lack of Xen messages in the log after the most
>> recent host install may suggest that a boot attempt failed very
>> early.
> Ah, sorry for this. I'm looking at this and have reproduced this.
> 
> It fails with below log:
> 
> (XEN) Xen call trace:
> (XEN)    [<0000000000204f08>] dt_irq_translate+0x14/0x58 (PC)
> (XEN)    [<0000000000205244>] dt_device_get_irq+0x2c/0x38 (LR)
> (XEN)    [<0000000000205244>] dt_device_get_irq+0x2c/0x38
> (XEN)    [<000000000024ab54>] platform_get_irq+0x14/0x44
> (XEN)    [<000000000028f088>] preinit_xen_time+0x8c/0x120
> (XEN)    [<000000000028ddc0>] start_xen+0x554/0xc8c
> (XEN)    [<000000000020061c>] arm64/head.o#paging+0x84/0xbc
> (XEN)
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Assertion 'dt_irq_xlate != NULL' failed at device_tree.c:1452
> 
With the attached patch, this problem disappeared.
Do I need to update the original patch or send a new one?

Thanks,
-- 
Shannon

[-- Attachment #2: fix-timer.patch --]
[-- Type: text/x-patch, Size: 1549 bytes --]

diff --git a/xen/arch/arm/time.c b/xen/arch/arm/time.c
index 5f8f974..66a4520 100644
--- a/xen/arch/arm/time.c
+++ b/xen/arch/arm/time.c
@@ -119,7 +119,6 @@ static void __init preinit_dt_xen_time(void)
     };
     int res;
     u32 rate;
-    unsigned int i;

     timer = dt_find_matching_node(NULL, timer_ids);
     if ( !timer )
@@ -133,16 +132,6 @@ static void __init preinit_dt_xen_time(void)
         cpu_khz = rate / 1000;
         timer_dt_clock_frequency = rate;
     }
-
-    /* Retrieve all IRQs for the timer */
-    for ( i = TIMER_PHYS_SECURE_PPI; i < MAX_TIMER_PPI; i++ )
-    {
-        res = platform_get_irq(timer, i);
-
-        if ( res < 0 )
-            panic("Timer: Unable to retrieve IRQ %u from the device tree", i);
-        timer_irq[i] = res;
-    }
 }

 void __init preinit_xen_time(void)
@@ -168,6 +157,22 @@ void __init preinit_xen_time(void)
 /* Set up the timer on the boot CPU (late init function) */
 int __init init_xen_time(void)
 {
+    int res;
+    unsigned int i;
+
+    if ( acpi_disabled )
+    {
+        /* Retrieve all IRQs for the timer */
+        for ( i = TIMER_PHYS_SECURE_PPI; i < MAX_TIMER_PPI; i++ )
+        {
+            res = platform_get_irq(timer, i);
+
+            if ( res < 0 )
+                panic("Timer: Unable to retrieve IRQ %u from the device tree", i);
+            timer_irq[i] = res;
+        }
+    }
+
     /* Check that this CPU supports the Generic Timer interface */
     if ( !cpu_has_gentimer )
         panic("CPU does not support the Generic Timer v1 interface");

[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel