I'll experiment some more and update this answer as I gather results. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. Affecting: linux (Ubuntu Vivid) Filed here by: Tim Gardner When: 2016-05-26 Confirmed: 2016-05-26 Assigned: 2016-05-26 Started work: 2016-05-26 Completed: 2016-06-27 Package (Find…) Status Importance Fix Released Undecided Assigned to Me Tim After boot, I have to unplug the keyboard, wait a few seconds, then plug in the keyboard again in order for it to be recognized. navigate here
I had my phone plugged into my laptop (charging) while listening to the radio on my phone, while the laptop was on. Unplug Kinesis keyboard, additional output from 'dmesg|grep -i usb' 4. Okajima ] * SAUCE: AUFS: mm/mmap: fix oopsing on remap_file_pages aufs mmap: bugfix, mainly for linux-4.5-rc5, remap_file_pages(2) emulation - LP: #1558120 [ Kamal Mostafa ] * [debian] getabis: Only git add No more problems! navigate to this website
Fred (eldmannen+launchpad) wrote on 2015-04-08: #5 journal.txt Edit (1.1 MiB, text/plain) journal as requested Martin Pitt (pitti) wrote on 2015-04-11: #6 Thanks. What are the specific devices triggering these issues for you? Next I tried shutting down, cut the power for a few minutes, then boot again.
Tags: xenial amd64 apport-bug kernel-da-key Edit Tag help Cristian Aravena Romero (caravena) wrote on 2016-04-02: #1 AlsaInfo.txt Edit (30.2 KiB, text/plain; charset="utf-8") CRDA.txt Edit (392 bytes, text/plain; charset="utf-8") CurrentDmesg.txt Edit (60.3 Vishal 11 months ago Thanks. It seems that the Xen hypervisor handles USB the way it should be handled, so if you happen to have VT-d or SVM, installing Xen is an easy fix. Usb1 1 Device Descriptor Read 64 Error Affecting: linux (Ubuntu Xenial) Filed here by: Tim Gardner When: 2016-05-26 Confirmed: 2016-05-26 Started work: 2016-05-26 Completed: 2016-06-27 Package (Find…) Status Importance Fix Released Undecided Assigned to Nobody Me Comment on
Sławek 7 months ago Thank you, it helped me also! Ubuntu Device Descriptor Read 8 Error I also have an X99-A motherboard. Adv Reply July 4th, 2008 #3 pytheas22 View Profile View Forum Posts Private Message Visit Homepage Staff Emeritus Join Date Aug 2007 Location Paris Beans 5,538 DistroUbuntu 11.04 Natty Narwhal http://askubuntu.com/questions/705542/usb-dont-work-for-a-time-after-boot-with-usb-1-3-device-descriptor-read-all Nabeel Moidu about 3 years ago Paul, had this same issue and my USB keyboard wouldn't power on.
Tristan Cormier (tristanc-3) wrote on 2015-11-10: #38 The BIOS setting I modified is: Settings-> Advanced-> USB Configuration-> External USB Power Control [Disabled] Awesome Donkey (awesomedonkey) wrote on 2015-11-10: #39 Unfortunately my Device Descriptor Read 64 Error 71 I started noticing this problem when I switched to a 4.0 kernel on Gentoo. How do I space quads evenly? Speed and Velocity in German Fast-growing vine, supposed to be a flowering plant Do tickets for these Korean trains have to be booked in advance?
saksmlz (saksmlz) wrote on 2015-06-06: #19 just tried older kernel (Linux 3.16.0-39-generic): [ 2.566599] ACPI: Battery Slot [BAT0] (battery present) [ 3.234348] usb 1-3: new full-speed USB device number 2 using more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed Device Descriptor Read 8 Error 32 passed by 7 months ago Thank you for this, to me i changed the USB to front panel and everything worked i guess it was drawing too much power from the Device Descriptor Read 8 Error 110 When the legacy mode is disabled but the two devices are plugged into the hub on my monitor (powered hub, I guess), boot sequence is blazingly fast if no device is
Thanks anyway - good to see that someone is looking through all the unanswered threads. http://applecountry.net/device-descriptor/device-descriptor-read-64-error-usb.php Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 8087:8008 Intel Corp. chivi 11 months ago Nice short article. I was desesperating from finding the root cause of my issue. Device Descriptor Read 64 Error
dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. But when I do a cold boot in Windows, and only reboot in Windows, I don't see the problem. share|improve this answer answered Dec 1 '12 at 16:53 garzanti 1,6041325 So far it worked well, and the only things I have pluged into the MB are 3 SATA-HDDs http://applecountry.net/device-descriptor/device-descriptor-read-8-error-61.php Ioannis Vranos (cppdeveloper) wrote on 2015-05-14: #9 I have the sane bug, "error -110" USB error messages, and when I reboot, the computer's UEFI initialisation during boot, at the USB device
I only have 4 settings on my MSI board. Device Descriptor Read 64 Error 18 This information was last pulled 55 minutes ago. If you remove the power plug, all USB ports turn off, so the issue gets fixed, until the issue reappears at some random time, when the kernel gets loaded again.
Thanks in advance.  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc2-wily/ Changed in linux (Ubuntu): importance: Undecided → Medium status: Confirmed → Incomplete Sebastien Bacher (seb128) wrote on 2016-05-25: #4 seems like the issue fixed with https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/patch/include/linux/usb.h?id=feb26ac31a2a5cb88d86680d9a94916a6343e9e6 I thought I had to buy a new HDD! If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. weblink Error message printed (just in the bare tty1, I don't have any type of login screen or anything): [ 11.034791] usb 3-3: device descriptor read/all, error -110 [ 21.383291] usb 3-3:
Browse other questions tagged linux usb data-recovery . systemd-analyze blame 31.344s systemd-udev-settle.service 8.823s NetworkManager-wait-online.service 1.067s apache2.service 1.010s mysql.service ... My home PC has been infected by a virus! First, some data which may be relevant to your case.
To fix it, I have to disable the ASMedia USB ports from the BIOS, then re-enable them. I am running: Linux marvin 3.19.0-22-generic #22-Ubuntu SMP Tue Jun 16 17:15:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux according to the fix above, this was supposed to be corrected in version With "USB Compatibility Patch" disabled: Same behaviour as above, but the other keyboard on the 2.0 Port did not work either... --> CMOS reset. share|improve this answer edited Feb 18 '13 at 14:39 Ivan Ferić 3,569112441 answered Feb 18 '13 at 14:18 canatan 61 add a comment| Your Answer draft saved draft discarded Sign
stands2reason over 2 years ago Saw this error trying to use an Arduino. Maybe it is the device you're trying to connect to the port causes the error? You're a genius! :) chromewavez over 3 years ago AWESOME!!! Yes, I believe this to be a regression, since I don't recall having this slow boot long time ago.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Martin Pitt (pitti) on 2015-05-23 Changed in linux (Ubuntu): status: Confirmed → Fix Released Fred (eldmannen+launchpad) wrote on 2015-05-27: #15 $ systemd-analyze blame 36.048s systemd-udev-settle.service No, I guess I still have See: 1) http://stackoverflow.com/questions/13653692/device-descriptor-read-64-error-110 2) http://ubuntuforums.org/showthread.php?t=1610142 share|improve this answer answered Jul 3 '15 at 12:35 Ron 8,37631937 I restarted the system and tested in on Windows. Comment on this change (optional) Email me about changes to this bug report linux (Ubuntu) Edit Status tracked in Yakkety Vivid Fix Released Undecided Tim Gardner Edit You need to