From: Heiko Thiery <heiko.thiery@gmail.com>
To: Guillaume Tucker <guillaume.tucker@collabora.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Jianxiong Gao <jxgao@google.com>, Christoph Hellwig <hch@lst.de>
Cc: iommu@lists.linux-foundation.org,
Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org,
"kernelci-results@groups.io" <kernelci-results@groups.io>
Subject: Re: next/master bisection: baseline.login on r8a77960-ulcb
Date: Wed, 24 Feb 2021 22:39:42 +0100 [thread overview]
Message-ID: <db197ccf-3b55-098e-bc19-ca8adc98c6b2@gmail.com> (raw)
In-Reply-To: <7ac4a45f-b95e-acc0-f5bc-e4f870ac0bf1@collabora.com>
Hi Christoph and all,
On 23.02.21 10:56, Guillaume Tucker wrote:
> Hi Christoph,
>
> Please see the bisection report below about a boot failure on
> r8a77960-ulcb on next-20210222.
>
> Reports aren't automatically sent to the public while we're
> trialing new bisection features on kernelci.org but this one
> looks valid.
>
> The log shows a kernel panic, more details can be found here:
>
> https://kernelci.org/test/case/id/6034bde034504edc9faddd2c/
>
> Please let us know if you need any help to debug the issue or try
> a fix on this platform.
I am also seeing this problem on an iMX8MQ board and can help test if
you have a fix.
BR
--
Heiko
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2021-02-24 21:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <60346234.1c69fb81.cd55e.770d@mx.google.com>
2021-02-23 9:56 ` next/master bisection: baseline.login on r8a77960-ulcb Guillaume Tucker
2021-02-24 21:39 ` Heiko Thiery [this message]
2021-02-25 11:09 ` Thierry Reding
2021-02-25 11:14 ` Robin Murphy
2021-02-25 11:50 ` Thierry Reding
2021-02-25 13:00 ` Heiko Thiery
2021-02-26 8:56 ` Yoshihiro Shimoda
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=db197ccf-3b55-098e-bc19-ca8adc98c6b2@gmail.com \
--to=heiko.thiery@gmail.com \
--cc=guillaume.tucker@collabora.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=jxgao@google.com \
--cc=kernelci-results@groups.io \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.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).