https://bugzilla.novell.com/show_bug.cgi?id=802347 https://bugzilla.novell.com/show_bug.cgi?id=802347#c5 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|nfbrown@suse.com | --- Comment #5 from Neil Brown <nfbrown@suse.com> 2013-02-17 23:59:32 UTC --- The prev pointer, in %rdx, is NULL, but the next pointer, in %rcx, is not. So maybe it was memset to 0 incorrectly, then the subsequent entry in the list was deleted, so the next pointer in this entry was updated..... In the first crash, req->rq_task->tk_client appear to be NULL in xprt_reset_majortimeo. However I cannot find that it is ever set to NULL - it is initialised by rpc_run_task calling rpc_task_set_client after getting an rpc_new_task(). If rpc_run_bc_task were used, tk_client wouldn't be set but that only happens for "back-channel" (bc) calls from the server back to the client, so unless you are running an NFS server on this machine, that cannot be happening. Given that the two crashes seem to be in unrelated places and both involve a NULL appearing where it shouldn't, I'm wondering if it might be some sort of hardware issue. It doesn't look like bad memory, but maybe a mis-directed DMA??? I suggest you spend sometime watching lots more youtube videos and try to collect some more stack traces. Hopefully we will either see a clear pattern, or a clear lack of a pattern.... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.