Cc: Vegard Nossum <vegard.nossum@...>, Alan Cox <alan@...>, Alan Cox <alan@...>, David Newall <davidn@...>, Willy Tarreau <w@...>, Harald Dunkel <harald.dunkel@...>, <linux-kernel@...>
...
In fact, in various laptops (Eeeepc, dell inspiron 1520, Dell inspiron
4000), I've got various tty screwups that have been introduced since
circa 2.6.19.
The 6 year old inspiron 4000 gets stuck at stty erase ^? . Randomly, but
most of the time.
All of my machines exhibit the ctrl-C being slower than ctrl-Z discussed
elswhere (I've almost developed a habit of typing ctrl-Z kill %1 <RET>).
Although even ctrl-Z recently has been reluctant to always work. I wonder
if this is the cause of dpkg recently not responding to ctrl-Z's? (debian
bug #486222). dpkg does respond to kill -STOP
ctrl-s doesn't always work anymore. Again, what prompted me to write this
email, was I couldn't pause dpkg. It's particularly unreliable at
stopping scrolling messages at bootup, and if I press it at the wrong time
at bootup (not a specific place - it can be starting up any number of
scripts), something deadlocks and won't resume upon a ctrl-q.
alt-sysrq-k is enough to kill whatever has deadlocked. I have a feeling,
but don't want to test on this system right now, that pressing scroll-lock
as opposed to ctrl-q once unlocked such a stuck display.
In summary, something in tty is certainly screwed. Does anyone see a
connection between all of these?
--
TimC
Electromagnetic pulse received (core dumped)
--
