In-kernel DTrace incompatible with in-kernel OpenZFS

From: Trond Endrestøl <trond.endrestol_at_ximalas.info>
Date: Sat, 5 Sep 2020 10:06:53 +0200 (CEST)
It would seem

options dtrace
options dtraceall

are incompatible with

options zfs

This is on base/head, r365358, amd64.

Fatal trap 12: page fault while in kernel mode
cpuid = 4; apic id = 04
fault virtual address   = 0x7fffffff8
fault code              = supervisor write data, page not present
instruction pointer     = 0x20:0xfffffffff808cf8db
stack pointer           = 0x20:0xfffffffff82378a00
frame pointer           = 0x20:0xfffffffff82378a00
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 0 (dtrace_taskq)
trap number             = 12
panic: page fault
cpuid = 4
time = 1
KDB: stack backtrace:
db_trace_self_wrapper() at
vpanic() at
panic() at
trap_fatal() at
trap_pfatal() at
trap() at
calltrap() at
--- trap 0xc, rip = 0xfffffffff808cf8db, rsp = 0xfffffffff82378a00, rbp = 0xfffffffff82378a00 ---
osd_set_reserved() at
taskqueue_thread_loop() at
fork_exit() at
fork_trampoline() at
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---
Uptime: 1s
Automatic reboot in 15 seconds - press a key on the console to abort

I don't mind having dtraceall_load="YES" in /boot/loader.conf; I have 
to do so anyway to get systrace_freebsd32.ko loaded at boot time.
Can this latter .ko file be made part of the kernel using an option 
statement?

-- 
Trond.
Received on Sat Sep 05 2020 - 06:07:06 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:25 UTC