Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[APL][IO Mediator]can't detect USB disk after switching the USB port of touch with build in hub and USB disk during USB mediator test #1365

Closed
mwang106 opened this issue Sep 29, 2018 · 2 comments
Labels
status: closed The issue been closed type: bug Something isn't working

Comments

@mwang106
Copy link
Contributor

•Environment:
•HW: MRB D0 Premium
•Build:
SOS version: 20180925-25170
acrn-hypervisor 2018w38.4.140000p
linux-pk414 4.14.68 99
IFWI Version: ABL_1820HF1
IOC Version :4. 0. 8
UOS kernel: c795424a331f [upstream] drm/i915/gvt: Fix stack-out-of-bounds bug in cmd parser

•Reproduce rate: 100%
•Reproduce steps:

1.connect touch screen with build in hub and usb2.0 disk on standard A port
2. boot to sos
3. Launch uos by usb mediator enabled in launch script:
-s 7,xhci,1-1:1-2:1-3:2-1:2-2:2-3:cap=apl \”
4. in aaag, check touch with build in hub and usb2.o work normally
5. switch the usb port of usb2.0 and hub
6, found only touch with build in hub can work , can't recognize usb2.0 disk.
•Expected result: touch with build in hub and usb2.0 disk work normally after switch USB port.
•Actual result: only touch with build in hub work normally . usb disk can't be recognized after step 5
•Debugging info:
console:/dev/block # xHCI: fail to find physical port 3
xHCI: do not support multiple hubs currently, reject device 1-3

@mwang106 mwang106 added type: bug Something isn't working status: open The issue is working in progress labels Sep 29, 2018
@mwang106
Copy link
Contributor Author

[External_System_ID] 255282

xiaoguangwu added a commit to xiaoguangwu/acrn-hypervisor that referenced this issue Sep 29, 2018
When USB hub is disconnected, its connection status is not cleared
in the DM, this defect will cause the related assigned port could
not be used any more.

This patch is used fix this issue.

Signed-off-by: Xiaoguang Wu <xiaoguang.wu@intel.com>
Reviewed-by: Liang Yang <liang3.yang@intel.com>
Acked-by: Yu Wang <yu1.wang@intel.com>
Tracked-On: projectacrn#1365
lijinxia pushed a commit that referenced this issue Sep 29, 2018
When USB hub is disconnected, its connection status is not cleared
in the DM, this defect will cause the related assigned port could
not be used any more.

This patch is used fix this issue.

Signed-off-by: Xiaoguang Wu <xiaoguang.wu@intel.com>
Reviewed-by: Liang Yang <liang3.yang@intel.com>
Acked-by: Yu Wang <yu1.wang@intel.com>
Tracked-On: #1365
@Mingyuan18 Mingyuan18 added status: closed The issue been closed and removed status: open The issue is working in progress labels Nov 20, 2018
@Mingyuan18
Copy link

Not reproduce the issue on this environment: Acrn-Hypervisor: 2018w42.5.140000p_103; SOS: 25730 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: closed The issue been closed type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants