Bug 434822
Summary: | OpenIB broken in 2.6.24.1-24.el5rt | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Gurhan Ozen <gozen> |
Component: | realtime-kernel | Assignee: | Clark Williams <williams> |
Status: | CLOSED CANTFIX | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 1.0 | CC: | bhu, dledford, jburke |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-07-02 14:34:29 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
Gurhan Ozen
2008-02-25 17:38:56 UTC
I just put the latest ofed-1.3 into our 2.6.24.3-rt3 based kernel. Please try that kernel from brew. Clark Ugh, I could have added the version you need, eh? kernel-rt-2.6.24.3-29.el5rt. As a follow up to my email to rhel-rt-internal list, i am changing the state to fails-qa because in kernel-rt-2.6.24.3-29.el5rt, for some reason, the order of IB devices returned is reversed somehow. I was making comparison between kernel-rt-2.6.24.3-29.el5rt and RHEL5.2 kernel, when i ran the tests on kernel-rt-2.6.24.3-29.el5rtvanilla, the order of ib devices were reversed as well. I have run all ib/openmpi tests and they all pass with kernel-rt-2.6.24.3-29.el5rt installed on RHEL5.2-Server-20030313.1 tree. Are we still broken in -65 (the GA kernel)? Clark, Looking a the change log from the kernel: Changelog: * Fri Jun 06 2008 Clark Williams <williams> - 2.6.24-65 - replaced peterz's slab fix with v2 patch - replaced rostedt's ftrace hotplug fix wth v2 patch What would have changed to have fix the issues Gurhan was seeing? Ah, I didn't read close enough to see that it's a device ordering issue. So yeah, we're still borken. Actually, we aren't broken and this bug should be closed. Upstream has obviously changed the sort order on Gurhan's hardware (so maybe pci=breadth or one of the other sort modifying options is possibly in order) and if it had happened in the middle of a single product lifecycle, that would be a bug we have to fix. However, this went out GA with the sort reversed, and now that sorting order has to be maintained in order to preserve existing systems when updates to MRG go out. In short, it's too late to anything about this issue, and we patently *can't* allow anything to be done about it. |