On Saturday 14 June 2008 11:30:50 Andy Green wrote: > Somebody in the thread at some point said: > |> Despite we made some real progress in fact the whole suspend / resume > |> thing remains extremely fragile due to probably just one or two more > |> monsters in the deep shadows we never understood yet. And they're the > |> kind of monsters that attack if you go hunting for them: > |> no_console_suspend on the kernel commandline kills resume the same way > |> as mdelay() in glamo suspend stuff, and equally with no real trace of > |> how or why it blew chunks. > | > | It works for a few times, then seems to crash. If I comment out the > | dev_info ()and msleep() calls in pcf50633_work it seems to be OK. Also, > > OK I think I just had a "major breakthrough in understanding" why > suspend action can be time-critical :-)
cool.
