[linux-cifs-client] difficult "bug" and kernel/network missbehavior with system freeze

[Christian Hartmann]

Hello list again,

I have switched off the cifsFYI debug today and got a crash within 2 hours again.

In the remote syslog on another machine I have noticed the following kernel
messages, but I do not know, what the cifs client is doing there or why it
begins to hang.


<snip>
Apr  4 13:44:23 box01 kernel: [756181.693313]  CIFS VFS: No response for cmd 50
mid 13917
Apr  4 13:44:23 box01 kernel: [756181.693327]  CIFS VFS: No response to cmd 46
mid 13915
Apr  4 13:44:23 box01 kernel: [756181.693336]  CIFS VFS: Send error in read = -11
Apr  4 13:44:27 box01 kernel: [756186.087476]  CIFS VFS: No response for cmd 50
mid 13918
Apr  4 13:44:27 box01 kernel: [756186.087493]  CIFS VFS: No response for cmd 50
mid 13919
Apr  4 13:44:27 box01 kernel: [756186.087504]  CIFS VFS: No response for cmd 50
mid 13920
Apr  4 13:44:27 box01 kernel: [756186.087514]  CIFS VFS: No response for cmd 50
mid 13921
Apr  4 13:44:27 box01 kernel: [756186.087524]  CIFS VFS: No response for cmd 50
mid 13922
Apr  4 13:44:27 box01 kernel: [756186.087534]  CIFS VFS: No response for cmd 50
mid 13923
Apr  4 13:44:27 box01 kernel: [756186.087552]  CIFS VFS: No response for cmd 50
mid 13924
Apr  4 13:44:27 box01 kernel: [756186.087793]  CIFS VFS: No response for cmd 162
mid 13916
Apr  4 13:44:31 box01 kernel: [756190.036429]  CIFS VFS: Send error in read = -9
Apr  4 12:56:36 box01 syslogd 1.4.1: restart (remote reception).
</snip>

I will try this week the patch I read about
(http://www.kernel.org/git/?p=linux/kernel/git/sfrench/cifs-2.6.git;a=commitdiff;h=6910ab30a29d10e0fec7710b2ed857a2201e2468)

And I will report here again, if the inode-patch resolves this issue


Sincerely
Chris


-- 
"With sufficient thrust, pigs fly just fine."  -- RFC 1925
:wq!