Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 147316 - Blue Screen of Death
Summary: Blue Screen of Death
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11
Version: 3
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: FC5Target
TreeView+ depends on / blocked
 
Reported: 2005-02-07 06:36 UTC by Joe Zwerko
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version: Fedora Core 4
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-08-30 07:45:56 UTC


Attachments (Terms of Use)
Xorg config file (deleted)
2005-02-08 21:48 UTC, Joe Zwerko
no flags Details
Xorg log file (deleted)
2005-02-08 21:49 UTC, Joe Zwerko
no flags Details
/var/log/messages (deleted)
2005-02-08 21:50 UTC, Joe Zwerko
no flags Details
lsmod output (deleted)
2005-02-08 21:50 UTC, Joe Zwerko
no flags Details
lspci -vvn output (deleted)
2005-02-08 21:51 UTC, Joe Zwerko
no flags Details

Description Joe Zwerko 2005-02-07 06:36:18 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; 
SV1; .NET CLR 1.1.4322)

Description of problem:
After installing, after dealing with the fact that Fedora Core 3 
doesn't recognize a PS/2 mouse (another issue), I cannot boot without 
a blank, blue screen.

I can ctrl-alt-F1 to get a text console, but there's no way I can 
find to kill the evil X-server and start it myself. I kill it, and it 
starts right back up with the BSOD.

I really, really, don't want to go back to Mandrake Linux, but the 
Fedora BSOD leaves me with little choice.


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

How reproducible:
Always

Steps to Reproduce:
1. Install Fedora core 3
2. Reboot
3. Shake fists at the uncaring gods
    

Actual Results:  BSOD

Expected Results:  A graphical or text prompt to log in.

Additional info:

Pentium 4, 3.0 GHz HT
Gigabyte GA-8KNXP motherboard
Abit (NVidia) 5600 ultra OTES Siluro graphics

Comment 1 Warren Togami 2005-02-07 06:50:47 UTC
It sounds like you are running into a legitimate bug with the video,
but  it is also partially a user problem.  Edit /etc/inittab and find:
id:5:initdefault:

Change that number to 3, and it will boot into text mode.  From there
you can manually startx into a graphical desktop.

Reassigning bug to xorg-x11.  They will probably close this as
duplicate of another bug, because there really isn't anything we can
do with no debugging information, logs, etc.

Comment 2 Sitsofe Wheeler 2005-02-07 09:01:49 UTC
Are you using nvidia binary drivers or the stock FC3 nvidia driver?

Comment 3 Mike A. Harris 2005-02-08 02:42:10 UTC
Install FC3 using text mode install.  Once the OS is installed,
run "system-config-display --reconfig" to generate a fresh X.Org
config file.  Also, edit /etc/inittab and change initdefault to
3 as suggested by Warren above, then use "startx" to start a new X
session.

After you've invoked X with the new config, please update the bug
report with the results.  Also attach your X server log file and
config file, /var/log/messages, and the output of "lsmod" and
"lspci -vvn".

Once you've attached this information to the bug report, we will
review it and try to troubleshoot the issue further.

Thanks for your report.

Comment 4 Mike A. Harris 2005-02-08 02:43:07 UTC
Setting status to "NEEDINFO", awaiting test results and file
attachments requested in comment #3, etc.  Thanks in advance.

Comment 5 Joe Zwerko 2005-02-08 21:48:59 UTC
Created attachment 110829 [details]
Xorg config file

Comment 6 Joe Zwerko 2005-02-08 21:49:31 UTC
Created attachment 110830 [details]
Xorg log file

Comment 7 Joe Zwerko 2005-02-08 21:50:30 UTC
Created attachment 110831 [details]
/var/log/messages

Comment 8 Joe Zwerko 2005-02-08 21:50:52 UTC
Created attachment 110832 [details]
lsmod output

Comment 9 Joe Zwerko 2005-02-08 21:51:21 UTC
Created attachment 110833 [details]
lspci -vvn output

Comment 10 Mike A. Harris 2005-04-20 11:19:07 UTC
From /var/log/messages:

Feb  8 09:52:15 ziggurat kernel: hdd: command error: status=0x51 { DriveReady
SeekComplete Error }
Feb  8 09:52:15 ziggurat kernel: hdd: command error: error=0x50
Feb  8 09:52:15 ziggurat kernel: ide: failed opcode was 100
Feb  8 09:52:15 ziggurat kernel: end_request: I/O error, dev hdd, sector 762496
Feb  8 09:52:15 ziggurat kernel: hdd: command error: status=0x51 { DriveReady
SeekComplete Error }
Feb  8 09:52:15 ziggurat kernel: hdd: command error: error=0x50
Feb  8 09:52:15 ziggurat kernel: ide: failed opcode was 100
Feb  8 09:52:15 ziggurat kernel: end_request: I/O error, dev hdd, sector 0
Feb  8 09:52:15 ziggurat kernel: hdd: command error: status=0x51 { DriveReady
SeekComplete Error }
Feb  8 09:52:15 ziggurat kernel: hdd: command error: error=0x50
Feb  8 09:52:15 ziggurat kernel: ide: failed opcode was 100
Feb  8 09:52:15 ziggurat kernel: end_request: I/O error, dev hdd, sector 0


Your hard disk appears to be dying or malfunctioning.  Make sure you
have good backups.  This may very well be the cause of your system hang.



In case it is not however....

From your log file:

>X Window System Version 6.8.1
>Release Date: 17 September 2004
>X Protocol Version 11, Revision 0, Release 6.8.1

The current release of xorg-x11 for FC3 is xorg-x11-6.8.2.  Please
upgrade to the new release via "yum install xorg-x11" and see if
the problem is resolved in this update or not.

You also appear to have had 3rd party kernel modules loaded into your
kernel.  When doing all testing, make sure you have either uninstalled
any/all 3rd party kernel modules (proprietary or open source) from your
system, or that they have not loaded into memory after the system
starts, as that will cause your system potentially to become unstable.

If you've got Nvidia's proprietary driver installed, be sure to disable
the kernel module from loading at boot time when testing the 'nv' driver,
and if you've used the proprietary driver at all since boot, be sure
to reboot the system in order to make sure the video hardware is reset
to factory default, as the 2 drivers do not program the hardware the
same way and this will cause conflicts.


Once you have updated to the latest FC3 update release of xorg-x11, ensured
you have not loaded any proprietary or other 3rd party kernel modules
into the running kernel, and still can reproduce the problem using the 'nv'
driver, report the problem in the X.Org bug tracker, located at:

    http://bugs.freedesktop.org in the "xorg" component.

Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes that
become available for consideration in future updates.



Comment 11 Mike A. Harris 2005-04-20 11:38:18 UTC
Setting status to "NEEDINFO", awaiting results of FC3 update testing,
and upstream bug report URL for tracking, if the issue persists.

Comment 12 Mike A. Harris 2005-05-17 22:44:08 UTC
ping

Comment 13 Mike A. Harris 2005-06-17 17:33:50 UTC
It's been several months since there has been feedback on this report.
Issues concerning the "nv" driver generally are only fixable by the
driver maintainer, an Nvidia employee whom is the only person familiar
with the operation of the hardware, and only person with the specifications.

If you are still having this problem with the latest FC3 updates, please
report this issue to X.Org developers by filing a bug report in the
X.Org bugzilla located at http://bugs.freedesktop.org in the "xorg"
component.

Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes that
become available for consideration in future updates.

Setting status to "NEEDINFO", awaiting X.Org bug URL for tracking.

Comment 14 Mike A. Harris 2005-08-30 07:45:56 UTC
Since this bugzilla report was filed, there have been several major
updates to the X Window System, which may resolve this issue.  Users
who have experienced this problem are encouraged to upgrade to the
latest version of Fedora Core, which can be obtained from:

        http://fedora.redhat.com/download

If this issue turns out to still be reproduceable in the latest
version of Fedora Core, please file a bug report in the X.Org
bugzilla located at http://bugs.freedesktop.org in the "xorg"
component.

Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes that
become available for consideration in future updates.

Setting status to "CURRENTRELEASE".


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