usb: device descriptor read/64, error -110

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
3
down vote

favorite












after this series of error in kernel




usb 2-1.5: reset full-speed USB device number 3 using ehci-pci

usb 2-1.5: device descriptor read/64, error -110

usb 2-1.5: USB disconnect, device number 3




this process (sadc of sysstat) or lsusb etc hang and stuck in D state forever




root 2543 0.0 0.0 9812 1204 ? D /usr/lib64/sa/sadc -F -L -S ALL 1 1 -

root 100998 0.0 0.0 22328 2116 ? D lsusb

root 84710 0.0 0.0 5476 636 ? D modprobe -r usbhid usbcore usb_common




Q: is it possible to release it without a reboot?



fyi the usb is related to this virtual keyboard and mouse




usb 2-1.5: new full-speed USB device number 3 using ehci-pci

usb 2-1.5: New USB device found, idVendor=046b, idProduct=ff10

usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3

usb 2-1.5: Product: Virtual Keyboard and Mouse

usb 2-1.5: Manufacturer: American Megatrends Inc.

usb 2-1.5: SerialNumber: serial
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver



input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input0

hid-generic 0003:046B:FF10.0001: input,hidraw0: USB HID v1.10 Keyboard [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0000:00:1d.0-1.5/input0



input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.1/input/input1

hid-generic 0003:046B:FF10.0002: input,hidraw1: USB HID v1.10 Mouse [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0000:00:1d.0-1.5/input1











share|improve this question



























    up vote
    3
    down vote

    favorite












    after this series of error in kernel




    usb 2-1.5: reset full-speed USB device number 3 using ehci-pci

    usb 2-1.5: device descriptor read/64, error -110

    usb 2-1.5: USB disconnect, device number 3




    this process (sadc of sysstat) or lsusb etc hang and stuck in D state forever




    root 2543 0.0 0.0 9812 1204 ? D /usr/lib64/sa/sadc -F -L -S ALL 1 1 -

    root 100998 0.0 0.0 22328 2116 ? D lsusb

    root 84710 0.0 0.0 5476 636 ? D modprobe -r usbhid usbcore usb_common




    Q: is it possible to release it without a reboot?



    fyi the usb is related to this virtual keyboard and mouse




    usb 2-1.5: new full-speed USB device number 3 using ehci-pci

    usb 2-1.5: New USB device found, idVendor=046b, idProduct=ff10

    usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3

    usb 2-1.5: Product: Virtual Keyboard and Mouse

    usb 2-1.5: Manufacturer: American Megatrends Inc.

    usb 2-1.5: SerialNumber: serial
    usbcore: registered new interface driver usbhid
    usbhid: USB HID core driver



    input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input0

    hid-generic 0003:046B:FF10.0001: input,hidraw0: USB HID v1.10 Keyboard [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0000:00:1d.0-1.5/input0



    input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.1/input/input1

    hid-generic 0003:046B:FF10.0002: input,hidraw1: USB HID v1.10 Mouse [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0000:00:1d.0-1.5/input1











    share|improve this question

























      up vote
      3
      down vote

      favorite









      up vote
      3
      down vote

      favorite











      after this series of error in kernel




      usb 2-1.5: reset full-speed USB device number 3 using ehci-pci

      usb 2-1.5: device descriptor read/64, error -110

      usb 2-1.5: USB disconnect, device number 3




      this process (sadc of sysstat) or lsusb etc hang and stuck in D state forever




      root 2543 0.0 0.0 9812 1204 ? D /usr/lib64/sa/sadc -F -L -S ALL 1 1 -

      root 100998 0.0 0.0 22328 2116 ? D lsusb

      root 84710 0.0 0.0 5476 636 ? D modprobe -r usbhid usbcore usb_common




      Q: is it possible to release it without a reboot?



      fyi the usb is related to this virtual keyboard and mouse




      usb 2-1.5: new full-speed USB device number 3 using ehci-pci

      usb 2-1.5: New USB device found, idVendor=046b, idProduct=ff10

      usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3

      usb 2-1.5: Product: Virtual Keyboard and Mouse

      usb 2-1.5: Manufacturer: American Megatrends Inc.

      usb 2-1.5: SerialNumber: serial
      usbcore: registered new interface driver usbhid
      usbhid: USB HID core driver



      input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input0

      hid-generic 0003:046B:FF10.0001: input,hidraw0: USB HID v1.10 Keyboard [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0000:00:1d.0-1.5/input0



      input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.1/input/input1

      hid-generic 0003:046B:FF10.0002: input,hidraw1: USB HID v1.10 Mouse [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0000:00:1d.0-1.5/input1











      share|improve this question















      after this series of error in kernel




      usb 2-1.5: reset full-speed USB device number 3 using ehci-pci

      usb 2-1.5: device descriptor read/64, error -110

      usb 2-1.5: USB disconnect, device number 3




      this process (sadc of sysstat) or lsusb etc hang and stuck in D state forever




      root 2543 0.0 0.0 9812 1204 ? D /usr/lib64/sa/sadc -F -L -S ALL 1 1 -

      root 100998 0.0 0.0 22328 2116 ? D lsusb

      root 84710 0.0 0.0 5476 636 ? D modprobe -r usbhid usbcore usb_common




      Q: is it possible to release it without a reboot?



      fyi the usb is related to this virtual keyboard and mouse




      usb 2-1.5: new full-speed USB device number 3 using ehci-pci

      usb 2-1.5: New USB device found, idVendor=046b, idProduct=ff10

      usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3

      usb 2-1.5: Product: Virtual Keyboard and Mouse

      usb 2-1.5: Manufacturer: American Megatrends Inc.

      usb 2-1.5: SerialNumber: serial
      usbcore: registered new interface driver usbhid
      usbhid: USB HID core driver



      input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input0

      hid-generic 0003:046B:FF10.0001: input,hidraw0: USB HID v1.10 Keyboard [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0000:00:1d.0-1.5/input0



      input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.1/input/input1

      hid-generic 0003:046B:FF10.0002: input,hidraw1: USB HID v1.10 Mouse [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0000:00:1d.0-1.5/input1








      usb






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Apr 28 '17 at 4:45

























      asked Apr 28 '17 at 4:38









      J H

      1841210




      1841210




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          The problem cause was for the usb disconnect was a partial success, ideally it should be like this in dmesg.




          [2759033.084067] ehci-pci 0000:00:1a.0: remove, state 4

          [2759033.084080] usb usb1: USB disconnect, device number 1

          [2759033.084082] usb 1-1: USB disconnect, device number 2

          [2759033.088425] ehci-pci 0000:00:1a.0: USB bus 1 deregistered

          [2759054.553007] ehci-pci 0000:00:1d.0: remove, state 1

          [2759054.553018] usb usb2: USB disconnect, device number 1

          [2759054.553020] usb 2-1: USB disconnect, device number 2

          [2759054.553022] usb 2-1.5: USB disconnect, device number 3




          Solution was to modify sysstat to prevent USB from causing the issue.



          FROM:
          180:ub:*:0:a:32:p:8:USB block devices



          TO:
          #180:ub:*:0:a:32:p:8:USB block devices



          Then restart sysstat service.
          systemctl restart sysstat.service






          share|improve this answer




















            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "106"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f361838%2fusb-device-descriptor-read-64-error-110%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            The problem cause was for the usb disconnect was a partial success, ideally it should be like this in dmesg.




            [2759033.084067] ehci-pci 0000:00:1a.0: remove, state 4

            [2759033.084080] usb usb1: USB disconnect, device number 1

            [2759033.084082] usb 1-1: USB disconnect, device number 2

            [2759033.088425] ehci-pci 0000:00:1a.0: USB bus 1 deregistered

            [2759054.553007] ehci-pci 0000:00:1d.0: remove, state 1

            [2759054.553018] usb usb2: USB disconnect, device number 1

            [2759054.553020] usb 2-1: USB disconnect, device number 2

            [2759054.553022] usb 2-1.5: USB disconnect, device number 3




            Solution was to modify sysstat to prevent USB from causing the issue.



            FROM:
            180:ub:*:0:a:32:p:8:USB block devices



            TO:
            #180:ub:*:0:a:32:p:8:USB block devices



            Then restart sysstat service.
            systemctl restart sysstat.service






            share|improve this answer
























              up vote
              0
              down vote













              The problem cause was for the usb disconnect was a partial success, ideally it should be like this in dmesg.




              [2759033.084067] ehci-pci 0000:00:1a.0: remove, state 4

              [2759033.084080] usb usb1: USB disconnect, device number 1

              [2759033.084082] usb 1-1: USB disconnect, device number 2

              [2759033.088425] ehci-pci 0000:00:1a.0: USB bus 1 deregistered

              [2759054.553007] ehci-pci 0000:00:1d.0: remove, state 1

              [2759054.553018] usb usb2: USB disconnect, device number 1

              [2759054.553020] usb 2-1: USB disconnect, device number 2

              [2759054.553022] usb 2-1.5: USB disconnect, device number 3




              Solution was to modify sysstat to prevent USB from causing the issue.



              FROM:
              180:ub:*:0:a:32:p:8:USB block devices



              TO:
              #180:ub:*:0:a:32:p:8:USB block devices



              Then restart sysstat service.
              systemctl restart sysstat.service






              share|improve this answer






















                up vote
                0
                down vote










                up vote
                0
                down vote









                The problem cause was for the usb disconnect was a partial success, ideally it should be like this in dmesg.




                [2759033.084067] ehci-pci 0000:00:1a.0: remove, state 4

                [2759033.084080] usb usb1: USB disconnect, device number 1

                [2759033.084082] usb 1-1: USB disconnect, device number 2

                [2759033.088425] ehci-pci 0000:00:1a.0: USB bus 1 deregistered

                [2759054.553007] ehci-pci 0000:00:1d.0: remove, state 1

                [2759054.553018] usb usb2: USB disconnect, device number 1

                [2759054.553020] usb 2-1: USB disconnect, device number 2

                [2759054.553022] usb 2-1.5: USB disconnect, device number 3




                Solution was to modify sysstat to prevent USB from causing the issue.



                FROM:
                180:ub:*:0:a:32:p:8:USB block devices



                TO:
                #180:ub:*:0:a:32:p:8:USB block devices



                Then restart sysstat service.
                systemctl restart sysstat.service






                share|improve this answer












                The problem cause was for the usb disconnect was a partial success, ideally it should be like this in dmesg.




                [2759033.084067] ehci-pci 0000:00:1a.0: remove, state 4

                [2759033.084080] usb usb1: USB disconnect, device number 1

                [2759033.084082] usb 1-1: USB disconnect, device number 2

                [2759033.088425] ehci-pci 0000:00:1a.0: USB bus 1 deregistered

                [2759054.553007] ehci-pci 0000:00:1d.0: remove, state 1

                [2759054.553018] usb usb2: USB disconnect, device number 1

                [2759054.553020] usb 2-1: USB disconnect, device number 2

                [2759054.553022] usb 2-1.5: USB disconnect, device number 3




                Solution was to modify sysstat to prevent USB from causing the issue.



                FROM:
                180:ub:*:0:a:32:p:8:USB block devices



                TO:
                #180:ub:*:0:a:32:p:8:USB block devices



                Then restart sysstat service.
                systemctl restart sysstat.service







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 16 '17 at 0:35









                J H

                1841210




                1841210



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f361838%2fusb-device-descriptor-read-64-error-110%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown






                    Popular posts from this blog

                    How to check contact read email or not when send email to Individual?

                    Displaying single band from multi-band raster using QGIS

                    How many registers does an x86_64 CPU actually have?