On May 30, 2005, at 13:31:07, Linus Torvalds wrote:
On Mon, 30 May 2005, Pekka Enberg wrote:
It is not just X. Running the following shell script when hitting the
bug:
Ok, this implies that the scheduler is really screwed up, we're not
scheduling anything else during that time.
If X is hung and not accepting data on any of its sockets, then this
could hang the Xterm in the background, and therefore hang the printout
from the "date" process. What happens if you do this?
Switch to VT 1:
# while true; do date; sleep 1; done
Switch to X and trigger hang
Switch back to VT 1 and look at output
Cheers,
Kyle Moffett
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a18 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$
L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$
r !y?(-)
------END GEEK CODE BLOCK------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
