Description of problem: System locks up. Have tried FC4 and FC5. Fresh
installs with good installation disk. Have 4 other computer running FC5 with
no problems. They never lock up. Have i running FC4. That does not lock up.
Only this computer. Does dual boot with windows XP. Windows XP does not lock
up on startup and usally does never locks up. Other then your normal windows
crashes by using it.
XFX 5600XT video card
Acer 19inch widescreen Montior
2 harddrives Western Digital 80gig and 120
1 52x Cdrom Sony
1 DVD/Writer Sony
Version-Release number of selected component (if applicable):
Restart system. Mostley locks up with Yum update. Kernel, Eclipse. Locks up
surfing Internet. Locks up after entering userid and password or at the login
Steps to Reproduce:
1. Update System
2. Search Interent
Completely Locks up system. Have to do a reset on the computer.
You might be encountering some sort of hardware fault if you're only seeing this
on one system. Is your CPU cooling fan working? You might also try running
memcheck to check that your memory is okay.
Windows runs on it fine. I ran it in init 3 and am getting kernel panics. What
Linux program will check the harddrive for errors? I cleared off all Linux
partions and had Windows scan the disk. Disk came up ok.
Today the kernel panics are for
Bug: sleeping function called from invaold contecnt at include/linux/rwsem.h:43
it also has some like this <ffffffff802638a5> a bunch of them. Is that coming
from the memory or the harddisk?
kernel panic-not syncing: Aiee, killing interrupt handler!
This computer worked great until a month ago. It started freezing up.
Thank you for your help.
Hi, I'm going to reassign this to the kernel team, so that they can investigate.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
Installed FC6 over FC5. Still getting same problems. Disk is showing no
errors. I am going to replace disk and try fresh install to see if it works.
Removing NeedsRetesting from whiteboard so we can repurpose it.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.