From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: Dotan Barak <dotanb-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: The kernel module rdma_ucm.ko can't be loaded in debug kernel of RHEL 6.2
Date: Tue, 24 Jul 2012 09:51:13 -0500 [thread overview]
Message-ID: <500EB661.5020109@opengridcomputing.com> (raw)
In-Reply-To: <CALvMawqdz=M1qx0NSmWfx+YRe0vzHdYrnbeLg=r21mHdRWj9bw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 7/24/2012 9:18 AM, Dotan Barak wrote:
>
>
> On Tue, Jul 24, 2012 at 4:50 PM, Steve Wise
> <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org <mailto:swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>> wrote:
>
> On 7/24/2012 3:27 AM, Dotan Barak wrote:
>> Hi Steve.
>>
>> I'm trying to load the RDMA stack, based on the upstream kernel
>> on debug kernel of RHEL 6.2 (2.6.32-220.el6.x86_64.debug).
>> The kernel module rdma_ucm.ko can't be loaded in this kernel and
>> i get the following error messages in 'dmesg':
>>
>
> No I haven't seen this issue. Is this a backport problem with the
> rhel debug kernel, or does this also happen on the upstream kernel
> as well?
>
>
> I don't think that the problem is with the backport of the code to
> RHEL6.2,
> But I didn't test the upstream kernel when the debug features enabled.
>
I don't even see sysctl_check_dir() upstream...
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
parent reply other threads:[~2012-07-24 14:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CALvMawqdz=M1qx0NSmWfx+YRe0vzHdYrnbeLg=r21mHdRWj9bw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=500EB661.5020109@opengridcomputing.com \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=dotanb-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).