Bug 15178
Summary: | Panic in tcp stack | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Brian Brock <bbrock> |
Component: | kernel | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | CC: | mnovi |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-08-22 16:59:41 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
Brian Brock
2000-08-02 20:43:41 UTC
They *really* need to try a 2.2.16-based kernel; many TCP bugs were fixed in those. Initially, stability goes up with 2.2.16-3. Waiting for a few days of production use to see if the problem is truly gone, or if it's just occuring less often now. After running with 2.2.16 for one day there was no panic. However, this kernel runs too slow for our production environment (the 2.2.16 box was several packets behind our 2.2.12 box all day). I've backed off to 2.2.14 which appears to be just as fast as the 2.2.12 kernel. Problem appears resolved with no change in many months. Changing status to "closed". |