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=datawareh...

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.

thanks,

greg k-h