From: "Guillaume Tucker" <guillaume.tucker@collabora.com>
To: kernelci@groups.io, robh+dt@kernel.org, Ard Biesheuvel <ardb@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
"kernelci-results@groups.io" <kernelci-results@groups.io>
Subject: Re: ardb/for-kernelci bisection: baseline.dmesg.alert on da850-lcdk
Date: Wed, 26 Jan 2022 11:28:14 +0000 [thread overview]
Message-ID: <921f80f5-a95d-ee12-2266-16503edea614@collabora.com> (raw)
In-Reply-To: <CAL_JsqJJEaer6Z5Vhu3G20GHgqq9mEn+Tjok_qU_2ax0iA5ETg@mail.gmail.com>
On 25/01/2022 22:27, Rob Herring wrote:
> On Tue, Jan 25, 2022 at 4:21 PM Ard Biesheuvel <ardb@kernel.org> wrote:
>>
>> (adding Arnd and Rob)
>>
>> On Tue, 25 Jan 2022 at 22:32, Guillaume Tucker
>> <guillaume.tucker@collabora.com> wrote:
>>>
>>> Hello Ard,
>>>
>>> Please see the bisection report below. I had a look around the
>>> results and git history, this is about an "alert" message which
>>> is present in mainline and linux-next but one day it disappeared
>>> on your for-kernelci branch and then it was introduced again.
>>> See the regression history here:
>>>
>>> https://linux.kernelci.org/test/case/id/61ef9d00e75a9ac935abbd26/
>>>
>>> The revision when it last passed was last Friday, and your branch
>>> has been force-pushed since then so I don't have access to the
>>> git history for it any more. The bisection found a revert commit
>>> that apparently re-introduced the issue, but it's all a bit
>>> confusing as this commit is not there any more but the alert
>>> message still is.
>>>
>>> The error can be found here in the log:
>>>
>>> https://storage.kernelci.org/ardb/for-kernelci/arm-irq-and-vmap-stacks-for-rmk-11-g12fa502217d5/arm/davinci_all_defconfig/gcc-10/lab-baylibre/baseline-da850-lcdk.html#L552
>>>
>>> BUG: Bad page state in process kworker/u2:0 pfn:c3000
>>>
>>> So I'm not sure what happened, but it has highlighted this kernel
>>> bug so I guess it might be worth taking a look in case there was
>>> a commit somewhere in your tree that resolved it at some point
>>> last week. What do you think?
>>>
>>
>> This may be related to a known problem regarding infinite recursion on
>> some DT nodes related to USB devices: Arnd or Rob would know more
>> about this.
>
> That should be fixed in rc1. Commit 9b22c17a3cc5 ("of: Check
> 'of_node_reused' flag on of_match_device()").
Well the particular issue with the BUG message on da850-lcdk is
still there in v5.17-rc1:
https://linux.kernelci.org/test/case/id/61ed2891c2717f210aabbd69/
So it doesn't look like there's a trivial solution to this in
Ard's tree. I believe this issue has been around for a while, so
we'll add it to the list of kernel bugs detected by KernelCI and
it might be something someone will want to fix one day.
Thanks,
Guillaume
prev parent reply other threads:[~2022-01-26 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <61e3f952.1c69fb81.3e21a.0062@mx.google.com>
2022-01-25 21:32 ` ardb/for-kernelci bisection: baseline.dmesg.alert on da850-lcdk Guillaume Tucker
2022-01-25 22:21 ` Ard Biesheuvel
2022-01-25 22:27 ` Rob Herring
2022-01-26 11:28 ` Guillaume Tucker [this message]
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=921f80f5-a95d-ee12-2266-16503edea614@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=kernelci-results@groups.io \
--cc=kernelci@groups.io \
--cc=robh+dt@kernel.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 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).