UP4 - Debian Bug#664842 Crashes my computer.

[BRedeemer]

After updating up to UP4 my computer crashes and becomes unresponsive at a black screen. It hasn't happened right in front of me, it usually becomes unresponsive while I'm out of the room.

uname -a
Linux warhorse 3.2.0-2-amd64 #1 SMP Sun Mar 4 22:48:17 UTC 2012 x86_64 GNU/Linux

The last entry in the syslog before i have to reboot is usually this:

Apr 28 08:31:54 warhorse kernel: [35080.491482] ------------[ cut here ]------------
Apr 28 08:31:54 warhorse kernel: [35080.491493] WARNING: at /build/buildd-linux-2.6_3.2.9-1-amd64-KTPapN/linux-2.6-3.2.9/debian/build/source_amd64_none/net/ipv4/tcp_input.c:3439 tcp_ack+0x71b/0x1658()
Apr 28 08:31:54 warhorse kernel: [35080.491498] Hardware name: System Product Name
Apr 28 08:31:54 warhorse kernel: [35080.491500] Modules linked in: mperf cpufreq_userspace cpufreq_stats cpufreq_conservative cpufreq_powersave parport_pc ppdev lp parport bnep rfcomm bluetooth rfkill binfmt_misc fuse loop dm_crypt dm_mod snd_hda_codec_hdmi nvidia(P) snd_hda_codec_realtek tuner_simple tuner_types wm8775 snd_hda_intel snd_hda_codec snd_hwdep tuner snd_pcm_oss snd_mixer_oss snd_pcm joydev snd_seq_midi cx25840 ivtv snd_rawmidi snd_seq_midi_event snd_seq cx2341x i2c_algo_bit v4l2_common videodev snd_timer snd_seq_device snd soundcore media snd_page_alloc v4l2_compat_ioctl32 edac_core edac_mce_amd k10temp tveeprom i2c_nforce2 i2c_core asus_atk0110 evdev pcspkr mxm_wmi psmouse button video serio_raw wmi processor ext4 mbcache jbd2 crc16 btrfs zlib_deflate crc32c libcrc32c usbhid hid sr_mod sd_mod cdrom crc_t10dif usb_storage ata_generic uas ahci libahci forcedeth firewire_ohci pata_amd firewire_core crc_itu_t libata scsi_mod ohci_hcd fan thermal thermal_sys ehci_hcd usbcore usb_common [last unloaded: sc
Apr 28 08:31:54 warhorse kernel: si_wait_scan]
Apr 28 08:31:54 warhorse kernel: [35080.491580] Pid: 0, comm: swapper/3 Tainted: P W O 3.2.0-2-amd64 #1
Apr 28 08:31:54 warhorse kernel: [35080.491584] Call Trace:
Apr 28 08:31:54 warhorse kernel: [35080.491586] <IRQ> [<ffffffff81046879>] ? warn_slowpath_common+0x78/0x8c
Apr 28 08:31:54 warhorse kernel: [35080.491596] [<ffffffff812bc7e7>] ? tcp_ack+0x71b/0x1658
Apr 28 08:31:54 warhorse kernel: [35080.491600] [<ffffffff812b9893>] ? tcp_validate_incoming+0x71/0x293
Apr 28 08:31:54 warhorse kernel: [35080.491604] [<ffffffff812be483>] ? tcp_rcv_established+0x4be/0x549
Apr 28 08:31:54 warhorse kernel: [35080.491609] [<ffffffff812c406e>] ? tcp_v4_do_rcv+0x166/0x323
Apr 28 08:31:54 warhorse kernel: [35080.491613] [<ffffffff812c5bd4>] ? tcp_v4_rcv+0x403/0x655
Apr 28 08:31:54 warhorse kernel: [35080.491618] [<ffffffff812aac03>] ? ip_local_deliver_finish+0x13Apr 28 11:37:29 warhorse kernel: imklog 5.8.6, log source = /proc/kmsg started.

the only google related item i could find on it was this:

http://lists.debian.org/debian-kernel/2 ... 00710.html

So it sounds like they hoping an update fixes it. Any idea what my workaround options are in the mean time?