All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: Myron Stowe <myron.stowe@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>, linux-pci@vger.kernel.org
Subject: Re: `pcilib: sysfs_read_vpd: read failed: Input/output error` on ASRock E350M1
Date: Mon, 16 May 2016 22:37:32 +0200	[thread overview]
Message-ID: <1463431052.1983.57.camel@users.sourceforge.net> (raw)
In-Reply-To: <CAL-B5D19esStG0=nbUa-mJggtRDX94t542Vzz1=u_avq9qRgYQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2034 bytes --]

Dear Myron,


thank you for your response.


Am Montag, den 16.05.2016, 12:02 -0600 schrieb Myron Stowe:
> On Sun, May 15, 2016 at 10:56 AM, Paul Menzel wrote:

[…]

> > Is that related to [1]?
>
> There have been a number of recent kernel commits to work-around know
> buggy devices -
>   v4.6-rc5
>     67e6587  cxgb4: Set VPD size so we can read both VPD structures
>     cb92148  PCI: Add pci_set_vpd_size() to set VPD size
>   v4.6 -
>     7c20078  PCI: Prevent VPD access for buggy devices
>     c521b01  PCI: Sleep rather than busy-wait for VPD access completion
>     408641e  PCI: Fold struct pci_vpd_pci22 into struct pci_vpd
>     f1cd93f  PCI: Rename VPD symbols to remove unnecessary "pci22"
>     da00684  PCI: Remove struct pci_vpd_ops.release function pointer
>     6437907  PCI: Move pci_vpd_release() from header file to pci/access.c
>     fc0a407  PCI: Move pci_read_vpd() and pci_write_vpd() close to other code
>     104daa7  PCI: Determine actual VPD size on first access
>     c556388  PCI: Use bitfield instead of bool for struct pci_vpd_pci22.busy
>     f52e562  PCI: Allow access to VPD attributes with size 0
>     9eb45d5  PCI: Update VPD definitions
>   v4.3 -
>     da2d03e  PCI: Use function 0 VPD only for identical functions
>     9d92407  PCI: Fix devfn for VPD access through function 0
>     7aa6ca4  PCI: Add VPD function 0 quirk for Intel Ethernet devices
>     932c435  PCI: Add dev_flags bit to access VPD through function 0
> 
> What were you getting/seeing before?

The error wasn’t shown. Sorry if that is not a helpful answer. If I
provide more information, please tell me how I can get them.

You can find a lot of lspci output for the ASRock E350M1 in coreboot’s
board status repository [2].


Thanks,

Paul


> > [1] https://lkml.org/lkml/2016/4/15/649
[2] http://review.coreboot.org/cgit/board-status.git/tree/asrock/e350m1

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-05-16 20:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-15 16:56 `pcilib: sysfs_read_vpd: read failed: Input/output error` on ASRock E350M1 Paul Menzel
2016-05-16 18:02 ` Myron Stowe
2016-05-16 20:37   ` Paul Menzel [this message]
2016-05-17  1:42     ` Myron Stowe
2016-05-17 21:21       ` Paul Menzel
2016-05-18  1:52         ` Myron Stowe
2016-05-21 20:18           ` Paul Menzel
2016-06-11 12:12             ` Paul Menzel

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=1463431052.1983.57.camel@users.sourceforge.net \
    --to=paulepanter@users.sourceforge.net \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=myron.stowe@gmail.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 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.