From: Christoph Hellwig <hch@lst.de>
To: Meelis Roos <mroos@linux.ee>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
sparclinux@vger.kernel.org, linux-pci@vger.kernel.org,
qla2xxx-upstream@qlogic.com,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: 4.13.0-rc4 sparc64: can't allocate MSI-X affinity masks for 2 vectors
Date: Thu, 17 Aug 2017 12:09:21 +0200 [thread overview]
Message-ID: <20170817100921.GA29888@lst.de> (raw)
In-Reply-To: <alpine.LRH.2.20.1708162136220.16834@math.ut.ee>
Just curious: these are all SMP builds, right?
Just got burnt again by an UP kernel issue in that area that I sent
a patch for (to Jens) a long time ago, but that didn't get fixed.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Meelis Roos <mroos@linux.ee>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
sparclinux@vger.kernel.org, linux-pci@vger.kernel.org,
qla2xxx-upstream@qlogic.com,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: 4.13.0-rc4 sparc64: can't allocate MSI-X affinity masks for 2 vectors
Date: Thu, 17 Aug 2017 10:09:21 +0000 [thread overview]
Message-ID: <20170817100921.GA29888@lst.de> (raw)
In-Reply-To: <alpine.LRH.2.20.1708162136220.16834@math.ut.ee>
Just curious: these are all SMP builds, right?
Just got burnt again by an UP kernel issue in that area that I sent
a patch for (to Jens) a long time ago, but that didn't get fixed.
next prev parent reply other threads:[~2017-08-17 10:09 UTC|newest]
Thread overview: 38+ 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 14:54 ` Meelis Roos
2017-08-15 18:44 ` Bjorn Helgaas
2017-08-15 18:44 ` Bjorn Helgaas
2017-08-15 20:24 ` Meelis Roos
2017-08-15 20:24 ` Meelis Roos
2017-08-16 18:39 ` Meelis Roos
2017-08-16 18:39 ` Meelis Roos
2017-08-16 19:02 ` Bjorn Helgaas
2017-08-16 19:02 ` Bjorn Helgaas
2017-08-17 14:47 ` Meelis Roos
2017-08-17 14:47 ` Meelis Roos
2017-08-21 18:27 ` David Miller
2017-08-21 18:27 ` David Miller
2017-08-21 18:34 ` Christoph Hellwig
2017-08-21 18:34 ` Christoph Hellwig
2017-08-21 19:20 ` mroos
2017-08-21 19:20 ` mroos
2017-08-21 20:35 ` David Miller
2017-08-21 20:35 ` David Miller
2017-08-22 5:02 ` Meelis Roos
2017-08-22 5:02 ` Meelis Roos
2017-08-22 6:35 ` Christoph Hellwig
2017-08-22 6:35 ` Christoph Hellwig
2017-08-22 16:31 ` David Miller
2017-08-22 16:31 ` David Miller
2017-08-22 16:33 ` Meelis Roos
2017-08-22 16:33 ` Meelis Roos
2017-08-22 16:45 ` David Miller
2017-08-22 16:45 ` David Miller
2017-08-22 16:39 ` Christoph Hellwig
2017-08-22 16:39 ` Christoph Hellwig
2017-08-22 16:52 ` David Miller
2017-08-22 16:52 ` David Miller
2017-08-17 10:09 ` Christoph Hellwig [this message]
2017-08-17 10:09 ` Christoph Hellwig
2017-08-17 10:17 ` Meelis Roos
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=20170817100921.GA29888@lst.de \
--to=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 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.