All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Arkver <ian.arkver.dev@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Need arm64/qemu help
Date: Sat, 3 Mar 2018 11:13:19 +0000	[thread overview]
Message-ID: <412d4c49-8956-38aa-a1ea-417541585b2d@gmail.com> (raw)
In-Reply-To: <91616f15-f805-22db-6073-8698f49bab86@gmail.com>

On 03/03/18 10:51, Ian Arkver wrote:
> On 03/03/18 09:00, Richard Purdie wrote:
>> Hi,
>>
>> I need some help with a problem we keep seeing:
>>
>> https://autobuilder.yocto.io/builders/nightly-arm64/builds/798
>>
>> Basically, now and again, for reasons we don't understand, all the
>> sanity tests fail for qemuarm64.
>>
>> I've poked at this a bit and if I go in onto the failed machine and run
>> this again, they work, using the same image, kernel and qemu binaries.
>> We've seen this on two different autobuilder infrastructure on varying
>> host OSs. They always seem to fail all three at once.
>>
>> Whilst this was a mut build, I saw this repeat three builds in a row on
>> the new autobuilder we're setting up with master.
>>
>> The kernels always seem to hang somewhere around the:
>>
>> | [    0.766079] raid6: int64x1  xor()   302 MB/s
>> | [    0.844597] raid6: int64x2  gen()   675 MB/s
> 
> I believe this is related to btrfs and comes from having btrfs compiled 
> in to the kernel. You could maybe side-step the problem (and hence leave 
> it lurking) by changing btrfs to a module.

Actually, this comes from a library (lib/raid6), and in 4.14.y's arm64 
defconfig BTRFS is already a module, so please disregard my hack suggestion.

> Regards,
> Ian
> 
>> raid timing measurements.
>>
>> In the past we've dived in and handled these kinds of things but I've
>> run out of people to lean on and I need help from the wider community.
>>
>> Can anyone help look into and fix this?
>>
>> This is serious as if nobody cares, I'll have to simply stop boot
>> testing qemuarm64.
>>
>> Not sure if there is an open bug yet either :/.
>>
>> Cheers,
>>
>> Richard
>>


  parent reply	other threads:[~2018-03-03 11:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-03  9:00 Need arm64/qemu help Richard Purdie
2018-03-03 10:51 ` Ian Arkver
2018-03-03 11:06   ` Richard Purdie
2018-03-03 11:13   ` Ian Arkver [this message]
2018-03-11  0:11     ` Victor Kamensky
2018-03-11 14:05       ` Richard Purdie
     [not found]       ` <CAFEAcA-d6-_tVRWKbZpVsQtece4fjuUqF+o+-m-AG4jPUHPY4g@mail.gmail.com>
2018-03-12  2:25         ` Victor Kamensky
2018-03-17 22:51           ` Victor Kamensky
     [not found]             ` <87a7v4kj5g.fsf@linaro.org>
2018-03-19  6:26               ` Victor Kamensky
     [not found]                 ` <87605sjvk4.fsf@linaro.org>
2018-03-19 17:46                   ` Victor Kamensky
     [not found]                     ` <CAFEAcA8p9uO_7MXzkqyAnc-gifTHhmUgyRyE8X7hZnW=sbgQOg@mail.gmail.com>
2018-03-19 23:24                       ` Victor Kamensky
     [not found]                         ` <e15e3ca1-ee9e-1efa-2247-2789aac05091@linaro.org>
2018-03-20  2:22                           ` Victor Kamensky
     [not found]                       ` <874llbk1xc.fsf@linaro.org>
2018-03-20  2:14                         ` Victor Kamensky
2018-03-03 18:21 ` Richard Purdie
2018-03-05 22:10   ` Ian Arkver

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=412d4c49-8956-38aa-a1ea-417541585b2d@gmail.com \
    --to=ian.arkver.dev@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.