Comment 7 for bug 218516

Revision history for this message
Steve Langasek (vorlon) wrote :

Chris, can you confirm that 2.6.24-17 resolves this problem for you in the environment where you're seeing it?