Red Hat Bugzilla – Bug 165121
Starting X causes reboot
Last modified: 2007-11-30 17:11:11 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Fedora/1.0.6-1.1.fc4 Firefox/1.0.6
Description of problem:
Machine is small form factor SiS 550 chipset-based unit. Starting X causes the box to reboot. This did not occur under FC3, but has done so with every patch level of X for FC4, including the current rawhide -45.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run X.
2. Watch machine reboot.
Actual Results: Machine reboots
Expected Results: Machine displays X.
Will attach xorg.conf, lspci -vvv, and Xorg.0.log files.
Created attachment 117450 [details]
lspci -vvv of the affected machine
Created attachment 117451 [details]
Xorg.0.log of the affected machine
Created attachment 117452 [details]
xorg.conf of the affected machine
Note that the DRI and 3D acceleration portions have been commented out by hand.
The SiS 550 is in the SiS 315 family and has no hardware 3D acceleration.
This commenting out of these portions makes no difference - the machine still
From your Xorg.log:
> OS Kernel: Linux version 2.6.12-1.1398_FC4 (email@example.com)
> (gcc version 4.0.0 20050519 (Red Hat 4.0.0-8))
Would you please update the kernel to the latest rawhide ?
This one is compiled with gcc-4.0.0-8 which has a volatile issue and may cause
Latest rawhide kernel (2.6.12-1.1448_FC5) exhibits the same problem. Attached
please see another Xorg.0.log from this trial.
Created attachment 117498 [details]
Xorg.0.log from the latest rawhide Xorg and kernel
What is the last version of xorg known to work on your system ?
One regression between FC3 and FC4 was due to bug #163331.
Can you test xorg-6.8.2-45 without this patch ?
In case you don't want to recompile by yourself, I have put the binaries here:
Please test the recommendation in comment #7 and provide feedback.
Also, if the problem still exists with rawhide X, try using:
in the device section of the xorg.conf, and report back wether or not that
works around the issue you're having.
Setting status to "NEEDINFO_REPORTER" and waiting for feedback from
Please review comment #7 and 8 above and provide a response, even if you
can't immediately test this.
We do not have this hardware, and are unable to investigate this further
until we receive a response to the above queries.
Thanks in advance.
There have been 3 comments requesting testing and feedback since the last
time we have heard from the reporter of this issue, however there have not
been any feedback since August 5, 2005. Almost 5 months now.
Since we do not have this hardware, we require a response in order to
diagnose the problem further. At this point I would recommend that if
the problem still exists in Fedora development, which contains X11R7 now,
that a bug be filed directly to X.Org bugzilla at http://bugs.freedesktop.org
so that the SiS driver maintainer will be made aware of the problem and
can diagnose the issue directly.
Setting bug status to "CANTFIX".