From: Veronika Kabatova <vkabatov@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: Memory Management <mm-qe@redhat.com>,
Ondrej Mosnacek <omosnace@redhat.com>,
Linux Stable maillist <stable@vger.kernel.org>,
CKI Project <cki-project@redhat.com>,
Jan Stancek <jstancek@redhat.com>,
LTP Mailing List <ltp@lists.linux.it>
Subject: Re: 💥 PANICKED: Test report for?kernel 5.5.12-rc1-8b841eb.cki (stable)
Date: Tue, 24 Mar 2020 07:44:32 -0400 (EDT) [thread overview]
Message-ID: <1768018191.15186361.1585050272846.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20200324111819.GA2234211@kroah.com>
----- Original Message -----
> From: "Greg KH" <greg@kroah.com>
> To: "Veronika Kabatova" <vkabatov@redhat.com>
> Cc: "Memory Management" <mm-qe@redhat.com>, "Ondrej Mosnacek" <omosnace@redhat.com>, "Linux Stable maillist"
> <stable@vger.kernel.org>, "CKI Project" <cki-project@redhat.com>, "Jan Stancek" <jstancek@redhat.com>, "LTP Mailing
> List" <ltp@lists.linux.it>
> Sent: Tuesday, March 24, 2020 12:18:19 PM
> Subject: Re: 💥 PANICKED: Test report for?kernel 5.5.12-rc1-8b841eb.cki (stable)
>
> On Tue, Mar 24, 2020 at 07:12:07AM -0400, Veronika Kabatova wrote:
> >
> >
> > ----- 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?
>
> Bisection to find the offending commit would be best.
>
This is going to be really tricky for hard to reproduce bugs but we'll do
some research on it, thanks!
Veronika
> thanks,
>
> greg k-h
>
>
>
next prev parent reply other threads:[~2020-03-24 11:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 5:42 💥 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
2020-03-24 11:18 ` 💥 PANICKED: Test report for?kernel " Greg KH
2020-03-24 11:44 ` Veronika Kabatova [this message]
2020-03-24 11:47 ` 💥 PANICKED: Test report?for?kernel " Greg KH
2020-03-24 12:42 ` Veronika Kabatova
2020-03-24 12:48 ` 💥 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=1768018191.15186361.1585050272846.JavaMail.zimbra@redhat.com \
--to=vkabatov@redhat.com \
--cc=cki-project@redhat.com \
--cc=greg@kroah.com \
--cc=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
--cc=mm-qe@redhat.com \
--cc=omosnace@redhat.com \
--cc=stable@vger.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).