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

--- Comment #4 from John Paul Adrian Glaubitz (glaubitz@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 printed.

Seems that this is the case in the Debian kernel, yes:

root@watson:~# grep -i ftrace /boot/config-5.4.0-0.bpo.3-powerpc64le 
CONFIG_KPROBES_ON_FTRACE=y
CONFIG_HAVE_KPROBES_ON_FTRACE=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_DYNAMIC_FTRACE_WITH_REGS=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_FTRACE=y
CONFIG_FTRACE_SYSCALLS=y
CONFIG_DYNAMIC_FTRACE=y
CONFIG_DYNAMIC_FTRACE_WITH_REGS=y
CONFIG_FTRACE_MCOUNT_RECORD=y
# CONFIG_FTRACE_STARTUP_TEST is not set
root@watson:~#

Do you have the kernel command option at hand which disables ftrace on the
command line? Is it just ftrace=off?

quoted

FWIW, the kernel image comes from this Debian package:

quoted

http://snapshot.debian.org/archive/debian/20200211T210433Z/pool/main/l/linux/linux-image-5.4.0-0.bpo.3-powerpc64le_5.4.13-1%7Ebpo10%2B1_ppc64el.deb

Okay. Any chance you could test an upstream kernel? 

Sure, absolutely. Any preference on the version number?

Don't bother testing that after the above -- panic_on_oops happens
after oops_begin(), so it won't help unfortunately.

Okay.

Attmepting to get into xmon might though, if you boot with xmon=on.
Try that if tracing wasn't enabled, or disabling it doesn't help.

Okay. I will try to disable ftrace first, then retrigger the crash.

quoted

Anything to be considered for the kernel running inside the big-endian VM?

Not that I'm aware of really. Certainly it shouldn't be able to crash
the host even if the guest was doing something stupid.

I agree.

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