From: Jan Stancek <jstancek@redhat.com>
To: Ondrej Mosnacek <omosnace@redhat.com>, Sasha Levin <sashal@kernel.org>
Cc: CKI Project <cki-project@redhat.com>,
Linux Stable maillist <stable@vger.kernel.org>,
Memory Management <mm-qe@redhat.com>,
LTP Mailing List <ltp@lists.linux.it>,
Ondrej Moris <omoris@redhat.com>,
William Gomeringer <wgomeringer@redhat.com>
Subject: Re: ❌ PANICKED: Test report for kernel 5.5.8-c30f33b.cki (stable-queue)
Date: Tue, 10 Mar 2020 03:58:48 -0400 (EDT) [thread overview]
Message-ID: <1743314452.221557.1583827128244.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAFqZXNugDTJ8MQePK1Cyz2TOJiPcPrq3ohmNZngJjaTCq1Y6mQ@mail.gmail.com>
----- Original Message -----
> > Following the link above I got to
> > https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawarehouse/2020/03/09/480158/audit__audit_testsuite_test/,
> > but it shows that all tests are passing? The console log looks fine too:
> > https://cki-artifacts.s3.us-east-2.amazonaws.com/datawarehouse/2020/03/09/480158/x86_64_5_console.log.
> > Where's the panic?
>
> The panic happened during the LTP test on s390x (note the lightning
> symbols under s390x, Host 1). The backtrace is at the end of
> https://cki-artifacts.s3.us-east-2.amazonaws.com/datawarehouse/2020/03/09/480158/s390x_1_console.log
Which looks like same panic reported for last couple days. See:
https://lore.kernel.org/stable/976629603.10711789.1583698043547.JavaMail.zimbra@redhat.com/
https://lore.kernel.org/lkml/20200224030007.3990-1-cai@lca.pw/
prev parent reply other threads:[~2020-03-10 7:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 21:24 ❌ PANICKED: Test report for kernel 5.5.8-c30f33b.cki (stable-queue) CKI Project
2020-03-09 21:53 ` Sasha Levin
2020-03-09 22:03 ` Ondrej Mosnacek
2020-03-10 7:58 ` Jan Stancek [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=1743314452.221557.1583827128244.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=cki-project@redhat.com \
--cc=ltp@lists.linux.it \
--cc=mm-qe@redhat.com \
--cc=omoris@redhat.com \
--cc=omosnace@redhat.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wgomeringer@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).