Results 1 to 3 of 3

Thread: USB 3.0 malfunction

  1. #1

    Default USB 3.0 malfunction

    So my usb 3.0 died randomly.. I can't find out why. Sometimes it works for days sometimes it dead after few second of work. Also I've found that it works longer if I do not use a usb hub, but anyway can die too. Is this a driver bug? Motherboard was replaced on new one and I have the same issue.

    Code:
    [  492.587402] usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd
    [  493.207992] usb 4-1.1: new SuperSpeed USB device number 4 using xhci_hcd
    [  493.829515] usb 4-1.1.1: new SuperSpeed USB device number 5 using xhci_hcd
    [  493.910527] usb 4-1.1.2: new SuperSpeed USB device number 6 using xhci_hcd
    [  526.332663] usb 4-1.1.1: reset SuperSpeed USB device number 5 using xhci_hcd
    [  526.344365] xhci_hcd 0000:04:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880244fe8240
    [  526.344376] xhci_hcd 0000:04:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880244fe8280
    [  571.246711] usb 4-1.1.1: new SuperSpeed USB device number 7 using xhci_hcd
    [  610.448473] usb 4-1.1.1: reset SuperSpeed USB device number 7 using xhci_hcd
    [  610.460303] xhci_hcd 0000:04:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801d2177d40
    [  610.460313] xhci_hcd 0000:04:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801d2177d80
    [  639.022048] usb 4-1.1.1: new SuperSpeed USB device number 8 using xhci_hcd
    [  696.805293] usb 3-1.1.2: new high-speed USB device number 8 using xhci_hcd
    [  701.809926] xhci_hcd 0000:04:00.0: Timeout while waiting for address device command
    [  718.130117] xhci_hcd 0000:04:00.0: Timeout while waiting for a slot
    [  732.183751] xhci_hcd 0000:04:00.0: Stopped the command ring failed, maybe the host is dead
    [  732.183767] xhci_hcd 0000:04:00.0: Abort command ring failed
    [  732.184281] xhci_hcd 0000:04:00.0: HC died; cleaning up
    [  732.184298] xHCI xhci_free_dev called with unaddressed device
    [  737.189067] xhci_hcd 0000:04:00.0: Timeout while waiting for a slot
    [  737.189077] xhci_hcd 0000:04:00.0: Abort the command ring, but the xHCI is dead.
    [  737.189101] xHCI xhci_free_dev called with unaddressed device
    [  742.194085] xhci_hcd 0000:04:00.0: Timeout while waiting for a slot
    [  742.194095] xhci_hcd 0000:04:00.0: Abort the command ring, but the xHCI is dead.
    [  742.194121] xHCI xhci_free_dev called with unaddressed device
    With usb 2.0 everthing is fine.
    Any suggestions?
    Laptop asus k53sd
    ~> uname -a
    Linux linux-7zm2.site 3.11.10-7-desktop #1 SMP PREEMPT Mon Feb 3 09:41:24 UTC 2014 (750023e) x86_64 x86_64 x86_64 GNU/Linux

    OpenSuSE 13.1.

    Practically because this bug I have no usb 3.0, only 2.0 is reliable

  2. #2

    Default Re: USB 3.0 malfunction

    I've made little investigation. It actually common problem for my controller


    04:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller



    I've found couple "solutions", but not sure how it works.
    I found a reference to adding the line
    PHP Code:
    blacklist uas

    to file 
    /etc/modprobe.d/blacklist.conf 
    Is this should be in the same file for netrunner? Or better use custom one? And what exactly do uas module?
    Second one related to usb suspend mode. I suppose it should be in udev config? Where exactly will be proper place for it?


    PHP Code:
    ACTION=="add"SUBSYSTEM=="usb"TEST=="power/autosuspend" ATTR{power/autosuspend}="0" 

  3. #3

    Default Re: USB 3.0 malfunction

    Quote Originally Posted by slimy View Post
    I found a reference to adding the line
    PHP Code:
    blacklist uas

    to file 
    /etc/modprobe.d/blacklist.conf 
    Is this should be in the same file for netrunner? Or better use custom one? And what exactly do uas module?
    In general I'd say better use a custom one, because the "50-blacklist.conf" is provided by an openSUSE package.
    Also this makes removing your custom stuff easier.

    But the standard /etc/modprobe.d/blacklist.conf as shipped in openSUSE 13.1 already contains that line:
    Code:
    wolfi@linux-lf90:~> tail -3 /etc/modprobe.d/50-blacklist.conf
    # uas has been confirmed to be hopelessly broken
    # Bug bnc#770301
    blacklist uas
    And the comment refers to this bug report: https://bugzilla.novell.com/show_bug.cgi?id=770301

    If yours doesn't have this, you should add it.

    Second one related to usb suspend mode. I suppose it should be in udev config? Where exactly will be proper place for it?


    PHP Code:
    ACTION=="add"SUBSYSTEM=="usb"TEST=="power/autosuspend" ATTR{power/autosuspend}="0" 
    This looks like an udev rule.
    You should add it to a custom file in /etc/udev/rules.d/.
    Last edited by wolfi323; 24-May-2014 at 23:30.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •