I have a storage server running openmediavault which is based on debian.
The OS is in a USB 3.0 Stick pluged directly on the motherboard (no USB-Hub or sth).
The system was running fine for about 3 Months and 2 days ago I got this errors:
usb 1-3: device descriptor read/64, error -110
usb 1-3: device not accepting address 33, error -110
usb 1-3: device not accepting address 34, error -110
hub 1-0:1.0: unable to enumerate USB device on port 3
When I restart the server, everything is fine again.
The next day I face the same error…
What can I do to fix this. I dont want to loose 3TB of data…
scohe001
14.9k2 gold badges31 silver badges51 bronze badges
asked Nov 30, 2012 at 21:49
USB error -110 means «Timeout expired before the transfer completed», which could be caused by anything. Most commonly, it’s because power was exceeded; the host could not provide enough electric power for the pendrive to operate. Because it has not enough power also the USB stick cannot provide the device descriptor to the host, as a result it cannot be identified and so on. Maybe your motherboard it’s overloaded with devices that consume all the available power.
whoKnows
9061 gold badge9 silver badges26 bronze badges
answered Dec 1, 2012 at 16:53
garzantigarzanti
2,1621 gold badge22 silver badges29 bronze badges
9
The problem was a USB 3.0 Stick that needed more current than usual for a USB 2.0 device.
This lead to the errors.
I replaced the stick and in addition to that I installed the latest BIOS-Drivers.
No more problems!
answered Feb 20, 2013 at 5:13
mxcdmxcd
1,5662 gold badges19 silver badges32 bronze badges
Just to add another data point: I was running into «error -110» messages for my Inateck dual bay USB 3.0 to SATA device (amazon link). This fixed it for me:
shutdown -h now(turn off the computer)- Unplug USB device from computer.
- Unplug power cord to back of the computer.
- Unplug power to Inateck — pull wall wart plug from wall socket.
- Noticed there was a green glowing LED on the Inateck wall wart; waited for that to go dark.
- Waited ~3min total.
- Plugged everything back in and booted up.
Worked liked a charm.
Note: Previously I tried just unplugging the computer and letting it sit for a while; that didn’t work. I had to unplug the USB from the computer and the usb device power adapter from the wall.
Must be something with USB power provisioning/negotiation?
answered Oct 20, 2016 at 13:43
JohnsterJohnster
1331 silver badge7 bronze badges
1
I had the same error, but with no USB device plugged in. I have a Suse 13.2 and 42.2 installed on an internal ssd drive in a HP ProBook 430. When I booted into 42.2, I got that error
device descriptor read/64, error -110
and booting simply stopped there. Weird enough with 13.2 on the same hard disk I could boot with no problems.
Following Johnsters advice to unplug any power supply including battery removal finally did it, so loads of thanks go there.
And to all running into this post without any obvious interaction of USB devices in their problems: Try making your system voltage free, it still might do the trick.
answered Jun 5, 2017 at 7:38
RoflRofl
611 silver badge2 bronze badges
1
Main voltage is not high enough in my home. It’s below 180V (normally 220-240). Sometimes I get the same error. Sometimes my PC restarts itself.
Ivan Ferić
4,70511 gold badges37 silver badges47 bronze badges
answered Feb 18, 2013 at 14:18
I have a 16GB flash drive. I’m running Ubuntu 14.04.
I can’t open my flash drive and I can’t see it in GParted.
After running tail -f /var/log/syslog .
After inserting my flash:
USB disconnect, device number 10
Jul 3 16:39:55 rihanna-VGN-Z56GG-B kernel: [ 3309.712166] usb 2-3: new high-speed USB device number 11 using ehci-pci
Jul 3 16:39:55 rihanna-VGN-Z56GG-B kernel: [ 3309.846591] usb 2-3: New USB device found, idVendor=090c, idProduct=1000
Jul 3 16:39:55 rihanna-VGN-Z56GG-B kernel: [ 3309.846601] usb 2-3:
New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 3 16:39:55 rihanna-VGN-Z56GG-B kernel: [ 3309.846609] usb 2-3: Product: Silicon-Power
Jul 3 16:39:55 rihanna-VGN-Z56GG-B kernel: [ 3309.846615] usb 2-3: Manufacturer: UFD 2.0
Jul 3 16:39:55 rihanna-VGN-Z56GG-B kernel: [ 3309.846622] usb 2-3: SerialNumber: 1401208423400131
Jul 3 16:39:55 rihanna-VGN-Z56GG-B kernel: [ 3309.847176] usb-storage 2-3:1.0: USB Mass Storage device detected
Jul 3 16:39:55 rihanna-VGN-Z56GG-B kernel: [ 3309.847309] scsi12 : usb-storage 2-3:1.0
Jul 3 16:39:55 rihanna-VGN-Z56GG-B mtp-probe: checking bus 2, device 11: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-3"
Jul 3 16:39:55 rihanna-VGN-Z56GG-B mtp-probe: bus: 2, device: 11 was not an MTP device
Jul 3 16:40:17 rihanna-VGN-Z56GG-B kernel: [ 3332.176107] usb 2-3: reset high-speed USB device number 11 using ehci-pci
Jul 3 16:40:33 rihanna-VGN-Z56GG-B kernel: [ 3347.288080] usb 2-3: device descriptor read/64, error -110
Jul 3 16:40:48 rihanna-VGN-Z56GG-B kernel: [ 3362.504081] usb 2-3: device descriptor read/64, error -110
Jul 3 16:40:48 rihanna-VGN-Z56GG-B kernel: [ 3362.720076] usb 2-3: reset high-speed USB device number 11 using ehci-pci
Jul 3 16:40:52 rihanna-VGN-Z56GG-B kernel: [ 3366.812110] usb 2-3: reset high-speed USB device number 11 using ehci-pci
Jul 3 16:41:07 rihanna-VGN-Z56GG-B kernel: [ 3381.924082] usb 2-3: device descriptor read/64, error -110
Jul 3 16:41:23 rihanna-VGN-Z56GG-B kernel: [ 3397.356093] usb 2-3: reset high-speed USB device number 11 using ehci-pci
Jul 3 16:41:38 rihanna-VGN-Z56GG-B kernel: [ 3412.468057] usb 2-3: device descriptor read/64, error -110
Jul 3 16:41:54 rihanna-VGN-Z56GG-B kernel: [ 3428.664065] usb 2-3: reset high-speed USB device number 11 using ehci-pci
Jul 3 16:42:09 rihanna-VGN-Z56GG-B kernel: [ 3443.776100] usb 2-3: device descriptor read/64, error -110
Jul 3 16:42:24 rihanna-VGN-Z56GG-B kernel: [ 3458.992085] usb 2-3: device descriptor read/64, error -110
Jul 3 16:42:25 rihanna-VGN-Z56GG-B kernel: [ 3459.208063] usb 2-3: reset high-speed USB device number 11 using ehci-pci
Jul 3 16:42:40 rihanna-VGN-Z56GG-B kernel: [ 3474.320039] usb 2-3: device descriptor read/64, error -110
Jul 3 16:42:50 rihanna-VGN-Z56GG-B kernel: [ 3484.516109] usb 2-3: reset high-speed USB device number 11 using ehci-pci
Jul 3 16:42:50 rihanna-VGN-Z56GG-B kernel: [ 3484.768108] usb 2-3: reset high-speed USB device number 11 using ehci-pci
Jul 3 16:43:05 rihanna-VGN-Z56GG-B kernel: [ 3499.880081] usb 2-3: device descriptor read/64, error -110
Jul 3 16:43:20 rihanna-VGN-Z56GG-B kernel: [ 3515.096081] usb 2-3: device descriptor read/64, error -110
Jul 3 16:43:21 rihanna-VGN-Z56GG-B kernel: [ 3515.312048] usb 2-3: reset high-speed USB device number 11 using ehci-pci
Jul 3 16:43:36 rihanna-VGN-Z56GG-B kernel: [ 3530.424032] usb 2-3: device descriptor read/64, error -110
Jul 3 16:43:46 rihanna-VGN-Z56GG-B kernel: [ 3540.505230] scsi 12:0:0:0: Device offlined - not ready after error recovery
Содержание
- Arch Linux
- #1 2016-06-21 10:02:13
- usb 2-6: device descriptor read/64, error -110
- #2 2016-06-21 13:21:11
- Re: usb 2-6: device descriptor read/64, error -110
- #3 2016-06-21 14:55:16
- Re: usb 2-6: device descriptor read/64, error -110
- #4 2016-06-21 20:05:51
- Re: usb 2-6: device descriptor read/64, error -110
- #5 2016-06-21 20:26:30
- Re: usb 2-6: device descriptor read/64, error -110
- #6 2016-06-21 21:13:24
- Re: usb 2-6: device descriptor read/64, error -110
- #7 2016-06-22 10:44:08
- Re: usb 2-6: device descriptor read/64, error -110
- #8 2016-06-22 20:10:28
- Re: usb 2-6: device descriptor read/64, error -110
- Thread: USB 2-5 device descriptor read/64, error -110 (nothing connected to usb)
- USB 2-5 device descriptor read/64, error -110 (nothing connected to usb)
- Re: USB 2-5 device descriptor read/64, error -110 (nothing connected to usb)
- Thread: USB 2-5 device descriptor read/64, error -110 (nothing connected to usb)
- USB 2-5 device descriptor read/64, error -110 (nothing connected to usb)
- Re: USB 2-5 device descriptor read/64, error -110 (nothing connected to usb)
- Usb device descriptor read 64 error 110
Arch Linux
You are not logged in.
#1 2016-06-21 10:02:13
usb 2-6: device descriptor read/64, error -110
I just finished installing Arch following the Beginners’ guide and I think it went relatively well.
Then I restarted the computer and before I had the time to type «root» at the login field this showed up:
And that’s how it goes every time I boot.
After that I can type the username and login and it all seems to work ok.
I’ve been googling this for a long time and I found many posts with similar errors, but they’re usually related to some usb device that doesn’t work… in my case there are no usb devices connected at all (it’s a laptop).
If I do connect a flash drive it shows up at /dev as it should, though.
I didn’t even start using Arch yet. As I said, I just finished installing, so I don’t know if this has any other consequences… but for now it’s just really annoying.
Thanks in advance,
Daniel
#2 2016-06-21 13:21:11
Re: usb 2-6: device descriptor read/64, error -110
Are you sure you don’t have any usb devices connected? Laptop have all kinds of «built-in» peripherals, such as webcams, cards readers, fingerprint readers, etc. Any of them can be connected to the usb bus.
If everything works then that message is just annoying, but I suppose it might be caused by a peripheral that takes a bit longer to initialize.
#3 2016-06-21 14:55:16
Re: usb 2-6: device descriptor read/64, error -110
To expand on what R00KIE said, that is a message that was posted to the console by the kernel. Log in should still work (press return and you will get a new log in prompt)
Edit: Then do a lsusb and see what the offending device is at that bus address
Last edited by ewaller (2016-06-21 14:55:52)
Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way
#4 2016-06-21 20:05:51
Re: usb 2-6: device descriptor read/64, error -110
Thank you for the answers.
ewaller, is the bus address that number in brackets that shows up before the error message? How do I know what’s at that address?
Here’s the result of lsusb:
I have no idea what any of this means except for the «Card Reader Controller», which I assume is the SD card reader.
R00KIE, I guess I do have usb devices connected then, like the card reader. But I still don’t know what’s causing this problem or how to fix it.
Last edited by danielbmarques (2016-06-21 20:06:42)
#5 2016-06-21 20:26:30
Re: usb 2-6: device descriptor read/64, error -110
The two 16 bit hex numbers after ‘ID’ are the VID and PID (Vendor identification, product identification) for the devices. 0cf3:e005 is your Bluetooth. 0bda:5684 is your camera. 0bda:0129 is (indeed) your card reader.
Nothing is living at bus 2 address 6. Take a look at your journal for the last boot (journalcrl -b) and look around time t=12.85 seconds and find that message, Then, see what happened just before and just after.
Edit: I did not answer your question. Yes 2-6 is bus 2, device 6. Note that the device numbers are assigned arbitrarily when a device attaches and enumerates.
Last edited by ewaller (2016-06-21 20:27:56)
Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way
#6 2016-06-21 21:13:24
Re: usb 2-6: device descriptor read/64, error -110
(Sorry about using a picture, I’m talking to you from a different computer and I didn’t know which lines were relevant to copy by hand.)
I don’t know if it has anything to do with anything, but there are other lines that are highlighted with contents that don’t sound so good, like:
Should I worry about any of this stuff?
I’m sorry if I’m asking obvious or silly questions, this is the first time I ever use linux. I don’t expect to fix every little problem, but since it’s a fresh install and I followed the guide by the letter I’m just hoping everything is ok before I start ruining things.
PS: It says «usb 1-6» now because I restarted the computer in the meanwhile. This post suggested cutting the power for a while, so I removed the battery and the power cord for a few minutes and tried again, but it’s still the same. Another post suggested turning off autosuspend, it didn’t work either.
Last edited by danielbmarques (2016-06-22 19:43:43)
#7 2016-06-22 10:44:08
Re: usb 2-6: device descriptor read/64, error -110
Please don’t post large images, use an image hosting service and post the link to the images [1]. I’m giving you the opportunity to move the image to an image hosting service of your choice, but if you don’t move it one of the moderators will move it, possibly to a service you might not like.
Regarding your actual problem, like I’ve said before, that may be caused by a usb device that takes longer to initialize and doesn’t answer the first enumeration request, therefore there might be nothing you can do about it short of not using it if possible.
I suspect you may have to use ‘lsusb -t’ and go by bus-port instead of bus-device, at least on my machine what ‘lsusb’ says doesn’t match to what can be found in ‘/sys/bus/usb/devices/’
#8 2016-06-22 20:10:28
Re: usb 2-6: device descriptor read/64, error -110
Sorry for that, it’s fixed now.
Well, then should I just ignore that and keep looking at that error every time I boot?
(It’s an honest question, I’ll take yes as an answer, haha).
I had some other problems trying to set up Gnome and I think I’ll do another fresh install of Arch, but in the meanwhile I gave Ubuntu a try and I get the same error (actually I get many more, but this is still one of them).
So now I tried `lsusb -t` in Ubuntu and here’s what it says:
So does that mean `usb 2-6` is `Class=Wireless, Driver=btusb`? And the «bt» in «btusb» means «bluetooth», I guess?
You said «there might be nothing you can do about it short of not using it if possible»… I don’t use bluetooth very often, so how would I go about «not using it»? I mean, except for physically disconnecting it from somewhere inside the laptop. Can I have it not connect automatically at boot and just start it if I need it sometime?
Edit: this didn’t happen in Arch, but now with Ubuntu if I do `journalctl -p 3 -xb` I also get many errors related to bluetooth:
Using Arch I only got that first line.
Last edited by danielbmarques (2016-06-22 20:18:51)
Источник
Thread: USB 2-5 device descriptor read/64, error -110 (nothing connected to usb)
Thread Tools
Display
USB 2-5 device descriptor read/64, error -110 (nothing connected to usb)
I am getting an error «USB 2-5 device descriptor read/64, error -110» when trying to boot Ubuntu.
Recently I ‘refreshed’ Windows and reinstalled Ubuntu (dual boot).
I am not sure if that has anything to do with it. Everything seemed to work OK for a few weeks.
There are many threads reporting this error, where the issue is supposed to be solved when unplugging all USB devices, shutting down, waiting a bit, and booting again.
Even after leaving my laptop off overnight, without any USB devices connected, the problem persists.
Windows works without problems, and I can boot Ubuntu from a USB drive as well.
Any help would be much appreciated
Re: USB 2-5 device descriptor read/64, error -110 (nothing connected to usb)
I’m not sure if it’s the same problem, but I was getting the same message a couple of weeks ago. I have a separate /home partition, it it seems the file system was corrupted. To resolve the problem, I restarted in recovery mode, and selected the root prompt option, once at the prompt I ran the following command:
if /dev/sda6 is the partition you are having problems with, make sure the drive is connected and start in recovery mode, select the root prompt option and run the following command:
Источник
Thread: USB 2-5 device descriptor read/64, error -110 (nothing connected to usb)
Thread Tools
Display
USB 2-5 device descriptor read/64, error -110 (nothing connected to usb)
I am getting an error «USB 2-5 device descriptor read/64, error -110» when trying to boot Ubuntu.
Recently I ‘refreshed’ Windows and reinstalled Ubuntu (dual boot).
I am not sure if that has anything to do with it. Everything seemed to work OK for a few weeks.
There are many threads reporting this error, where the issue is supposed to be solved when unplugging all USB devices, shutting down, waiting a bit, and booting again.
Even after leaving my laptop off overnight, without any USB devices connected, the problem persists.
Windows works without problems, and I can boot Ubuntu from a USB drive as well.
Any help would be much appreciated
Re: USB 2-5 device descriptor read/64, error -110 (nothing connected to usb)
I’m not sure if it’s the same problem, but I was getting the same message a couple of weeks ago. I have a separate /home partition, it it seems the file system was corrupted. To resolve the problem, I restarted in recovery mode, and selected the root prompt option, once at the prompt I ran the following command:
if /dev/sda6 is the partition you are having problems with, make sure the drive is connected and start in recovery mode, select the root prompt option and run the following command:
Источник
Usb device descriptor read 64 error 110
1) Compile USBcore as a kernel module
Device Drivers —> USB support —> Support for Host-side USB
2) Add pertinent modules that will now need to be loaded at boot time to /etc/modules.autoload.d/kernel-2.6
Here’s what I added:
| Код: |
| usbcore ohci_hcd usblp usb-storage usbhid |
3) Append «options usbcore use_both_schemes=y» to your /etc/modules.conf
Alternatively you could do «old_scheme_first=y»
Where I got the info and more details can be found: http://www.spinics.net/lists/usb/msg02644.html
_________________
-Greg Surbey Вернуться к началу
misho
Apprentice
Зарегистрирован: 15 апр 2004
Сообщений: 189
| Добавлено: вс янв 23, 2005 6:12 pm Заголовок сообщения: | |
| Thanks. This helped me a lot.
As an addendum, intel users should use uhci_hcd, rather than ohci_hcd. |
Вернуться к началу
Thomas Conneely
n00b
Зарегистрирован: 28 окт 2004
Сообщений: 11
| Добавлено: вс янв 23, 2005 7:26 pm Заголовок сообщения: | |
| This doesn’t seem to work for me, when I plug the stick in I get told:
usb 4-1: new high speed USB device using ehci_hcd and address 3 or if ehci module not loaded usb 4-1: new high speed USB device using ohci_hcd and address 3 but nothing else, and device /dev/sda1 still doesn’t appear. Just to make sure I have eveyything enabled this is what I’ve ticked in the kernel (all modules):
uhci_hcd ehci_hcd usb device filesystem usb mass storage support scsi device support scsi disk support These are what I believe I need, am I missing something? |
Вернуться к началу
theDreamer
Tux’s lil’ helper
Зарегистрирован: 20 окт 2003
Сообщений: 118
| Добавлено: вс янв 23, 2005 7:47 pm Заголовок сообщения: different problem | |
| you’re actually having a different problem. did you work with the specific hardware before 2.6.10? as far as i see the kernel does not detect your hardware not-related to the hardware detection sceheme problem talked here.. check kernel menu / device drivers / usb and verify that the driver for your hardware is enabled. |
Вернуться к началу
Thomas Conneely
n00b
Зарегистрирован: 28 окт 2004
Сообщений: 11
| Добавлено: вс янв 23, 2005 8:07 pm Заголовок сообщения: | |
| I think it is, I have no problem with a USB floppy drive, that works perfectly.
I have a problem with my USB stick only. I think the stick is probably shoddy when it comes to standards as its quite a cheap one. I would have given up by now, but the stick works under knoppix fine. Also I don’t think I’ve said this before but the device did work the first time I plugged it in, and after that it would occasionally work (seemingly at random). The solution above does solve the «usb device descriptor read/64, error» which I was getting before. I’ll see how it works with an older kernel sometime in the week (i’ve got last semester’s exams, 5 in 5 days sheesh so my heads in the books) |
Вернуться к началу
gsurbey
Apprentice
Зарегистрирован: 24 мар 2003
Сообщений: 212
Откуда: Nashua, NH
| Добавлено: вт янв 25, 2005 6:13 am Заголовок сообщения: | |
| Thomas Conneely: I don’t believe you should be loading both uhci_hcd and ehci_hcd. It’s either or, not both. BTW I love your sig _________________ -Greg Surbey |
Вернуться к началу
Thomas Conneely
n00b
Зарегистрирован: 28 окт 2004
Сообщений: 11
| Добавлено: вт янв 25, 2005 11:37 am Заголовок сообщения: | |
| As I understood it, ohci is usb version one and ehci is usb version 2 (correct me if I’m wrong). Though I have tried using only ohci with no joy.
p.s thanks its nice to be appreciated |
Вернуться к началу
theDreamer
Tux’s lil’ helper
Зарегистрирован: 20 окт 2003
Сообщений: 118
| Добавлено: вт янв 25, 2005 11:47 am Заголовок сообщения: | ||
i think you’re right, i’ve performed the same tests.. and also from the comments in dmesg this is what i understood. |
Вернуться к началу
gsurbey
Apprentice
Зарегистрирован: 24 мар 2003
Сообщений: 212
Откуда: Nashua, NH
| Добавлено: вт янв 25, 2005 7:29 pm Заголовок сообщения: | |
| Oh my bad, you guys are right. I was thinking of OHCI and UHCI support. _________________ -Greg Surbey |
Вернуться к началу
julmust
n00b
Зарегистрирован: 13 окт 2002
Сообщений: 57
Откуда: Landskrona, Sweden
| Добавлено: чт янв 27, 2005 2:33 pm Заголовок сообщения: | ||
| hey, maybe you can help me out, i posted the following topic yesterday: https://forums.gentoo.org/viewtopic.php?p=2024111 i have a similar problem with the 2.6.10-gentoo-r6 kernel. i recompiled it with usbcore and stuff as modules and passed «old_scheme_first=y» parameter.. still this didn’t help me much, although i believe the «usb 2-4: device descriptor read/64, error -110» disappeared.. the problem is that the disk seems to disconnect itself right after it is detected.. snip form the logs :
.. and so it goes on.. |
Вернуться к началу
theDreamer
Tux’s lil’ helper
Зарегистрирован: 20 окт 2003
Сообщений: 118
| Добавлено: чт янв 27, 2005 2:58 pm Заголовок сообщения: maybe | ||||
| it looks like it detected the existance of new hardware but when detected it did not find the driver for the specific hardware.
verify that you have all the other usb driver loaded also. just for the sake of an optional bug in kernel, try adding;
instead of options
_________________ |
Вернуться к началу
julmust
n00b
Зарегистрирован: 13 окт 2002
Сообщений: 57
Откуда: Landskrona, Sweden
| Добавлено: чт янв 27, 2005 3:04 pm Заголовок сообщения: | |
| I tried «use_both_schemes=y» but with the same result..
Im almost 100% I’ve got all of the right kernel modules.. my two usb memory sticks works just fine. I guess I’ll have to downgrade to 2.6.9 for the time being.. |
Вернуться к началу
geko2004
n00b
Зарегистрирован: 11 авг 2004
Сообщений: 15
| Добавлено: пт янв 28, 2005 12:07 am Заголовок сообщения: | ||
you could disable
I red it somewhere else in the forums, (can’t find where i would have quoted ) but you won’t be able to use usb 2.0 just 1.1, it worked for me. dunno if it helped. |
Вернуться к началу
Mr Faber
n00b
Зарегистрирован: 14 мар 2005
Сообщений: 47
| Добавлено: пн апр 25, 2005 7:45 pm Заголовок сообщения: | |
| Isn’t it better to use the file /etc/modules.d/usbcore for the entry?
cu |
Вернуться к началу
Вы не можете начинать темы
Вы не можете отвечать на сообщения
Вы не можете редактировать свои сообщения
Вы не можете удалять свои сообщения
Вы не можете голосовать в опросах
Copyright 2001-2023 Gentoo Foundation, Inc. Designed by Kyle Manna © 2003; Style derived from original subSilver theme. | Hosting by Gossamer Threads Inc. © | Powered by phpBB 2.0.23-gentoo-p11 © 2001, 2002 phpBB Group
Privacy Policy
Источник
Adblock
detector
Модератор: Модераторы разделов
-
held
- Сообщения: 75
[Решено]usb 1-1: device descriptor read/64, error -110
Доброго времени суток!
Перестали определятся USB устройства. Команда lsusb долго весит в конце выдает список usb без тех к которым подключен сканер и принтер. При загрузки и выключении выходит ошибка
usb 1-4: device descriptor read/64, error -110
usb 1-4: device descriptor read/64, error -110
usb 1-4: device descriptor read/8, error -110
usb 1-4: device descriptor read/8, error -110
в kern.log постоянно сыпится
Код: Выделить всё
Jun 8 16:23:40 as-desktop kernel: [ 1613.609046] hub 4-0:1.0: unable to enumerate USB device on port 1
Jun 8 16:23:41 as-desktop kernel: [ 1613.856045] hub 4-0:1.0: unable to enumerate USB device on port 1
Jun 8 16:23:41 as-desktop kernel: [ 1614.105046] hub 4-0:1.0: unable to enumerate USB device on port 1
Jun 8 16:23:41 as-desktop kernel: [ 1614.353071] hub 4-0:1.0: unable to enumerate USB device on port 1
Jun 8 16:23:41 as-desktop kernel: [ 1614.600134] hub 4-0:1.0: unable to enumerate USB device on port 1
Jun 8 16:23:42 as-desktop kernel: [ 1614.849041] hub 4-0:1.0: unable to enumerate USB device on port 1
Jun 8 16:23:42 as-desktop kernel: [ 1615.829057] hub 4-0:1.0: unable to enumerate USB device on port 1
Jun 8 16:23:43 as-desktop kernel: [ 1616.077062] hub 4-0:1.0: unable to enumerate USB device on port 1
Jun 8 16:23:43 as-desktop kernel: [ 1616.315292] hub 4-0:1.0: unable to enumerate USB device on port 1
Jun 8 16:23:43 as-desktop kernel: [ 1616.561048] hub 4-0:1.0: unable to enumerate USB device on port 1
Jun 8 16:23:43 as-desktop kernel: [ 1616.808039] hub 4-0:1.0: unable to enumerate USB device on port 1
Jun 8 16:23:44 as-desktop kernel: [ 1617.057038] hub 4-0:1.0: unable to enumerate USB device on port 1
Jun 8 16:23:44 as-desktop kernel: [ 1617.304317] hub 4-0:1.0: unable to enumerate USB device on port 1
Jun 8 16:23:44 as-desktop kernel: [ 1617.553041] hub 4-0:1.0: unable to enumerate USB device on port 1В журнале в messages временами добовляется
Код: Выделить всё
Jun 8 16:13:47 as-desktop kernel: [ 1020.672034] usb 2-2: new full speed USB device using ohci_hcd and address 8
Jun 8 16:14:18 as-desktop kernel: [ 1051.408037] usb 2-2: new full speed USB device using ohci_hcd and address 9
Jun 8 16:14:45 as-desktop kernel: [ 1078.296026] usb 1-4: new high speed USB device using ehci_hcd and address 7
Jun 8 16:14:55 as-desktop kernel: [ 1088.652027] usb 1-4: new high speed USB device using ehci_hcd and address 8
Jun 8 16:15:06 as-desktop kernel: [ 1099.008027] usb 1-4: new high speed USB device using ehci_hcd and address 9
Jun 8 16:15:36 as-desktop kernel: [ 1129.552044] usb 1-4: new high speed USB device using ehci_hcd and address 10
Jun 8 16:16:07 as-desktop kernel: [ 1160.808049] usb 2-2: new full speed USB device using ohci_hcd and address 10
Jun 8 16:16:18 as-desktop kernel: [ 1171.232027] usb 2-2: new full speed USB device using ohci_hcd and address 11
Jun 8 16:16:28 as-desktop kernel: [ 1181.652026] usb 2-2: new full speed USB device using ohci_hcd and address 12
Jun 8 16:16:59 as-desktop kernel: [ 1212.388022] usb 2-2: new full speed USB device using ohci_hcd and address 13
Jun 8 16:17:34 as-desktop kernel: [ 1247.080031] usb 2-2: new full speed USB device using ohci_hcd and address 14
Jun 8 16:17:44 as-desktop kernel: [ 1257.500032] usb 2-2: new full speed USB device using ohci_hcd and address 15
Jun 8 16:17:55 as-desktop kernel: [ 1267.920033] usb 2-2: new full speed USB device using ohci_hcd and address 16
Jun 8 16:18:25 as-desktop kernel: [ 1298.664739] usb 2-2: new full speed USB device using ohci_hcd and address 17В чем проблема, подскажите, пожалуйста.
-
Anhel
- Сообщения: 136
- ОС: Kubuntu
Re: [Решено]usb 1-1: device descriptor read/64, error -110
Сообщение
Anhel » 09.11.2009 14:14
у меня такая же проблема с материнкой ASUS P5VD2-MX, валяться ошибки с такой скоростью, что нельзя написать ни одной команды…
ставил Debian Etch, Debian Squeeze, FreeBSD 8.0 — не помогает, никаких устройств к серверу не подключено…
похоже эта материнка работает только с мастдаем 
- Печать
Страницы: [1] Вниз
Тема: usb 1-4: device descriptor read/64, error -110 (Ubuntu 9.04) (Прочитано 4572 раз)
0 Пользователей и 1 Гость просматривают эту тему.
rvkdw
Сегодня утром без видимых на то причин при загрузке экран пошел желтой рябью, после чего при следующей загрузке стали выдаваться сообщения
usb 1-4: device descriptor read/64, error -110
usb 2-4: device descriptor read/64, error -110
а при загрузке через recovery mode -> resume normal boot и последующем выключении компьютера:
usb 1-4: device descriptor read/8, error -110
После вытыкивания всех usb-кабелей сообщение исчезло. Думаю, дело было в принтере hp-1020, который подключен по usb, но доказать это не могу, т.к. после вынимания usb-кабелей сразу его выключил, а после включения принтера и обратного втыкания всех кабелей, проблема заново не появилась. Такие дела.
« Последнее редактирование: 02 Июня 2009, 12:21:31 от rvkdw »
BSB
Сглючило устройство. Отмирает оно у тебя по-тихому 
rvkdw
При этом принтер работает, но своеобразно, то есть если сразу включить комп и послать задание на печать он молчит и делать ничего не хочет, а система пишет что задание выполнено. Однако если напечатать пробную страницу, то после этого начинает печатать
Я под Ubuntu 8.10 ставил вот это: http://foo2zjs.rkkda.com/ (foo2zjs есть в синаптиксе в репозитории, однако его нельзя устанавливать оттуда, а нужно скачивать с сайта). Смысл в том, что hp1020 требует заливания в себя через USB порт драйверов во время каждого подключения. Ставил я это дело потому что после перезагрузки компьютера он у меня не хотел печатать.
Сейчас все работает нормально, а глюки с принтером были, возможно вызываны тем, что он всегда находится во включенном состоянии.
« Последнее редактирование: 11 Сентября 2009, 10:36:02 от rvkdw »
- Печать
Страницы: [1] Вверх
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 driverinput: 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/input0input: 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
#1 2019-04-13 06:08:20
- george55
- Member
- Registered: 2011-08-10
- Posts: 68
USB: device descriptor read/64, error -110
I have a micro-sd port on my laptop that I use to add capacity to my relatively small hard drive. However, when I boot the machine I am regularly unable to mount the card because of the following error:
[ +11.847354] usb 1-4: device descriptor read/64, error -110
[ +0.270006] usb 1-4: new full-speed USB device number 5 using xhci_hcd
[ +15.249836] usb 1-4: device descriptor read/64, error -110
[ +15.360160] usb 1-4: device descriptor read/64, error -110
[ +0.120063] usb usb1-port4: attempt power cycle
[ +0.709905] usb 1-4: new full-speed USB device number 6 using xhci_hcd
[ +5.019956] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[ +0.220194] usb 1-4: Device not responding to setup address.
[ +0.219849] usb 1-4: device not accepting address 6, error -71
[ +0.150036] usb 1-4: new full-speed USB device number 7 using xhci_hcd
[Apr13 12:53] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[ +0.220235] usb 1-4: Device not responding to setup address.
[ +0.219866] usb 1-4: device not accepting address 7, error -71
[ +0.000101] usb usb1-port4: unable to enumerate USB deviceI generally try removing the card, putting it back in, etc. for a while and suddenly it will start working:
[ +0.349903] usb 1-7: new high-speed USB device number 8 using xhci_hcd
[ +0.185507] usb 1-7: New USB device found, idVendor=05e3, idProduct=0727, bcdDevice= 2.08
[ +0.000006] usb 1-7: New USB device strings: Mfr=3, Product=4, SerialNumber=2
[ +0.000004] usb 1-7: Product: USB Storage
[ +0.000004] usb 1-7: Manufacturer: Generic
[ +0.000004] usb 1-7: SerialNumber: 000000000208I am not sure, however, if this is a problem with my machine itself, or with the sd card. Sometimes when I have taken out the card, the errors continue to be added to dmesg, which gives me the idea it’s a problem with the port itself, not the card. Any idea what could be causing this error?
#2 2019-04-13 06:59:01
- seth
- Member
- Registered: 2012-09-03
- Posts: 35,307
Re: USB: device descriptor read/64, error -110
https://stackoverflow.com/questions/136 … -error-110
There’s a good chance that the reader has an implicit switch and is only activated by pushing in a card (it’s probably a push-eject one?)
#3 2019-04-13 07:34:27
- george55
- Member
- Registered: 2011-08-10
- Posts: 68
Re: USB: device descriptor read/64, error -110
Thanks. It could be, but there are a couple indicators this is not the case:
1) The issue is erratic; I have this problem sometimes at boot, sometimes I don’t (say 5-10% of the time)
2) It is a push-eject system, but sometimes I will have to eject and put it back in once for it to start working, sometimes 5+ times, and sometimes it just starts working again after waiting 10-30 seconds
3) It does not seem to reactivate upon pushing the card back in. Even if I do, it takes another 2-30 seconds for it to start working with no indication in dmesg that pushing it back in made any change
4) In response to the linked thread: other devices using too much power would be odd, because it generally happens at boot with no other devices attached. Sometimes there is a mouse attached, but often there is no other device whatsoever drawing power
Any ideas what would match these symptoms?
#4 2019-04-13 07:42:02
- seth
- Member
- Registered: 2012-09-03
- Posts: 35,307
Re: USB: device descriptor read/64, error -110
There’s probably much more on the USB («it’s a bus, not a plug»), check lsusb and «lsusb -t»
Things that are often wired via USB and could suck some power (next to anything spinning, but that’d be rather external) are wifi/BT — you could try to deactivate those in the BIOS (is possible)
#5 2019-04-13 07:57:11
- george55
- Member
- Registered: 2011-08-10
- Posts: 68
Re: USB: device descriptor read/64, error -110
Thanks. I’ve checked it out:
$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 05e3:0727 Genesys Logic, Inc. microSD Reader/Writer
Bus 001 Device 003: ID 0bda:5685 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 1d57:fa20 Xenta
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M
|__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 1: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 3: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 3: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 7: Dev 8, If 0, Class=Mass Storage, Driver=usb-storage, 480MI’m not sure… I’ve tried looking things up but it seems that the hub and Xenta are all related to the ports themselves. Do they draw power??
And if this is the case, wouldn’t this be a poorly designed laptop (if its internal devices draw too much power to make the micro-sd port malfunction). It’s certainly possible, but I would be quite sad to find out the laptop was built like that. It’s a Dell Chromebook BTW, which also means I can’t access a traditional bios to turn anything off…
#6 2019-04-13 08:11:27
- seth
- Member
- Registered: 2012-09-03
- Posts: 35,307
Re: USB: device descriptor read/64, error -110
«0bda:5685 Realtek Semiconductor Corp.» is a webcam, «1d57:fa20 Xenta » *seems* to be bluetooth.
Does the reader work reliably for «normal» use cases (ie. when you boot empty and slot a card somewhen after the DE started like you wanted to copy some photos from it)?
#7 2019-04-13 08:32:51
- george55
- Member
- Registered: 2011-08-10
- Posts: 68
Re: USB: device descriptor read/64, error -110
I have a small HD so there are some files on my SD card that I need to fully boot my system (some config files for i3). So I never fully boot without the drive being mounted.
Ah I see with the webcam/bluetooth. I’d be happy to somehow turn them off during boot but don’t have a regular bios so this is difficult with the ChromeOS setup I have I’m afraid.
#8 2019-04-13 12:03:04
- seth
- Member
- Registered: 2012-09-03
- Posts: 35,307
Re: USB: device descriptor read/64, error -110
You should try. Another possibility is that it simply takes a while for the reader to initialize and accessing it before messes that up.
Do you have a static fstab entry for the card (forcing the system to wait for it shoing up)?
What if you resort to «noauto,x-systemd.automount» to only mount it on accessing the path?