linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Aristeu Rozanski <aris@redhat.com>
To: Robin Murphy <robin.murphyatarm.com@redhat.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisiatarm.com@redhat.com>,
	Catalin Marinas <catalin.marinasatarm.com@redhat.com>,
	Will Deacon <willatkernel.org@redhat.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: ??? FAIL: Test report for kernel 5.13.0-rc7 (arm-next, 8ab9b1a9)
Date: Fri, 4 Mar 2022 14:31:07 -0500	[thread overview]
Message-ID: <20220304193107.5ljii5h4kmkwpl3f@redhat.com> (raw)
In-Reply-To: <7c058806-6967-5df9-2a33-b8f9be0d2a5f@arm.com>

Hi Robin,

(Old thread, so reference to it: https://lists.infradead.org/pipermail/linux-arm-kernel/2021-June/668228.html)
(Also, please keep me on Cc since I'm not subscribed to linux-arm)

On Tue, Jun 29, 2021 at 06:27:57PM +0100, Robin Murphy wrote:
> Ah, from that I can only assume that this must be stress-ng's --sysfs 
> test reading things at random, so not only would it have to be on a 
> machine whose firmware presents the right thing in the right way but the 
> random test conditions would also have to line up to poke it the "right" 
> (wrong) way too.
> 
> As a temporary workaround for the CI flakes, might it be possible to 
> configure stress-ng to stay away from just these ACPI "data" files?

I started looking at this issue and managed to reproduce the issue
instantly with

	dd if=/sys/firmware/acpi/tables/data/BERT of=/dev/null bs=7

I've attempted a few ways of fixing it based on the comments on this
thread but wasn't successful so far (my knowledge is pretty limited in
this area too, so not a big surprise). How can I be of assistance to debug/test
patches for this issue?

-- 
Aristeu


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-03-04 19:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24 19:46 ❌ FAIL: Test report for kernel 5.13.0-rc7 (arm-next, 8ab9b1a9) CKI Project
2021-06-25  8:39 ` Will Deacon
     [not found]   ` <CA+tGwn=rP_hAMLLtoy_s90ZzBjfMggu7T2Qj8HyFfGh1BGUoRA@mail.gmail.com>
2021-06-25 11:02     ` Robin Murphy
2021-06-25 11:09       ` Catalin Marinas
2021-06-25 11:15         ` Robin Murphy
2021-06-29 11:48           ` Robin Murphy
2021-06-29 14:44             ` Lorenzo Pieralisi
2021-06-29 15:14               ` Robin Murphy
2021-06-29 16:35                 ` Catalin Marinas
2021-06-30 10:37                   ` Lorenzo Pieralisi
2021-06-30 11:17                     ` Robin Murphy
     [not found]                       ` <CAMj1kXH=Q+WNgGsbApiq94z5OpJOnNLcFk_dyoVm_-VQunv3MA@mail.gmail.com>
2021-06-30 15:49                         ` Lorenzo Pieralisi
     [not found]                           ` <CAMj1kXHgPmJV6sPO8OWYj84Ncts00fzn+gJ=+xzcXYhCxvm-aA@mail.gmail.com>
2021-07-05 16:17                             ` Lorenzo Pieralisi
     [not found]                               ` <CAMj1kXHQKKnzJUEXMMzt3D1NUodeik8FZN1OTpD9zf8ZWrp6Lw@mail.gmail.com>
2021-07-16 16:26                                 ` Lorenzo Pieralisi
     [not found]                                   ` <CA+tGwnmu-uL1v3vWO1yzH1i1ru6+EbVdEKnGOifoS6fLuTTGoQ@mail.gmail.com>
2021-07-22 13:51                                     ` Robin Murphy
     [not found]                 ` <CA+tGwn=r=BZK08CHBUkk1m5NB-W7GqC9Cwj6Qj+_MbYzqdEjDg@mail.gmail.com>
2021-06-29 17:27                   ` Robin Murphy
2022-03-04 19:31                     ` Aristeu Rozanski [this message]
2022-03-04 19:39                     ` ??? " Aristeu Rozanski
2022-03-04 20:00                       ` Robin Murphy
2022-03-07 10:19                       ` Lorenzo Pieralisi
2022-03-07 19:01                         ` Aristeu Rozanski

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=20220304193107.5ljii5h4kmkwpl3f@redhat.com \
    --to=aris@redhat.com \
    --cc=catalin.marinasatarm.com@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lorenzo.pieralisiatarm.com@redhat.com \
    --cc=robin.murphyatarm.com@redhat.com \
    --cc=willatkernel.org@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).