On Tuesday 03 July 2007 14:29:18 Matthew Garrett wrote: > Suspend to RAM on a machine with / on a fuse filesystem turns out to be > a screaming nightmare - either the suspend fails because syslog (for > instance) can't be frozen, or the machine deadlocks for some other > reason I haven't tracked down. We could "fix" fuse, or alternatively we > could do what we do for suspend to RAM on other platforms (PPC and APM) > and just not use the freezer. > > Signed-off-by: Matthew Garrett <[email protected]> Note, though, that this won't help at all when people use the "suspend-to-ram instead of powering down after writing a hibernation image" feature in (uswsusp | tuxonice). Fuse is just a broken idea in the first place, but given that it exists, we still need to find the underlying cause. Regards, Nigel
Attachment:
pgpYyl3qlw2fj.pgp
Description: PGP signature
- Follow-Ups:
- Re: [PATCH] Remove process freezer from suspend to RAM pathway
- From: Benjamin Herrenschmidt <[email protected]>
- Re: [PATCH] Remove process freezer from suspend to RAM pathway
- From: Matthew Garrett <[email protected]>
- Re: [PATCH] Remove process freezer from suspend to RAM pathway
- References:
- [PATCH] Remove process freezer from suspend to RAM pathway
- From: Matthew Garrett <[email protected]>
- [PATCH] Remove process freezer from suspend to RAM pathway
- Prev by Date: Re: [PATCH 10/12] add module parameter for users who need more outstanding I/O
- Next by Date: Re: [PATCH 3/4] usb: allocated usb releated dma buffer with kmalloc_node
- Previous by thread: [PATCH] Remove process freezer from suspend to RAM pathway
- Next by thread: Re: [PATCH] Remove process freezer from suspend to RAM pathway
- Index(es):
 |