On Wed, 10 Apr 2002, K. Petersen wrote: >I have come upon a reproducible lockup on my system when switching from a >console virtual terminal to X. It can be produced as follows: > >Begin X >Switch back to a virtual console >Switch back to X > >This causes the X display to appear on the screen, with a strip along the >top deformed. In this state, the X server is unresponsive to >ctrl-alt-backspace, and I am unable to switch to any other virtual >terminals. However, I can still log in remotely. >Using alt-sysreq-k, the display then changes colors, to what I believe >might be a lower color palatte, but cannot be certain of. After this, I >am then able to switch virtual terminals, log in as root, run mode3, and >have the display restored. >At this point, vc/7 has not been restored to an unused state. Instead >there is any text I typed while the display was locked, followed by a >blinking cursor. >If I now attempt to restart X, the system will lock completely. The >monitor will go into power saving mode, the keyboard is unresponsive, and >I am unable to log in remotely. > >I hope this has been a reasonably thorough description of the problem, now >my hardware and software configuration. > >Hardware: >ATI Radeon 64DDR >AMD AthlonMP in SMP configuration >AMD 760MP chipset on a Tyan S2460 Motherboard > >Software: >Linux kernel 2.4.18 >Latest DRI cvs, with kernel module from the dri > >This problem has occurred since X410, and kernel versions back at least >through 2.4.16, both with kernel DRM, and the DRM provided with the DRI. >I should also note that this only occurs when DRI is enabled. There is no >problem switching between X and other virtual terminals when DRI is >disabled. > >I believe this to be the correct forum for this issue, but if it is not, >then feel free to forward me to the linux kernel lists or whatever's more >appropriate. > >I thank you in advance for your assistance,
We have massive reports of VT switching hangs in XFree86 4.2.0 with almost all Radeon hardware, but with other hardware as well. This problem has occured aparently since the prereleases 4.1.99.* and up through to the final release of 4.2.0. The kernel version doesn't seem to make any difference. As I understand, the Radeon is not being initialized properly or restored properly, however it occurs on other hardware as well. The problem seems common enough that I'm surprised it has not been determined yet, althought it seems that it is not one problem, but is more likely individual problems in different drivers, and the kernel isn't ruled out either. I've tried debugging it myself but have yet to determine the problem or a solution. -- Mike A. Harris Shipping/mailing address: OS Systems Engineer 190 Pittsburgh Ave., Sault Ste. Marie, XFree86 maintainer Ontario, Canada, P6C 5B3 Red Hat Inc. http://www.redhat.com ftp://people.redhat.com/mharris _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
