Back to BFS+TOI issue

Oleksandr Natalenko <[email protected]>
Newsgroups gmane.linux.swsusp.devel
Message-ID <[email protected]>
Hi all.

I mailed Con Kolivas about TOI+BFS issue and he answered that won't fix
it as BFS is written to get mainline hibernation work but not TOI. He is
surprised that BFS+TOI works *somehow*.

The only quote about technical reason is:

"I suspect that something to do with the way the
compression threads are woken up on resume is broken when run on BFS."

So the last hope is Nigel.

As BFS+TOI users community is large enough, I expect it to help solving
the issue at least by providing debug info. We really need these
3rd-party patches work together.

For now, I discovered that LZO fails as well as LZF does, but with
different error.

In case of LZF it fails at tuxonice_compress.c:257 (outlen != PAGE_SIZE).

In case of LZO it fails at tuxonice_compress.c:254 (ret), and also at
tuxonice_io.c:645 (io_pageset == 1).

So crypto_comp_decompress call at tuxonice_compress.c:245 fails. Why —
no idea. I cannot investigate it deeper because of lack of knowledge
about kernel internals.

Nigel, help us if you can. Hope you HDDs are up and spinning .

Regards,
  Oleksandr "post-factum" Natalenko, B.S.
  http://pf.natalenko.name/

_______________________________________________
TuxOnIce-devel mailing list
[email protected]
http://lists.tuxonice.net/listinfo/tuxonice-devel
signature.asc (application/pgp-signature, 554 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPWT7QAAoJELftKrVLdx04VkoH/2WB6YwkJ+F5V2fdHCmxvons
Uk0gLbDbCIdlVGYfCfBJwMnqvlEHAm5pyVxR/xky4+KfBeRQCgeQUTSlplGJZYLv
2fwW8WXRHH3MdLuXHV+3Qg+b9r3SijVYrAJms7/2cf+tFMeqzQ7anv9UC85orbWo
pTyG3tqZG3fg0feKsHBRRpePtgJBCQoSDNltiUK8izbM2McDrxTHBjwbu6xjsag0
3gypG0YQY37bxANoejyhCIotP9HzslYuYWJvYQg/VDkVlxPoTerNj7/IMnqZqfUa
RVLN9rsS2XJp+bUIcSZ+ifU2z9uFHhB7ZUxtA9z+X1ELW9q6Udbi9Y1ISdmDjK8=
=Cb87
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.