Messages in this thread | | | From | "Jim Crilly" <> | Date | Mon, 6 Feb 2006 16:07:36 -0500 | Subject | Re: [Suspend2-devel] Re: [ 00/10] [Suspend2] Modules support. |
| |
On 02/06/06 12:56:43AM +0100, Rafael J. Wysocki wrote: > > > > Oh. What's Pavel's solution? Fail freezing if uninterruptible threads > > > > don't freeze? > > > > > > Yes. > > > > > > AFAICT it's to avoid situations in which we would freeze having a > > > process in the D state that holds a semaphore or a mutex neded for > > > suspending or resuming devices (or later on for saving the image etc.). > > > > > > [I didn't answer this question previously, sorry.] > > > > S'okay. This thread is an ocotpus :) > > > > Are there real life examples of this? I can't think of a single time that > > I've heard of something like this happening. I do see rare problems with > > storage drivers not having driver model support right, and thereby causing > > hangs, but that's brokenness in a completely different way. > > > > In short, I'm wondering if (apart from the forking issue), this is a straw > > man. > > It doesn't seem to be very probable to me too, but I take this argument > as valid. > > Greetings, > Rafael
CIFS was good for that, if you have a CIFS filesystem mounted and take the network interface down (which I have my hibernate script do) before the filesystem is umounted it'll become impossible to umount the filesystem until the next reboot and I believe the cifsd kernel thread will be unfreezable. It's been a while since I've done that so it might be fixed now, but someone should verify it if it still exists and potentially work with the CIFS people to get it fixed.
Jim. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |