Date: Fri, 22 May 2015 18:36:32 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 200384] ctld panic at boot on 10.1-STABLE Message-ID: <bug-200384-8-JMSHbTADsg@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-200384-8@https.bugs.freebsd.org/bugzilla/> References: <bug-200384-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200384 --- Comment #3 from Jimmy Olgeni <olgeni@FreeBSD.org> --- I managed to get a better backtrace (below). A few more data points, always booting with the debug options enabled: - Booting with ctld_enable -> panic - Booting without ctld_enable, and then starting the ctld service -> panic - Booting without ctld_enable, and kldloading ctl -> panic - Booting without ctld_enable, and kldloading ctl after loading iscsi -> ok - Booting with ctld_enable, but with iscsi_load and ctl_load in loader.conf -> ok There seems to be something going on between ctl and iscsi when ctl is loaded without iscsi already present. (kgdb) bt #0 doadump (textdump=0) at pcpu.h:219 #1 0xffffffff803600fe in db_dump (dummy=<value optimized out>, dummy2=0, dummy3=0, dummy4=0x0) at /usr/src/sys/ddb/db_command.c:533 #2 0xffffffff8035fb9d in db_command (cmd_table=0x0) at /usr/src/sys/ddb/db_command.c:440 #3 0xffffffff8035f914 in db_command_loop () at /usr/src/sys/ddb/db_command.c:493 #4 0xffffffff803622f0 in db_trap (type=<value optimized out>, code=0) at /usr/src/sys/ddb/db_main.c:231 #5 0xffffffff809953d9 in kdb_trap (type=3, code=0, tf=<value optimized out>) at /usr/src/sys/kern/subr_kdb.c:656 #6 0xffffffff80d8b73e in trap (frame=0xfffffe046a445210) at /usr/src/sys/amd64/amd64/trap.c:554 #7 0xffffffff80d6fc52 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:236 #8 0xffffffff80994ae5 in kdb_break () at cpufunc.h:63 #9 0xffffffff80776d9b in scgetc (sc=0xffffffff8185be18, flags=<value optimized out>) at /usr/src/sys/dev/syscons/syscons.c:3591 #10 0xffffffff807795ff in sc_cngetc (cd=0xffffffff81643f70) at /usr/src/sys/dev/syscons/syscons.c:1782 #11 0xffffffff809071c5 in cngetc () at /usr/src/sys/kern/kern_cons.c:406 #12 0xffffffff8095a54e in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:455 #13 0xffffffff8095a9d5 in vpanic (fmt=<value optimized out>, ap=<value optimized out>) at /usr/src/sys/kern/kern_shutdown.c:759 #14 0xffffffff8095aa23 in panic (fmt=0xffffffff81643f70 "\004") at /usr/src/sys/kern/kern_shutdown.c:688 #15 0xffffffff80d8be3f in trap_fatal (frame=<value optimized out>, eva=<value optimized out>) at /usr/src/sys/amd64/amd64/trap.c:857 #16 0xffffffff80d8ba98 in trap (frame=<value optimized out>) at /usr/src/sys/amd64/amd64/trap.c:203 #17 0xffffffff80d6fc52 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:236 #18 0xffffffff802e494a in cam_periph_alloc (periph_ctor=0xffffffff802f9c30 <proberegister>, periph_oninvalidate=<value optimized out>, periph_dtor=<value optimized out>, periph_start=<value optimized out>, name=<value optimized out>, type=<value optimized out>, path=0xfffff80163591600, ac_callback=<value optimized out>, code=<value optimized out>) at /usr/src/sys/cam/cam_periph.c:227 #19 0xffffffff802f94fb in scsi_scan_lun (request_ccb=<value optimized out>) at /usr/src/sys/cam/scsi/scsi_xpt.c:2339 #20 0xffffffff802fd659 in scsi_scan_bus (periph=<value optimized out>, request_ccb=0xfffff80163b33800) at /usr/src/sys/cam/scsi/scsi_xpt.c:2037 #21 0xffffffff802f045b in xpt_scanner_thread (dummy=<value optimized out>) at /usr/src/sys/cam/cam_xpt.c:2453 #22 0xffffffff809215d4 in fork_exit (callout=0xffffffff802f0350 <xpt_scanner_thread>, arg=0x0, frame=0xfffffe046a445c00) at /usr/src/sys/kern/kern_fork.c:1017 #23 0xffffffff80d7018e in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:611 #24 0x0000000000000000 in ?? () -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-200384-8-JMSHbTADsg>