Bug 697794 - USB topology change test for USB 3.0 device with ExpressCard USB 3.0 host port failed
Summary: USB topology change test for USB 3.0 device with ExpressCard USB 3.0 host por...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.1
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Don Zickus
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-19 09:46 UTC by qcui
Modified: 2011-05-03 03:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-03 03:31:26 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description qcui 2011-04-19 09:46:34 UTC
Description of problem:
USB topology change test for USB 3.0 device with ExpressCard USB 3.0
host port always failed. The system could not probe the USB 3.0 device out. 

Version-Release number of selected component (if applicable):
# uname -a
Linux wlan-5-235.nay.redhat.com 2.6.32-128.el6.x86_64 #1 SMP Mon Mar 28
21:55:33 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
# more /etc/redhat-release
Red Hat Enterprise Linux Workstation release 6.0 (Santiago)

How reproducible:
Always

Steps to Reproduce:
1.attach the ExpressCard USB 3.0 to the USB 2.0 port
2.attach the USB 3.0 device to the ExpressCard USB 3.0 host port
3.change the USB topology of the USB 3.0 device 
4.# fdisk -l

Actual results:
Fail

Expected results:
Pass

Comment 2 Qian Cai 2011-04-20 00:38:01 UTC
(In reply to comment #0)
> Description of problem:
> USB topology change test for USB 3.0 device with ExpressCard USB 3.0
> host port always failed. The system could not probe the USB 3.0 device out. 
> 
> Version-Release number of selected component (if applicable):
> # uname -a
> Linux wlan-5-235.nay.redhat.com 2.6.32-128.el6.x86_64 #1 SMP Mon Mar 28
> 21:55:33 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
> # more /etc/redhat-release
> Red Hat Enterprise Linux Workstation release 6.0 (Santiago)
> 
> How reproducible:
> Always
> 
> Steps to Reproduce:
> 1.attach the ExpressCard USB 3.0 to the USB 2.0 port
I think that is to attach ExpressCard USB 3.0 to an ExpressCard slot in the laptop.

Comment 3 RHEL Program Management 2011-04-20 06:01:33 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 4 qcui 2011-04-20 06:59:23 UTC

(In reply to comment #0)

> 
> Steps to Reproduce:
> 1.attach the ExpressCard USB 3.0 to the USB 2.0 port
> 2.attach the USB 3.0 device to the ExpressCard USB 3.0 host port
> 3.change the USB topology of the USB 3.0 device 
> 4.# fdisk -l
> 

For your information, the specific steps to change the USB topology are as
follows.
1.attach a USB 2.0 hub to another ExpressCard USB 3.0 port.
2.detach the USB 3.0 device from the ExpressCard USB 3.0 port and reattach the
 USB 3.0 device to the USB 2.0 hub port.

Comment 5 Don Zickus 2011-04-25 13:57:39 UTC
(In reply to comment #4)
> 
> (In reply to comment #0)
> 
> > 
> > Steps to Reproduce:
> > 1.attach the ExpressCard USB 3.0 to the USB 2.0 port
> > 2.attach the USB 3.0 device to the ExpressCard USB 3.0 host port
> > 3.change the USB topology of the USB 3.0 device 
> > 4.# fdisk -l
> > 
> 
> For your information, the specific steps to change the USB topology are as
> follows.
> 1.attach a USB 2.0 hub to another ExpressCard USB 3.0 port.
> 2.detach the USB 3.0 device from the ExpressCard USB 3.0 port and reattach the
>  USB 3.0 device to the USB 2.0 hub port.

Hubs plugged into USB3.0 cards are not going to be fully supported for RHEL-6.1.  There are various issues with the code that will be worked out in RHEL-6.2.

Cheers,
Don

Comment 6 Qian Cai 2011-05-03 03:31:26 UTC
This is fixed in recent usb-2.6 tree.


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