sorry, I've somehow missed this bug report first

Can you still reproduce this?
With 100 % probability?
Do you have any selinux messages related in logs?

Selinux is disabled. Nothing shows up via syslog or auditd.

System is minimalist/headless/server install so maybe there's some hidden dep that yum/rpm didn't catch? It's 100% reproducible on this particular HP ProLiant DL360-G5, and I'll test out on a few more as soon as I find more round tuits.

I've found this machine in our lab, I'll test it

I still can't get the machine, seems it's broken, but I'm still trying...

Did you find this problem on any other machine?

"Connection timed out" - it seems it's waiting, how long does it wait? (you can use 'time lspci -vv >/dev/null'

to everyone who can see this bug:

1) check what device is causing this problem
strace lspci -vv 2>&1 | grep -B 10 'sysfs_read_vpd: read failed' | grep open | tail -n1

for example:
open("/sys/bus/pci/devices/0000:07:00.0/vpd", O_RDONLY) = 4

the 07:00.0 part is important, you will probably have different value

2) check what device is it

lspci -nn | grep 07:00.0

(replace 07:00.0 with what you got in step 1)

thanks

an example output (one failing device) is:

07:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS 1078 [1000:0060] (rev 04)

Same issue on HP DL 380 G4 with SmartArray 6i RAID controller.

There was a selinux alert, but the error still occurs after completing the 
#setsebool -P allow_unconfined_mmap_low 1.

#strace lspci -vv 2>&1 | grep -B 10 'sysfs_read_vpd: read failed' | grep open | tail -n1
open("/sys/bus/pci/devices/0000:04:03.0/vpd", O_RDONLY) = 4

04:03.0 RAID bus controller: Compaq Computer Corporation Smart Array 64xx (rev 01)

#ocsinventory-agent --server=ocs.example.com
pcilib: sysfs_read_vpd: read failed: Connection timed out

This error occurs because sysfs_read_vpd fails. File exists and is successfully opened, for example:

> open("/sys/bus/pci/devices/0000:07:00.0/vpd", O_RDONLY) = 4

but reading from it fails:

> pread64(4, 0xfffc4daef57, 1, 0) = -1 ETIMEDOUT (Connection timed out)

cat /sys/bus/pci/devices/0000:07:00.0/vpd
cat: /sys/bus/pci/devices/0000:07:00.0/vpd: Connection timed out

This means problem reported by lspci really exists, but it's not caused by pciutils, more likely by kernel driver?

reassigning

This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Setting to Fedora 12 since I still see it there. Also, this has been cloned to RHEL6 beta (BZ 586979).

Most likely this error is due to bad firmware on the card.  I've seen cards advertise an erroneous number of vpd entries that cause this warning.

I've pushed a patch to linux-pci and it has been queued for linux-next/linux-2.6 here:

http://www.spinics.net/lists/linux-pci/msg08858.html

P.