Re: USB Mass Storage - Kernel Bug?
Hi,
I don't know if I had the same problem as you have: problems with
copying large files on an external HD but I can't remember what dmesg
said.
The error always showed up as something like "control timeout on ep0in"
in /var/log/messages.
The solution was to disable the palm pilot daemon, that I kept running,
while having the usb-harddrive connected and getting or sending data to
it. Strange that the two were related. But disabling it solved the
issue.
pascal
On Tue, 2004-09-14 at 16:36, Damien Solley wrote:
> Greetings,
>
> I am having trouble using an external USB 2.0 to IDE converter box with
> recent 2.6 kernels. The box houses a 200GB IDE drive. When I try to
> perform large transfers (eg 500MB files) to the box it aborts after a
> variable proportion of the file/s have been transferred.
>
> The dmesg output calls it a kernel bug... Google is unhelpful, does
> anybody know what this is or where I could go for further assistance.
> Kernel versions that seem affected are 2.6.7 to 2.6.9-rc2.
>
> Note that the drive works under Windows 2k/XP and previously worked
> under 2.6 kernels (about 2.6.5 IIRC). Dmesg output is attached, with the
> most relevant section below.
>
> Warm regards,
>
> Damien
>
>
> ------------[ cut here ]------------
> kernel BUG at drivers/block/as-iosched.c:1853!
> invalid operand: 0000 [#1]
> Modules linked in: visor usbserial yenta_socket ds pcmcia_core
> usb_storage
> CPU: 0
> EIP: 0060:[<c021d777>] Not tainted VLI
> EFLAGS: 00010293 (2.6.9-rc2damo)
> EIP is at as_exit+0x65/0x79
> eax: df79968c ebx: df799680 ecx: d1e42aa0 edx: d030be74
> esi: c15ac0b4 edi: 00000292 ebp: c151ceb4 esp: d030beb0
> ds: 007b es: 007b ss: 0068
> Process scsi_eh_0 (pid: 2082, threadinfo=d030a000 task=d1e42aa0)
> Stack: df799708 c15ac028 c0214b10 c15ac028 c15ac034 c02169e2 c15ac028
> 00000001
> dea71824 dea71800 c0245fac c15ac028 dea719a8 c03d7248 c03d7260
> c151ced8
> c0210b94 dea71984 00cec98a 00cec98a ffffffff c019ca63 dea719a8
> dea719c0
> Call Trace:
> [<c0214b10>] elevator_exit+0x1e/0x20
> [<c02169e2>] blk_cleanup_queue+0x36/0x81
> [<c0245fac>] scsi_device_dev_release+0xd9/0xeb
> [<c0210b94>] device_release+0x58/0x5c
> [<c019ca63>] kobject_cleanup+0x98/0x9a
> [<c019ca65>] kobject_release+0x0/0xa
> [<c019cdae>] kref_put+0x39/0x93
> [<c0119d2e>] vprintk+0xfe/0x12f
> [<c019ca8d>] kobject_put+0x1e/0x22
> [<c019ca65>] kobject_release+0x0/0xa
> [<c023fd87>] __scsi_iterate_devices+0x4f/0x59
> [<c024219b>] scsi_eh_stu+0x92/0xf4
> [<c02428a6>] scsi_eh_ready_devs+0x2b/0x93
> [<c0242a4e>] scsi_unjam_host+0xb7/0xb9
> [<c0242aee>] scsi_error_handler+0x9e/0xc6
> [<c0242a50>] scsi_error_handler+0x0/0xc6
> [<c010225d>] kernel_thread_helper+0x5/0xb
> Code: f1 ff 8b 83 d8 00 00 00 89 04 24 e8 67 b0 ff ff 8b 43 38 89 04 24
> e8 69 cb f1 ff 89 5c 24 0c 8b 5c 24 04 83 c4 08 e9 59 cb f1 ff <0f> 0b
> 3d 07 fd f1 34 c0 eb c2 0f 0b 3c 07 fd f1 34 c0 eb b0 55
>
>
>
>
Reply to: