> I initially upgraded my kernel from 2.4.2-ac5 to 2.4.3 and the first thing I > noticed was that mysqld was stuck. Killing it left it hanging in a D state. > Then I tried 2.4.2-ac28 (which I am using now), and the got the same result. I'd expect that bit. 2.4.2-ac28 basically has the same new rwlock VM and behaviour as 2.4.3pre8. What would be really useful to know is if anyone can duplicate the problem non x86 > Can anyone reproduce this problem? Yes - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
