linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 206669] New: Little-endian kernel crashing on POWER8 on heavy big-endian PowerKVM load
Date: Tue, 25 Feb 2020 15:26:14 +0000	[thread overview]
Message-ID: <bug-206669-206035@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=206669

            Bug ID: 206669
           Summary: Little-endian kernel crashing on POWER8 on heavy
                    big-endian PowerKVM load
           Product: Platform Specific/Hardware
           Version: 2.5
    Kernel Version: 5.4.x
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: PPC-64
          Assignee: platform_ppc-64@kernel-bugs.osdl.org
          Reporter: glaubitz@physik.fu-berlin.de
                CC: matorola@gmail.com
        Regression: No

Created attachment 287605
  --> https://bugzilla.kernel.org/attachment.cgi?id=287605&action=edit
Backtrace of host system crashing with little-endian kernel

We have an IBM POWER server (8247-42L) running Linux kernel 5.4.13 on Debian
unstable hosting a big-endian ppc64 virtual machine running the same kernel in
big-endian mode.

When building OpenJDK-11 on the big-endian VM, the testsuite crashes the *host*
system which is little-endian with the following kernel backtrace. The problem
reproduces both with kernel 4.19.98 as well as 5.4.13, both guest and host
running 5.4.x.

Backtrace attached.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2020-02-25 15:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25 15:26 bugzilla-daemon [this message]
2020-02-26  4:02 ` [Bug 206669] New: Little-endian kernel crashing on POWER8 on heavy big-endian PowerKVM load Nicholas Piggin
2020-02-26  4:06 ` [Bug 206669] " bugzilla-daemon
2020-02-26  7:26 ` bugzilla-daemon
2020-02-26  9:25   ` Nicholas Piggin
2020-02-26  9:29 ` bugzilla-daemon
2020-02-26 10:28 ` bugzilla-daemon
2020-02-26 11:03   ` Nicholas Piggin
2020-02-26 11:08 ` bugzilla-daemon
2020-02-26 12:02 ` bugzilla-daemon
2020-02-27 16:07 ` bugzilla-daemon
2020-03-07 21:56 ` bugzilla-daemon
2020-03-10 12:25 ` bugzilla-daemon
2020-03-10 12:28 ` bugzilla-daemon
2020-03-14 10:08 ` bugzilla-daemon
2020-03-16 18:13 ` bugzilla-daemon
2020-03-19 20:22 ` bugzilla-daemon
2021-09-10  9:40 ` bugzilla-daemon
2021-09-13  8:52 ` bugzilla-daemon
2021-09-13  9:24 ` bugzilla-daemon
2021-09-30 15:44 ` bugzilla-daemon
2021-10-25  8:45 ` bugzilla-daemon
2022-01-31  9:53 ` bugzilla-daemon
2022-07-29  7:02 ` bugzilla-daemon

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=bug-206669-206035@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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).