And another one: "mmcblk0: retrying because a re-tune was needed" static int mmc_blk_err_check(struct mmc_card *card, struct mmc_async_req *areq) { ... if (brq->data.error) { if (need_retune && !brq->retune_retry_done) { pr_info("%s: retrying because a re-tune was needed\n", req->rq_disk->disk_name); brq->retune_retry_done = 1; return MMC_BLK_RETRY; This looks like it'll spam the kernel log regularly if MMC/SD is used heavily with a UHS card, which (iirc) requires regular retunes. Why is this message at info level, and not debug level? -- RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/ FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. -- 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