From: Matan Barak <matanb@mellanox.com>
To: Alex Thorlton <athorlton@sgi.com>, Or Gerlitz <gerlitz.or@gmail.com>
Cc: andrew banman <abanman@sgi.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Doug Ledford <dledford@redhat.com>,
"Sean Hefty" <sean.hefty@intel.com>,
Hal Rosenstock <hal.rosenstock@gmail.com>,
"Or Gerlitz" <ogerlitz@mellanox.com>,
"David S. Miller" <davem@davemloft.net>,
Roland Dreier <roland@purestorage.com>,
Moni Shoua <monis@mellanox.com>,
"Jack Morgenstein" <jackm@dev.mellanox.co.il>,
Yishai Hadas <yishaih@mellanox.com>,
Eran Ben Elisha <eranbe@mellanox.com>,
Ira Weiny <ira.weiny@intel.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [BUG] mellanox IB driver fails to load on large config
Date: Wed, 15 Jul 2015 14:33:33 +0300 [thread overview]
Message-ID: <55A6450D.80300@mellanox.com> (raw)
In-Reply-To: <20150714202848.GD58053@asylum.americas.sgi.com>
On 7/14/2015 11:28 PM, Alex Thorlton wrote:
> On Tue, Jul 14, 2015 at 11:06:26PM +0300, Or Gerlitz wrote:
>> On Tue, Jul 14, 2015 at 9:48 PM, Alex Thorlton <athorlton@sgi.com> wrote:
>>> On Tue, Jul 14, 2015 at 01:22:34PM -0500, andrew banman wrote:
>>>> On Sat, Jul 11, 2015 at 11:20:19PM +0300, Or Gerlitz wrote:
>>>>> On Fri, Jul 10, 2015 at 10:15 PM, andrew banman <abanman@sgi.com> wrote:
>>>>>> I'm seeing a large number of allocation errors originating from the Mellanox IB
>>>>>> driver when booting the 4.2-rc1 kernel on a 4096cpu 32TB memory system:
>>>>>
>>>>> Just to make sure, mlx4 works fine on this small (...) system with 4.1
>>>>> and 4.2-rc1 breaks, or 4.2-rc1 is the 1st time you're trying that
>>>>> config?
>>>>
>>>> I'll let Alex comment on that, he did some testing on that.
>>>
>>> I started seeing this on a 4.1-rc8 kernel, so it's been around for a
>>> little while. It may have been around before 4.1-rc8, but I haven't run
>>> any kernels older than that on the big machine for some time.
>>
>> To make sure I am correctly following, on 4.1-rc8 you also see
>> something, right?
>
> Yes, that's correct.
>
>> are these the same messages or different ones? if the latter send to us.
>
> We see the same exact messages on 4.1-rc8.
Hi,
We don't recall getting those error with 32cpu machines, but we'll try
to reproduce this issue.
Matan
>
> Thanks for looking into this!
>
> - Alex
>
next prev parent reply other threads:[~2015-07-15 12:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 19:15 [BUG] mellanox IB driver fails to load on large config andrew banman
2015-07-11 20:20 ` Or Gerlitz
2015-07-14 18:22 ` andrew banman
2015-07-14 18:48 ` Alex Thorlton
2015-07-14 20:06 ` Or Gerlitz
2015-07-14 20:28 ` Alex Thorlton
2015-07-15 11:33 ` Matan Barak [this message]
2015-07-16 6:25 ` Or Gerlitz
2015-07-20 16:28 ` Alex Thorlton
2015-07-21 2:56 ` Alex Thorlton
2015-07-21 14:21 ` Matan Barak
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=55A6450D.80300@mellanox.com \
--to=matanb@mellanox.com \
--cc=abanman@sgi.com \
--cc=athorlton@sgi.com \
--cc=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=eranbe@mellanox.com \
--cc=gerlitz.or@gmail.com \
--cc=hal.rosenstock@gmail.com \
--cc=ira.weiny@intel.com \
--cc=jackm@dev.mellanox.co.il \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=monis@mellanox.com \
--cc=ogerlitz@mellanox.com \
--cc=roland@purestorage.com \
--cc=sean.hefty@intel.com \
--cc=yishaih@mellanox.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