Comment 17 for bug 276641

Revision history for this message
Sergio Tosti (zeno979) wrote :

I've been used the proposed 2.6.24-23.46 kernel in a 4 nodes cluster for a period of about 40 days so I can confirm that the newer kernel resolves the oops.
Sergio