Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #201229 > unrolled thread
| Started by | deloptes <deloptes@gmail.com> |
|---|---|
| First post | 2018-10-14 20:20 +0200 |
| Last post | 2018-10-16 10:00 +0200 |
| Articles | 8 — 3 participants |
Back to article view | Back to linux.debian.user
USB device not accepting address <n>, error -71 deloptes <deloptes@gmail.com> - 2018-10-14 20:20 +0200
Re: USB device not accepting address <n>, error -71 Reco <recoverym4n@enotuniq.net> - 2018-10-14 20:20 +0200
Re: USB device not accepting address <n>, error -71 deloptes <deloptes@gmail.com> - 2018-10-15 01:40 +0200
Re: USB device not accepting address <n>, error -71 deloptes <deloptes@gmail.com> - 2018-10-15 19:30 +0200
Re: USB device not accepting address <n>, error -71 Reco <recoverym4n@enotuniq.net> - 2018-10-15 19:40 +0200
Re: USB device not accepting address <n>, error -71 Roberto C. Sánchez <roberto@debian.org> - 2018-10-15 20:00 +0200
Re: USB device not accepting address <n>, error -71 deloptes <deloptes@gmail.com> - 2018-10-16 09:10 +0200
Re: USB device not accepting address <n>, error -71 deloptes <deloptes@gmail.com> - 2018-10-16 10:00 +0200
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2018-10-14 20:20 +0200 |
| Subject | USB device not accepting address <n>, error -71 |
| Message-ID | <wIT9D-5BN-5@gated-at.bofh.it> |
Hi, can someone help to debug? After many years I again started having USB issues. Now this is the web cam (web cam works in windows), but it was working fine just few days ago, but since today I get following: [ 4.624284] usb 1-1-port5: Cannot enable. Maybe the USB cable is bad? [ 4.688011] usb 1-1.5: new high-speed USB device number 9 using ehci-pci [ 5.104010] usb 1-1.5: device not accepting address 9, error -71 [ 5.104158] usb 1-1-port5: unable to enumerate USB device [ 5.276010] usb 1-1.5: new high-speed USB device number 10 using ehci-pci [ 6.128273] usb 1-1-port5: Cannot enable. Maybe the USB cable is bad? [ 6.192010] usb 1-1.5: new high-speed USB device number 11 using ehci-pci [ 7.048267] usb 1-1-port5: Cannot enable. Maybe the USB cable is bad? [ 7.048393] usb 1-1-port5: attempt power cycle [ 8.200260] usb 1-1-port5: Cannot enable. Maybe the USB cable is bad? [ 8.264010] usb 1-1.5: new high-speed USB device number 13 using ehci-pci [ 8.680009] usb 1-1.5: device not accepting address 13, error -71 [ 8.680137] usb 1-1-port5: unable to enumerate USB device [ 8.852010] usb 1-1.5: new high-speed USB device number 14 using ehci-pci /var/log/syslog Oct 14 08:41:30 fujitsu kernel: [200161.905684] usb 1-1.3: device not accepting address 3, error -22 Oct 14 08:41:35 fujitsu kernel: [200166.513688] usb 1-1.3: device not accepting address 13, error -71 Oct 14 08:46:52 fujitsu kernel: [200483.529669] usb 1-1.3: device not accepting address 17, error -71 Debian Stretch kernel 4.17.13 also kernel 4.18.14 components of recent update that caused initrd to be rebuild Start-Date: 2018-10-11 23:36:01 Commandline: apt-get upgrade Requested-By: emanoil (1000) Upgrade: intel-microcode:amd64 (3.20180703.2~deb9u1, 3.20180807a.1~deb9u1), I'll try removing microcode if possible. If you have any suitable ideas, it will be appreciated thanks
[toc] | [next] | [standalone]
| From | Reco <recoverym4n@enotuniq.net> |
|---|---|
| Date | 2018-10-14 20:20 +0200 |
| Message-ID | <wIT9E-5BN-11@gated-at.bofh.it> |
| In reply to | #201229 |
Hi. On Sun, Oct 14, 2018 at 08:15:11PM +0200, deloptes wrote: > Hi, > can someone help to debug? > > After many years I again started having USB issues. Now this is the web cam > (web cam works in windows), but it was working fine just few days ago, but > since today I get following: > > > [ 4.624284] usb 1-1-port5: Cannot enable. Maybe the USB cable is bad? What is says here, basically. You USB port is burned out, USB connector lacks contact, USB power is insufficient, etc. About the only thing you can try from the OS side is to disable USB powersaving, but that should be disabled by default. Reco
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2018-10-15 01:40 +0200 |
| Message-ID | <wIY9k-8tW-7@gated-at.bofh.it> |
| In reply to | #201230 |
Reco wrote: > What is says here, basically. > You USB port is burned out, USB connector lacks contact, USB power is > insufficient, etc. > > About the only thing you can try from the OS side is to disable USB > powersaving, but that should be disabled by default. I'll try the webcam tomorrow with windows for a longer time. In my linux box it appears and after a while disappears. IT could be that after 10y it is giving up ... But it could be also that the host hardware is giving up. hard to say, however other devices work fine on the host, so might be the camera. regards
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2018-10-15 19:30 +0200 |
| Message-ID | <wJeQO-1MF-13@gated-at.bofh.it> |
| In reply to | #201230 |
Reco wrote: > What is says here, basically. > You USB port is burned out, USB connector lacks contact, USB power is > insufficient, etc. > > About the only thing you can try from the OS side is to disable USB > powersaving, but that should be disabled by default. Hi, might be that indeed the local controller has something, because on office pc with windows today it was working just fine. I may test the local controller from windows - never erased the original disk. The other option is that after removing some packages and installing updates, the initrd or whatever got f**ked. regards
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@enotuniq.net> |
|---|---|
| Date | 2018-10-15 19:40 +0200 |
| Message-ID | <wJf0t-1Qj-1@gated-at.bofh.it> |
| In reply to | #201267 |
Hi. On Mon, Oct 15, 2018 at 07:28:46PM +0200, deloptes wrote: > Reco wrote: > > > What is says here, basically. > > You USB port is burned out, USB connector lacks contact, USB power is > > insufficient, etc. > > > > About the only thing you can try from the OS side is to disable USB > > powersaving, but that should be disabled by default. > > Hi, > might be that indeed the local controller has something, because on office > pc with windows today it was working just fine. > > I may test the local controller from windows - never erased the original > disk. > > The other option is that after removing some packages and installing > updates, the initrd or whatever got f**ked. I sincerely doubt that hardware errors can be beat that easily. Reco
[toc] | [prev] | [next] | [standalone]
| From | Roberto C. Sánchez <roberto@debian.org> |
|---|---|
| Date | 2018-10-15 20:00 +0200 |
| Message-ID | <wJfjP-1WN-1@gated-at.bofh.it> |
| In reply to | #201267 |
On Mon, Oct 15, 2018 at 07:28:46PM +0200, deloptes wrote: > > Hi, > might be that indeed the local controller has something, because on office > pc with windows today it was working just fine. > It could be the physical ports themselves. I have my desktop system in a 15+ year old case. As of a few years ago, the front USB ports got to the point where the number of devices they could not recognize (I would get the same log messages) annoyed me enough that I got 3.5" front panel with 2 USB 3.0 connectors and gave up the empty bay for that panel. I suspect a combination of physical age and protocol age (they might even be pre-2.0) is the cause of the problem in my case. I will sometimes still use the old ports and when they have a problem I switch to the new ports, which have not yet encountered a problem recognizing a device. Regards, -Roberto -- Roberto C. Sánchez
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2018-10-16 09:10 +0200 |
| Message-ID | <wJrEl-1aA-1@gated-at.bofh.it> |
| In reply to | #201270 |
Roberto C. Sánchez wrote: > > It could be the physical ports themselves. I have my desktop system in > a 15+ year old case. As of a few years ago, the front USB ports got to > the point where the number of devices they could not recognize (I would > get the same log messages) annoyed me enough that I got 3.5" front panel > with 2 USB 3.0 connectors and gave up the empty bay for that panel. I > suspect a combination of physical age and protocol age (they might even > be pre-2.0) is the cause of the problem in my case. > > I will sometimes still use the old ports and when they have a problem I > switch to the new ports, which have not yet encountered a problem > recognizing a device. I have 4-5 USB ports in the back and 4 ports on the front. I tried most of them with same result. IMO it can not be the physical port to connect USB device(s). I have a bluetooth stick, mouse, keyboard and scanner attached and all of them work, but just the camera, since Sunday morning not working. No other updates but the microcode package impact kernel code. I was using 4.17 and now moved to 4.18.14, but nothing helps. I read that microcode is disabled by default (modprobe blacklist) and this is also in the initrd. I have a suspicion it is something with the kernel module that can not be handled, while in windows the driver handles it. Any ideas? thanks regards
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2018-10-16 10:00 +0200 |
| Message-ID | <wJsqK-1qy-7@gated-at.bofh.it> |
| In reply to | #201270 |
Roberto C. Sánchez wrote: > On Mon, Oct 15, 2018 at 07:28:46PM +0200, deloptes wrote: >> >> Hi, >> might be that indeed the local controller has something, because on >> office pc with windows today it was working just fine. >> > It could be the physical ports themselves. I have my desktop system in > a 15+ year old case. As of a few years ago, the front USB ports got to > the point where the number of devices they could not recognize (I would > get the same log messages) annoyed me enough that I got 3.5" front panel > with 2 USB 3.0 connectors and gave up the empty bay for that panel. I > suspect a combination of physical age and protocol age (they might even > be pre-2.0) is the cause of the problem in my case. > > I will sometimes still use the old ports and when they have a problem I > switch to the new ports, which have not yet encountered a problem > recognizing a device. > > Regards, > > -Roberto I plugged in camera again and tested with mplayer mplayer -vo gl2 -tv driver=v4l2:width=640:height=480:device=/dev/video0 tv:// it works. In Skype video does not work, but mic is working again. I am just wondering what could have changed the way it works. Again, I have installed just the regular updates on the 11.10. Upgrade: intel-microcode:amd64 (3.20180703.2~deb9u1, 3.20180807a.1~deb9u1), git-man:amd64 (1:2.11.0-3+deb9u3, 1:2.11.0-3+deb9u4), libgs9:amd64 (9.20~dfsg-3.2+deb9u4, 9.20~dfsg-3.2+deb9u5), python2.7-minimal:amd64 (2.7.13-2+deb9u2, 2.7.13-2+deb9u3), libsnmp-base:amd64 (5.7.3+dfsg-1.7, 5.7.3+dfsg-1.7+deb9u1), libpython2.7:amd64 (2.7.13-2+deb9u2, 2.7.13-2+deb9u3), python2.7:amd64 (2.7.13-2+deb9u2, 2.7.13-2+deb9u3), chromium:amd64 (69.0.3497.81-1~deb9u1, 69.0.3497.92-1~deb9u1), libpython3.5:amd64 (3.5.3-1, 3.5.3-1+deb9u1), libptexenc1:amd64 (2016.20160513.41080.dfsg-2, 2016.20160513.41080.dfsg-2+deb9u1), python3.5:amd64 (3.5.3-1, 3.5.3-1+deb9u1), git:amd64 (1:2.11.0-3+deb9u3, 1:2.11.0-3+deb9u4), python3.5-minimal:amd64 (3.5.3-1, 3.5.3-1+deb9u1), libsnmp30:amd64 (5.7.3+dfsg-1.7, 5.7.3+dfsg-1.7+deb9u1), flashplayer-chromium:amd64 (30.0.0.154-dmo1, 31.0.0.122-dmo1), libtexluajit2:amd64 (2016.20160513.41080.dfsg-2, 2016.20160513.41080.dfsg-2+deb9u1), ghostscript:amd64 (9.20~dfsg-3.2+deb9u4, 9.20~dfsg-3.2+deb9u5), ghostscript-x:amd64 (9.20~dfsg-3.2+deb9u4, 9.20~dfsg-3.2+deb9u5), libgs9-common:amd64 (9.20~dfsg-3.2+deb9u4, 9.20~dfsg-3.2+deb9u5), libsynctex1:amd64 (2016.20160513.41080.dfsg-2, 2016.20160513.41080.dfsg-2+deb9u1), texlive-binaries:amd64 (2016.20160513.41080.dfsg-2, 2016.20160513.41080.dfsg-2+deb9u1), libpython2.7-minimal:amd64 (2.7.13-2+deb9u2, 2.7.13-2+deb9u3), flashplayer-mozilla:amd64 (3:30.0.0.154-dmo1, 3:31.0.0.122-dmo1), libjasper1:amd64 (1.900.1-debian1-2.4debian9.0.0+3, 1.900.1-debian1-2.4+deb8u3), libpython3.5-stdlib:amd64 (3.5.3-1, 3.5.3-1+deb9u1), libpython2.7-stdlib:amd64 (2.7.13-2+deb9u2, 2.7.13-2+deb9u3), libpython3.5-minimal:amd64 (3.5.3-1, 3.5.3-1+deb9u1), libtexlua52:amd64 (2016.20160513.41080.dfsg-2, 2016.20160513.41080.dfsg-2+deb9u1), libjasper-dev:amd64 (1.900.1-debian1-2.4debian9.0.0+3, 1.900.1-debian1-2.4+deb8u3), libkpathsea6:amd64 (2016.20160513.41080.dfsg-2, 2016.20160513.41080.dfsg-2+deb9u1) End-Date: 2018-10-11 23:36:33 In dmesg I see following [131219.842996] usb 1-1.5: new high-speed USB device number 6 using ehci-pci [131219.952674] usb 1-1.5: New USB device found, idVendor=0471, idProduct=2036, bcdDevice= 1.00 [131219.952678] usb 1-1.5: New USB device strings: Mfr=2, Product=1, SerialNumber=0 [131219.952681] usb 1-1.5: Product: Philips SPC 1030NC Webcam [131219.952683] usb 1-1.5: Manufacturer: Philips CE [131219.953363] uvcvideo: Found UVC 1.00 device Philips SPC 1030NC Webcam (0471:2036) [131219.977182] uvcvideo 1-1.5:1.0: Entity type for entity Extension 5 was not initialized! [131219.977185] uvcvideo 1-1.5:1.0: Entity type for entity Extension 4 was not initialized! [131219.977188] uvcvideo 1-1.5:1.0: Entity type for entity Processing 3 was not initialized! [131219.977190] uvcvideo 1-1.5:1.0: Entity type for entity Camera 1 was not initialized! [131219.977286] input: Philips SPC 1030NC Webcam as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input18 [131220.004428] usb 1-1.5: 3:1: cannot get freq at ep 0x84 [131220.012674] usb 1-1.5: Warning! Unlikely big volume range (=2560), cval->res is probably wrong. [131220.012678] usb 1-1.5: [2] FU [Mic Capture Volume] ch = 1, val = 4608/7168/1 [131220.098807] usb 1-1.5: 3:1: cannot get freq at ep 0x84 [131220.131939] usb 1-1.5: 3:1: cannot get freq at ep 0x84 [131417.080597] retire_capture_urb: 71 callbacks suppressed [131461.841846] retire_capture_urb: 72 callbacks suppressed [131504.212917] retire_capture_urb: 66 callbacks suppressed [131568.005217] retire_capture_urb: 73 callbacks suppressed [131585.707125] retire_capture_urb: 70 callbacks suppressed [131612.814875] retire_capture_urb: 60 callbacks suppressed [131925.759964] retire_capture_urb: 77 callbacks suppressed [131944.784063] retire_capture_urb: 60 callbacks suppressed [132164.373953] usbcore: deregistering interface driver uvcvideo [132181.815365] uvcvideo: Found UVC 1.00 device Philips SPC 1030NC Webcam (0471:2036) [132181.870463] uvcvideo 1-1.5:1.0: Entity type for entity Extension 5 was not initialized! [132181.870467] uvcvideo 1-1.5:1.0: Entity type for entity Extension 4 was not initialized! [132181.870469] uvcvideo 1-1.5:1.0: Entity type for entity Processing 3 was not initialized! [132181.870471] uvcvideo 1-1.5:1.0: Entity type for entity Camera 1 was not initialized! [132181.870569] input: Philips SPC 1030NC Webcam as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input19 [132181.870680] usbcore: registered new interface driver uvcvideo [132181.870681] USB Video Class driver (1.1.1) emanoil@fujitsu:/home-lisa/emanoil$ mplayer -vo gl2 -tv driver=v4l2:width=640:height=480:device=/dev/video0 tv://
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web