From: David Miller <davem@davemloft.net>
To: mroos@linux.ee
Cc: hch@lst.de, helgaas@kernel.org, sparclinux@vger.kernel.org,
linux-pci@vger.kernel.org, qla2xxx-upstream@qlogic.com,
linux-kernel@vger.kernel.org
Subject: Re: 4.13.0-rc4 sparc64: can't allocate MSI-X affinity masks for 2 vectors
Date: Mon, 21 Aug 2017 13:35:49 -0700 (PDT) [thread overview]
Message-ID: <20170821.133549.1817020810110297960.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LRH.2.20.1708212209280.31611@math.ut.ee>
From: mroos@linux.ee
Date: Mon, 21 Aug 2017 22:20:22 +0300 (EEST)
>> I think with this patch from -rc6 the symptoms should be cured:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c005390374957baacbc38eef96ea360559510aa7
>>
>> if that theory is right.
>
> The result with 4.13-rc6 is positive but mixed: the message about MSI-X
> affinty maks are still there but the rest of the detection works and the
> driver is loaded successfully:
Is this an SMP system?
I ask because the commit log message indicates that this failure is
not expected to ever happen on SMP.
We really need to root cause this.
next prev parent reply other threads:[~2017-08-21 20:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 14:54 4.13.0-rc4 sparc64: can't allocate MSI-X affinity masks for 2 vectors Meelis Roos
2017-08-15 18:44 ` Bjorn Helgaas
2017-08-15 20:24 ` Meelis Roos
2017-08-16 18:39 ` Meelis Roos
2017-08-16 19:02 ` Bjorn Helgaas
2017-08-17 14:47 ` Meelis Roos
2017-08-21 18:27 ` David Miller
2017-08-21 18:34 ` Christoph Hellwig
2017-08-21 19:20 ` mroos
2017-08-21 20:35 ` David Miller [this message]
2017-08-22 5:02 ` Meelis Roos
2017-08-22 6:35 ` Christoph Hellwig
2017-08-22 16:31 ` David Miller
2017-08-22 16:33 ` Meelis Roos
2017-08-22 16:45 ` David Miller
2017-08-22 16:39 ` Christoph Hellwig
2017-08-22 16:52 ` David Miller
2017-08-17 10:09 ` Christoph Hellwig
2017-08-17 10:17 ` Meelis Roos
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=20170821.133549.1817020810110297960.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hch@lst.de \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=qla2xxx-upstream@qlogic.com \
--cc=sparclinux@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).