From: Veronika Kabatova <vkabatov@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] 💥 PANICKED: Test report for kernel 5.5.12-rc1-8b841eb.cki (stable)
Date: Tue, 24 Mar 2020 07:12:07 -0400 (EDT) [thread overview]
Message-ID: <970614328.15180583.1585048327050.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20200324062213.GA1961100@kroah.com>
----- Original Message -----
> From: "Greg KH" <greg@kroah.com>
> To: "CKI Project" <cki-project@redhat.com>
> Cc: "Memory Management" <mm-qe@redhat.com>, "Ondrej Mosnacek" <omosnace@redhat.com>, "Linux Stable maillist"
> <stable@vger.kernel.org>, "Jan Stancek" <jstancek@redhat.com>, "LTP Mailing List" <ltp@lists.linux.it>
> Sent: Tuesday, March 24, 2020 7:22:13 AM
> Subject: Re: ? PANICKED: Test report for kernel 5.5.12-rc1-8b841eb.cki (stable)
>
> On Tue, Mar 24, 2020 at 05:42:38AM -0000, CKI Project wrote:
> >
> > Hello,
> >
> > We ran automated tests on a recent commit from this kernel tree:
> >
> > Kernel repo:
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > Commit: 8b841eb697e1 - Linux 5.5.12-rc1
> >
> > The results of these automated tests are provided below.
> >
> > Overall result: FAILED (see details below)
> > Merge: OK
> > Compile: OK
> > Tests: PANICKED
> >
> > All kernel binaries, config files, and logs are available for download
> > here:
> >
> > https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawarehouse/2020/03/23/502039
> >
> > One or more kernel tests failed:
> >
> > ppc64le:
> > ? xfstests - ext4
> >
> > aarch64:
> > ? LTP
> >
> > x86_64:
> > ? xfstests - ext4
>
> Ok, it's time I start just blacklisting this report again, it's not
> being helpful in any way :(
>
> Remember, if something starts breaking, I need some way to find out what
> caused it to break...
>
Hi Greg,
do you have any specific suggestions about what to include to help you out?
The linked console logs contain call traces for the panics [0]. Is there
anything else that would help you with debugging those? We're planning on
releasing core dumps, would those be helpful?
[0]: While these are new ones and not matching what we saw previously
(that's why they weren't filtered out), the following commits from
block tree should likely fix them:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?id=fd1bb3ae54a9a2e0c42709de861c69aa146b8955
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?id=c8997736650060594845e42c5d01d3118aec8d25
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?id=576682fa52cbd95deb3773449566274f206acc58
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?id=4d38a87fbb77fb9ff2ff4e914162a8ae6453eff5
Veronika
> greg k-h
>
>
>
next prev parent reply other threads:[~2020-03-24 11:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 5:42 [LTP] 💥 PANICKED: Test report for kernel 5.5.12-rc1-8b841eb.cki (stable) CKI Project
2020-03-24 6:22 ` Greg KH
2020-03-24 11:12 ` Veronika Kabatova [this message]
2020-03-24 11:18 ` [LTP] 💥 PANICKED: Test report for?kernel " Greg KH
2020-03-24 11:44 ` Veronika Kabatova
2020-03-24 11:47 ` [LTP] 💥 PANICKED: Test report?for?kernel " Greg KH
2020-03-24 12:42 ` Veronika Kabatova
2020-03-24 12:48 ` [LTP] 💥 PANICKED: Test?report?for?kernel " Greg KH
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=970614328.15180583.1585048327050.JavaMail.zimbra@redhat.com \
--to=vkabatov@redhat.com \
--cc=ltp@lists.linux.it \
/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