Re: Adding set_freezable() to xfs_trans_ail.c breaks suspend to RAM
Andrey Rahmatullin <[email protected]> Sat, 23 Feb 2013 04:54:50 +0600
| Newsgroups | gmane.linux.swsusp.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Feb 21, 2013 at 10:54:39AM +0200, Oleksandr Natalenko wrote: > We've discovered that adding set_freezable() cal to xfs_trans_ail.c makes > hibernation impossible. Commenting that call results in successful suspending. > > Whose issue is that? XFS or TuxOnIce? Or kernel freezer? > > The whole discussion could be read here: > > http://pf.natalenko.name/forum/index.php?topic=196 > > Another question — is it safe to remove set_freezable() call from FS code? I've just tried ToI on 3.8 and it doesn't hibernate, with xfsaild/dm-* refusing to freeze. Is this the same issue? On the other hand, the patch that fixed XFS OOPSes doesn't apply anymore and I can't resume for several months even with it, so it probably doesn't matter. swsusp works, of course. -- WBR, wRAR _______________________________________________ TuxOnIce-devel mailing list [email protected] http://lists.tuxonice.net/listinfo/tuxonice-devel
signature.asc
(application/pgp-signature, 836 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJRJ/c1AAoJEDNi9wMaSZLhIDsP+wdLm+Hwgi8zg2OxYUcwZTzI gPUME0Yj3+h9szrzcIdiEuVOdqgLAgalP6reBlI7CmoHsNCa4XFm9Aa7sK3jYNwM 7goooUKNOIx6OVmmwwwQ0/SsAnyo5D9itFIs701+bmYkFYN9ZfPe0YrbmNSUO4dJ qcuHjn3QBVGBSAZwze+YE1MbqdzRtjosM+fruRU3C8iRhtthd3SE+/4HG1df8IIc 5yfYrbmxPI/yAAFbrI7brI2Tcc/IHabSqWqPX4e1P0w6oOEBjj9H4LvaFxdL2u8k JTygX/FnfhJClxt4SUvDM2byg3l43kckM4VrDz2QMjMU3AodftJGPVT7BSqdoFWd KuyacERE7fBny/VQPwgluBiU/epkSYtDWTttWwTKO4l+75Scqq3GB7IN+GOZ9ohJ 6sVpffZPeWLB0MFc4VnybbZyIaBmDXTEaOb09pkp6nGcKsZP1Va88W5Lr6FdyJjH ZtU7Hpn4Hx6AWW0FbzKkff6oYtEzxg2sQbuTONhngwGJkYA0PauO/WRB8MQ5x/pf RBgjXVkwVgzn6P17ATGZyQ+PKj27EEblco082G6DAOgMc+T/2JRtOLJKeqgIu3Vd 68+j79a9a6qknWVJMgPipiteSKFgWuWNdlVhiT2/LO+s9qvYKDJxb+zen5Rme0FM doDQagZrdj3FffC+aBlt =Clhc -----END PGP SIGNATURE-----