On Thu, Mar 22, 2018 at 7:37 AM, Eugene M. Zheganin <eug...@zhegan.in> wrote:
> Hello, > > On 22.03.2018 18:05, Eugene M. Zheganin wrote: > >> today I eventyally got "panic: vdrop: holdcnt 0" on an iSCSI host, on an >> 11.1. Since I don't see any decent information on this - I just wanted to >> ask - what this kind of panic generally mean ? And where do I go with this. >> The only PR I see is about 9.[, and the author there got multiple >> reproducing crashes, not just one. >> > To be more specific - here's a backtrace: > > Unread portion of the kernel message buffer: > panic: vdrop: holdcnt 0 > cpuid = 11 > KDB: stack backtrace: > #0 0xffffffff80aadac7 at kdb_backtrace+0x67 > #1 0xffffffff80a6bba6 at vpanic+0x186 > #2 0xffffffff80a6ba13 at panic+0x43 > #3 0xffffffff80b28739 at _vdrop+0x3e9 > #4 0xffffffff80b295d8 at vputx+0x2f8 > #5 0xffffffff80b38342 at vn_close1+0x182 > #6 0xffffffff82639d1a at ctl_be_block_ioctl+0x86a > #7 0xffffffff82632bdc at ctl_ioctl+0x48c > #8 0xffffffff8093ae38 at devfs_ioctl_f+0x128 > #9 0xffffffff80ac9415 at kern_ioctl+0x255 > #10 0xffffffff80ac914f at sys_ioctl+0x16f > #11 0xffffffff80ee0394 at amd64_syscall+0x6c4 > #12 0xffffffff80ec39bb at Xfast_syscall+0xfb > Uptime: 1d17h36m25s > > I also have the full crashdump and stuff, in case someone will show an > interest. This is currently the only panic I got, but this > happened on a production system, which is, by the way 11.1-RELEASE-p6 > r329259M, an iSCSI host and M stands for iscsi holdoff patch > which was recently MFC'd, but appeared later than the 11.1 was released. Can you try the latest -current with https://reviews.freebsd.org/D14792? Warner _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
