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, 16 Mar 2020 18:13:34 +0000 [thread overview]
Message-ID: <bug-206669-206035-5S7BEUrz3g@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 #12 from John Paul Adrian Glaubitz (glaubitz@physik.fu-berlin.de) ---
Another crash:
watson login: [17667512263.751484] BUG: Unable to handle kernel data access at
0xc000000ff06e4838
[17667512263.751507] Faulting instruction address: 0xc00000000017a778
[17667512263.751513] BUG: Unable to handle kernel data access at
0xc0000007f9070c08
[17667512263.751517] Faulting instruction address: 0xc0000000002659a0
[17667512263.751521] BUG: Unable to handle kernel data access at
0xc0000007f9070c08
[17667512263.751525] Faulting instruction address: 0xc0000000002659a0
[17667512263.751529] BUG: Unable to handle kernel data access at
0xc0000007f9070c08
[17667512263.751533] Faulting instruction address: 0xc0000000002659a0
[17667512263.751537] BUG: Unable to handle kernel data access at
0xc0000007f9070c08
[17667512263.751541] Faulting instruction address: 0xc0000000002659a0
[17667512263.751545] BUG: Unable to handle kernel data access at
0xc0000007f9070c08
[17667512263.751548] Faulting instruction address: 0xc0000000002659a0
[17667512263.751552] BUG: Unable to handle kernel data access at
0xc0000007f9070c08
[17667512263.751556] Faulting instruction address: 0xc0000000002659a0
[17667512263.751560] BUG: Unable to handle kernel data access at
0xc0000007f9070c08
[17667512263.751564] Faulting instruction address: 0xc0000000002659a0
[17667512263.751569] BUG: Unable to handle kernel data access at
0xc0000007f9070c08
[17667512263.751574] Faulting instruction address: 0xc0000000002659a0
[17667512263.751578] BUG: Unable to handle kernel data access at
0xc0000007f9070c08
[17667512263.751583] Faulting instruction address: 0xc0000000002659a0
[17667512263.751587] BUG: Unable to handle kernel data access at
0xc0000007f9070c08
[17667512263.751591] Faulting instruction address: 0xc0000000002659a0
[17667512263.751596] BUG: Unable to handle kernel data access at
0xc0000007f9070c08
[17667512263.751600] Faulting instruction address: 0xc0000000002659a0
[17667512263.751604] Thread overran stack, or stack corrupted
[17667512263.751608] BUG: Unable to handle kernel data access at
0xc0000007f9070c08
[17667512263.751612] Faulting instruction address: 0xc0000000002659a0
[17667512263.751615] Thread overran stack, or stack corrupted
[17667512263.751618] BUG: Unable to handle kernel data access at
0xc0000007f9070c08
[ 1835.743178] BUG: Unable to handle unknown paging fault at 0xc000000000c4b363
[ 1835.743180] Faulting instruction address: 0x00000000
[17667512263.751633] Faulting instruction address: 0xc0000000002659a0
[ 1835.743195] Oops: Kernel access of bad area, sig: 11 [#1]
[ 1835.743198] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV
[ 1835.743203] Modules linked in:
[17667512263.751652] Thread overran stack, or stack corrupted
[ 1835.743205]
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-03-16 18:21 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 [this message]
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-5S7BEUrz3g@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.