On Wednesday, January 30, 2013 11:17:06 PM Jiri Slaby wrote: > On 01/30/2013 10:39 PM, Rafael J. Wysocki wrote: > >> What is cool is that I have steps to reproduce: > >> 1) boot > >> 2) run the attached script (turn on all possible power savings -- in > >> fact everything what powertop suggests) > >> 3) suspend to _disk_ (mem is not enough, BIOS apparently has to > >> interfere here) > > > > No, I don't think it's the BIOS. Most likely the boot kernel. > > Or that... > > >> 4) resume from disk > >> 5) boom > >> > >> I tried to remove also wireless drivers, no change. > > > > Is the resume boot kernel the same as the one in the image? > > Yeah, the same ones: 3.7.5
Well, I guess that we leak some state from the boot kernel to the image kernel. I have no idea what it is, but I suspect something arch-specific. I wonder what the affected systems have in common apart from e1000e? Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
