(#219074 is similar in subject, but stack trace is different).
Today I wanted to record a CDRW, I inserted a non empty one (which I intended to blank) and my system crashed.
#0 doadump (textdump=<value optimized out>) at pcpu.h:233
(kgdb) #0 doadump (textdump=<value optimized out>) at pcpu.h:233
#1 0xffffffff805755db in kern_reboot (howto=260)
#2 0xffffffff80575a01 in vpanic (fmt=<value optimized out>,
ap=<value optimized out>) at /usr/src/sys/kern/kern_shutdown.c:776
#3 0xffffffff80575843 in panic (fmt=<value optimized out>)
#4 0xffffffff807f516f in trap_fatal (frame=0xfffffe01f3916a60, eva=8)
#5 0xffffffff807f51c9 in trap_pfault (frame=0xfffffe01f3916a60, usermode=0)
#6 0xffffffff807f49c7 in trap (frame=0xfffffe01f3916a60)
#7 0xffffffff807d668c in calltrap ()
#8 0xffffffff804ecd4e in g_dev_orphan (cp=0xfffff8002d1b9700)
#9 0xffffffff804f5081 in g_resize_provider_event (arg=<value optimized out>,
flag=<value optimized out>) at /usr/src/sys/geom/geom_subr.c:631
#10 0xffffffff804f04ce in g_run_events ()
#11 0xffffffff80541a63 in fork_exit (
callout=0xffffffff804f2890 <g_event_procbody>, arg=0x0,
frame=0xfffffe01f3916c00) at /usr/src/sys/kern/kern_fork.c:1054
#12 0xffffffff807d75be in fork_trampoline ()
#13 0x0000000000000000 in ?? ()
Current language: auto; currently minimal
Possibly devd or some other component (from XFCE?) tried to access the disk, alhough I didn't ask to mount it in any way.
Notice this is my first multi-user boot after the upgrade to 11.2-RELEASE-p11: this might be related or not to FreeBSD-SA-19:11.cd_ioctl, but it never happened before.
I don't believe this is related to the SA.
Could you provide the core.txt from this crash?
I've tried attaching it several times, but connection always times out.
Please, find it here:
Notice I've made some other tests and was unable to reproduce this crash again.
Created attachment 205586 [details]
Thanks. My guess is that this would be fixed by r323977, which is unfortunately not present in 11.x. If you're able to test kernel patches, please try the attached diff.
Please re-open the bug if you are able to reproduce the panic. The bug should be fixed in the 11.4 release candidate images, and in 12.0 and later.