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: Sat, 14 Mar 2020 10:08:45 +0000 [thread overview]
Message-ID: <bug-206669-206035-yFQfcbTsa3@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 #11 from John Paul Adrian Glaubitz (glaubitz@physik.fu-berlin.de) ---
It seems I can provoke the crash by running the glibc testsuite in a big-endian
guest VM.
The machine just crashed with the IPMI console open but the only message the
kernel printed was:
"watson login: [ 1809.138398] KVM: couldn't grab cpu 115"
I have not observed the kernel buffer though. But I will try to provoke the
crash now while having the kernel log open.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-03-14 10:10 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 [this message]
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-yFQfcbTsa3@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).