public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sean Hefty" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: 'Mike Heinz'
	<michael.heinz-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>,
	LINUX-RDMA <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: RE: Hang in ib_umad when attempting to unregister.
Date: Mon, 3 May 2010 08:47:32 -0700	[thread overview]
Message-ID: <57C080F9018D4C488FD7F575E2CE231F@amr.corp.intel.com> (raw)
In-Reply-To: <4C2744E8AD2982428C5BFE523DF8CDCB49A47409EA-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>

>In my company's test labs, we've been seeing nodes occasionally hang when a
>process tries to disconnect from the ib_mad interface. Can anyone suggest what
>might be causing this?

What kernel are you running?

--
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:[~2010-05-03 15:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 15:15 Hang in ib_umad when attempting to unregister Mike Heinz
     [not found] ` <4C2744E8AD2982428C5BFE523DF8CDCB49A47409EA-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2010-05-03 15:47   ` Sean Hefty [this message]
     [not found]     ` <57C080F9018D4C488FD7F575E2CE231F-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2010-05-03 15:58       ` Mike Heinz
     [not found]         ` <4C2744E8AD2982428C5BFE523DF8CDCB49A47409F6-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2010-05-03 16:08           ` Sean Hefty
     [not found]             ` <4C2744E8AD2982428C5BFE523DF8CDCB49A47409FE@MNEXMB1.qlogic.org>
     [not found]               ` <CF9C39F99A89134C9CF9C4CCB68B8DDF254C321EFA@orsmsx501.amr.corp.intel.com>
     [not found]                 ` <CF9C39F99A89134C9CF9C4CCB68B8DDF254C321EFA-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-05-03 17:06                   ` Mike Heinz
     [not found]                     ` <4C2744E8AD2982428C5BFE523DF8CDCB49A4740A0C-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2010-05-03 18:25                       ` Mike Heinz
     [not found]                         ` <4C2744E8AD2982428C5BFE523DF8CDCB49A4740A1C-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2010-05-03 18:40                           ` Sean Hefty
     [not found]                             ` <B552CE79A4134D83A6F5122C6A021FFF-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2010-05-03 19:10                               ` Mike Heinz
     [not found]                                 ` <4C2744E8AD2982428C5BFE523DF8CDCB49A4740A29-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2010-05-03 20:17                                   ` Sean Hefty
     [not found]                                     ` <BC9A3E31E4234E599F7FC99094789B2F-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2010-05-03 20:24                                       ` Mike Heinz

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=57C080F9018D4C488FD7F575E2CE231F@amr.corp.intel.com \
    --to=sean.hefty-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=michael.heinz-h88ZbnxC6KDQT0dZR+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