linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: Giridhar Malavali <gmalavali@marvell.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"qla2xxx-upstream@qlogic.com" <qla2xxx-upstream@qlogic.com>
Subject: Re: qla2xxx init warning with blk_mq at drivers/pci/msi.c:1273 pci_irq_get_affinity+0xf4/0x120
Date: Tue, 12 Feb 2019 10:21:53 +0200	[thread overview]
Message-ID: <f9334c87-644b-b584-d3cc-60cfc148790c@linux.ee> (raw)
In-Reply-To: <9D8CA1BB-21B3-42AD-B2A7-7986A40C06EB@marvell.com>

> We are working on this and we will have an update for this.
>      I tested todays 5.0.0-rc5-00358-gdf3865f on my sparcs and a couple of servers that have qla2xxx
>      FC adapter gave me this warning:
>      
>      [   19.746300] qla2xxx [0000:00:00.0]-0005: : QLogic Fibre Channel HBA Driver: 10.00.00.12-k.
>      [   19.746599] qla2xxx [0000:02:00.0]-001d: : Found an ISP2432 irq 18 iobase 0x(____ptrval____).
>      [   20.203186] ------------[ cut here ]------------
>      [   20.203306] WARNING: CPU: 8 PID: 268 at drivers/pci/msi.c:1273 pci_irq_get_affinity+0xf4/0x120
Today I tried another sparc with newer OS and gcc and older hardware platform (Sun V445)
and that did not exhibit the problem with QLA2422. PCI-MSI is still present there too but
does not seem to be used for qla2xxx (it has "sun4v -IVEC" irq type).

Relevant dmesg lines:

[   47.905692] qla2xxx [0000:00:00.0]-0005: : QLogic Fibre Channel HBA Driver: 10.00.00.12-k.
[   47.905801] qla2xxx [0000:06:01.0]-001d: : Found an ISP2422 irq 6 iobase 0x(____ptrval____).
[   48.744347] scsi host3: qla2xxx
[   48.864173] qla2xxx [0000:06:01.0]-00fb:3: QLogic QLA2460 - SG-(X)PCI1FC-QF4, Sun StorageTek 4 Gb FC Enterprise PCI-X Single Channel Host B.
[   48.938909] scsi: waiting for bus probes to complete ...
[   49.044973] qla2xxx [0000:06:01.0]-00fc:3: ISP2422: PCI-X Mode 1 (133 MHz) @ 0000:06:01.0 hdma- host#=3 fw=8.07.00 (9496).
[   49.045110] qla2xxx [0001:08:02.0]-001d: : Found an ISP2422 irq 17 iobase 0x(____ptrval____).
[   49.604393] scsi host4: qla2xxx
[   49.794640] qla2xxx [0001:08:02.0]-00fb:4: QLogic QLA2460 - SG-(X)PCI1FC-QF4, Sun StorageTek 4 Gb FC Enterprise PCI-X Single Channel Host B.
[   50.160011] qla2xxx [0001:08:02.0]-00fc:4: ISP2422: PCI-X Mode 1 (100 MHz) @ 0001:08:02.0 hdma- host#=4 fw=8.07.00 (9496).
[   69.884173] qla2xxx [0000:06:01.0]-8038:3: Cable is unplugged...
[   71.068227] qla2xxx [0001:08:02.0]-8038:4: Cable is unplugged...

-- 
Meelis Roos <mroos@linux.ee>

  reply	other threads:[~2019-02-12  8:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-10 12:29 qla2xxx init warning with blk_mq at drivers/pci/msi.c:1273 pci_irq_get_affinity+0xf4/0x120 Meelis Roos
2019-02-11 19:09 ` Giridhar Malavali
2019-02-12  8:21   ` Meelis Roos [this message]
2019-02-12 18:38   ` Meelis Roos
2019-02-13  2:36     ` Ming Lei
2019-02-16  0:56       ` Himanshu Madhani
2019-02-16 19:14         ` 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=f9334c87-644b-b584-d3cc-60cfc148790c@linux.ee \
    --to=mroos@linux.ee \
    --cc=gmalavali@marvell.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=qla2xxx-upstream@qlogic.com \
    /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).