From: Roland Dreier <rdreier@cisco.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: netdev@vger.kernel.org
Subject: Re: [IB] 2.6.31-rc9: SW2HW_EQ failed on Dell R610
Date: Tue, 08 Sep 2009 20:11:20 -0700 [thread overview]
Message-ID: <ada1vmgn76v.fsf@cisco.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0909081805110.7733@V090114053VZO-1> (Christoph Lameter's message of "Tue, 8 Sep 2009 18:06:54 -0400 (EDT)")
> The problem with the interrupts is not solved in rc9:
Yes, by the time we got this all resolved, it was already rc8 and I
though 2.6.31 was right around the corner ... the issue didn't seem
severe enough to stick in so late in the cycle, so I queued the patch
for .32 with a cc to stable to get in 2.6.31.1.
The workaround of limiting possible cpus to 16 should be OK for the time
between 2.6.31 and 2.6.31.1.
- R.
next prev parent reply other threads:[~2009-09-09 3:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 22:06 [IB] 2.6.31-rc9: SW2HW_EQ failed on Dell R610 Christoph Lameter
2009-09-09 3:11 ` Roland Dreier [this message]
2009-09-09 14:02 ` Christoph Lameter
2009-09-09 16:36 ` Roland Dreier
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=ada1vmgn76v.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=cl@linux-foundation.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).