Bug 1470 - USB3 External HD mounting problem
Summary: USB3 External HD mounting problem
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2011-05-29 09:20 CEST by Ojangu
Modified: 2011-12-06 12:24 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
dmesg output before (49.20 KB, text/plain)
2011-05-29 09:21 CEST, Ojangu 		Details
dmesg output after (49.32 KB, application/octet-stream)
2011-05-29 09:22 CEST, Ojangu 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Ojangu 2011-05-29 09:20:55 CEST 
For mounting USB3 external HD I must first swich them of, unplug from USB3, then swich on and plug HS to USB3 back. Tehn it woeks normally. IF in spme situation s have done colt restart, tehn it't mounting automatically. External HD is frpm WD (My Book).

dmesg outputs before and after unplugungin are in files: after and before
Comment 1 Ojangu 2011-05-29 09:21:47 CEST 
Created attachment 493 [details]
dmesg output before
Comment 2 Ojangu 2011-05-29 09:22:35 CEST 
Created attachment 494 [details]
dmesg output after
Comment 3 Marja Van Waes 2011-10-16 11:13:08 CEST 
@ Jaanus

Sorry for responding so late. 
We have a newer kernel now, and AFAIK some xhci issues for USB3 were fixed 

Can you confirm your problem is solved, now?

Keywords: (none) => NEEDINFO
CC: (none) => marja11

Comment 4 Marja Van Waes 2011-11-12 22:44:11 CET 
Reporter, could you please reply to the previous question? If you don't reply this bug can be closed as OLD two weeks from now. Thank you.
Manuel Hiebel 2011-11-17 14:56:17 CET

Component: Release (media or process) => RPM Packages

Comment 5 Marja Van Waes 2011-12-06 12:24:55 CET 
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.