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

In article . com,
writes
Hmm! Actually there is both:

You're missing the point. According to your posts, you're booting with
the kernel parameters "acpi=off noacpi" which do the same thing, so one
parameter is redundant. It sounds to me as if you don't realise that
ACPI and APIC are two different things.

When diagnosing possible hardware problems such as the one you're
having, it's useful to disable the ACPI BIOS with "acpi=off" and disable
the advanced programmable interrupt controller with "noacpi".

The APIC is relevant, as you mention getting this output:

"usb 1-4: new high speed USB device using ehci_hcd and address 3
ehci_hcd 0000:00:1d.7: Unlink after no-IRQ? Controller is probably
using the wrong IRQ."

This suggests an APIC routing problem, possibly due to a buggy BIOS, so
it's worth trying again with APIC turned off.

--
(\__/) Bunny says NO to Windows Vista!
(='.'=) http://www.badvista.org/
(")_(") http://www.cs.auckland.ac.nz/~pgut00...ista_cost.html
http://www.theinquirer.net/default.aspx?article=38926
http://www.schneier.com/crypto-gram-0702.html#8
http://www.theinquirer.net/default.aspx?article=39051
http://www.theinquirer.net/default.aspx?article=39087
http://www.theinquirer.net/default.aspx?article=37091
http://www.theinquirer.net/default.aspx?article=36653

In article , Mike Tomlinson
writes

When diagnosing possible hardware problems such as the one you're
having, it's useful to disable the ACPI BIOS with "acpi=off" and disable
the advanced programmable interrupt controller with "noacpi".
^^^^^^
That should read noapic, dammit.

--
(\__/) Bunny says NO to Windows Vista!
(='.'=) http://www.badvista.org/
(")_(") http://www.cs.auckland.ac.nz/~pgut00...ista_cost.html
http://www.theinquirer.net/default.aspx?article=38926
http://www.schneier.com/crypto-gram-0702.html#8
http://www.theinquirer.net/default.aspx?article=39051
http://www.theinquirer.net/default.aspx?article=39087
http://www.theinquirer.net/default.aspx?article=37091
http://www.theinquirer.net/default.aspx?article=36653

Previously Mike Tomlinson wrote:
In article , Mike Tomlinson
writes

When diagnosing possible hardware problems such as the one you're
having, it's useful to disable the ACPI BIOS with "acpi=off" and disable
the advanced programmable interrupt controller with "noacpi".
^^^^^^
That should read noapic, dammit.

Well, I have been mixing these up since the option exixts ;-)

Arno

On 3 Mai, 12:02, lbrtchx wrote:
Hi,
~
I am using knoppix 5.1.1 based on the Linux 2.6.19 kernel
~
sh-3.1# uname -r
2.6.19
~
I started Linux/knoppix with the cheatcode
~
knoppix init 2
~
then, after plugging in an external minidrive (before even starting X/KDE),
I got:
~
Synchronizing SCSI cache for disk sda:
FAILED
status = 0, message = 00, vhost = 1, driver = 00
7 APIC error on CPU00: 01(01)
usb 1-2: device descriptor read/64, error -71
usb 1-2: device descriptor read/64, error -71
usb 1-2: device descriptor read/64, error -71
usb 1-2: device descriptor read/64, error -71
usb 1-2: device descriptor read/64, error -71
usb 1-2: device descriptor read/64, error -71
. . .
~
I read from the error message and from some postings out there that it is
related to the combination of USB + APIC (+ low speed devices + bad
drivers?), that it also happens with printers, pen drives and wireless
cards connected via USB, so I started Linux/knoppix with:
~
knoppix apic=off noapic init 2
~
then I didn't get the first error stanzas, but only the
~
usb 1-2: device descriptor read/64, error -71
usb 1-2: device descriptor read/64, error -71
usb 1-2: device descriptor read/64, error -71
. . .
~
ones repeatedly
~
Why are these problems happening?
~
How can I fix them?
~
Thanks
lbrtchx

I had a bad (low quality) cable. Replacing it with an USB 2.0 spec
cable fixed it.
You should exclude other hard ware problems as well.

I had a bad (low quality) cable. Replacing it with an USB 2.0 spec
cable fixed it.
You should exclude other hard ware problems as well.
~
Well, yeah, I guess!
~
Any specifics about what you just mentioned? Any way to test USB
cables to spec? What would be other the hardware problems?
~
lbrtchx