Hi, On the past, the write timeout was increased from 300 ms to 3 seconds (see commit 3bdc9ba892d6a294d16e9e6e0c4041926aa3d58c from Paul Walmsley) as some cards had issues with that limit, which is correct as the issue can be reproduced by me. Increasing that timeout solves the problem, however increasing the timeout to 3 seconds is a bit too much and following error message occurs in the kernel log: mmc1: Too large timeout requested for CMD25! Empirically using 2 seconds for the 3.4.x kernel works fine. On a 2.6.24 kernel, the timeout was reduced to 1.5 s to avoid the message. Can someone tell me on what basis was the timeout set to 3s? Was it also empirically deduced? Would it make sense to reduce the timeout? Regards, -- ________________________________ Juan Carlos Garza -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
