From: "Bryan O'Sullivan" <bos@pathscale.com>
To: Roger Heflin <rheflin@atipa.com>
Cc: openib-general@openib.org, Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [openib-general] Openmpi/xhpl kernel crash 2.6.17-rc3 with Pathscale htx
Date: Wed, 10 May 2006 11:41:31 -0700 [thread overview]
Message-ID: <1147286491.22656.45.camel@localhost.localdomain> (raw)
In-Reply-To: <445FB9C7.8060507@atipa.com>
On Mon, 2006-05-08 at 16:36 -0500, Roger Heflin wrote:
> I don't see the crash under ip over ib (ran for over an hour),
> the crash occurs immediately upon attempting to start xhpl.
Hi, Roger -
Thanks for the report. We've recently fixed some locking problems that
may help with this, but I haven't fed them to Roland yet. If you need
some updated code to test before I sort out and send patches to Roland,
please let me know.
Thanks,
<b
prev parent reply other threads:[~2006-05-10 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 21:36 Openmpi/xhpl kernel crash 2.6.17-rc3 with Pathscale htx Roger Heflin
2006-05-10 18:41 ` Bryan O'Sullivan [this message]
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=1147286491.22656.45.camel@localhost.localdomain \
--to=bos@pathscale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=rheflin@atipa.com \
/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