linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Himanshu Madhani <hmadhani@marvell.com>
Cc: Andrew Vasquez <andrewv@marvell.com>,
	Girish Basrur <gbasrur@marvell.com>,
	Giridhar Malavali <gmalavali@marvell.com>,
	Myron Stowe <mstowe@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Quinn Tran <quinn.tran@qlogic.com>,
	Linux PCI <linux-pci@vger.kernel.org>
Subject: Re: [EXT] VPD access Blocked by commit 0d5370d1d85251e5893ab7c90a429464de2e140b
Date: Thu, 30 May 2019 15:58:23 -0500	[thread overview]
Message-ID: <20190530205823.GA45696@google.com> (raw)
In-Reply-To: <D8764654-E2A0-43B8-97D9-6644F2BC8D0E@marvell.com>

On Thu, May 30, 2019 at 07:33:01PM +0000, Himanshu Madhani wrote:

> We are able to successfully read VPD config data using lspci and cat
> command

Yes, you mentioned that in the very first email.  I was hoping you
would include the actual data, e.g., "cat vpd | xxd".  That would help
us figure out why you don't see the panic any more.  I suspect either:

  - new QLogic firmware fixed the structure of the VPD data so Linux
    no longer attempts to read past the end of the implemented region,
    or,

  - we still read past the end of the implemented VPD region, but the
    device doesn't report an error or the platform deals with the
    error without causing a panic.

> We also verified this same configuration on a SuperMicro X10SRA-F
> server (which i had sent in earlier email)’ and were able to verify
> that the VPD read was good and there were no errors on PCIe trace.

Since you saw no PCIe errors here, this suggests that new firmware has
changed the format of the VPD data.

> Given this information, Please consider reverting the patch until we
> further debug the issue and resolve as it is affecting general
> availability of our adapter.

1) The way Linux works is that you would post a patch that does the
revert you'd like to see done.

2) It's unlikely that a simple revert of 0d5370d1d852 ("PCI: Prevent
VPD access for QLogic ISP2722") is the right answer because that would
make Ethan's machine panic again.  It's possible that a QLogic
firmware update would avoid the panic, but we can't simply revert the
patch and force users to do that update.

If a QLogic firmware update indeed fixed the VPD format, I suggest
that you ask the folks responsible for the firmware to identify the
specific version where that was fixed and how the OS can figure that
out.

Then you could make a new quirk specific to this device that allows
VPD reads if the adapter has new enough firmware.  If it finds older
firmware, it could even print a message suggesting that users could
update the firmware if they need to read VPD data.

Bjorn

  reply	other threads:[~2019-05-30 20:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B5B745A3-96B4-46ED-8F3F-D3636A96057F@marvell.com>
     [not found] ` <CAErSpo5qy6WuUe9cz1vTBBnc5P_uZaPzc-Yqbag2eBBxzi+ENg@mail.gmail.com>
2019-05-21 20:11   ` VPD access Blocked by commit 0d5370d1d85251e5893ab7c90a429464de2e140b Bjorn Helgaas
2019-05-30 19:33     ` [EXT] " Himanshu Madhani
2019-05-30 20:58       ` Bjorn Helgaas [this message]
2019-06-03 21:30         ` Himanshu Madhani
2019-06-03 22:40           ` Bjorn Helgaas

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=20190530205823.GA45696@google.com \
    --to=helgaas@kernel.org \
    --cc=andrewv@marvell.com \
    --cc=gbasrur@marvell.com \
    --cc=gmalavali@marvell.com \
    --cc=hmadhani@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mstowe@redhat.com \
    --cc=quinn.tran@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).