On 13-01-16 05:51 PM, Mark Lord wrote: > On 13-01-16 12:20 AM, Stanislav Kinsbursky wrote: >> >> Mark, could you provide any call traces? > > Call traces from where/what? > There's this one, posted earlier in the BUG report: > > kernel BUG at net/sunrpc/svc_xprt.c:921! > Call Trace: > [<ffffffffa016a56a>] ? svc_recv+0xcc/0x338 [sunrpc] > [<ffffffffa0318bfc>] ? nfs_callback_authenticate+0x20/0x20 [nfsv4] > [<ffffffffa0318c19>] ? nfs4_callback_svc+0x1d/0x3c [nfsv4] > [<ffffffff810407e6>] ? kthread+0x81/0x89 > [<ffffffff81040765>] ? kthread_freezable_should_stop+0x36/0x36 > [<ffffffff812ea62c>] ? ret_from_fork+0x7c/0xb0 > [<ffffffff81040765>] ? kthread_freezable_should_stop+0x36/0x36 ..
This might be of some interest. Here are the first few lines of the same BUG occurance, with timestamps and the dmesg lines that immediately preceeded it. Perhaps they might help indicate who's triggering the action that results in the BUG(?). Jan 14 10:58:05 zippy kernel: [66045.627952] NFS: Registering the id_resolver key type Jan 14 10:58:05 zippy kernel: [66045.628014] Key type id_resolver registered Jan 14 10:58:05 zippy kernel: [66045.628020] Key type id_legacy registered Jan 14 10:58:05 zippy kernel: [66045.636302] ------------[ cut here ]------------ Jan 14 10:58:05 zippy kernel: [66045.648342] kernel BUG at net/sunrpc/svc_xprt.c:921! -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
