Bug 210119
Summary: | Kernel panic after loading iptables nat rule and producing traffic over gigabit ethernet card | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Egon Kastelijn <redhat2> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | pfrields, twoerner, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-11-05 21:03:17 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Egon Kastelijn
2006-10-10 05:30:17 UTC
iptables is a userland config tool. Assigning to kernel. After some more testing the problem has narrowed down a bit. It is not the ip_conntrack module that is causing the problem but the iptable_nat module. Here some test results: ----------------------------- Module | Loaded? | ----------------------------- iptable_nat | n | n | n | y | ----------------------------- ip_nat | n | n | y | y | ----------------------------- nfnetlink | n | y | y | y | ============================= panic? | N | N | N | Y | From these test results can be concluded that the problem can only be reproduced when the iptable_nat module is loaded. Tests with mangle, filter and raw table do not result in a Kernel Panic. The problem is also not present when the SSH connection (with dmesg) is done over the lo interface. 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. I am unable to boot the new kernel, because my root filesystem lives on a RAID5 disk. The mkinitrd does not handle the raid456.ko kernel module correctly, rendering my initrd useless. As soon as this problem has been fixed I would be happy to give it another try. My mkinitrd problem is covered in bug 211030. I used the workaround in Comment #2 from Dieter Stolte. This made 2.6.18-1.2200.fc5 bootable for me. I tested the new 2.6.18-1.2200.fc5 kernel and I am unable to reproduce the problem now. It looks to me that the problem has been solved! Great work guys! |