https://bugzilla.kernel.org/show_bug.cgi?id=206669
Michael Ellerman (mich...@ellerman.id.au) changed:
What|Removed |Added
Status|NEEDINFO|ASSIGNED
--
https://bugzilla.kernel.org/show_bug.cgi?id=206669
--- Comment #19 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de)
---
In case any runs into this issue, a workaround is disabling "dynamic_mt_modes":
# echo 0 > /sys/module/kvm_hv/parameters/dynamic_mt_modes
This fixes the crashes
https://bugzilla.kernel.org/show_bug.cgi?id=206669
--- Comment #18 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de)
---
There seems to be a related discussion:
> https://yhbt.net/lore/all/20200831091523.gc29...@kitsune.suse.cz/T/
This suspects
https://bugzilla.kernel.org/show_bug.cgi?id=206669
--- Comment #17 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de)
---
POWER server crashes with 100% reproducibility when building GCC in a powerpc
chroot and GCC in a ppc64 chroot on the ppc64 KVM instance at the same time.
And I
https://bugzilla.kernel.org/show_bug.cgi?id=206669
--- Comment #16 from John Paul Adrian Glaubitz (glaub...@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
https://bugzilla.kernel.org/show_bug.cgi?id=206669
Michael Ellerman (mich...@ellerman.id.au) changed:
What|Removed |Added
Status|NEW |NEEDINFO
https://bugzilla.kernel.org/show_bug.cgi?id=206669
--- Comment #14 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de)
---
Still reproduces with Linux 5.10.46 from Debian Bullseye.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching
https://bugzilla.kernel.org/show_bug.cgi?id=206669
--- Comment #13 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de)
---
watson login: [30887.552539] KVM: CPU 4 seems to be stuck
[30900.094713] watchdog: CPU 8 detected hard LOCKUP on other CPUs 0
[30900.094730] watchdog: CPU 8
https://bugzilla.kernel.org/show_bug.cgi?id=206669
--- Comment #12 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de)
---
Another crash:
watson login: [17667512263.751484] BUG: Unable to handle kernel data access at
0xc00ff06e4838
[17667512263.751507] Faulting instruction
https://bugzilla.kernel.org/show_bug.cgi?id=206669
--- Comment #11 from John Paul Adrian Glaubitz (glaub...@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
https://bugzilla.kernel.org/show_bug.cgi?id=206669
--- Comment #10 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de)
---
(In reply to Aneesh Kumar KV from comment #9)
> Also, can you try disabling THP. echo "never" >
> /sys/kernel/mm/transparent_hugepage/enabled
Yes. Just disabled.
https://bugzilla.kernel.org/show_bug.cgi?id=206669
Aneesh Kumar KV (aneesh.ku...@linux.ibm.com) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=206669
--- Comment #8 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de) ---
Created attachment 287823
--> https://bugzilla.kernel.org/attachment.cgi?id=287823=edit
kern.log containing some crash dumps
I have another trace of the crash.
https://bugzilla.kernel.org/show_bug.cgi?id=206669
--- Comment #7 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de) ---
I have set /sys/kernel/debug/tracing/tracing_on to "0" and
/sys/kernel/debug/tracing/free_buffer to "1" and it seems I can no longer
reproduce the issue.
I will
https://bugzilla.kernel.org/show_bug.cgi?id=206669
--- Comment #6 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de) ---
(In reply to npiggin from comment #5)
> I thought it might only be going down that path if you have already done
> some tracing. Perhaps ensure
https://bugzilla.kernel.org/show_bug.cgi?id=206669
--- Comment #5 from npig...@gmail.com ---
bugzilla-dae...@bugzilla.kernel.org's on February 26, 2020 8:28 pm:
> https://bugzilla.kernel.org/show_bug.cgi?id=206669
>
> --- Comment #4 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de)
>
bugzilla-dae...@bugzilla.kernel.org's on February 26, 2020 8:28 pm:
> https://bugzilla.kernel.org/show_bug.cgi?id=206669
>
> --- Comment #4 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de)
> ---
> (In reply to npiggin from comment #3)
>> Do you have tracing / ftrace enabled in the
https://bugzilla.kernel.org/show_bug.cgi?id=206669
--- Comment #4 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de) ---
(In reply to npiggin from comment #3)
> Do you have tracing / ftrace enabled in the host kernel for any
> reason? Turning that off might let the oops message get
bugzilla-dae...@bugzilla.kernel.org's on February 26, 2020 5:26 pm:
> https://bugzilla.kernel.org/show_bug.cgi?id=206669
>
> --- Comment #2 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de)
> ---
> (In reply to npiggin from comment #1)
>> Thanks for the report, we need to get more
https://bugzilla.kernel.org/show_bug.cgi?id=206669
--- Comment #3 from npig...@gmail.com ---
bugzilla-dae...@bugzilla.kernel.org's on February 26, 2020 5:26 pm:
> https://bugzilla.kernel.org/show_bug.cgi?id=206669
>
> --- Comment #2 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de)
>
https://bugzilla.kernel.org/show_bug.cgi?id=206669
--- Comment #2 from John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de) ---
(In reply to npiggin from comment #1)
> Thanks for the report, we need to get more data about the first BUG if
> we can. What function in your vmlinux contains
https://bugzilla.kernel.org/show_bug.cgi?id=206669
--- Comment #1 from npig...@gmail.com ---
bugzilla-dae...@bugzilla.kernel.org's on February 26, 2020 1:26 am:
> https://bugzilla.kernel.org/show_bug.cgi?id=206669
>
> Bug ID: 206669
>Summary: Little-endian kernel crashing
22 matches
Mail list logo
