Comment # 62 on bug 1200461 from Mike DeMicco

(In reply to Martin Wilck from comment #61)
> I'm wondering if the strace in comment 35 is a red herring. The config space
> is obviously readable just fine. This is just a bridge, so my musings about
> VPD in comment 43 don't apply here, I suppose.
> 
> I pretty much out of ideas here. J���rg?

This is the limited contents of the directory where the crash occurs when read:

mike@mike-pc:~$ ls /sys/devices/pci0000:00/
0000:00:00.0  0000:00:10.0  0000:00:13.0  0000:00:15.0  0000:00:1a.7 
0000:00:1c.3  0000:00:1d.2  0000:00:1f.2   PNP0C14:00
0000:00:01.0  0000:00:10.1  0000:00:14.0  0000:00:1a.0  0000:00:1b.0 
0000:00:1c.4  0000:00:1d.7  0000:00:1f.3   power
0000:00:02.0  0000:00:11.0  0000:00:14.1  0000:00:1a.1  0000:00:1c.0 
0000:00:1d.0  0000:00:1e.0  firmware_node  uevent
0000:00:03.0  0000:00:11.1  0000:00:14.2  0000:00:1a.2  0000:00:1c.1 
0000:00:1d.1  0000:00:1f.0  pci_bus        waiting_for_supplier

Perhaps it's looking for a file (config?) that isn't there and crashes when it
isn't found? 

Why can I execute "udevadm info -a /dev/block/8:16" as a user, and no crash
occurs yet when done as root, the computer crashes?