Bug 133991

Summary: Unable to debug random X failures
Product: Red Hat Enterprise Linux 4 Reporter: Matthew Booth <mbooth>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED WONTFIX QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: nobody+pnasrat
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-09-28 21:11:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Matthew Booth 2004-09-28 20:52:05 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Gecko/20040922

Description of problem:
I have tried to install RHEL4 beta 1 on 2 different machines now and
experienced X failures. After probing for video, monitor, mouse the X
server fails to start. The two machines have very different hardware,
including different graphics cards (matrox and nvidia). On the second
machine, I ran the installer and X failed, I allowed it to reboot and
did exactly the same again and X did not fail.

I am unable to debug the failures, because immediately they have
occurred anaconda exists. An X log which might give a clue to the
cause is reported to have been written to /tmp/X.log, but I am unable
to access it.

Version-Release number of selected component (if applicable):


How reproducible:
Sometimes

Steps to Reproduce:
1. Start installing RHEL4 Beta 1.
2. Hope that X fails to start this time.
    

Actual Results:  System exits.

Expected Results:  System allows an opportunity to examine log files
from failed X startup.

Additional info:

Comment 1 Jeremy Katz 2004-09-28 21:11:16 UTC
Booting with 'linux nokill' will let you access things. 
Unfortunately, we have to kill processes to be able to unmount
filessystems and let you reboot cleanly in most cases.