Bug 5842

Summary: Switching to text console and back hangs X server
Product: xorg Reporter: Pawel Salek <pawsa-gpa>
Component: Driver/SiSAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED MOVED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: high CC: ildar
Version: 7.0.0   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
xorg.conf
none
Xorg.0.log before the hang
none
Xorg.0.log-after-hang (observe the corruption of the first line) none

Description Pawel Salek 2006-02-09 02:24:52 UTC 
It appears that this is probably a bug in the SiS driver not
saving/restoring properly. Switching the virtual console to text mode and back
leaves the Xorg process unresponsive and the screen white. This problem has
appearead in Fedora rawhide in the last month, I believe. The box as such is
alive and one can connect via ssh to it. See also 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=180465 for the original report.

After the hang, the Xorg process gets stuck. It utilizes 100% CPU. When I
connect gdb to Xorg, I get following stack trace:
(gdb) where
#0  0x00000036286bd900 in __write_nocancel () from /lib64/libc.so.6
#1  0x0000003628667793 in _IO_new_file_write () from /lib64/libc.so.6
#2  0x0000003628668bef in _IO_new_file_xsputn () from /lib64/libc.so.6
#3  0x000000362865e89b in fwrite () from /lib64/libc.so.6
#4  0x00000000005666a2 in LogVWrite ()
#5  0x000000000056717d in LogVMessageVerb ()
#6  0x0000000000481f2c in xf86VDrvMsgVerb ()
#7  0x00002b59ab2893c2 in sisRestoreExtRegisterLock ()
   from /usr/lib64/xorg/modules/drivers/sis_drv.so
#8  0x00002b59ab28b2f5 in sisSaveUnlockExtRegisterLock ()
   from /usr/lib64/xorg/modules/drivers/sis_drv.so
#9  0x00002b59ab28f4d9 in SiS_SetSISTVedgeenhance ()
   from /usr/lib64/xorg/modules/drivers/sis_drv.so
#10 0x00002b59ab29b3cd in SISAdjustFrame ()
   from /usr/lib64/xorg/modules/drivers/sis_drv.so
#11 0x00002b59ab29b850 in SISAdjustFrame ()
   from /usr/lib64/xorg/modules/drivers/sis_drv.so
#12 0x00002b59ab5fa69b in xf86ForceHWCursor ()
   from /usr/lib64/xorg/modules/libramdac.so
#13 0x000000000047f7d1 in xf86InitFBManagerArea ()
#14 0x000000000048c152 in xf86XVScreenInit ()
#15 0x0000000000479714 in xf86Wakeup ()
#16 0x000000000044e2a5 in WakeupHandler ()
#17 0x0000000000559cb4 in WaitForSomething ()
#18 0x000000000044a33a in Dispatch ()
#19 0x0000000000432c95 in main ()
Comment 1 Pawel Salek 2006-02-09 02:25:18 UTC 
Created attachment 4580 [details]
xorg.conf
Comment 2 Pawel Salek 2006-02-09 02:25:53 UTC 
Created attachment 4581 [details]
Xorg.0.log before the hang
Comment 3 Pawel Salek 2006-02-09 02:26:54 UTC 
Created attachment 4582 [details]
Xorg.0.log-after-hang (observe the corruption of the first line)
Comment 4 Daniel Stone 2007-02-27 01:30:22 UTC 
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 5 Brice Goglin 2007-05-27 01:55:20 UTC 
Nicola Girardi reported another problem about switching to console and back to X with the Sis driver. It looks like a freeze instead of a crash as reported here, but at least it confirms that the Sis driver has problems in this area, even with latest 0.9.3 release.

He was using the following board:
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760/761 PCI/AGP VGA Display Adapter

See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375553 for details.
Comment 6 Ildar Muyukov 2013-06-17 07:59:49 UTC 
https://bugs.freedesktop.org/show_bug.cgi?id=15190 might help.
Comment 7 GitLab Migration User 2018-08-10 20:47:11 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-sis/issues/1.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.