You are not logged in.
Hi all,
Since upgrading my kernel to the latest version, I'm experiencing this issue when plugging in my Nokia 6288 mobile phone:
usb x-x: device not accepting address x, error -62
eg:
usb 2-1: new full speed USB device using ohci_hcd and address 2
usb 2-1: device descriptor read/64, error -62
usb 2-1: device descriptor read/64, error -62
usb 2-1: new full speed USB device using ohci_hcd and address 3
usb 2-1: device descriptor read/64, error -62
usb 2-1: device descriptor read/64, error -62
usb 2-1: new full speed USB device using ohci_hcd and address 4
usb 2-1: device not accepting address 4, error -62
usb 2-1: new full speed USB device using ohci_hcd and address 5
usb 2-1: device not accepting address 5, error -62
With the previous kernel version, I also experienced this problem, but in later revisions (.21 onwards IIRC) it was fixed. What would be the best course of action for me to take to resolve this issue?
Thanks
Offline
I have a similar problem with my USB HDD since I'm using kernel .23, so you are not the only one with this kind of problem.
Demsg:
usb 3-1: new high speed USB device using ehci_hcd and address 4
usb 3-1: device descriptor read/64, error -71
usb 3-1: device descriptor read/64, error -71
usb 3-1: new high speed USB device using ehci_hcd and address 5
usb 3-1: device descriptor read/64, error -71
usb 3-1: device descriptor read/64, error -71
usb 3-1: new high speed USB device using ehci_hcd and address 6
usb 3-1: device not accepting address 6, error -71
usb 3-1: new high speed USB device using ehci_hcd and address 7
usb 3-1: device not accepting address 7, error -71
My USB flash drive works fine:
usb 3-6.3: new high speed USB device using ehci_hcd and address 8
usb 3-6.3: configuration #1 chosen from 1 choice
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Initializing USB Mass Storage driver...
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 8
usb-storage: waiting for device to settle before scanning
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
scsi 2:0:0:0: Direct-Access USB 2.0 Flash Disk 1100 PQ: 0 ANSI: 0 CCS
sd 2:0:0:0: [sdc] 4013056 512-byte hardware sectors (2055 MB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 43 00 00 00
sd 2:0:0:0: [sdc] Assuming drive cache: write through
sd 2:0:0:0: [sdc] 4013056 512-byte hardware sectors (2055 MB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 43 00 00 00
sd 2:0:0:0: [sdc] Assuming drive cache: write through
sdc: sdc1
sd 2:0:0:0: [sdc] Attached SCSI removable disk
sd 2:0:0:0: Attached scsi generic sg4 type 0
usb-storage: device scan complete
Offline
Similar problem with a WD usb HDD, since kernel 2.6.23, on both 32 and 64 bit systems. No other devices I use have this problem.
usb 1-3: new high speed USB device using ehci_hcd and address 5
usb 1-3: device descriptor read/64, error -110
usb 1-3: device descriptor read/64, error -110
usb 1-3: new high speed USB device using ehci_hcd and address 6
usb 1-3: device descriptor read/64, error -110
usb 1-3: device descriptor read/64, error -110
usb 1-3: new high speed USB device using ehci_hcd and address 7
APIC error on CPU1: 40(40)
APIC error on CPU0: 40(40)
usb 1-3: device descriptor read/8, error -110
usb 1-3: device descriptor read/8, error -110
usb 1-3: new high speed USB device using ehci_hcd and address 8
usb 1-3: device descriptor read/8, error -110
usb 1-3: device descriptor read/8, error -110
Any ideas?
Offline
I pluged the HDD in my Notebook with same kernel and it worked, so I guess it can't be a problem with the device driver. Maybe it is a problem with the driver for the USB contoller on the Mainboard.
Offline
Same here. I posted it in desktop environments, not realising this problem is kernel-related: http://bbs.archlinux.org/viewtopic.php?id=39238
Tonight I will try to disable USB 2.0 in my BIOS. The system I'm using is 'oldish': mainbord is a Via KT400 and the external HDD I'm connecting is a HP Pocket Media Drive 120GB.
I don't see any APIC-errors in my logs, but someone on the internet had the same problem two years ago and he solved it by disbaling APIC in his BIOS.
Zl.
/EDIT: On the Gentoo forum I found something similar (although not the same), and the first reply suggests it to be kernel-related: http://forums.gentoo.org/viewtopic-t-607631.html - I have never before tried my pocket drive on Arch, so I don't know if the problem is caused by the new kernel...
Last edited by zenlord (2007-10-30 13:26:43)
Offline
I don't know it'll help solving the puzzle, but tonight I booted with the 'acpi=off' option passed in grub, and besides HAL not starting, I got this extra line in dmesg:
usb 2-2: new full speed USB device using uhci_hcd and address 2
uhci_hcd 0000:00:10.1: Unlink after no-IRQ? Controller is probably using the wrong IRQ.
usb 2-2: device descriptor read/64, error -110
Could this be causing all these problems? A faulty IRQ? And if yes, how do I change the IRQ?
Zl.
Offline
And another update: Ubuntu 7.10 desktop in livecd mode has the same problem. This afternoon I will try an older livecd.
Zl.
Offline
I have not had the time to test another distro, but I tried a PCI USB-hub and got the same results (although now its ehci_hcd that is complaining instead of uhci_hcd). So I guess a BIOS upgrade won't make a difference.
Anyone else got a similar problem? Could it be that the USB-drive I'm using is too new to be recognised by HAL or UDEV?
Zl.
Offline
Having the same issue with a Seagate FreeAgent here. I also have a SuSE 10.3 installation with the 2.6.22 kernel which doesn't have this problem.
One thing I noticed is that once you get that damn error, it continues to happen across all operating systems (have Arch/SuSE/WinXP) until the device is unplugged and restarted. Then it becomes detectable again.
Last edited by Mazaev (2007-11-10 14:36:30)
Offline
Has there been any solution found for this problem? I am currently unable to use an external harddrive for the same -71 error. Thanks a bunch.
Offline
Bumping this. I thought maybe the newly released .24 kernel might have solved this issue, but nope. I'm still stuck using 2.6.22.
Does anyone at all know what the deal is?
EDIT: After futzing around with this for entirely too long, switching cables did the trick.
Last edited by Mazaev (2008-02-27 01:59:19)
Offline
Just thought I'd say that I was having the
usb 1-3: device descriptor read/64, error -110
error, and changing the USB cable fixed it. Also, with the bad cable, devices other then the one with the bad cable (a hub) were affected. Makes locating the problem difficult. It would appear the -110 error is a power-related error, if anyone else is having issues. (I think maybe the cable was shorting)
Last edited by compwiz18 (2008-04-16 10:27:59)
Offline
hi, i have had this issue before!!!
if the dmeg error is '-110';
try to unload module ehci_hcd
modprobe -r ehci_hcd
or blacklist it in
/etc/hotplug/blacklist
if the dmesg error is '-62';
its a bit more complicated! -62 means ur usb device has been badly corrupted!!! i had this issue from live distros on it!! i put puppy on usb once, then it got buggered up!! fixed it but cant remember how exactly! same issue again now, so will remember in a bit and post back the solution! i think i reformated it and used some other tools available thru pacman, but will post the solution later!!
not sure on other errors, sorry! hope this helps!
2007 - Started using Arch Linux as my only/main OS
- Samsung Series 3, Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz - 8Gb DDR3 ram - 700Gb HDD
On board intel Graphics & Sound
Offline
ok, solution to '-62' is simple(ish)!!!!!!
I remember now that the first thing you need to do is
lsusb
if the device isnt listed there, replug it it, then re run lsusb, there will be a few seconds delay! once lsusb picks the device up, just run fsck on it;
su
password
fsck /dev/sdcx
fsck 1.41.3 (12-Oct-2008)
dosfsck 3.0.1, 23 Nov 2008, FAT32, LFN
/dev/sdc1: 0 files, 0/60102 clusters
as long as the output is similiar to this its fixed!! easy! however, there is another outcome! sometimes, u can get an error, but i cant remember it properly! something to do with the number of sectors!! if this happens, u need to properly start repairing! format it first, then start playing with hd repair tools!
2007 - Started using Arch Linux as my only/main OS
- Samsung Series 3, Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz - 8Gb DDR3 ram - 700Gb HDD
On board intel Graphics & Sound
Offline
solution to '-71'
not 100% sure, but stumbled upon a couple of posts to do with usb suspend
http://kerneltrap.org/mailarchive/linux … /19/106270
http://www.linuxquestions.org/questions … 71-643022/
2007 - Started using Arch Linux as my only/main OS
- Samsung Series 3, Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz - 8Gb DDR3 ram - 700Gb HDD
On board intel Graphics & Sound
Offline