USB Device not responding to set address












0














I have a built-in USB device that is not responding to setup address. It tries to set the device up continuously and fails continuously: wasting battery, CPU, disk space, etc.



Is there a way to kill the USB port or otherwise stop the kernel from trying to configure it?



I've tried rebooting, using uhubctl (not known as a smart hub), playing with port's power/autosuspend_delay_ms (gets input/output error), playing with the port's power/control (already auto), playing with the hub's power/level (invalid argument). Of course I cannot try another cable--it is an embedded device
and I would prefer to not disable the hub entirely, but I'd be willing to try it. I can virtually remove the PCI card via Linux, but that takes out stuff I actually need (the high speed usb hub).



I'm going to guess that the device is actually a laptop fingerprint reader that I've never used or been able to use, but I remember being around.



[ 7283.684834] usb usb1-port7: attempt power cycle
[ 7284.312659] usb 1-7: new full-speed USB device number 41 using xhci_hcd
[ 7284.312858] usb 1-7: Device not responding to setup address.
[ 7284.516966] usb 1-7: Device not responding to setup address.
[ 7284.724647] usb 1-7: device not accepting address 41, error -71
[ 7284.838653] usb 1-7: new full-speed USB device number 42 using xhci_hcd
[ 7284.838852] usb 1-7: Device not responding to setup address.
[ 7285.044852] usb 1-7: Device not responding to setup address.
[ 7285.252760] usb 1-7: device not accepting address 42, error -71
[ 7285.252861] usb usb1-port7: unable to enumerate USB device
[ 7285.366647] usb 1-7: new full-speed USB device number 43 using xhci_hcd
[ 7285.480810] usb 1-7: device descriptor read/64, error -71
[ 7285.702811] usb 1-7: device descriptor read/64, error -71
[ 7285.918653] usb 1-7: new full-speed USB device number 44 using xhci_hcd
[ 7286.032729] usb 1-7: device descriptor read/64, error -71
[ 7286.254780] usb 1-7: device descriptor read/64, error -71
[ 7286.356717] usb usb1-port7: attempt power cycle
Repeat forever


Running lsusb of course does not report the device. However the upstream hub is:



Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)








share



























    0














    I have a built-in USB device that is not responding to setup address. It tries to set the device up continuously and fails continuously: wasting battery, CPU, disk space, etc.



    Is there a way to kill the USB port or otherwise stop the kernel from trying to configure it?



    I've tried rebooting, using uhubctl (not known as a smart hub), playing with port's power/autosuspend_delay_ms (gets input/output error), playing with the port's power/control (already auto), playing with the hub's power/level (invalid argument). Of course I cannot try another cable--it is an embedded device
    and I would prefer to not disable the hub entirely, but I'd be willing to try it. I can virtually remove the PCI card via Linux, but that takes out stuff I actually need (the high speed usb hub).



    I'm going to guess that the device is actually a laptop fingerprint reader that I've never used or been able to use, but I remember being around.



    [ 7283.684834] usb usb1-port7: attempt power cycle
    [ 7284.312659] usb 1-7: new full-speed USB device number 41 using xhci_hcd
    [ 7284.312858] usb 1-7: Device not responding to setup address.
    [ 7284.516966] usb 1-7: Device not responding to setup address.
    [ 7284.724647] usb 1-7: device not accepting address 41, error -71
    [ 7284.838653] usb 1-7: new full-speed USB device number 42 using xhci_hcd
    [ 7284.838852] usb 1-7: Device not responding to setup address.
    [ 7285.044852] usb 1-7: Device not responding to setup address.
    [ 7285.252760] usb 1-7: device not accepting address 42, error -71
    [ 7285.252861] usb usb1-port7: unable to enumerate USB device
    [ 7285.366647] usb 1-7: new full-speed USB device number 43 using xhci_hcd
    [ 7285.480810] usb 1-7: device descriptor read/64, error -71
    [ 7285.702811] usb 1-7: device descriptor read/64, error -71
    [ 7285.918653] usb 1-7: new full-speed USB device number 44 using xhci_hcd
    [ 7286.032729] usb 1-7: device descriptor read/64, error -71
    [ 7286.254780] usb 1-7: device descriptor read/64, error -71
    [ 7286.356717] usb usb1-port7: attempt power cycle
    Repeat forever


    Running lsusb of course does not report the device. However the upstream hub is:



    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)








    share

























      0












      0








      0







      I have a built-in USB device that is not responding to setup address. It tries to set the device up continuously and fails continuously: wasting battery, CPU, disk space, etc.



      Is there a way to kill the USB port or otherwise stop the kernel from trying to configure it?



      I've tried rebooting, using uhubctl (not known as a smart hub), playing with port's power/autosuspend_delay_ms (gets input/output error), playing with the port's power/control (already auto), playing with the hub's power/level (invalid argument). Of course I cannot try another cable--it is an embedded device
      and I would prefer to not disable the hub entirely, but I'd be willing to try it. I can virtually remove the PCI card via Linux, but that takes out stuff I actually need (the high speed usb hub).



      I'm going to guess that the device is actually a laptop fingerprint reader that I've never used or been able to use, but I remember being around.



      [ 7283.684834] usb usb1-port7: attempt power cycle
      [ 7284.312659] usb 1-7: new full-speed USB device number 41 using xhci_hcd
      [ 7284.312858] usb 1-7: Device not responding to setup address.
      [ 7284.516966] usb 1-7: Device not responding to setup address.
      [ 7284.724647] usb 1-7: device not accepting address 41, error -71
      [ 7284.838653] usb 1-7: new full-speed USB device number 42 using xhci_hcd
      [ 7284.838852] usb 1-7: Device not responding to setup address.
      [ 7285.044852] usb 1-7: Device not responding to setup address.
      [ 7285.252760] usb 1-7: device not accepting address 42, error -71
      [ 7285.252861] usb usb1-port7: unable to enumerate USB device
      [ 7285.366647] usb 1-7: new full-speed USB device number 43 using xhci_hcd
      [ 7285.480810] usb 1-7: device descriptor read/64, error -71
      [ 7285.702811] usb 1-7: device descriptor read/64, error -71
      [ 7285.918653] usb 1-7: new full-speed USB device number 44 using xhci_hcd
      [ 7286.032729] usb 1-7: device descriptor read/64, error -71
      [ 7286.254780] usb 1-7: device descriptor read/64, error -71
      [ 7286.356717] usb usb1-port7: attempt power cycle
      Repeat forever


      Running lsusb of course does not report the device. However the upstream hub is:



      Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
      00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)








      share













      I have a built-in USB device that is not responding to setup address. It tries to set the device up continuously and fails continuously: wasting battery, CPU, disk space, etc.



      Is there a way to kill the USB port or otherwise stop the kernel from trying to configure it?



      I've tried rebooting, using uhubctl (not known as a smart hub), playing with port's power/autosuspend_delay_ms (gets input/output error), playing with the port's power/control (already auto), playing with the hub's power/level (invalid argument). Of course I cannot try another cable--it is an embedded device
      and I would prefer to not disable the hub entirely, but I'd be willing to try it. I can virtually remove the PCI card via Linux, but that takes out stuff I actually need (the high speed usb hub).



      I'm going to guess that the device is actually a laptop fingerprint reader that I've never used or been able to use, but I remember being around.



      [ 7283.684834] usb usb1-port7: attempt power cycle
      [ 7284.312659] usb 1-7: new full-speed USB device number 41 using xhci_hcd
      [ 7284.312858] usb 1-7: Device not responding to setup address.
      [ 7284.516966] usb 1-7: Device not responding to setup address.
      [ 7284.724647] usb 1-7: device not accepting address 41, error -71
      [ 7284.838653] usb 1-7: new full-speed USB device number 42 using xhci_hcd
      [ 7284.838852] usb 1-7: Device not responding to setup address.
      [ 7285.044852] usb 1-7: Device not responding to setup address.
      [ 7285.252760] usb 1-7: device not accepting address 42, error -71
      [ 7285.252861] usb usb1-port7: unable to enumerate USB device
      [ 7285.366647] usb 1-7: new full-speed USB device number 43 using xhci_hcd
      [ 7285.480810] usb 1-7: device descriptor read/64, error -71
      [ 7285.702811] usb 1-7: device descriptor read/64, error -71
      [ 7285.918653] usb 1-7: new full-speed USB device number 44 using xhci_hcd
      [ 7286.032729] usb 1-7: device descriptor read/64, error -71
      [ 7286.254780] usb 1-7: device descriptor read/64, error -71
      [ 7286.356717] usb usb1-port7: attempt power cycle
      Repeat forever


      Running lsusb of course does not report the device. However the upstream hub is:



      Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
      00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)






      linux-kernel usb





      share












      share










      share



      share










      asked 1 min ago









      Seth RobertsonSeth Robertson

      21513




      21513






















          0






          active

          oldest

          votes











          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%2f493607%2fusb-device-not-responding-to-set-address%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          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%2f493607%2fusb-device-not-responding-to-set-address%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

          Accessing regular linux commands in Huawei's Dopra Linux

          Can't connect RFCOMM socket: Host is down

          Kernel panic - not syncing: Fatal Exception in Interrupt