From: Roland Dreier <rdreier@cisco.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: netdev@vger.kernel.org, Yevgeny Petrilin <yevgenyp@mellanox.co.il>
Subject: Re: mlx4 2.6.31-rc5: SW2HW_EQ failed.
Date: Wed, 19 Aug 2009 00:03:26 -0700 [thread overview]
Message-ID: <adaljlg1e0x.fsf@cisco.com> (raw)
In-Reply-To: <ada3a7p3o6f.fsf@cisco.com> (Roland Dreier's message of "Mon, 17 Aug 2009 18:28:56 -0700")
By the way, my dual-socket nehalem EP system says:
SMP: Allowing 16 CPUs, 0 hotplug CPUs
which I think (haven't checked but the code sure looks that way) means
that num_possible_cpus() is 16. This is a supermicro workstation board,
forget the exact model.
And the fact that your system is different is not really a bug -- it
just points to slightly incorrect data somewhere, most likely ACPI
tables; having 32 possible CPUs on a system that can only ever really
have 16 CPUs just leads to some overallocations, and tickles the mlx4
bug where it can't handle more than 32 interrupts).
Just FWIW.
- R.
next prev parent reply other threads:[~2009-08-19 7:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 19:26 mlx4 2.6.31-rc5: SW2HW_EQ failed Christoph Lameter
2009-08-17 22:04 ` Roland Dreier
2009-08-17 22:17 ` Christoph Lameter
2009-08-18 1:28 ` Roland Dreier
2009-08-18 15:50 ` Christoph Lameter
2009-08-18 16:56 ` Roland Dreier
2009-08-19 7:03 ` Roland Dreier [this message]
2009-08-19 11:46 ` Christoph Lameter
2009-08-19 15:29 ` Roland Dreier
2009-08-19 15:47 ` Christoph Lameter
2009-08-19 19:46 ` Roland Dreier
2009-08-19 19:58 ` Christoph Lameter
2009-08-19 21:42 ` Roland Dreier
2009-08-19 16:29 ` Christoph Lameter
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=adaljlg1e0x.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=cl@linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=yevgenyp@mellanox.co.il \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.