Tuxonice + BFS?
Harald Judt <[email protected]>
| Newsgroups | gmane.linux.swsusp.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi, Out of interest, I've tried to get tuxonice and Con Kolivas' BFS patch running (linux-3.1-rc2). As long as compression is not used, everything works fine. As soon as I turn on compression (lzo or lzf), I get some errors -22 on resuming (or some byte count mismatch with lzf). I can get tuxonice + compression + bfs to work correctly when I revert the following two commits (and leave no_flusher_thread = 1): 3eaa98fda1f9d6727ab2862bf83c9bcfd8c83789: Fix progress update with flusher thread. c2a116d1236344e6ce2556bbc674489ee5d2f703: Start/stop I/O worker threads outside of freezer Actually, it's c2a116d which causes the problem. I think the commit should fix the hangs when using no_flusher_thread=0? Any idea what's going on here? Why does this cause problems with BFS but work fine with the default kernel scheduler? Harald -- `Experience is the best teacher.'