Bug 625173
| Summary: | [RHEL6][Kernel] FATAL: Error inserting ipv6, Cannot allocate memory, causes panic | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jeff Burke <jburke> | ||||
| Component: | kernel | Assignee: | Neil Horman <nhorman> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 6.0 | CC: | arozansk, jolsa, lwang, nhorman, pbunyan, tgraf | ||||
| Target Milestone: | rc | Keywords: | RHELNAK | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| URL: | http://rhts.redhat.com/cgi-bin/rhts/test_log.cgi?id=16198367 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | kernel-2.6.32-85.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-05-23 20:49:25 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: | |||||||
| Attachments: |
|
||||||
|
Description
Jeff Burke
2010-08-18 18:51:25 UTC
This issue has been proposed when we are only considering blocker issues in the current Red Hat Enterprise Linux release. ** If you would still like this issue considered for the current release, ask your support representative to file as a blocker on your behalf. Otherwise ask that it be considered for the next Red Hat Enterprise Linux release. ** Thank you for your bug report. This issue was evaluated for inclusion in the current release of Red Hat Enterprise Linux. Unfortunately, we are unable to address this request in the current release. Because we are in the final stage of Red Hat Enterprise Linux 6 development, only significant, release-blocking issues involving serious regressions and data corruption can be considered. If you believe this issue meets the release blocking criteria as defined and communicated to you by your Red Hat Support representative, please ask your representative to file this issue as a blocker for the current release. Otherwise, ask that it be evaluated for inclusion in the next minor release of Red Hat Enterprise Linux. I think this actually is a problem in how we manage the pernet list. I'm reserving one of the hp z600 systems to investigate. Note to self: This might be solved inadvertently upstream by 72ad937abd0a43b7cf2c557ba1f2ec75e608c516 and some supporting patches. I'll try a backport in the AM Created attachment 449477 [details]
patch to balance addrconf/addrlabel pernet registration
so good news bad news.
I fixed the problem with the oops, we have an unbalanced registration that leaves a list in an inconsistent state if the code doesn't load properly.
The bad news is that the kernel still doesn't boot, which is bad, but we're in a constrained memory position anyway. Theres not much we can, save for put the ipv6 module and the kernel as a whole on a diet, but we should probably track that in a separate bz.
This needs to go upstream as well, so I'll send it there and then post internally
http://brewweb.devel.redhat.com/brew/taskinfo?taskID=2782687 Test build of backport This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Patch(es) available on kernel-2.6.32-89.el6 Have not seen this happening in the last few runs of Kernel Tier 1 and other tests so this can be verified. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2011-0542.html |