Re: maxtroxfb deadlock (and generic fbcon race?)
Petr Vandrovec Ing. VTEI (VANDROVE@vc.cvut.cz)
Mon, 18 Jan 1999 10:51:10 MET-1
> At 640x480x8 (I haven't tried others), if I cause alot of output (while
> true; do cat /usr/src/linux/*/*.c; done) and switch consoles rapidly, I
> get a deadlock after about 10 seconds.
I tried it here (PII/350MHz, G200 and Millenium I), on my both matroxes,
and it survived about 3 minutes of switching. With hardware cursor and
acceleration. Are you using hardware or software cursor (software cursor
is flashing block, hardware cursor is by default small flashing underline)
> If I do something similar (lots of output on the current console, switch to
> another console) with vesafb, text intended for the previous
> (heavy scrolling) console will sometimes end up on the current
> console, or the cursor will be in the wrong place (I just tried this on
> another box (p100 running 2.1.132ac3, s3 virge video), and got the same
> result). I think that the problem I am experiencing with vesafb is not
> specific to vesafb. 2.1.109ish I had something like this happen with
> sbusfb (sparc).
I hope that since 2.1.109 there was couple of bugfixes, some of them
were related to console switching.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
Please read the FAQ at http://www.tux.org/lkml/