Bug 819925 - atl1c 0000:04:00.0: vpd r/w failed. This is likely a firmware bug on this device.
atl1c 0000:04:00.0: vpd r/w failed. This is likely a firmware bug on this de...
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
17
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-08 12:01 EDT by James Ettle
Modified: 2012-05-08 12:42 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-05-08 12:42:32 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
dmesg output (74.69 KB, text/x-log)
2012-05-08 12:01 EDT, James Ettle
no flags Details
lspci -vvvv output (27.27 KB, text/plain)
2012-05-08 12:03 EDT, James Ettle
no flags Details

  None (edit)
Description James Ettle 2012-05-08 12:01:24 EDT
Created attachment 583031 [details]
dmesg output

Description of problem:
My notebook has an AR8151 gigabit ethernet chip supported by atl1c. Upon running lspci -vv (or more verbose), the following message appears in dmesg:


[  819.730511] atl1c 0000:04:00.0: vpd r/w failed.  This is likely a firmware bug on this device.  Contact the card vendor for a firmware update.


lspci itself prints this to stderr:


pcilib: sysfs_read_vpd: read failed: Connection timed out


Full dmesg and lspci -vvvv output attached. No detrimental effect on network card performance observed.

Version-Release number of selected component (if applicable):
kernel-3.3.4-4.fc17.x86_64

How reproducible:
Always upon running lspci -vv.
Comment 1 James Ettle 2012-05-08 12:03:10 EDT
Created attachment 583032 [details]
lspci -vvvv output
Comment 2 Dave Jones 2012-05-08 12:42:32 EDT
as the message says, this is likely a firmware bug. nothing we can fix.

alternatively, "don't do that".

Note You need to log in before you can comment on or make changes to this bug.