Description of problem:dmesg crashes kernel Version-Release number of selected component (if applicable):2.6.17-1.2187_FC5smp How reproducible: Almost every time Steps to Reproduce: 1.service iptables start 2.iptables -I FORWARD -p tcp --dport 80 -j LOG 3.dmesg Actual results:Crash Expected results:Doesn't Crash Additional info: See this on an SMP IBM 330 will attach docs with crash, lspci and lsmod.
Created attachment 137883 [details] console output
Created attachment 137884 [details] terminal command to induce crash
Created attachment 137885 [details] lpsci -vvv output
Created attachment 137886 [details] lsmod output
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.