BFS vs Tuxonice issue

Hi Nigel,

Did you have time to look into the BFS compatibility issue when 
multi-threaded compression is enabled?

With the current tuxonice 3.2.1 linux-3.3.2 from git I get the following 
error now (it's the same message repeated many many many times):

BUG: scheduling while atomic: BFS/2/0/0x00000002
Modules linked in: tun ehci_hcd w83627ehf hwmon_vid coretemp ipt_REJECT 
ipt_LOG xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack 
xt_multiport ipv6 iptable_filter ip_tables x_tables vboxdrv(O) loop 
joydev gspca_pac207 gspca_main videodev v4l2_compat_ioctl32 usbhid 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_emu10k1 
snd_hwdep snd_util_mem snd_ac97_codec ac97_bus snd_rawmidi 
snd_seq_device snd_hda_codec sr_mod xhci_hcd usbcore 8250_pnp 8250 
serial_core emu10k1_gp gameport snd_pcm processor snd_page_alloc 
snd_timer snd soundcore usb_common i2c_i801 thermal_sys button [last 
unloaded: ehci_hcd]
Pid: 0, comm: BFS/2 Tainted: G      D    O 3.3.2+ #24
Call Trace:
  [<ffffffff813f2c3f>] __schedule_bug+0x55/0x59
  [<ffffffff813f8e6a>] schedule+0x9f/0xb2e
  [<ffffffff813fa2ad>] ? _raw_spin_unlock_irqrestore+0x28/0x2a
  [<ffffffff8103f8a0>] ? __hrtimer_start_range_ns+0x25d/0x26f
  [<ffffffff8103f8d6>] ? hrtimer_start_range_ns+0xf/0x11
  [<ffffffff81000817>] cpu_idle+0xab/0xb4
  [<ffffffff813ee551>] start_secondary+0x1ca/0x1cf

Apart from these error messages there seem to be no other negative 
effects. These errors did not occur when using tuxonice+linux-3.3.0 
(same configuration).

ProcSetting no_multithreaded_io 1
ProcSetting no_flusher_thread 1

BTW: It's a pity they turned around the snapshot/atomic copy 
reading/writing. Now the nice tuxoniceui is only visible for a very 
short time (atomic copy) when resuming. But as long as it works, one 
should not complain...

Thanks for keeping tuxonice up-to-date.

Harald

-- 
`Experience is the best teacher.'