From: Konstantin Boyanov <konstantin.boyanov-T5F83Mi6MZE@public.gmane.org>
To: Konstantin Boyanov <kkboyanov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "Hefty,
Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Segmentation Fault when accessing QPN of a RC Queue pair
Date: Mon, 28 Mar 2011 12:57:23 +0200 [thread overview]
Message-ID: <4D906993.7030404@desy.de> (raw)
In-Reply-To: <AANLkTi=ppeQSxHTA18pFM6=y06Q_eNGsY8Fn=gXtXaBM-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Sorry for the last incomplete mail, I accidentaly pressed the enter when
in the wrong focus...
here we go again:
Hello,
First of all thanks for the reply! I was really getting desperate about
this issue.
I have looked in the libibverbs examples and I cannot see differences
between my code and the one in the examples (at least functionally, I
clearly have another structure in my programm).
About the snippets: I didn't want to copy/paste all the code into my
mail, that's why I provided a link to where the code can be found:
http://www.ifh.de/~boyanov/ibpipo/ <http://www.ifh.de/%7Eboyanov/ibpipo/>
I still cannot understand what I am doing wrong, and why the errors ocur
only on one of the Queue Pairs. Is it possible that I try to interact
with some of the "reserved" QPs like the QP0 and QP1?
Another thing: I am also getting segfaults when trying to modify the LID
of the QP contexts. i first get the LID from the device and then when
trying to set it in my custom QP context structure I get a segfault:
struct ibv_port_attr tmp_port_attr;
ret = ibv_query_port(ping_ib_thread.ibctx, barg.port, &tmp_port_attr);
if ( ret != 0){
printf("error querying IB port %d for context %s\n", port,
ping_ib_thread.ibctx->device->dev_path);
perror("ibv_query_port");
}
ping_ib_thread.ibport_attr->lid = tmp_port_attr.lid;
pong_ib_thread.ibport_attr->lid = tmp_port_attr.lid;
Here, barg.port = 1 and port 1 is in the PORT_ACTIVE state. I know I am
missing something small but I am so confused and frustrated from this
code I cannot see anything anymore in it...
Please, if you have some clues to what can be wrong, at least where I
can dig for more info and possible problems, let me know.
Best Regards,
Konstantin
--
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
next prev parent reply other threads:[~2011-03-28 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 12:55 Segmentation Fault when accessing QPN of a RC Queue pair Konstantin Boyanov
[not found] ` <4D89EDC4.4050309-T5F83Mi6MZE@public.gmane.org>
2011-03-23 16:54 ` Hefty, Sean
[not found] ` <AANLkTi=ppeQSxHTA18pFM6=y06Q_eNGsY8Fn=gXtXaBM@mail.gmail.com>
[not found] ` <AANLkTi=ppeQSxHTA18pFM6=y06Q_eNGsY8Fn=gXtXaBM-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-28 10:57 ` Konstantin Boyanov [this message]
[not found] ` <4D906993.7030404-T5F83Mi6MZE@public.gmane.org>
2011-03-28 11:22 ` Konstantin Boyanov
2011-03-28 23:13 ` Hefty, Sean
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=4D906993.7030404@desy.de \
--to=konstantin.boyanov-t5f83mi6mze@public.gmane.org \
--cc=kkboyanov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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