Date: Sat, 25 Mar 2017 03:03:14 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Darren <darren780@yahoo.com> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>, glebius@freebsd.org Subject: Re: r315684 panic: sleepq_add: td 0xfffff80003c01a40 to sleep on wchan 0xfffff80006f0873c with sleeping prohibited Message-ID: <20170325010314.GG43712@kib.kiev.ua> In-Reply-To: <1824572972.3096988.1490377215756@mail.yahoo.com> References: <1824572972.3096988.1490377215756.ref@mail.yahoo.com> <1824572972.3096988.1490377215756@mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 24, 2017 at 05:40:15PM +0000, Darren wrote: > I am getting this panic every hour to every couple of hours. > > FreeBSD asrock 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r315684: Thu Mar 23 14:56:45 EDT 2017šššš darren@asrock:/usr/obj/usr/src/sys/GENERICš amd64 > I manually typed out the following, apologize for any typos. > > > panic: sleepq_add: td 0xfffff80003c01a40 to sleep on wchan 0xfffff80006f0873c with sleeping prohibited > cpuid = 0 > time = 1490372797 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0072e33690 > vpanic() at vpanic+0x19c/frame 0xfffffe0072e33710 > kassert_panic() at kassert_panic+0x126/frame 0xfffffe0072e33780 > sleepq_add() at sleepq_add+0x34f/frame 0xfffffe0072337d0 > _sleep() at _sleep+0x28d/frame 0xfffffe0072e33870 > soclose() at soclose+0xda/frame 0xfffffe0072e338b0 > _fdrop() at _fdrop+0x1a/frame 0xfffffe0072e338d0 > sendfile_iodone() at sendfile_iodone+0x19d/frame 0xfffffe0072e33910 > vnode_pager_generic_getpages_done_async() at vnode_pager_generic_getpages_done_async+037/frame 0xfffffe0072e33930 > bufdone() at bufdone+0x64/frame 0xfffffe0072e33960 > g_io_deliver() at g_io_deliver+0x276/frame 0xfffffe0072e339b0 > g_io_deliver() at g_io_deliver+0x276/frame 0xfffffe0072e33a00 > g_disk_done() at g_disk_done+0x104/frame 0xfffffe0072e33a40 > xpt_done_process() at xpt_done_process+0x35f/frame 0xfffffe0072e33a80 > xpt_done_direct() at ahci_ch_intr_direct+0xd5/frame 0xfffffe0072e33af0 > ahci_itr() at ahci_intr+0x102/frame 0xfffffe0072e33b20 > intr_event_execute_handlers() at intr_event_execute_handlers+0x99/frame 0xfffffe0072e33b60 > ithread_loop() at ithread_loop+0xb6/frame 0xfffffe0072e33bb0 > fork_exit() at fork_exit+0x84/frame 0xfffffe0072e33bf0 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0072e33bf0 > --- trap 0, rip = 0, rsp = 0, rbp = 0 --- > KDB: enter: panic > [ thread pid 12 tid 100038 ] > Stopped atššššš kdb_enter+0x3b: movqššš $0,kdb_why > db> Indeed, the context where sendfile_iodone() is executed, cannot call fdrop().
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170325010314.GG43712>