From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752401AbdHOUYY (ORCPT ); Tue, 15 Aug 2017 16:24:24 -0400 Received: from smtp1.it.da.ut.ee ([193.40.5.66]:44546 "EHLO smtp1.it.da.ut.ee" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751427AbdHOUYW (ORCPT ); Tue, 15 Aug 2017 16:24:22 -0400 Date: Tue, 15 Aug 2017 23:24:18 +0300 (EEST) From: Meelis Roos To: Bjorn Helgaas cc: sparclinux@vger.kernel.org, linux-pci@vger.kernel.org, qla2xxx-upstream@qlogic.com, Linux Kernel list , Christoph Hellwig Subject: Re: 4.13.0-rc4 sparc64: can't allocate MSI-X affinity masks for 2 vectors In-Reply-To: <20170815184403.GB4099@bhelgaas-glaptop.roam.corp.google.com> Message-ID: References: <20170815184403.GB4099@bhelgaas-glaptop.roam.corp.google.com> User-Agent: Alpine 2.20 (LRH 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On Tue, Aug 15, 2017 at 05:54:27PM +0300, Meelis Roos wrote: > > I noticed that in 4.13.0-rc4 there is a new error in dmesg on my sparc64 > > t5120 server: can't allocate MSI-X affinity masks. > > > > [ 30.274284] qla2xxx [0000:00:00.0]-0005: : QLogic Fibre Channel HBA Driver: 10.00.00.00-k. > > [ 30.274648] qla2xxx [0000:10:00.0]-001d: : Found an ISP2432 irq 21 iobase 0x000000c100d00000. > > [ 30.275447] qla2xxx 0000:10:00.0: can't allocate MSI-X affinity masks for 2 vectors > > [ 30.816882] scsi host1: qla2xxx > > [ 30.877294] qla2xxx: probe of 0000:10:00.0 failed with error -22 > > [ 30.877578] qla2xxx [0000:10:00.1]-001d: : Found an ISP2432 irq 22 iobase 0x000000c100d04000. > > [ 30.878387] qla2xxx 0000:10:00.1: can't allocate MSI-X affinity masks for 2 vectors > > [ 31.367083] scsi host1: qla2xxx > > [ 31.427500] qla2xxx: probe of 0000:10:00.1 failed with error -22 > > > > I do not know if the driver works since nothing is attached to the FC > > HBA at the moment, but from the error messages it looks like the driver > > fails to load. > > > > I booted 4.12 and 4.11 - the red error is not there but the failure > > seems to be the same error -22: 4.10.0 works, 4.11.0 errors out with EINVAL and 4.13-rc4 errorr sout with more verbose MSI messages. So something between 4.10 and 4.11 has broken it. Also, 4.13-rc4 is broken on another sun4v here (T1000). So it seems to be sun4v interrupt related. -- Meelis Roos (mroos@linux.ee)