Re: 2.6.31-rc2 soft lockups; traces point at rpc_wake_up, nfs4_run_state_manager, bit_waitqueue

[Paul Collins]

Trond Myklebust <Trond.Myklebust@xxxxxxxxxx> writes:

> On Sun, 2009-07-05 at 10:12 +0200, Ingo Molnar wrote:
>> (added more Cc:s)
>> 
>> potential suspects are:
>> 
>> 1f84603: Merge branch 'devel-for-2.6.31' into for-2.6.31
>> 3f09df7: NFS: Ensure we always hold the BKL when dereferencing inode->i_flock
>> 965b5d6: NFSv4: Handle more errors when recovering open file and locking state
>> 34dc1ad: nfs41: increment_{open,lock}_seqid
>> 78722e9: nfs41: only retry EXCHANGE_ID on recoverable errors
>> b4b8260: nfs41: get_clid_cred for EXCHANGE_ID
>> 90a1661: nfs41: add a get_clid_cred function to nfs4_state_recovery_ops
>> 591d71c: nfs41: establish sessions-based clientid
>> a7b7210: nfs41: introduce get_state_renewal_cred
>> 8e69514f: nfs41: support minorversion 1 for nfs4_check_lease
>> c3fad1b: nfs41: add session reset to state manager
>> 76db6d95: nfs41: add session setup to the state manager
>> c2e713d: nfs41: translate NFS4ERR_MINOR_VERS_MISMATCH to EPROTONOSUPPORT
>
> Or possibly either rpc.gssd or rpc.idmapd dying. Have you checked to see
> if they are up and running correctly?

I hadn't checked because my NFS4 setup has been solid for a while now.
But I'll give it a lash again.  I don't have NFS 4.1 support enabled,
which may eliminate some of the commits above from consideration.

        Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/