dtrace on rpi3 panics
Michael Tuexen
tuexen at freebsd.org
Fri Nov 4 19:16:07 UTC 2016
Dear all,
when running
kldload dtraceall
on a rpi3 with
tuexen at rpi3:~ % uname -a
FreeBSD rpi3 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r307671M: Thu Oct 20 15:52:24 CEST 2016 tuexen at bsd5.fh-muenster.de:/usr/home/tuexen/arm64/obj/arm64.aarch64/usr/home/tuexen/head/sys/GENERIC-UP arm64
I get
root at rpi3:/home/tuexen # kldload dtraceall
x0: ffff0000003194c4
x1: fffffd00014ad500
x2: ffff0000003194c4
x3: ffff0000409d2a6c
x4: ffff0000003194c4
x5: 0
x6: ffff000000966850
x7: 40
x8: fffffd0001c1c9c0
x9: 1
x10: 1
x11: 0
x12: fffffd00015ef628
x13: fffffd00014c1300
x14: ffff00000092c670
x15: 0
x16: ffff0000409e7678
x17: ffff000000319414
x18: ffff0000533bff80
x19: ffff0000409d2a6c
x20: ffff0000003194c4
x21: ffff0000003194c4
x22: fffffd00014ad500
x23: fffffd00015ef5e0
x24: 8
x25: 1
x26: ffff0000409e8000
x27: ffff0000409e7000
x28: ffff0000409e7000
x29: ffff0000533bffa0
x30: ffff0000533bffa0
sp: ffff0000533bff80
lr: ffff000000319444
elr: fffffd00014ad500
spsr: 800003c5
panic: Unknown kernel exception 0 esr_el1 2000000
KDB: stack backtrace:
db_trace_self() at db_trace_self_wrapper+0x28
pc = 0xffff000000590e60 lr = 0xffff00000005e50c
sp = 0xffff0000533bfa80 fp = 0xffff0000533bfc90
db_trace_self_wrapper() at vpanic+0x9c
pc = 0xffff00000005e50c lr = 0xffff0000002ce7b8
sp = 0xffff0000533bfca0 fp = 0xffff0000533bfd10
vpanic() at panic+0x4c
pc = 0xffff0000002ce7b8 lr = 0xffff0000002ce898
sp = 0xffff0000533bfd20 fp = 0xffff0000533bfda0
panic() at do_el1h_sync+0x138
pc = 0xffff0000002ce898 lr = 0xffff0000005a6a90
sp = 0xffff0000533bfdb0 fp = 0xffff0000533bfdd0
do_el1h_sync() at handle_el1h_sync+0x68
pc = 0xffff0000005a6a90 lr = 0xffff000000592868
sp = 0xffff0000533bfde0 fp = 0xffff0000533bfef0
handle_el1h_sync() at smp_rendezvous_cpus+0x2c
pc = 0xffff000000592868 lr = 0xffff000000319440
sp = 0xffff0000533bff00 fp = 0xffff0000533bffa0
smp_rendezvous_cpus() at dtrace_probe_create+0x20c
pc = 0xffff000000319440 lr = 0xffff0000409bd7cc
sp = 0xffff0000533bffb0 fp = 0xffff0000533c0000
dtrace_probe_create() at dtrace_load+0x420
pc = 0xffff0000409bd7cc lr = 0xffff0000409c8ff8
sp = 0xffff0000533c0010 fp = 0xffff0000533c0040
dtrace_load() at linker_load_module+0xaec
pc = 0xffff0000409c8ff8 lr = 0xffff0000002a4ae4
sp = 0xffff0000533c0050 fp = 0xffff0000533c0360
linker_load_module() at linker_load_dependencies+0x29c
pc = 0xffff0000002a4ae4 lr = 0xffff0000002a7044
sp = 0xffff0000533c0370 fp = 0xffff0000533c03e0
linker_load_dependencies() at link_elf_load_file+0x680
pc = 0xffff0000002a7044 lr = 0xffff0000002f1cc8
sp = 0xffff0000533c03f0 fp = 0xffff0000533c05a0
link_elf_load_file() at linker_load_module+0x8a8
pc = 0xffff0000002f1cc8 lr = 0xffff0000002a48a0
sp = 0xffff0000533c05b0 fp = 0xffff0000533c08c0
linker_load_module() at kern_kldload+0xac
pc = 0xffff0000002a48a0 lr = 0xffff0000002a6190
sp = 0xffff0000533c08d0 fp = 0xffff0000533c0900
kern_kldload() at sys_kldload+0x68
pc = 0xffff0000002a6190 lr = 0xffff0000002a6270
sp = 0xffff0000533c0910 fp = 0xffff0000533c0940
sys_kldload() at do_el0_sync+0x540
pc = 0xffff0000002a6270 lr = 0xffff0000005a72f8
sp = 0xffff0000533c0950 fp = 0xffff0000533c0a70
do_el0_sync() at handle_el0_sync+0x64
pc = 0xffff0000005a72f8 lr = 0xffff0000005929d0
sp = 0xffff0000533c0a80 fp = 0xffff0000533c0b90
handle_el0_sync() at 0x400fbc
pc = 0xffff0000005929d0 lr = 0x0000000000400fbc
sp = 0xffff0000533c0ba0 fp = 0x0000ffffffffebb0
KDB: enter: panic
[ thread pid 686 tid 100076 ]
Stopped at kdb_enter+0x40: undefined d4200000
db>
Is this supposed to work already and this is a bug or is there some more
work needed?
Best regards
Michael
More information about the freebsd-arm
mailing list