Messages in this thread | | | Subject | 2.0.30 consoles locking | Date | Tue, 29 Apr 1997 11:49:47 +0200 (MET DST) | From | Rafal Maszkowski <> |
| |
I don't know how to reproduce the problem but I managed to lock 3 consoles already. They just stop and screen attached to it waits in D state, it looks like some unrelated processes (or related via lock files common with those of processes locked together with screen) are getting block too. Console locking may be somehow connected with unintentional CTRL-S pressing. 2 of the 3 stopped with ScrollLock on which means stopped by CTRL-S. It is not possible to unlock it with CTRL-Q. I was using .29, .28 and some other 2.0 kernels without such problems. I don't exclude hardware problems (I do have incorrectly connected SCSI CDROM, I'm not using it now though) but I doubt anything in the hardware can matter.
gcc 2.7.2.1 (changed recently), libc 5.4.23, binutils 2.7.0.3 (could it be this?), modutils 2.1.34
R. -- Rafal Maszkowski rzm@torun.pdi.net http://www.torun.pdi.net/~rzm Opinia publiczna powinna byc zaalarmowana swoim nieistnieniem - St. J. Lec
| |