From: Bill Gatliff <bgat@bi...> - 2006-10-18 02:43:01
Bear with me, this one is a bit tricky to describe... :)
I'm testing a 2.6.12 kernel and a 126.96.36.199 kernel, and a few in between,
and they all do it. All on ARM targets: PXA255 with onboard LCD
framebuffer, and AT91RM9200 with an S1D13xxx framebuffer. Duplicated
with Qt 4.x and SDL 1.2-debian.
The first time I start up a framebuffer-based application, say Qt or
Antigrain/SDL, things appear to go fine. But if I abort said program
with a CTRL-C and restart it, then the application appears to start up
fine but there's no screen output. I don't see any output until I do a
CTRL-Z and then restore the program to the foreground with "fg". Then
the screen clears and things start drawing as usual. The screen also
draws if I do a CTRL-C instead of -Z, but then the program aborts as you
If I'm running the program under strace then the screen never recovers
whether I do a CTRL-Z or not. I see the code hanging in an
ioctl(KGDKBENT) on /dev/tty8.
Honestly, I'm totally stumped. Anyone have any suggestions?