From: Meelis Roos <mroos@linux.ee>
To: Christoph Hellwig <hch@infradead.org>
Cc: Laurence Oberman <loberman@redhat.com>,
Jens Axboe <axboe@kernel.dk>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-block@vger.kernel.org, Don Brace <don.brace@microsemi.com>,
Scott Benesh <scott.benesh@microsemi.com>,
Scott Teel <scott.teel@microsemi.com>,
Kevin Barnett <kevin.barnett@microsemi.com>,
linux-scsi@vger.kernel.org, Hannes Reinecke <hare@suse.de>
Subject: Re: device support in hpsa, was: Re: OOPS from cciss_ioctl in 4.12+git
Date: Mon, 10 Jul 2017 17:08:18 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1707101523470.5280@math.ut.ee> (raw)
In-Reply-To: <20170707180857.GA19790@infradead.org>
> On Fri, Jul 07, 2017 at 11:42:38AM -0400, Laurence Oberman wrote:
> > What happens when hpsa_allow_any=1 with the Smart Array 64xx
> > It should probe.
>
> But only if it has a HP vendor ID as far as I can tell. We'd
> still need to add the compaq ids so that these controllers get
> probed. But maybe it's time to add them and flip the hpsa_allow_any
> default (maybe conditionally on a config option?) and mark cciss
> deprecated.
I added hpsa_allow_any=1, did not help.
Added a wildcard Compaq entry with RAID class, like the one for HP,
still no go:
[ 5.199125] hpsa 0000:00:04.0: unrecognized board ID: 0x40800e11, ignoring.
[ 5.282517] hpsa 0000:00:04.0: Board ID not found
Added specific PCI ID and subdevice ID quad and I still get the same
messages and the adapter is ignored.
What am I doing wrong?
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2017-07-10 14:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 12:58 OOPS from cciss_ioctl in 4.12+git Meelis Roos
2017-07-05 22:51 ` Christoph Hellwig
2017-07-06 9:55 ` Meelis Roos
2017-07-07 15:00 ` device support in hpasa, was: " Christoph Hellwig
2017-07-07 15:03 ` Jens Axboe
2017-07-07 15:42 ` Laurence Oberman
2017-07-07 18:08 ` device support in hpsa, " Christoph Hellwig
2017-07-07 18:20 ` Laurence Oberman
2017-07-10 14:08 ` Meelis Roos [this message]
2017-07-10 21:56 ` Don Brace
2017-07-07 16:05 ` device support in hpasa, " Hannes Reinecke
2017-07-07 19:15 ` Don Brace
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=alpine.LRH.2.20.1707101523470.5280@math.ut.ee \
--to=mroos@linux.ee \
--cc=axboe@kernel.dk \
--cc=don.brace@microsemi.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=kevin.barnett@microsemi.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=scott.benesh@microsemi.com \
--cc=scott.teel@microsemi.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).