public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche-Sjgp3cTcYWE@public.gmane.org>
To: "oulijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org"
	<oulijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: 【ask for help】
Date: Fri, 3 Nov 2017 14:59:11 +0000	[thread overview]
Message-ID: <1509721149.2473.3.camel@wdc.com> (raw)
In-Reply-To: <757dcf37-4fb3-c6e9-c915-de10b4e2326f-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>

On Fri, 2017-11-03 at 17:14 +0800, oulijun wrote:
> unhandled level 2 translation fault (11) at 0x00000000, esr 0x92000006, in librdmacm.so.1.1.11
> [ffff9a6e8000+11000]

Is this perhaps a user space fault reported by the kernel? From kernel source
file arch/arm64/mm/fault.c:

		pr_info("%s[%d]: unhandled %s (%d) at 0x%08lx, esr 0x%03x",
			tsk->comm, task_pid_nr(tsk), inf->name, sig,
			addr, esr);

You will need to identify what code in librdmacm caused this fault by using
tools that report a stack trace for the fault. Had you already considered to
run the application that uses librdmacm and that triggers this fault under gdb
or valgrind?

Bart.

  parent reply	other threads:[~2017-11-03 14:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-03  9:14 【ask for help】 oulijun
     [not found] ` <757dcf37-4fb3-c6e9-c915-de10b4e2326f-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-11-03 14:59   ` Bart Van Assche [this message]
     [not found]     ` <1509721149.2473.3.camel-Sjgp3cTcYWE@public.gmane.org>
2017-11-04  9:02       ` oulijun

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=1509721149.2473.3.camel@wdc.com \
    --to=bart.vanassche-sjgp3ctcywe@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=oulijun-hv44wF8Li93QT0dZR+AlfA@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