On 03/07/2010 07:46 AM, Pasi Kärkkäinen wrote:
On Fri, Mar 05, 2010 at 05:07:53AM -0600, Mike Christie wrote:
On 03/01/2010 08:53 PM, Mike Christie wrote:
On 03/01/2010 12:06 PM, bet wrote:
1. Based on my timeouts I would think that my session would time out
Yes. It should timeout about 15 secs after you see
> Mar 1 07:14:27 bentCluster-1 kernel: connection4:0: ping timeout of
> 5 secs expired, recv timeout 5, last rx 4884304, last ping 4889304,
> now 4894304
You might be hitting a bug where the network layer gets stuck trying to
send data. I attached a patch that should fix the problem.
It looks like we have two bugs.
1. We can get stuck in the network code.
2. There is a race where the session->state can get reset due to the
xmit thread throwing an error after we have set the session->state but
before we have set the stop_stage.
The attached patch for RHEL 5.5 should fix them all.
Will this patch be in the next RHEL 5.5 beta kernel? Easier to test if there's
no need to build custom kernel :)
I am not sure if it will be in the next 5.5 beta. It should be in 5.5
though. Do you have a bugzilla account? I made this bugzilla
You can add yourself to it and when the patch is merged you will get a
notification and a link to a test kernel.
If you do not have a bugzilla account, just let me know and I will ping
you when it is available in a test kernel.
You received this message because you are subscribed to the Google Groups
To post to this group, send email to open-is...@googlegroups.com.
To unsubscribe from this group, send email to
For more options, visit this group at