Description of problem: I used to have Core 4 which worked fine on the machine (wo/dmraid). I have tried to make a fresh installation of Core 5 onto the machine. The machine experiences freezes and automatic reboots after installation. It happens sometimes during bootup (as early as enabling the firewall) and the other times after some light use (eg. open firefox in GNOME or untar a file in init level 3). I have tried to 1. disable sound cards 2. disable network interfaces 3. shutdown X-server (set init level 3 as default) 4. install without dmraid None of these help the situation, although it seems it lasts longer when I progress from item 1 to item 4. Freezes and reboots never occur throughout installation (~6 times). Machine configuration: nFORCE3-A chipset (ECS) AMD Sempron 3100+ nVidia FX 5200 VGA w/digital graphics output 2x 80 Gbs ATA/133 harddisks CDRW/DVD Rom combo Version-Release number of selected component (if applicable): How reproducible: Any graphics or disk intensive applications is likely to cause the freeze, although there is no definite sequence which can cause the freeze. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
*** Bug 186853 has been marked as a duplicate of this bug. ***
*** Bug 186854 has been marked as a duplicate of this bug. ***
Created attachment 126878 [details] kernel config file
I had the same problem. I was able to get a stable system by compiling a kernel with the attached .config .
I have the same problem though for me it freezes in a completely random way. I've had it freeze even on the login screen. my box has a AMD Sempron 64 Daivid
Created attachment 127733 [details] good config file for 2.6.16
I managed to create another stable kernel with this config. I'm suspecting the "optimize for size" parameter.
Could someone PLEASE post the kernel config leading to the system freezes? Or even better: try to find out what exactly caused the problem?
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. Thank you.
This bug has been mass-closed along with all other bugs that have been in NEEDINFO state for several months. Due to the large volume of inactive bugs in bugzilla, this is the only method we have of cleaning out stale bug reports where the reporter has disappeared. If you can reproduce this bug after installing all the current updates, please reopen this bug. If you are not the reporter, you can add a comment requesting it be reopened, and someone will get to it asap. Thank you.
Closing since there was an error in previous mass-close and they remained in NEEDINFO.