On Thu, 2005-04-28 at 13:05, Nigel Cunningham wrote: > > On Wed, 2005-04-27 at 17:53, Nigel Cunningham wrote: > > > > Sorry for raising the problem again after a long time. I got > some > > > > reports about ' xxx not stopped' at suspend time. The general > cause > > > is > > > > one task is waiting for another task which has been into > > > refrigerator > > > > first. Report an error and stop suspend can't solve the problem. > > > After > > > > the task's dependent task is released from refrigerator, the > task > > > itself > > > > will soon go into refrigerator and will never be waked up. > > > > Nigel's refrigerator patch half solves the problem. It distinct > > > kernel > > > > tasks and user tasks, so can solve the dependence between kernel > > > tasks > > > > and user tasks, but can't solve the user tasks dependence. > Right, > > > Nigel? > > > > > > That's right, but the example you give below is userspace > (syslogd) vs > > > kernel space (kjournald), so I wonder if something could be wrong > with > > > your implementation. > > Right, my example can be solved with your patch. But I'd like a more > > generic solution to solve all the dependences, like user space tasks > > dependencies. > > Do you have a particular example in mind? I haven't seen or heard of > any > freezing failures in Suspend2 for ages, so I'm struggling to see what > is > lacking. No, actually. Maybe I should send the proposal till I really find a case :). I only noticed the syslogd case. Somebody reported the 'mdnsresponder' process case, but didn't look at it yet. http://bugme.osdl.org/show_bug.cgi?id=3964 Thanks, Shaohua
