Description of problem: FYI the nonfatal crash dump. Version-Release number of selected component (if applicable): kernel-smp-2.6.17-1.2174_FC5 How reproducible: First time (crash dump without dead-lockup). Steps to Reproduce: 1. Normal editing now, this oops occured on cron.daily updatedb(8). Actual results: Crash. Expected results: No crash. Additional info: Complete lockups (no SysRq on PS/2 kbd functionable) occured already 3+ times, like in about 12 hours. No problems with non-SMP kernel, though. It was a mistake I was running SMP now. Crash dump attached. kernel-2.6.9-42.EL.i686 of RHEL4 will lockup the machine on the first PS/2 mouse move. Some more debugging upon request (I am non-kernel staff, from Tools Team).
Created attachment 135181 [details] BUG: unable to handle kernel paging request at virtual address f0985880
Reassigning to correct owner, kernel-maint.
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.
These common SMP crashes got recently fixed in some build around .2600 or so. It was workaroundable by "maxcpus=1" before.