Using a custom-compiled kernel 2.6.18 (has to be custom - or it won't boot on this crypto'ed machine), I have exactly the same symptoms (plus other unrelated trouble trying to resume-from-ram). I don't think it is kernel-related. Actually, I realize that it dies when I'm within screen with TERM=screen.linux as fare, but not when I am in a session outside of screen, when I override TERM with "screen" or "linux", or run as root or a different user in screen. Note that screen.linux is defined in $TERMCAP (that is the same in both working and non-working sessions). Something is fishy, possibly in cmucl's TERM handling. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Wealth, like happiness, is never attained when sought after directly. It comes as a by-product of providing a useful service. -- Henry Ford