Bug 368351 - RHEL4 U6: usb test does not detect plugged in device
Summary: RHEL4 U6: usb test does not detect plugged in device
Alias: None
Product: Red Hat Hardware Certification Program
Classification: Red Hat
Component: Test Suite (tests)
Version: 5
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Greg Nichols
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2007-11-06 15:11 UTC by Greg Nichols
Modified: 2008-07-16 21:57 UTC (History)
0 users

Clone Of:
Last Closed: 2008-02-15 15:25:29 UTC

Attachments (Terms of Use)
all files attached. (1.26 MB, application/x-gzip)
2008-01-11 05:52 UTC, Satyabrata Maitra
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2008:0033 normal SHIPPED_LIVE hts new package and bug fix update 2008-02-15 15:25:27 UTC

Description Greg Nichols 2007-11-06 15:11:50 UTC
Description of problem:

For RHEL 4, the usb test does not detect usb devices when 
they are plugged in as requested.

Version-Release number of selected component (if applicable):

HTS 5.1 R12, RHEL 4 U6

How reproducible:


Comment 1 Greg Nichols 2007-11-06 15:12:46 UTC
Actually, it's HTS 5.1 R11.

Comment 2 Greg Nichols 2007-11-27 15:16:12 UTC
Fixed R13

Comment 4 Satyabrata Maitra 2008-01-04 09:16:26 UTC
I attempted to test this bug, but faced a problem creating hts plan for a
particular arch - ia64 El4.6-AS system. Bug filed and URL given below.


Comment 5 Greg Nichols 2008-01-04 13:56:40 UTC
You won't be able to run the USB test in a guest environment, as you have
attempted in 427339.  You need to run the test on a direct RHEL 4 U6 install.

Comment 7 Satyabrata Maitra 2008-01-09 06:38:16 UTC
Hi Greg

I have something to explain about my comment in #4 and your comment in #5.

First of all, I did not use guest environment or virtual system. I used an ia64
system with EL4-U6, full installation. And obviously it was with remote access
with ssh as, this system is in Brisbane!

And in Comment #4, my concern was "unable to create test plan for ia64 system',
Not "the USB test issue on it". 

Because, if the test plan can not be created, none of the tests can be run.

So, now my queries are as follows :-
If the system-under-test is remotely placed to me, and installed with Full
EL4-U6 (not in guest environment), and I am having the access on it via ssh, and
there is somebody who can assists me to ensure that there is at least one USB
device attached in the system, Can I run USB testing for hts there? I should,
and the test also should PASS, if I put the right information during testing
like "how many usb devise attached" etc. 

Actually this was the scenario I followed when attempted to test USB on EL4-U6
system, but It FAILED to create test plan, and I had to postpone my test,
because without Test Plan, I can't proceed to run any tests. 

Please inform your suggestions.

Comment 9 Greg Nichols 2008-01-09 12:19:02 UTC
You can not run the USB test remotely, as you need to be able to insert and
remove physical USB devices.

You can not run the USB test in a guest OS install.

Comment 10 Satyabrata Maitra 2008-01-11 05:52:32 UTC
Created attachment 291353 [details]
all files attached.

Comment 11 Satyabrata Maitra 2008-01-11 05:59:57 UTC
Tested this bug on ia64 system with EL4-U6.
This bug is fixed now.
Its now detecting the plugged in usb devices and its ports during testing. Both
the usb test and associated info test are PASS.

Version of the component Tested :
Arch :- ia64 (Not guest Environment)
O.S : EL4-U6

Additional Information :- All the .xml files, .log files, .rpm files and other
related files are attached in .tar file above in comment #10. 

i created a hardware certification also with its result .rpm file. Certification
number is 265513.

Comment 14 errata-xmlrpc 2008-02-15 15:25:29 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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