conserver freezes when console presents binary data?

Hi!

We seem to be having this problem concerning binary data shoved out a
console and though conserver making conserver freeze.  When this happens
taking a kernel stack trace, conserver looks like this:

Apr 14 10:03:14 xoff kernel: conserver     S 00000001     0 24243      1 24244          2371 (NOTLB)
Apr 14 10:03:14 xoff kernel: Call Trace:   [<c0155a67>] __alloc_pages [kernel] 0x97 (0xf2b11e8c)
Apr 14 10:03:14 xoff kernel: [<c01232f4>] schedule [kernel] 0x2f4 (0xf2b11ea0)
Apr 14 10:03:14 xoff kernel: [<c0133e3c>] schedule_timeout [kernel] 0xbc (0xf2b11ee4)
Apr 14 10:03:14 xoff kernel: [<c024aaa6>] tcp_poll [kernel] 0x36 (0xf2b11ee8)
Apr 14 10:03:14 xoff kernel: [<c021e43c>] sock_poll [kernel] 0x2c (0xf2b11f08)
Apr 14 10:03:14 xoff kernel: [<c01753bb>] do_select [kernel] 0x13b (0xf2b11f1c)
Apr 14 10:03:14 xoff kernel: [<c017585e>] sys_select [kernel] 0x34e (0xf2b11f60)
Apr 14 10:03:14 xoff kernel: 
Apr 14 10:03:14 xoff kernel: conserver     S 00000000  1484 24244  24243         24247       (NOTLB)
Apr 14 10:03:14 xoff kernel: Call Trace:   [<c01232f4>] schedule [kernel] 0x2f4 (0xe0f97e44)
Apr 14 10:03:14 xoff kernel: [<c01b2412>] tty_wait_until_sent [kernel] 0xc2 (0xe0f97e5c)
Apr 14 10:03:14 xoff kernel: [<f8afcb14>] cy_port [cyclades] 0x1214 (0xe0f97e78)
Apr 14 10:03:14 xoff kernel: [<c01239f2>] interruptible_sleep_on [kernel] 0x52 (0xe0f97e88)
Apr 14 10:03:14 xoff kernel: [<f8afcb18>] cy_port [cyclades] 0x1218 (0xe0f97e94)
Apr 14 10:03:14 xoff kernel: [<f8afcb18>] cy_port [cyclades] 0x1218 (0xe0f97e98)
Apr 14 10:03:14 xoff kernel: [<f8afc990>] cy_port [cyclades] 0x1090 (0xe0f97eb0)
Apr 14 10:03:14 xoff kernel: [<f8af2399>] cy_close [cyclades] 0x4f9 (0xe0f97eb8)
Apr 14 10:03:14 xoff kernel: [<f8afb820>] cy_card [cyclades] 0x0 (0xe0f97ebc)
Apr 14 10:03:14 xoff kernel: [<c01ad9ba>] release_dev [kernel] 0x61a (0xe0f97ee8)
Apr 14 10:03:14 xoff kernel: [<c021ded8>] sock_recvmsg [kernel] 0x58 (0xe0f97f08)
Apr 14 10:03:14 xoff kernel: [<c021e006>] sock_read [kernel] 0x96 (0xe0f97f50)
Apr 14 10:03:14 xoff kernel: [<c01ade42>] tty_release [kernel] 0x32 (0xe0f97f6c)
Apr 14 10:03:14 xoff kernel: [<c01617ba>] __fput [kernel] 0xea (0xe0f97f78)
Apr 14 10:03:14 xoff kernel: [<c015f93e>] filp_close [kernel] 0x8e (0xe0f97f94)
Apr 14 10:03:14 xoff kernel: [<c015f9e6>] sys_close [kernel] 0x66 (0xe0f97fb0)
Apr 14 10:03:15 xoff kernel: 
Apr 14 10:03:15 xoff kernel: conserver     S 00000001     0 24247  24243 24248         24244 (NOTLB)
Apr 14 10:03:15 xoff kernel: Call Trace:   [<c0155a67>] __alloc_pages [kernel] 0x97 (0xf4349e8c)
Apr 14 10:03:15 xoff kernel: [<c01232f4>] schedule [kernel] 0x2f4 (0xf4349ea0)
Apr 14 10:03:15 xoff kernel: [<c0133de5>] schedule_timeout [kernel] 0x65 (0xf4349ee4)
Apr 14 10:03:15 xoff kernel: [<c0133d70>] process_timeout [kernel] 0x0 (0xf4349f04)
Apr 14 10:03:15 xoff kernel: [<c01753bb>] do_select [kernel] 0x13b (0xf4349f1c)
Apr 14 10:03:15 xoff kernel: [<c017585e>] sys_select [kernel] 0x34e (0xf4349f60)

So, the conserver process seems "frozen" in that any console commands
seem to hang.  I assume that's cause it's locked waiting for tty
operations.

So my question is: is this expected or possible buglet fodder?  I'm
thinking that just telling conserver to strip the 7th bit shoudl hopefully
make this go away, but any guidance folks could share would be much
appreciated.

This is conserver 8.1.3 on Red Hat Enterprise Linux Workstation 3 Update 1.
Hardware is a Compaq DL350 Tower with 1 HT'ed CPU and 1GB RAM

-n
-- 
-------------------------------------------
nathan hruby <nhruby@uga.edu>
uga enterprise information technology services
production systems support
metaphysically wrinkle-free
-------------------------------------------