All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 206669] Little-endian kernel crashing on POWER8 on heavy big-endian PowerKVM load
Date: Mon, 13 Sep 2021 09:24:25 +0000	[thread overview]
Message-ID: <bug-206669-206035-BxC4KK75AL@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206669-206035@https.bugzilla.kernel.org/>

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

--- Comment #16 from John Paul Adrian Glaubitz (glaubitz@physik.fu-berlin.de) ---
Hi Michael!

Thanks a lot for looking into this!

If you have installed a Debian unstable big-endian system, the easiest way to
get such a setup by creating an sbuild chroot. You should set up an sbuild
chroot for both powerpc and ppc64:

$ sbuild-createchroot --arch=powerpc
$ sbuild-createchroot --arch=ppc64

and then build the glibc package using sbuild for both powerpc and ppc64 in
parallel which is what makes the VM and the host crash during the testsuite:

$ dget -u https://deb.debian.org/debian/pool/main/g/glibc/glibc_2.32-2.dsc

In one shell:

$ sbuild -d sid --arch=ppc64 --no-arch-all glibc_2.32-2.dsc

and in a second one:

$ sbuild -d sid --arch=powerpc --no-arch-all glibc_2.32-2.dsc

If glibc doesn't trigger the crash, try gcc-10 or llvm-toolchain-13:

$ dget -u
https://deb.debian.org/debian/pool/main/l/llvm-toolchain-13/llvm-toolchain-13_13.0.0~+rc2-3.dsc
$ dget -u https://deb.debian.org/debian/pool/main/g/gcc-11/gcc-11_11.2.0-5.dsc

-- 
You may reply to this email to add a comment.

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

  parent reply	other threads:[~2021-09-13  9:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25 15:26 [Bug 206669] New: Little-endian kernel crashing on POWER8 on heavy big-endian PowerKVM load bugzilla-daemon
2020-02-26  4:02 ` 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 [this message]
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-BxC4KK75AL@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.