Device descriptor read all error 71 - Исправление ошибок и поиск оптимальных решений проблем

Содержание

Thread: [SOLVED] device descriptor read/64, error -71 — USB problem
[SOLVED] device descriptor read/64, error -71 — USB problem
Re: device descriptor read/64, error -71 — USB problem
Re: device descriptor read/64, error -71 — USB problem
Usb device descriptor read all error 71

Thread: [SOLVED] device descriptor read/64, error -71 — USB problem

Thread Tools

Display

[SOLVED] device descriptor read/64, error -71 — USB problem

I have a problem with my USB connections. for some resons they are not quite doing what they should. I have a new camera and on my old laptop (running Ubuntu 8.04) it is deteted immediately on the old USB 1.0. On my brand new PC also running Ubuntu 8.04 it is not detected. dmesg is showing the following:

Any help appreciated — don’t quite understand why it is not working. Thanks!

Re: device descriptor read/64, error -71 — USB problem

Did you ever solve this problem? I’m trying to help someone with the same issue. I think it comes down to disabling CONFIG_USB_SUSPEND, which can be done by reloading the module «usbcore» with the option «autosuspend=-1.» However doing that is tricky because it’s hard to unload usbcore once the system is booted.

There are instructions here on other ways to disable CONFIG_USB_SUSPEND without reloading usbcore. Have you tried them? I don’t want to try them myself I can’t break my computer right now, and it’s hard to test USB stuff in a virtual machine.

Comes with usbcore (CONFIG_USB) compiled as a module and CONFIG_USB_SUSPEND
enabled (at least on Ubuntu).

Therefore, to disable autosuspend you either:

— recompile kernel without CONFIG_USB_SUSPEND

— configure /etc/modprobe.d/ with a file containing
«options usbcore autosuspend=-1»
or set to 0 depending on your kernel

If your system needs the modprobe configuration file above, and if your
system uses initrd (probably does) then you will need to rebuild the
initrd for your kernel for this to take effect. For example:

Источник

Usb device descriptor read all error 71

Патриарх

Группа: Модератор
Сообщений: 11102
Регистрация: 12.09.2004
Пользователь №: 3794

Linux myhost 2.6.29-ARCH #1 SMP PREEMPT Wed May 20 07:06:02 UTC 2009 i686 AMD Athlon 64 Processor 3000+ AuthenticAMD GNU/Linux

пытаюсь подключить внешний USD HDD на 40gb.
один раздел FAT32.

Флешки подключаются нормально.
В винде HDD40 подключается нормально.

Запарился, чесслово.
Уже близок к тому, чтобы форматить и пробовать вновь.

Ветеран

Группа: Участник
Сообщений: 1082
Регистрация: 23.02.2005
Пользователь №: 7608

Патриарх

Группа: Модератор
Сообщений: 11102
Регистрация: 12.09.2004
Пользователь №: 3794

форматнул все-таки.
Диск сразу начал определяться.

раздел создавался в windows сторонним приложением. Насколько я помню он и в linux нормально определялся, но в один прекрасный день перестал.

сейчас я вновь создал файловую систему в gparted, и все шоколадно )

не думал я, что раздел, какой бы он там ни был, может влиять на определяемость устройства в системе.

Патриарх

Группа: Модератор
Сообщений: 11102
Регистрация: 12.09.2004
Пользователь №: 3794

проблема оказалась глубже
во-первых, под linux на этот винт записываются только пустые файлы. Файл есть, имя верное, размер 0 байт.

во-вторых, ровно через день он опять перестал определяться:

через несколько секунд:

еще через какое-то время:

Если это имеет значение, скажу, что у винта разветвитель на 2 слота. Подключены оба.

Подскажите, где копать. у меня руки опускаются.
Еще раз напомню, в Win32 диск работает прекрасно.

Патриарх

Группа: Модератор
Сообщений: 11102
Регистрация: 12.09.2004
Пользователь №: 3794

Подкапываюсь к истине
sudo rmmod ehci_hcd частично решает проблему

диск определяется и работает

на этот раз запись на диск проходит нормально, но очень медленно. Используется USB1.
прочитал, что эта проблема не нова и не ограничивается только arch, никто не знает, почему некоторые USB2 устройства ведут себя так с ehci_hcd. Очевидно баг.
насколько я понял, ее адресовали kernel team еще с 2.6.26

вот тут описана полная копия моей проблемы
http://www.linuxquestions.org/questions/li. chipset-715835/
у меня тоже nforce4
как водится, ответа человек не дождался.
Linux вообще на удивление не любит nforce4. не смотря на то, что это самый популярный чипсет прошлых лет. Например, Suspend и Hibernate в принципе не работает

может есть альтернативы?

crypt, ядро не самосборное. 2.6.29

прикладываю
dmesg > dmesg.txt
lsusb > lsusb.txt
sudo dmidecode > dmidecode.txt
lspci -vv > lspci.txt

Патриарх

Группа: Модератор
Сообщений: 11102
Регистрация: 12.09.2004
Пользователь №: 3794

Проблема оказалась вообще многоэтажной.

медленно по USB1 залил на диск файлы. Все открываются, читаются. Анмаунт.
на работе винда, приношу файлы — на диске пусто. Показывает вчерашние 2 файла с верными названиями но пустым содержанием

берем еще один комп с Arch но на другом чипсете, там диск определяется сразу, полноскоростной, файлы с последней записи видны и заполнены.
кидаем пару новых файлов. анмаунт

возвращаемся к винде. Видны и читабельны все файлы, как записанные на арче с nforce4, так и новые.

баг на баге и багом погоняет. Что делать и как еще тестить — не знаю.

Ветеран

Группа: Ведущий
Сообщений: 2922
Регистрация: 12.11.2002
Пользователь №: 74

Патриарх

Группа: Модератор
Сообщений: 11102
Регистрация: 12.09.2004
Пользователь №: 3794

FAT32. указано в первом сообщении

думаю, этот глюк с потерянной сессией можно не брать во внимание. гораздо интереснее почему диск работает только по USB1

Активист

Группа: Участник
Сообщений: 266
Регистрация: 13.09.2004
Пользователь №: 3810

Патриарх

Группа: Модератор
Сообщений: 11102
Регистрация: 12.09.2004
Пользователь №: 3794

Много репортов, что на 2.6.28 он сломан ничуть не меньше.

а вот 2.6.27 вроде бы в этом плане лучше. Только я очень не хочу откатывать ядро. Куча модулей, зависимостей пакетов и т.д. придется переставлять.
собираюсь на днях брать новый комп, многое буду ставить с нуля. Надеюсь, там проблем не будет, ни с дровами, ни с кибернейтами и суспендами.

думал, что nvidia зачастую = linux compatible, но видно что это не так. Да и кернель тим багоделы еще те. В прошлом бывали совсем абсурдные ситуации, например, когда дистриб (бубунта 8.10) сам себя с определенного момента установить не мог из-за проблем с sata cdrom. А 8.04 при этом ставился нормально.

я сообщу об изменениях с ehci_hcd в этой теме.

Ветеран

Группа: Участник
Сообщений: 1082
Регистрация: 23.02.2005
Пользователь №: 7608

Droid, в принципе, если есть желание, можно ковырять дальше. Вот, например, что предлагается для убунту:
https://wiki.ubuntu.com/DebuggingRemovableDevices

я бы проверил, загрузившись с лайв сд, под другим ядром.
Кроме того, все-таки можно подгрузить модуль для дебага USB. Попробовать выгрузить сначал один, потом второй модуль. Чтобы работал только один. Посмотреть, чтобы разные автомаунтеры типа hal не мутили воду. Интересно, что все-таки означает код ошибки -71.
Насчет исчезнувших файлов: точно отмонтировалось нормально? Может, сделать на всякий случай sync && umount. Вдруг устройство отсоединил рано.

Источник

Forum
The Ubuntu Forum Community
Ubuntu Official Flavours Support
Hardware
[ubuntu] [SOLVED] device descriptor read/64, error -71 — USB problem

I have a problem with my USB connections. for some resons they are not quite doing what they should. I have a new camera and on my old laptop (running Ubuntu 8.04) it is deteted immediately on the old USB 1.0. On my brand new PC also running Ubuntu 8.04 it is not detected. dmesg is showing the following:

[ 563.332000] end_request: I/O error, dev sdb, sector 60796
[ 563.332000] printk: 24 messages suppressed.
[ 563.332000] Buffer I/O error on device sdb1, logical block 60745
[ 717.556000] usb 2-4: new high speed USB device using ehci_hcd and address 12
[ 717.668000] usb 2-4: device descriptor read/64, error -71
[ 717.884000] usb 2-4: device descriptor read/64, error -71
[ 718.100000] usb 2-4: new high speed USB device using ehci_hcd and address 13
[ 718.212000] usb 2-4: device descriptor read/64, error -71
[ 718.428000] usb 2-4: device descriptor read/64, error -71
[ 718.644000] usb 2-4: new high speed USB device using ehci_hcd and address 14
[ 719.052000] usb 2-4: device not accepting address 14, error -71
[ 719.164000] usb 2-4: new high speed USB device using ehci_hcd and address 15
[ 719.572000] usb 2-4: device not accepting address 15, error -71
[ 801.752000] usb 2-4: new high speed USB device using ehci_hcd and address 16
[ 801.864000] usb 2-4: device descriptor read/64, error -71
[ 802.080000] usb 2-4: device descriptor read/64, error -71
[ 802.296000] usb 2-4: new high speed USB device using ehci_hcd and address 17
[ 802.408000] usb 2-4: device descriptor read/64, error -71
[ 802.624000] usb 2-4: device descriptor read/64, error -71
[ 802.840000] usb 2-4: new high speed USB device using ehci_hcd and address 18
[ 803.248000] usb 2-4: device not accepting address 18, error -71
[ 803.360000] usb 2-4: new high speed USB device using ehci_hcd and address 19
[ 803.768000] usb 2-4: device not accepting address 19, error -71

Any help appreciated — don’t quite understand why it is not working. Thanks!
Re: device descriptor read/64, error -71 — USB problem
Re: device descriptor read/64, error -71 — USB problem

Did you ever solve this problem? I’m trying to help someone with the same issue. I think it comes down to disabling CONFIG_USB_SUSPEND, which can be done by reloading the module «usbcore» with the option «autosuspend=-1.» However doing that is tricky because it’s hard to unload usbcore once the system is booted.

There are instructions here on other ways to disable CONFIG_USB_SUSPEND without reloading usbcore. Have you tried them? I don’t want to try them myself I can’t break my computer right now, and it’s hard to test USB stuff in a virtual machine.

Debian / Ubuntu systems:
========================

Comes with usbcore (CONFIG_USB) compiled as a module and CONFIG_USB_SUSPEND
enabled (at least on Ubuntu).

Therefore, to disable autosuspend you either:

— recompile kernel without CONFIG_USB_SUSPEND

— configure /etc/modprobe.d/ with a file containing
«options usbcore autosuspend=-1»
or set to 0 depending on your kernel

If your system needs the modprobe configuration file above, and if your
system uses initrd (probably does) then you will need to rebuild the
initrd for your kernel for this to take effect. For example:

dpkg-reconfigure linux-image-2.6.22.1
Re: device descriptor read/64, error -71 — USB problem

I have the same problem. With a camera

I tried the modprobe thing, but it did solve the problem
Re: device descriptor read/64, error -71 — USB problem

pytheas22: thanks. sorted it, can’t remember how though. Thanks anyway — good to see that someone is looking through all the unanswered threads.
Re: device descriptor read/64, error -71 — USB problem

pytheas22: thanks. sorted it, can’t remember how though. Thanks anyway — good to see that someone is looking through all the unanswered threads.

Do you have any idea how you fixed it? At least, do you remember if CONFIG_USB_SUSPEND had anything to do with it?

I’m sorry no one answered your post earlier, too. It’s a good example of why looking through unanswered posts is a good way to kill time when you’re bored.
Re: device descriptor read/64, error -71 — USB problem

hey guys, just put a clean install of Ubuntu back on my computer and of course had the same problem with the USB/Camera. Did a bit of research and found this so damn easy solution on the Mint Forum:

in the terminal type: echo -1 >/sys/module/usbcore/parameters/autosuspend

I was logged in as root — not sure whether necessary. Then just reboot and Bob’s your Uncle.

Worked a treat for me.
Re: device descriptor read/64, error -71 — USB problem

I tried this fix for the same error message with a different error number (-110), but it did not seem to have any effect.

Thanks,
Justin

Last edited by just_mcateer; October 23rd, 2008 at 02:10 AM.

Reason: New information
Re: device descriptor read/64, error -71 — USB problem

I tried this fix for the same error message with a different error number (-110), but it did not seem to have any effect.

What is the total output of ‘dmesg | tail’ after you plug in the device?
Re: [SOLVED] device descriptor read/64, error -71 — USB problem

Did you try this:
http://www.mepis.org/node/5860

In short as root:
echo Y > /sys/module/usbcore/parameters/old_scheme_first

Tags for this Thread

Bookmarks

Posting Permissions

Источник

That is the code for Protocol error (EPROTO). While there have been kernel issues that occasionally caused this, from my experience, this is usually a hardware issue with the USB subsystem.

The error message (which, incidentally, you didn’t post) usually refers to the USB port that caused the issue. A few pieces of advice:

Verify that the device is working properly on another computer.
Check whether the device is working correctly on another USB port.
Check your cables: 90% of such issues are caused by bad cables. Switching for another cable
could very well solve the issue.
Check your connectors: This is a common issue on old computers where oxidization has settled on the USB port pins. You could try removing it by inserting and removing the USB plug repeatedly. Warning: Don’t overdo it — USB connectors can and will break if you do.

I also doubt that GNOME has anything to do with the actual issue. It’s far more probable that installing a windowing system merely hides the error message. It’s probably still there in your dmesg output or the system logs.

It would help if you mentioned which USB device (make and model) causes this problem. Some devices are notorious for being rather unreliable…

Источник

Right then have done the same test schedule checks on each setting.

Start cold boot then 10 soft reboots then 4 power off/on/off cycles finally then 3 soft reboots.

If a setup gives enumeration or device descriptor error that test run is ended

0x0, 0x1, 0x4 & 0x08 fail either straight away or v.quickly

0x2 is much better only failing three times on odd errors

[ 5.173805] rtc rtc0: __rtc_set_alarm: err=-22

[ 5.017155] ftdi_sio ttyUSB3: Unable to write latency timer: -71

[ 3.929411] usb 1-1.4: New USB device found, idVendor=1199, idProduct=6832
[ 3.929422] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3.929429] usb 1-1.4: Product: Mini Card
[ 3.929945] usb 1-1.4: can’t set config #1, error -32

0x10 is the clear winner, I’ve not been able to «break» the setup at all using that one

I do occasionally see this message at the end but it’s not red so I can’t say if it’s a fault

[ 16.750450] random: crng init done
[ 16.750463] random: 7 urandom warning(s) missed due to ratelimiting

Does that help at all?

EDIT : Dropped back in the office this morning to pick something up, noticed I’d forgotten to to 0x08 so retested.

On first power up with setup still on 0x10 saw this error

[ 3.475621] usb 1-1.4: string descriptor 0 read error: -32
[ 3.475635] usb 1-1.4: New USB device found, idVendor=1199, idProduct=6832
[ 3.475644] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3.505822] usb 1-1.4: can’t set config #1, error -32

So I don’t have anything 100% working, but 0x10 appears the best of the bunch

FWIW I don’t think this prioblem is the same as OPs

Источник

I’m getting a lot of errors during bootup on Linux Mint 17.3 Cinnamon 64 bit. For the most time, I’ve been able to boot (the error messages just flash and disappear) with no problems with my system. A few times, Mint hasn’t booted up, now being one of those times. The error messages are as follows:

[0.668973] ACPI PCC probe failed.

and

[2.135031] usb 4-2: device descriptor read/all, error -71.

When I pressed the power button (just once) I get this:

[21.3186(or 06)50] ACPI: _SB_.PCI0.SBRG.ASOC: Device cannot be
configured due to a frequency mismatch.

I read on another question on Askubuntu (https://askubuntu.com/questions/584248/boot-error-acpi-pcc-probe-failed) that the «ACPI PCC probe failed» error is «harmless» so I guess that’s not a problem (I didn’t read it very thoroughly).

But it’d be nice to find out the cause of the two other errors. I’ll help to my best ability, of course. Thanks in advance.

asked Mar 2, 2016 at 20:54

ACPI PCC probe failed. means that your mainboard doesn’t support a relatively new (specified in 2011) feature called «Platform Communication Channel». It’s only a debug message and completely harmless.

usb 4-2: device descriptor read/all, error -71. means that an USB device was detected but could not be initialized at boot. There’s probably a faulty USB device connected to your computer or it’s an old device that only supports an old initialization scheme (See the comment by @munircontractor). You might be able to identify the device by running lsusb -s 4:$(cat /sys/bus/usb/devices/4-2/devnum).

ACPI: _SB_.PCI0.SBRG.ASOC: Device cannot be configured due to a frequency mismatch. means that a PCI card in your computer is incompatible with the PCI bus because it runs with another frequency, possibly because it’s too old. As the error message names the event source PCI0 it’s probably the first (topmost) PCI slot. Normally this error should only occur when the system boots or when a PCI card is hotplugged. It’s strange that it occurs when pressing the power button. That might be hinting at more complex hardware errors or BIOS bugs.

The PCI error is the most probable candidate for being related with your boot problems. If you have any PCI expansion cards in your computer, you should take a look at them and try if removing the one in the topmost PCI slot or moving it to another slot helps.

answered Mar 9, 2016 at 1:30

cg909cg909

6,6931 gold badge27 silver badges30 bronze badges

Источник

Печать

Страницы: [1] Вниз

Тема: USB ошибка 71 (Прочитано 6323 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Берия

Проблема такая есть: на буке стоит Ubuntu 8.04 kernel 2.6.24-19. Вчера пробовал поставить модем он у меня winmodem, полазив по форуму нашел что нужны дрова от slamr-2.6.24-19-generic попробовал поставил — модем неопределился, пробовал скомпилить из slmodem-2.9.11-20080803, тоже ничего не вышло, перегрузился и у меня отвалилась мышка usb, родной тачпад работает. Сегодня поробывал другую мышу результат — неопределяется, собщения в логах:
Aug 5 15:43:35 linux kernel: [ 234.251849] usb 3-2: new low speed USB device using uhci_hcd and address 2
Aug 5 15:43:35 linux kernel: [ 234.371735] usb 3-2: device descriptor read/64, error -71
Aug 5 15:43:35 linux kernel: [ 234.595506] usb 3-2: device descriptor read/64, error -71
Aug 5 15:43:35 linux kernel: [ 234.811289] usb 3-2: new low speed USB device using uhci_hcd and address 3
Aug 5 15:43:36 linux kernel: [ 234.931143] usb 3-2: device descriptor read/64, error -71
Aug 5 15:43:36 linux kernel: [ 235.158922] usb 3-2: device descriptor read/64, error -71
Aug 5 15:43:36 linux kernel: [ 235.374641] usb 3-2: new low speed USB device using uhci_hcd and address 4
Aug 5 15:43:36 linux kernel: [ 235.782243] usb 3-2: device not accepting address 4, error -71
Aug 5 15:43:37 linux kernel: [ 235.894127] usb 3-2: new low speed USB device using uhci_hcd and address 5
Aug 5 15:43:37 linux kernel: [ 236.305725] usb 3-2: device not accepting address 5, error -71

гугл не дал информации по этому поводу, на форуме тоже не нашел ничего подобного.
причем попробывал web камеру подключилась пес проблем, а вот флешка не хочет подключаться, встроенный кард ридер все видет беспроблем!
Чем можно исправить данную ситуацию?(кроме переустановки )

DALDON

Имею нечто подобное при загрузке настольного ПК. Но всё USB устройства работают без проблем — собственно увидил когда отключил сплеш заставку. Ну вот первое, что приходит в голову это удалить пакеты которые ставили? И потом гуглить снова на тему установки модема. И посмотреть куда раскидал пакет файлы/конфиги, всё удалить.

Берия

Пробовал. Удалил все пакеты от модема — ошибка осталась.

shagrat

Aug 5 15:43:35 linux kernel: [ 234.371735] usb 3-2: device descriptor read/64, error -71

У меня таже проблема….. в lsusb видит все а никакие устройства работать не хотят, я думаю это система мою материнку принимать никак не хочет
Материнка: Acorp 7NFU400(U)
PS: Может есть у кого дрова на эту материнку???

almur

Аналогичная ошибка на этапе загрузки ядра иногда проскакивает! Никаких ошибок или глюков ЮСБ при работе нет и не было. Предлагаю просто не обращать внимания

Печать

Страницы: [1] Вверх

Источник

Description

Harald Braun

2006-12-21 13:09:26 UTC

Description of problem:

Fedora 6 ignores Intel ICH5 Controller. USB-Interfaces don't work.
After booting FC6 and the message "RedHat nash version 5.1.19.0.2 starting" 
follows the errormessage "usb 1-1: device descriptor read/all, error -71". 
After this message, the computer does 50 - 60 seconds nothing. After this time 
the computer boots up. USB doesn't work.

On the same Computer exists an Windows 2000-Installation. The USB-Handling is 
correct.
Before Installing FC6 I had installed FC5. Under FC5 the USB-Handling was 
correct too.
After Updating FC5 to FC6 the errormessage comes up.

Version-Release number of selected component (if applicable):

kernel 2.6.18-1.2868.fc6

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2

Sammy

2006-12-21 14:37:52 UTC

I am getting a similar error but I am not sure how it effects the system since
my usb devices seem to be working (I have not tried the scsi disks on attached
usb photoprinter). The message is embedded in the SCSI initialization:

============================================================================
Fusion MPT base driver 3.04.01
Copyright (c) 1999-2005 LSI Logic Corporation
Fusion MPT SAS Host driver 3.04.01
ACPI: PCI Interrupt 0000:03:08.0[A] -> GSI 16 (level, low) -> IRQ 169
mptbase: Initiating ioc0 bringup
ioc0: SAS1068: Capabilities={Initiator}
usb 1-1: device not accepting address 2, error -71
scsi0 : ioc0: LSISAS1068, FwRev=00063200h, Ports=1, MaxQ=511, IRQ=169
  Vendor: SEAGATE   Model: ST373454SS        Rev: S410
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sda: 143374650 512-byte hdwr sectors (73408 MB)
sda: Write Protect is off
========================================================================

Comment 3

Harald Braun

2006-12-23 17:38:13 UTC

My USB-Interface now works well. 
Only the long boot-sequence and the error-message are cumbersome.

Comment 4

Pete Zaitcev

2007-01-12 20:45:30 UTC

It was suggested that such things happen during the port sharing between
ehci and uhci. For other people it did not occur if ehci was loaded first.

Harald, can we close it? How many messages do you receive? If just one,
it's all right. If they repeat, I'll look into it closer.

Comment 5

Will Woods

2007-01-15 16:43:27 UTC

I believe the "usb 1-1: device not accepting address 2, error -71" message is a
different problem than the message and hang originally reported - see bug
#213411 for that one.

Since Harald reports that the hang and the "device descriptor read/all" message
are gone, I think this bug can be closed.

Comment 6

Harald Braun

2007-01-21 19:15:42 UTC

I think, the bug cannot be closed. The following is fact:

After booting FC6 and the message "RedHat nash version 5.1.19.0.2 starting" 
follows the errormessage "usb 1-1: device descriptor read/all, error -71". 
After this message, the computer does 50 - 60 seconds nothing. After this time 
the computer boots up.

I think, it's a problem with USB 2.0 (ehci) or a problem during initializing the
SCSI Subsystem.

Comment 7

Rolf Fokkens

2007-02-12 12:27:58 UTC

When plugging in a Memory Stick, I get the following:

Feb 12 13:20:25 home01 kernel: usb 5-4: new high speed USB device using ehci_hcd
and address 6
Feb 12 13:20:25 home01 kernel: usb 2-2: new full speed USB device using uhci_hcd
and address 5
Feb 12 13:20:25 home01 kernel: usb 2-2: device descriptor read/64, error -71
Feb 12 13:20:25 home01 kernel: usb 2-2: device descriptor read/64, error -71
Feb 12 13:20:25 home01 kernel: usb 2-2: new full speed USB device using uhci_hcd
and address 6
Feb 12 13:20:26 home01 kernel: usb 2-2: device descriptor read/64, error -71
Feb 12 13:20:26 home01 kernel: usb 2-2: device descriptor read/64, error -71
Feb 12 13:20:26 home01 kernel: usb 2-2: new full speed USB device using uhci_hcd
and address 7
Feb 12 13:20:26 home01 kernel: usb 2-2: device not accepting address 7, error -71
Feb 12 13:20:27 home01 kernel: usb 2-2: new full speed USB device using uhci_hcd
and address 8
Feb 12 13:20:27 home01 kernel: usb 2-2: device not accepting address 8, error -71

The device doesn't operate. When connecting a USB hard drive I get the following:

usb 5-4: new high speed USB device using ehci_hcd and address 7
usb 5-4: unable to read config index 0 descriptor/all
usb 5-4: can't read configurations, error -71
usb 5-4: new high speed USB device using ehci_hcd and address 8
usb 5-4: configuration #1 chosen from 1 choice
Initializing USB Mass Storage driver...
scsi2 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 8
usb-storage: waiting for device to settle before scanning
usb 5-4: reset high speed USB device using ehci_hcd and address 8
usb 5-4: reset high speed USB device using ehci_hcd and address 8
usb 5-4: reset high speed USB device using ehci_hcd and address 8
usb 5-4: reset high speed USB device using ehci_hcd and address 8
usb-storage: device scan complete

And all works well

Comment 8

Paul Johnson

2007-02-14 19:39:02 UTC

I get that same usb 1-1 error at start up, but until now I ignored it because
everything worked.  

After the most recent set of Fedora updates, my usb printer will not work and
gives the same error messages that your memory stick gives.

But my usb external CDROM does work!

Go figure.

That's with FC6 all updated to kernel-2.6.19-1.2895.fc6

Comment 9

Pete Zaitcev

2007-02-14 19:52:10 UTC

Paul, file a new bug for me, please. Don't be fooled by messages, it's
a different problem.

Comment 10

Rolf Fokkens

2007-03-08 20:58:01 UTC

kernel-2.6.19-1.2911.6.5.fc6, when connecting Memory stick, like Comment #7:

Mar  8 21:55:01 home01 kernel: usb 5-4: new high speed USB device using ehci_hcd
and address 5
Mar  8 21:55:01 home01 kernel: usb 2-2: new full speed USB device using uhci_hcd
and address 6
Mar  8 21:55:01 home01 kernel: usb 2-2: device descriptor read/64, error -71
Mar  8 21:55:02 home01 kernel: usb 2-2: device descriptor read/64, error -71
Mar  8 21:55:02 home01 kernel: usb 2-2: new full speed USB device using uhci_hcd
and address 7
Mar  8 21:55:02 home01 kernel: usb 2-2: device descriptor read/64, error -71
Mar  8 21:55:02 home01 kernel: usb 2-2: device descriptor read/64, error -71
Mar  8 21:55:02 home01 kernel: usb 2-2: new full speed USB device using uhci_hcd
and address 8
Mar  8 21:55:03 home01 kernel: usb 2-2: device not accepting address 8, error -71
Mar  8 21:55:03 home01 kernel: usb 2-2: new full speed USB device using uhci_hcd
and address 9
Mar  8 21:55:03 home01 kernel: usb 2-2: device not accepting address 9, error -71
Mar  8 21:55:05 home01 be[5036]: user rolf start assuming role root (root:root) 
[

Comment 11

Bug Zapper

2008-04-04 05:19:59 UTC

Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
http://fedoraproject.org/wiki/LifeCycle/EOL

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 12

Bug Zapper

2008-05-06 17:13:27 UTC

This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Источник

If Linux suddenly happen to fail to recognize a USB drive, check dmesg for errors. Once you see a bunch of errors like

usb 1-5: device descriptor read/64, error -32  
usb 1-5: new high speed USB device using ehci_hcd and address 21  
usb 1-5: device not accepting address 21, error -32

most probably it’s a result of hardware failure rather than a driver or kernel bug. USB has an over-current protection, which gets triggered when power consumption from the port is too high.

Unplug all USB devices from PC, turn power off, and wait a minute or two. Plug everything back and boot into Linux.

I spent the whole morning, until found out why. I hope that this message will save someone a few hours, and nerves.

PS: Actual errors may vary. You may see different port and/or error code. Ex.:

usb 3-1: device descriptor read/64, error -62

usb 4-2: device descriptor read/64, error -71

usb 2-3: device descriptor read/64, error -101

but the root of the problem is the same.

Источник

January 27, 2009

I recently obtained an external USB hard disk, and have been irritated by it ever since I got it. Or rather, I’ve been irritated by the way Ubuntu Hardy interacts with the disk. Half of the time when I connected the hard disk to my computer, I would get the following error messages:

	[ 4159.607574] usb 1-1: new full speed USB device using uhci_hcd and address 4
	[ 2079.875502] usb 1-1: device descriptor read/64, error -71
	[ 2080.099379] usb 1-1: device descriptor read/64, error -71
	[ 2080.319263] usb 1-1: new full speed USB device using uhci_hcd and address 5
	[ 2080.443858] usb 1-1: device descriptor read/64, error -71
	[ 4161.322029] usb 1-1: device descriptor read/64, error -71
	[ 4161.537896] usb 1-1: new full speed USB device using uhci_hcd and address 6
	[ 4161.945615] usb 1-1: device not accepting address 6, error -71
	[ 4162.057577] usb 1-1: new full speed USB device using uhci_hcd and address 7
	[ 4162.465330] usb 1-1: device not accepting address 7, error -71

Other than this error message, the device was totally unrecognised. The USB port worked fine, and there were no problems with the hard disk, which I could use without any problems on other computers. Ubuntu’s behaviour was very unpredictable: I could detect no pattern why it sometimes recognised the disk, and why at other times it would ignore it.

An internet search indicated this is not an uncommon problem, and usbcore, which is compiled as a module in Hardy’s kernel, seems to be the culprit. Plenty of suggestions were offered online (including recompiling the kernel) but most of them did not help me at all.

Finally, I found something on an old mailing list that solved the problem. All I needed to do was add the following line to /etc/modprobe.d/options:

	options usbcore use_both_schemes=y

(If you are curious as to why this solved the problem, please read this clear explanation.)

After a reboot, my external USB drive is now recognised without any difficulties every time I plug it in.

Источник

Thread: [SOLVED] device descriptor read/64, error -71 — USB problem

Thread Tools

Display

[SOLVED] device descriptor read/64, error -71 — USB problem

Re: device descriptor read/64, error -71 — USB problem

Re: device descriptor read/64, error -71 — USB problem

Usb device descriptor read all error 71

Re: device descriptor read/64, error -71 — USB problem

Re: device descriptor read/64, error -71 — USB problem

Re: device descriptor read/64, error -71 — USB problem

Re: device descriptor read/64, error -71 — USB problem

Re: device descriptor read/64, error -71 — USB problem

Re: device descriptor read/64, error -71 — USB problem

Re: device descriptor read/64, error -71 — USB problem

Re: device descriptor read/64, error -71 — USB problem

Re: [SOLVED] device descriptor read/64, error -71 — USB problem

Tags for this Thread

Bookmarks

Bookmarks

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://ubuntuforums.org/images/ubuntu-VB4/buttons/collapse_40b.png" alt /> Posting Permissions

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> Берия

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> DALDON

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> Берия

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> shagrat

almur

January 27, 2009

Читайте также:

Posting Permissions

Берия

DALDON

Берия

shagrat