From: Julien Grall <julien.grall@arm.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: Ian Jackson <ian.jackson@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xenproject.org
Subject: Re: [qemu-upstream-4.11-testing test] 136184: regressions - FAIL
Date: Tue, 21 May 2019 17:52:12 +0100 [thread overview]
Message-ID: <9df7707d-8aa4-2abf-d7c3-0fd101ec3e68@arm.com> (raw)
In-Reply-To: <d2ac0071-149e-0c03-016c-d9ad2a423f5e@arm.com>
Hi,
Answering to myself.
On 5/17/19 8:00 PM, Julien Grall wrote:
> Hi,
>
> On 5/17/19 6:23 PM, Anthony PERARD wrote:
>> On Thu, May 16, 2019 at 10:38:54PM +0100, Julien Grall wrote:
>>> Hi Anthony,
>>>
>>> Thank you for CCing me.
>>>
>>> On 5/16/19 11:37 AM, Anthony PERARD wrote:
>>>> On Wed, May 15, 2019 at 07:48:17PM +0000, osstest service owner wrote:
>>>>> flight 136184 qemu-upstream-4.11-testing real [real]
>>>>> http://logs.test-lab.xenproject.org/osstest/logs/136184/
>>>>>
>>>>> Regressions :-(
>>>>>
>>>>> Tests which did not succeed and are blocking,
>>>>> including tests which could not be run:
>>>>> build-arm64-pvops <job status>
>>>>> broken in 134594
>>>>> build-arm64 <job status>
>>>>> broken in 134594
>>>>> build-arm64-xsm <job status>
>>>>> broken in 134594
>>>>> build-arm64-xsm 4 host-install(4) broken in 134594
>>>>> REGR. vs. 125575
>>>>> build-arm64-pvops 4 host-install(4) broken in 134594
>>>>> REGR. vs. 125575
>>>>> build-arm64 4 host-install(4) broken in 134594
>>>>> REGR. vs. 125575
>>>>> test-arm64-arm64-libvirt-xsm 7 xen-boot fail
>>>>> REGR. vs. 125575
>>>>> test-arm64-arm64-xl 7 xen-boot fail
>>>>> REGR. vs. 125575
>>>>> test-arm64-arm64-xl-xsm 7 xen-boot fail
>>>>> REGR. vs. 125575
>>>>> test-arm64-arm64-xl-credit2 7 xen-boot fail
>>>>> REGR. vs. 125575
>>>>>
>>>>
>>>> Ian, Julien,
>>>>
>>>> I can't figure out why Xen consistently fails to boot on rochester* in
>>>> the qemu-upstream-4.11-testing flights. The xen-4.11-testing seems to
>>>> pass.
>>>>
>>>> At boot, the boot loader seems to load blobs, but when it's time to Xen
>>>> to shine, there are no output from Xen on the serial.
>>>
>>> The serial console is initializing fairly late in the process. Any
>>> useful
>>> message (such as memory setup or even part of the interrupts) will be
>>> hide
>>> out. For getting them, you need earlyprintk. Unfortunately they can't be
>>> configured at runtime today :(.
>>
>> I think I managed to run the job with earlyprintk on rochester, but
>> Xen have booted:
>> http://logs.test-lab.xenproject.org/osstest/logs/136451/
>
> Yes this is with earlyprintk. That's going to be fun to reproduce if
> earlyprintk modifies the behavior.
>
> I think we can interpret as earlyprintk add enough latency to make
> everything working.
>
> There are two possible issues I can think of:
> 1) The boot code does not follow the Arm Arm, so it may be possible
> the board is doing something different compare to the other regarding
> the memory. IIRC, this is the first hardware we have with core not
> directly designed by Arm.
> 2) We are missing some errata in Xen. Linux contains 6 errata for
> that platform. Looking at them, I don't think they matter for boot time.
>
> 1) is currently been looked at (see MM-PART* patches on the ML). 2)
> should probably be addressed at some point, but I may not be able to
> send them as Arm employee (we tend to avoid sending patch showing
> brokenness in partner silicon).
Ian kindly started a couple of jobs over the week-end to confirm whether
it can be reproduced on laxton* (Seattle board).
The same error cannot be reproduced on laxton*. Looking at the test
history, it looks like qemu-upstream-4.12-testing flight has run
successfully a few times on rochester*. So we may have fixed the error
in Xen 4.12.
Potential candidates would be:
- 00c96d7742 "xen/arm: mm: Set-up page permission for Xen mappings
earlier on"
- f60658c6ae "xen/arm: Stop relocating Xen"
Ian, is it something the bisector could automatically look at?
If not, I will need to find some time and borrow the board to bisect the
issues.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Julien Grall <julien.grall@arm.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: Ian Jackson <ian.jackson@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] [qemu-upstream-4.11-testing test] 136184: regressions - FAIL
Date: Tue, 21 May 2019 17:52:12 +0100 [thread overview]
Message-ID: <9df7707d-8aa4-2abf-d7c3-0fd101ec3e68@arm.com> (raw)
Message-ID: <20190521165212.faxNaH65REPpADqXkduLbeNMrKYzdqN7gynZ1jsp-6g@z> (raw)
In-Reply-To: <d2ac0071-149e-0c03-016c-d9ad2a423f5e@arm.com>
Hi,
Answering to myself.
On 5/17/19 8:00 PM, Julien Grall wrote:
> Hi,
>
> On 5/17/19 6:23 PM, Anthony PERARD wrote:
>> On Thu, May 16, 2019 at 10:38:54PM +0100, Julien Grall wrote:
>>> Hi Anthony,
>>>
>>> Thank you for CCing me.
>>>
>>> On 5/16/19 11:37 AM, Anthony PERARD wrote:
>>>> On Wed, May 15, 2019 at 07:48:17PM +0000, osstest service owner wrote:
>>>>> flight 136184 qemu-upstream-4.11-testing real [real]
>>>>> http://logs.test-lab.xenproject.org/osstest/logs/136184/
>>>>>
>>>>> Regressions :-(
>>>>>
>>>>> Tests which did not succeed and are blocking,
>>>>> including tests which could not be run:
>>>>> build-arm64-pvops <job status>
>>>>> broken in 134594
>>>>> build-arm64 <job status>
>>>>> broken in 134594
>>>>> build-arm64-xsm <job status>
>>>>> broken in 134594
>>>>> build-arm64-xsm 4 host-install(4) broken in 134594
>>>>> REGR. vs. 125575
>>>>> build-arm64-pvops 4 host-install(4) broken in 134594
>>>>> REGR. vs. 125575
>>>>> build-arm64 4 host-install(4) broken in 134594
>>>>> REGR. vs. 125575
>>>>> test-arm64-arm64-libvirt-xsm 7 xen-boot fail
>>>>> REGR. vs. 125575
>>>>> test-arm64-arm64-xl 7 xen-boot fail
>>>>> REGR. vs. 125575
>>>>> test-arm64-arm64-xl-xsm 7 xen-boot fail
>>>>> REGR. vs. 125575
>>>>> test-arm64-arm64-xl-credit2 7 xen-boot fail
>>>>> REGR. vs. 125575
>>>>>
>>>>
>>>> Ian, Julien,
>>>>
>>>> I can't figure out why Xen consistently fails to boot on rochester* in
>>>> the qemu-upstream-4.11-testing flights. The xen-4.11-testing seems to
>>>> pass.
>>>>
>>>> At boot, the boot loader seems to load blobs, but when it's time to Xen
>>>> to shine, there are no output from Xen on the serial.
>>>
>>> The serial console is initializing fairly late in the process. Any
>>> useful
>>> message (such as memory setup or even part of the interrupts) will be
>>> hide
>>> out. For getting them, you need earlyprintk. Unfortunately they can't be
>>> configured at runtime today :(.
>>
>> I think I managed to run the job with earlyprintk on rochester, but
>> Xen have booted:
>> http://logs.test-lab.xenproject.org/osstest/logs/136451/
>
> Yes this is with earlyprintk. That's going to be fun to reproduce if
> earlyprintk modifies the behavior.
>
> I think we can interpret as earlyprintk add enough latency to make
> everything working.
>
> There are two possible issues I can think of:
> 1) The boot code does not follow the Arm Arm, so it may be possible
> the board is doing something different compare to the other regarding
> the memory. IIRC, this is the first hardware we have with core not
> directly designed by Arm.
> 2) We are missing some errata in Xen. Linux contains 6 errata for
> that platform. Looking at them, I don't think they matter for boot time.
>
> 1) is currently been looked at (see MM-PART* patches on the ML). 2)
> should probably be addressed at some point, but I may not be able to
> send them as Arm employee (we tend to avoid sending patch showing
> brokenness in partner silicon).
Ian kindly started a couple of jobs over the week-end to confirm whether
it can be reproduced on laxton* (Seattle board).
The same error cannot be reproduced on laxton*. Looking at the test
history, it looks like qemu-upstream-4.12-testing flight has run
successfully a few times on rochester*. So we may have fixed the error
in Xen 4.12.
Potential candidates would be:
- 00c96d7742 "xen/arm: mm: Set-up page permission for Xen mappings
earlier on"
- f60658c6ae "xen/arm: Stop relocating Xen"
Ian, is it something the bisector could automatically look at?
If not, I will need to find some time and borrow the board to bisect the
issues.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-05-21 16:52 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 19:48 [qemu-upstream-4.11-testing test] 136184: regressions - FAIL osstest service owner
2019-05-15 19:48 ` [Xen-devel] " osstest service owner
2019-05-16 10:37 ` Anthony PERARD
2019-05-16 10:37 ` [Xen-devel] " Anthony PERARD
2019-05-16 21:38 ` Julien Grall
2019-05-16 21:38 ` [Xen-devel] " Julien Grall
2019-05-17 15:53 ` Ian Jackson
2019-05-17 15:53 ` [Xen-devel] " Ian Jackson
2019-05-17 17:23 ` Anthony PERARD
2019-05-17 17:23 ` [Xen-devel] " Anthony PERARD
2019-05-17 19:00 ` Julien Grall
2019-05-17 19:00 ` [Xen-devel] " Julien Grall
2019-05-21 16:52 ` Julien Grall [this message]
2019-05-21 16:52 ` Julien Grall
2019-06-03 17:15 ` Anthony PERARD
2019-06-03 17:15 ` [Xen-devel] " Anthony PERARD
2019-06-04 7:06 ` Jan Beulich
2019-06-04 7:06 ` [Xen-devel] " Jan Beulich
2019-06-04 9:01 ` Julien Grall
2019-06-04 9:01 ` [Xen-devel] " Julien Grall
2019-06-04 9:17 ` Jan Beulich
2019-06-04 9:17 ` [Xen-devel] " Jan Beulich
2019-06-04 9:57 ` Julien Grall
2019-06-04 9:57 ` [Xen-devel] " Julien Grall
2019-06-04 10:02 ` Jan Beulich
2019-06-04 10:02 ` [Xen-devel] " Jan Beulich
2019-06-04 17:09 ` Stefano Stabellini
2019-06-04 17:22 ` Julien Grall
2019-06-04 17:39 ` Stefano Stabellini
2019-06-04 17:52 ` Ian Jackson
2019-06-04 18:03 ` Stefano Stabellini
2019-06-04 18:27 ` Ian Jackson
2019-06-04 18:53 ` Stefano Stabellini
2019-06-04 20:50 ` Julien Grall
2019-06-04 23:11 ` Stefano Stabellini
2019-06-05 10:59 ` Julien Grall
2019-06-05 20:29 ` Stefano Stabellini
2019-06-05 21:38 ` Julien Grall
2019-06-06 8:42 ` Jan Beulich
2019-06-06 8:47 ` Julien Grall
2019-06-06 22:21 ` Stefano Stabellini
2019-06-07 9:33 ` Julien Grall
2019-06-05 10:19 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9df7707d-8aa4-2abf-d7c3-0fd101ec3e68@arm.com \
--to=julien.grall@arm.com \
--cc=anthony.perard@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=osstest-admin@xenproject.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.