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

Discussion in 'Storage Devices' started by lbrtchx, May 3, 2007.

  1. lbrtchx

    lbrtchx Guest

    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
     
    lbrtchx, May 3, 2007
    #1
    1. Advertisements

  2. lbrtchx

    Arno Wagner Guest

    In comp.sys.ibm.pc.hardware.storage 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


    What is this ''external minidrive'' exactly? Typically all
    USB storage needs only the USB storage drive under Linux,
    so this seems to be either a hardware problem or a kernel bug.

    Bug 7932 might be what is the issue, see
    http://bugzilla.kernel.org/show_bug.cgi?id=7932

    It seems to have been introduced some time after kernel 2.6.18.6
    and is currently unresolved. The only advice I can give you
    at this time is to try with an older kernel, e.g. any
    2.6.18-variant.

    Arno
     
    Arno Wagner, May 3, 2007
    #2
    1. Advertisements

  3. lbrtchx

    Guest

    > What is this ''external minidrive'' exactly?
    a Toshiba 40.00 Gb HDD2171 MK40196GAX
    ~
    I started Linux/knoppix with the cheatcode
    ~
    acpi=off noacpi testcd init 2
    ~
    I ran dmesg:
    ~
    ....
    usb 1-1: new high speed USB device using ehci_hcd and address 2
    usb 1-1: device descriptor read/64, error -71
    usb 1-1: configuration #1 chosen from 1 choice
    scsi0 : SCSI emulation for USB Mass Storage devices
    usb-storage: device found at 2
    usb-storage: waiting for device to settle before scanning
    scsi 0:0:0:0: Direct-Access Generic USB Disk 9.02 PQ: 0
    ANSI: 2
    SCSI device sda: 78140160 512-byte hdwr sectors (40008 MB)
    sda: Write Protect is off
    sda: Mode Sense: 03 00 00 00
    sda: assuming drive cache: write through
    SCSI device sda: 78140160 512-byte hdwr sectors (40008 MB)
    sda: Write Protect is off
    sda: Mode Sense: 03 00 00 00
    sda: assuming drive cache: write through
    sda: sda1 sda2 sda3 sda4 < sda5 >
    sd 0:0:0:0: Attached scsi disk sda
    usb-storage: device scan complete
    ~
    then fdisk and got
    ~
    Disk /dev/sda: 40.0 GB, 40007761920 bytes
    256 heads, 63 sectors/track, 4845 cylinders
    Units = cylinders of 16128 * 512 = 8257536 bytes

    Device Boot Start End Blocks Id System
    /dev/sda1 1 255 2056288+ 83 Linux
    /dev/sda2 256 1024 6201216 83 Linux
    /dev/sda3 1025 1892 6999552 c W95 FAT32
    (LBA)
    /dev/sda4 1893 4845 23812992 5 Extended
    /dev/sda5 1893 4845 23812960+ 83 Linux
    ~
    I am able to fdisk, mount and access this USB-based (it is also
    powered through the USB cable) external minidrive without any problems
    now, which makes me wonder how safe my perception is.
    ~
    Is there any way I could test the drive by other means? Even in a low
    level way to see what is really going on with it and try to tell apart
    hardware from software problems and if they are software ones, of
    which kind? Or do you think the drive si just fine (I will regularly
    backup my data anyway ;-))
    ~
    lbrtchx
     
    , May 4, 2007
    #3
  4. lbrtchx

    Guest

    Notice I am still getting the pesky
    ~
    "device descriptor read/64, error -71"
    ~
    error message
    ~
    lbrtchx
     
    , May 4, 2007
    #4
  5. lbrtchx

    Arno Wagner Guest

    Previously wrote:
    >> What is this ''external minidrive'' exactly?

    > a Toshiba 40.00 Gb HDD2171 MK40196GAX
    > ~
    > I started Linux/knoppix with the cheatcode
    > ~
    > acpi=off noacpi testcd init 2
    > ~
    > I ran dmesg:
    > ~
    > ...
    > usb 1-1: new high speed USB device using ehci_hcd and address 2
    > usb 1-1: device descriptor read/64, error -71
    > usb 1-1: configuration #1 chosen from 1 choice
    > scsi0 : SCSI emulation for USB Mass Storage devices
    > usb-storage: device found at 2
    > usb-storage: waiting for device to settle before scanning
    > scsi 0:0:0:0: Direct-Access Generic USB Disk 9.02 PQ: 0
    > ANSI: 2
    > SCSI device sda: 78140160 512-byte hdwr sectors (40008 MB)
    > sda: Write Protect is off
    > sda: Mode Sense: 03 00 00 00
    > sda: assuming drive cache: write through
    > SCSI device sda: 78140160 512-byte hdwr sectors (40008 MB)
    > sda: Write Protect is off
    > sda: Mode Sense: 03 00 00 00
    > sda: assuming drive cache: write through
    > sda: sda1 sda2 sda3 sda4 < sda5 >
    > sd 0:0:0:0: Attached scsi disk sda
    > usb-storage: device scan complete
    > ~
    > then fdisk and got
    > ~
    > Disk /dev/sda: 40.0 GB, 40007761920 bytes
    > 256 heads, 63 sectors/track, 4845 cylinders
    > Units = cylinders of 16128 * 512 = 8257536 bytes


    > Device Boot Start End Blocks Id System
    > /dev/sda1 1 255 2056288+ 83 Linux
    > /dev/sda2 256 1024 6201216 83 Linux
    > /dev/sda3 1025 1892 6999552 c W95 FAT32
    > (LBA)
    > /dev/sda4 1893 4845 23812992 5 Extended
    > /dev/sda5 1893 4845 23812960+ 83 Linux
    > ~
    > I am able to fdisk, mount and access this USB-based (it is also
    > powered through the USB cable) external minidrive without any problems
    > now, which makes me wonder how safe my perception is.
    > ~
    > Is there any way I could test the drive by other means? Even in a low
    > level way to see what is really going on with it and try to tell apart
    > hardware from software problems and if they are software ones, of
    > which kind? Or do you think the drive si just fine (I will regularly
    > backup my data anyway ;-))
    > ~
    > lbrtchx


    Well, I don't think you need to worry too much. If it reads and
    writes fine, thebn it should be ok. However if something breaks,
    it will likely be the USB interface. In that case you can still
    connect the disk directly via IDE and get the data.

    Arno
     
    Arno Wagner, May 4, 2007
    #5
  6. lbrtchx

    Arno Wagner Guest

    Previously wrote:
    > Notice I am still getting the pesky
    > ~
    > "device descriptor read/64, error -71"
    > ~
    > error message
    > ~
    > lbrtchx


    Yes. But is does not seem to impact drive functionality.

    Arno
     
    Arno Wagner, May 4, 2007
    #6
  7. lbrtchx

    Guest

    well, I think you are right. It might be most probably kernel related
    ~
    I tried using knoppix 4.0.2 which uses kernel
    ~
    2.6.12
    ~
    and even though I still got "device descriptor read/64, error -71"
    the full dump read
    ~
    usb 4-1: new full speed USB device using uhci_hcd and address 2
    usb 4-1: device descriptor read/64, error -71
    scsi1 : SCSI emulation for USB Mass Storage devices
    usb-storage: device found at 2
    usb-storage: waiting for device to settle before scanning
    Vendor: Generic Model: USB Disk Rev: 9.02
    Type: Direct-Access ANSI SCSI revision: 02
    SCSI device sdb: 78140160 512-byte hdwr sectors (40008 MB)
    sdb: assuming drive cache: write through
    SCSI device sdb: 78140160 512-byte hdwr sectors (40008 MB)
    sdb: assuming drive cache: write through
    sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 >
    Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
    usb-storage: device scan complete
    ~
    and I was able to use the disk without any problems
    ~
    However it might also be hardware/BIOS related. When I try knoppix
    5.1.1 CD at work with:
    ~
    acpi=off noacpi init 2
    ~
    using my box at work, I am getting
    ~
    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.
    usb 1-4: device descriptor read/64, error -71
    usb 1-4: device not accepting address 3, error -110
    usb 1-4: new high speed USB device using ehci_hcd and address 4
    usb 1-4: device not accepting address 4, error -110
    usb 1-4: new high speed USB device using ehci_hcd and address 5
    usb 1-4: device not accepting address 5, error -110
    usb 1-4: new high speed USB device using ehci_hcd and address 6
    usb 1-4: device not accepting address 6, error -110
    ~
    usb 2-4: new high speed USB device using ehci_hcd and address 2
    ehci_hcd 0000:0a:0a.2: Unlink after no-IRQ? Controller is probably
    using the wrong IRQ.
    usb 2-4: device descriptor read/64, error -71
    usb 2-4: device not accepting address 2, error -110
    usb 2-4: new high speed USB device using ehci_hcd and address 3
    usb 2-4: device descriptor read/64, error -110
    usb 2-4: device not accepting address 3, error -110
    usb 2-4: new high speed USB device using ehci_hcd and address 4
    usb 2-4: device not accepting address 4, error -110
    usb 2-4: new high speed USB device using ehci_hcd and address 5
    usb 2-4: device not accepting address 5, error -110
    usb 1-5: new high speed USB device using ehci_hcd and address 7
    usb 1-5: device descriptor read/64, error -71
    usb 1-5: device not accepting address 7, error -110
    usb 1-5: new high speed USB device using ehci_hcd and address 8
    usb 1-5: device descriptor read/64, error -110
    usb 1-5: device not accepting address 8, error -110
    usb 1-5: new high speed USB device using ehci_hcd and address 9
    usb 1-5: device not accepting address 9, error -110
    usb 1-5: new high speed USB device using ehci_hcd and address 10
    usb 1-5: device not accepting address 10, error -110

    ~
    usb 1-6: 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.
    usb 1-6: device descriptor read/64, error -71
    usb 1-6: device not accepting address 3, error -110
    usb 1-6: new high speed USB device using ehci_hcd and address 4
    usb 1-6: device not accepting address 4, error -110
    usb 1-6: new high speed USB device using ehci_hcd and address 5
    usb 1-6: device not accepting address 5, error -110
    usb 1-6: new high speed USB device using ehci_hcd and address 6
    usb 1-6: device not accepting address 6, error -110
    ~
    lbrtchx
     
    , May 4, 2007
    #7
  8. lbrtchx

    Arno Wagner Guest

    Previously Mike Tomlinson <> wrote:
    > In article <>,
    > writes


    >> acpi=off noacpi testcd init 2


    > Shouldn't that be "acpi=off noapic" ?


    I think it should.

    Arno
     
    Arno Wagner, May 5, 2007
    #9
  9. lbrtchx

    Guest

  10. In article <>,
    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/~pgut001/pubs/vista_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
     
    Mike Tomlinson, May 6, 2007
    #11
  11. 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/~pgut001/pubs/vista_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
     
    Mike Tomlinson, May 6, 2007
    #12
  12. lbrtchx

    Arno Wagner Guest

    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
     
    Arno Wagner, May 6, 2007
    #13
  13. lbrtchx

    Guest

    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.
     
    , Jun 11, 2007
    #14
  14. lbrtchx

    Guest

    > 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
     
    , Jun 12, 2007
    #15
    1. Advertisements

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. > > > Alan
    Replies:
    2
    Views:
    306
    The little lost angel
    May 2, 2004
  2. Samson

    Network Storage Device back to USB device

    Samson, Mar 26, 2005, in forum: Storage Devices
    Replies:
    5
    Views:
    207
    Samson
    Mar 27, 2005
  3. ndy
    Replies:
    2
    Views:
    1,287
    Rod Speed
    Feb 25, 2006
  4. Rob Nicholson

    The device, \Device\Harddisk1, has a bad block.

    Rob Nicholson, May 15, 2006, in forum: Storage Devices
    Replies:
    2
    Views:
    362
    Rob Nicholson
    May 16, 2006
  5. Replies:
    9
    Views:
    1,689
    Rod Speed
    Jul 2, 2006
Loading...

Share This Page