Prev: Debugging I/O errors?
Next: mmaping a kernel buffer to user space
From: Marc Perkel on 30 Oct 2006 18:30
Running the latest FC6 kernel based on 2.6.18.1. What does this error mean?

device descriptor read/64, error -110

Is this a kernel bug? Thanks in advance?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Adrian Bunk on 30 Oct 2006 19:00
On Mon, Oct 30, 2006 at 03:29:00PM -0800, Marc Perkel wrote:
> Running the latest FC6 kernel based on 2.6.18.1. What does this error mean?
>
> device descriptor read/64, error -110
>
> Is this a kernel bug? Thanks in advance?

That's a timeout.

Your bug report lacks any any information for further debugging your
problem.

- When does it occur?
- What is failing?
- Please send the output of "dmesg -s 1000000".

And please read and follow REPORTING-BUGS in the kernel sources before
sending your next bug report.

cu
Adrian

--

"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Marc Perkel on 30 Oct 2006 19:10


Adrian Bunk wrote:
> On Mon, Oct 30, 2006 at 03:29:00PM -0800, Marc Perkel wrote:
>
>> Running the latest FC6 kernel based on 2.6.18.1. What does this error mean?
>>
>> device descriptor read/64, error -110
>>
>> Is this a kernel bug? Thanks in advance?
>>
>
> That's a timeout.
>
> Your bug report lacks any any information for further debugging your
> problem.
>
> - When does it occur?
> - What is failing?
> - Please send the output of "dmesg -s 1000000".
>
> And please read and follow REPORTING-BUGS in the kernel sources before
> sending your next bug report.
>
> cu
> Adrian
>
>

Thanks for your help. The device is a module that lets me plug in
various kinds og camera memory sticks.

usb 1-7: new full speed USB device using ohci_hcd and address 2
usb 1-7: device descriptor read/64, error -110
usb 1-7: device descriptor read/64, error -110
usb 1-7: new full speed USB device using ohci_hcd and address 3
usb 1-7: device descriptor read/64, error -110


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Adrian Bunk on 30 Oct 2006 20:20
On Mon, Oct 30, 2006 at 03:59:32PM -0800, Marc Perkel wrote:
>
>
> Adrian Bunk wrote:
> >On Mon, Oct 30, 2006 at 03:29:00PM -0800, Marc Perkel wrote:
> >
> >>Running the latest FC6 kernel based on 2.6.18.1. What does this error
> >>mean?
> >>
> >>device descriptor read/64, error -110
> >>
> >>Is this a kernel bug? Thanks in advance?
> >>
> >
> >That's a timeout.
> >
> >Your bug report lacks any any information for further debugging your
> >problem.
> >
> >- When does it occur?
> >- What is failing?
> >- Please send the output of "dmesg -s 1000000".
> >
> >And please read and follow REPORTING-BUGS in the kernel sources before
> >sending your next bug report.
> >
> >cu
> >Adrian
> >
> >
>
> Thanks for your help. The device is a module that lets me plug in
> various kinds og camera memory sticks.
>
> usb 1-7: new full speed USB device using ohci_hcd and address 2
> usb 1-7: device descriptor read/64, error -110
> usb 1-7: device descriptor read/64, error -110
> usb 1-7: new full speed USB device using ohci_hcd and address 3
> usb 1-7: device descriptor read/64, error -110

Please send the _complete_ output of "dmesg -s 1000000".
If you want help, you should include as much information as possible.

If you are concerned about the size of your email, please remember that
linux-kernel has a 100 kB size limit - and everything smaller is
perfectly OK.

cu
Adrian

--

"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Marc Perkel on 30 Oct 2006 20:30


Adrian Bunk wrote:
> On Mon, Oct 30, 2006 at 03:59:32PM -0800, Marc Perkel wrote:
>
>> Adrian Bunk wrote:
>>
>>> On Mon, Oct 30, 2006 at 03:29:00PM -0800, Marc Perkel wrote:
>>>
>>>
>>>> Running the latest FC6 kernel based on 2.6.18.1. What does this error
>>>> mean?
>>>>
>>>> device descriptor read/64, error -110
>>>>
>>>> Is this a kernel bug? Thanks in advance?
>>>>
>>>>
>>> That's a timeout.
>>>
>>> Your bug report lacks any any information for further debugging your
>>> problem.
>>>
>>> - When does it occur?
>>> - What is failing?
>>> - Please send the output of "dmesg -s 1000000".
>>>
>>> And please read and follow REPORTING-BUGS in the kernel sources before
>>> sending your next bug report.
>>>
>>> cu
>>> Adrian
>>>
>>>
>>>
>> Thanks for your help. The device is a module that lets me plug in
>> various kinds og camera memory sticks.
>>
>> usb 1-7: new full speed USB device using ohci_hcd and address 2
>> usb 1-7: device descriptor read/64, error -110
>> usb 1-7: device descriptor read/64, error -110
>> usb 1-7: new full speed USB device using ohci_hcd and address 3
>> usb 1-7: device descriptor read/64, error -110
>>
>
> Please send the _complete_ output of "dmesg -s 1000000".
> If you want help, you should include as much information as possible.
>
> If you are concerned about the size of your email, please remember that
> linux-kernel has a 100 kB size limit - and everything smaller is
> perfectly OK.
>
> cu
> Adrian
>

OK - I was just trying to send what I thought was relevant. Here's all
of it.

Bootdata ok (command line is ro root=LABEL=/ vga=1 pci=nommconf)
Linux version 2.6.18-1.2798.fc6 (brewbuilder(a)hs20-bc1-6.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)) #1 SMP Mon Oct 16 14:39:22 EDT 2006
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 00000000cdef0000 (usable)
BIOS-e820: 00000000cdef0000 - 00000000cdef3000 (ACPI NVS)
BIOS-e820: 00000000cdef3000 - 00000000cdf00000 (ACPI data)
BIOS-e820: 00000000ce000000 - 00000000d0000000 (reserved)
BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
BIOS-e820: 0000000100000000 - 0000000130000000 (usable)
DMI 2.4 present.
ACPI: RSDP (v002 Nvidia ) @ 0x00000000000f7560
ACPI: XSDT (v001 Nvidia ASUSACPI 0x42302e31 AWRD 0x00000000) @ 0x00000000cdef30c0
ACPI: FADT (v003 Nvidia ASUSACPI 0x42302e31 AWRD 0x00000000) @ 0x00000000cdefb3c0
ACPI: HPET (v001 Nvidia ASUSACPI 0x42302e31 AWRD 0x00000098) @ 0x00000000cdefb5c0
ACPI: MCFG (v001 Nvidia ASUSACPI 0x42302e31 AWRD 0x00000000) @ 0x00000000cdefb640
ACPI: MADT (v001 Nvidia ASUSACPI 0x42302e31 AWRD 0x00000000) @ 0x00000000cdefb500
ACPI: DSDT (v001 NVIDIA ASUSACPI 0x00001000 MSFT 0x0100000e) @ 0x0000000000000000
Scanning NUMA topology in Northbridge 24
Number of nodes 1
Node 0 MemBase 0000000000000000 Limit 0000000130000000
NUMA: Using 63 for the hash shift.
Using node hash shift of 63
Bootmem setup node 0 0000000000000000-0000000130000000
On node 0 totalpages: 1019245
DMA zone: 2621 pages, LIFO batch:0
DMA32 zone: 823088 pages, LIFO batch:31
Normal zone: 193536 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x4008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:11 APIC version 16
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1 15:11 APIC version 16
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
ACPI: IRQ14 used by override.
ACPI: IRQ15 used by override.
Setting APIC routing to physical flat
ACPI: HPET id: 0x10de8201 base: 0xfefff000
Using ACPI (MADT) for SMP configuration information
Nosave address range: 000000000009f000 - 00000000000a0000
Nosave address range: 00000000000a0000 - 00000000000f0000
Nosave address range: 00000000000f0000 - 0000000000100000
Nosave address range: 00000000cdef0000 - 00000000cdef3000
Nosave address range: 00000000cdef3000 - 00000000cdf00000
Nosave address range: 00000000cdf00000 - 00000000ce000000
Nosave address range: 00000000ce000000 - 00000000d0000000
Nosave address range: 00000000d0000000 - 00000000e0000000
Nosave address range: 00000000e0000000 - 00000000f0000000
Nosave address range: 00000000f0000000 - 00000000fec00000
Nosave address range: 00000000fec00000 - 0000000100000000
Allocating PCI resources starting at d1000000 (gap: d0000000:10000000)
SMP: Allowing 2 CPUs, 0 hotplug CPUs
Built 1 zonelists. Total pages: 1019245
Kernel command line: ro root=LABEL=/ vga=1 pci=nommconf
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
time.c: Using 25.000000 MHz WALL HPET GTOD HPET timer.
time.c: Detected 2405.453 MHz processor.
Console: colour VGA+ 80x50
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Checking aperture...
CPU 0: aperture @ 9c20000000 size 32 MB
Aperture too small (32 MB)
No AGP bridge found
Your BIOS doesn't leave a aperture memory hole
Please enable the IOMMU option in the BIOS setup
This costs you 64 MB of RAM
Mapping aperture over 65536 KB of RAM @ 8000000
Memory: 4003372k/4980736k available (2409k kernel code, 156688k reserved, 1722k data, 204k init)
Calibrating delay using timer specific routine.. 4815.99 BogoMIPS (lpj=9631996)
Security Framework v1.0.0 initialized
SELinux: Initializing.
SELinux: Starting in permissive mode
selinux_register_security: Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/l
 | 
Pages: 1
Prev: Debugging I/O errors?
Next: mmaping a kernel buffer to user space