Bug 133991 - Unable to debug random X failures
Summary: Unable to debug random X failures
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: anaconda   
(Show other bugs)
Version: 4.0
Hardware: i686
OS: Linux
Target Milestone: ---
: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2004-09-28 20:52 UTC by Matthew Booth
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-28 21:11:16 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

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)

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:

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.

Note You need to log in before you can comment on or make changes to this bug.