Red Hat Bugzilla – Bug 1001308
FEAT: expresscard test should use dmidecode data to plan expresscard test
Last modified: 2013-11-13 04:56:42 EST
Description of problem:
Currently the expresscard test uses battery + pcie + usb to say there is probably an expresscard slot. At least recent versions of dmidecode provide expresscard data, though it must be researched which versions in RHEL6.x provide this and which versions provide correct information and how often some set of laptop vendors properly populate this field.
From a Lenovo X220
[rlandry@unused ~]$ rpm -qf /etc/redhat-release
[rlandry@unused ~]$ uname -a
Linux unused 2.6.32-358.el6.x86_64 #1 SMP Tue Jan 29 11:47:41 EST 2013 x86_64 x86_64 x86_64 GNU/Linux
[root@unused ~]# rpm -q dmidecode
Handle 0x0027, DMI type 9, 17 bytes
System Slot Information
Designation: ExpressCard Slot
Type: x1 PCI Express
Current Usage: Available
Hot-plug devices are supported
Bus Address: 0000:00:00.0
...My understanding is the x1 is referring to the capabilities of the slot, and the fact that there is only a single entry is referring to there being a single slot.
Created attachment 802418 [details]
patch to use dmidecode as an expresscard slot detection
I couldn't find what object we're storing the dmidecode data in the harness, it didn't look like we were so I just added a new call. This over time should probably just be part of the hardware dictionary object? Also I only added detection but from the output I think we could look for multiple stanza's with express card, and use the count of those as the number of expresscard slots. Unfortunately I have no way to test that as my box only has a single slot
Patch appears to be present, and expresscard at least partially pass. Tests with the USB expresscard pass as expected, tests for pcie on expresscard fail due to lack of a peripheral. Will retry later with a drive attached.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.