Description of problem: Machine works fine for days with 2133 kernel. If I boot the 2139 version, it locks up within 15 minutes every time. No mouse no video updates, nothing in X, can't ssh in, can't get to text consoles, pressing power button doesn't initiate any disk activity. Must power cycle to recover. Reproduced 6 times in last 2 days. No problems at all with the 2133 kernel. Version-Release number of selected component (if applicable): How reproducible: Every time Steps to Reproduce: 1. Boot the 2139 kernel 2. start x 3. work until it locks up, less than 15 minutes. Actual results: complete Hang Expected results: No Hang Additional info: Will upload X config and lspci. Willing to run any tests necessary. Machine is a Dell Inspiron 9200
Created attachment 131613 [details] xorg.conf
Created attachment 131614 [details] lspci output
Does it become stable again if you comment out the Load "dri" in your Xorg conf ?
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 is a mass-close to kernel bugs in NEEDINFO state) As indicated previously there has been no update on the progress of this bug therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue still occurs for you and I will try to assist in its resolution. Thank you for taking the time to report the initial bug. If you believe that this bug was closed in error, please feel free to reopen this bug.