Bug 217941
Summary: | HTS: RHEL 5 usb test failed on system with internal hub chip | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Hardware Certification Program | Reporter: | Garry Wong <garry.wong> | ||||||||||
Component: | Test Suite (tests) | Assignee: | Greg Nichols <gnichols> | ||||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Greg Nichols <gnichols> | ||||||||||
Severity: | high | Docs Contact: | |||||||||||
Priority: | medium | ||||||||||||
Version: | 5 | CC: | hcp-admin, hien1, markwiz, sglass, wwlinuxengineering | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | i686 | ||||||||||||
OS: | Linux | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2007-01-29 16:35:41 UTC | Type: | --- | ||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||
Documentation: | --- | CRM: | |||||||||||
Verified Versions: | Category: | --- | |||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
Embargoed: | |||||||||||||
Bug Depends On: | |||||||||||||
Bug Blocks: | 217940 | ||||||||||||
Attachments: |
|
Description
Garry Wong
2006-11-30 20:45:19 UTC
Created attachment 142523 [details]
hts test logs
It did not recognize the usb device when the test was asking you to plug the device. But it does recognize outside the test. The internal usb 2.0 hub is a Cypress chip. *** Bug 217940 has been marked as a duplicate of this bug. *** Please attach a HAL dump with the USB device plugged in: 1) Plug in the USB device into a port 2) run: "hal-device > hal.txt" Thanks! Created attachment 142997 [details]
hal txt
hal-device > hal.txt
See attached hal txt. I tried the hts version 14 and this problem still exists. Thanks, I tried hts version 14 on pSeries systems and it hangs at the end of the text on the console. Then it showed usb test failed when I hit <Enter> after 2 hours of hanging there: ---- How many unused USB sockets are there ? response: 2 Cypress Semiconductor Corp. USB-2.0 IDE Adapter appears to be plugged into bus number 1 port number 1 Cypress Semiconductor Corp. CY7C65640 USB-2.0 "TetraHub" appears to be plugged into bus number 1 port number 1 Cypress Semiconductor Corp. CY7C65640 USB-2.0 "TetraHub" appears to be plugged into bus number 1 port number 1 IBM Corp. IBM MM2 appears to be plugged into bus number 2 port number 1 testing socket 1 of 2... Please plug in a USB device - continue? (yes|no) Vendor: Generic Model: USB Flash Drive Rev: 1.00 Type: Direct-Access ANSI SCSI revision: 02 SCSI device sdb: 495616 512-byte hdwr sectors (254 MB) sdb: Write Protect is off sdb: assuming drive cache: write through SCSI device sdb: 495616 512-byte hdwr sectors (254 MB) sdb: Write Protect is off sdb: assuming drive cache: write through sd 5:0:0:0: Attached scsi removable disk sdb sd 5:0:0:0: Attached scsi generic sg3 type 0 ..... usb test hangs here ...... Hit <Enter>, then it continues... ...finished running ./usb.py, exit code=1 recovered exit code=1 rhts-report-result /HTS/hts/usb FAIL /var/log/hts/runs/2/usb/output.log saveOutput: /var/log/hts/runs/2/usb/output.log ----------------- Created attachment 144864 [details]
hal-device log
hal log on pSeries system Power5 720
However, the test command I ran is: hts certify --test=usb I tried HTS-5.0-15 and the results is the same. usb test failed. Fixed R16. Created attachment 146043 [details]
usb info in hts 17
I used hts R17 and still seeing this issue.
Thanks
I ran HTS R17 on a DL360 G5 without incident. The test log follows: USB test: Hewlett-Packard Virtual Keyboard appears to be plugged into bus number 5 port number 1 Hewlett-Packard Virtual Hub appears to be plugged into bus number 5 port number 2 How many unused USB sockets are there? response: 3 testing socket 1 of 3... Please plug in a USB device - continue? (yesno) response: yes SanDisk Corp. U3 Cruzer Micro appears to be plugged into bus number 6 port number 5 found device at 6-5 Please unplug the device and hit the Enter key: confirmed device 6-5 testing socket 2 of 3... Please plug in a USB device - continue? (yesno) response: yes SanDisk Corp. U3 Cruzer Micro appears to be plugged into bus number 6 port number 3 found device at 6-3 Please unplug the device and hit the Enter key: confirmed device 6-3 testing socket 3 of 3... Please plug in a USB device - continue? (yesno) response: yes SanDisk Corp. U3 Cruzer Micro appears to be plugged into bus number 6 port number 4 found device at 6-4 Please unplug the device and hit the Enter key: confirmed device 6-4 ...finished running ./usb.py, exit code=0 Please supply R17 log output similar to above. - Thanks! The system is DL365 G1 which I already mentioned on the repro steps, also I already said this in Description of problem: -However, the usb test passed on system without additional internal 2.0 hub such as ProLiant DL360 G5. The R17 log had been submiited, see comment #15. Thanks, Fixed R21 Verified passing in R21/ Hello IBM, Closing IT based on update from: ----- Additional Comments From hien1.com 2007-01-27 11:35 EDT ------- HTS-5.0-21: fixed USB test. I tested on three different systems: JS20, JS21, p5 720. All PASSED. Congratulation ! Thank You Joe kachuck Internal Status set to 'Resolved' Status set to: Closed by Client Resolution set to: 'Closed by Client' This event sent from IssueTracker by jkachuck issue 111170 |