Laine Walker-Avina <lwalkera@xxxxxxxxx> writes: > On Wed, Sep 22, 2010 at 3:21 PM, Laine Walker-Avina <lwalkera@xxxxxxxxx> wrote: >> On Tue, Sep 14, 2010 at 4:02 PM, Kevin Hilman >> <khilman@xxxxxxxxxxxxxxxxxxx> wrote: >>> Laine Walker-Avina <lwalkera@xxxxxxxxx> writes: >>> >>>> I just pulled the latest changes today from the linux-omap git tree, >>>> and something appears to have broken suspend to RAM on my OMAP3503 >>>> board. >>> >>> Is this on the master branch? What defconfig? When was this last >>> working for you? -rc3? >> Yes, on the master branch. I'm using my own config. It was working on >> 2.6.35 or so. I tried backporting my board patches to 2.6.36 and it >> fails there too now for some reason. It might be the SD card, I'll >> have to find another one and try it out. >>> >>> Looks like you may have your rootfs on MMC. Do you have >>> CONFIG_MMC_UNSAFE_RESUME=y in your .config? >> No [...] > > This appears to be caused by commit 4c2ef25f (mmc: fix all hangs > related to mmc/sd card insert/removal during suspend/resume). Enabling > CONFIG_MMC_UNSAFE_RESUME seems to fix it. Good. > Ideally, it would be nice to have the root file-system on a mmc > regardless of whether or not it's removable or not. You'll have to take that one up with the MMC core. I'm sure they would welcome patches to fix it. ;) Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
