> > [ 9840.533372] Call Trace: > > [ 9840.533391] [<ffffffff80665559>] schedule+0x9/0x20 > > [ 9840.533399] [<ffffffff806655a7>] io_schedule+0x37/0x50 > > [ 9840.533409] [<ffffffff8031776d>] sync_buffer+0x3d/0x50 > > [ 9840.533416] [<ffffffff80665c5a>] __wait_on_bit+0x5a/0x90 > > [ 9840.533424] [<ffffffff80317730>] ? sync_buffer+0x0/0x50 > > [ 9840.533431] [<ffffffff80317730>] ? sync_buffer+0x0/0x50 > > [ 9840.533438] [<ffffffff80665d04>] out_of_line_wait_on_bit+0x74/0x90 > > [ 9840.533448] [<ffffffff80269640>] ? wake_bit_function+0x0/0x40 > > [ 9840.533456] [<ffffffff80317726>] __wait_on_buffer+0x26/0x30 > > [ 9840.533464] [<ffffffff803185ad>] bh_submit_read+0x4d/0x80 > > [ 9840.533483] [<ffffffffa040373b>] read_block_bitmap+0x9b/0x170 [ext2] > > [ 9840.533497] [<ffffffffa0404521>] ext2_new_blocks+0x201/0x700 [ext2] The trace doesn't tell a lot. This may be block, scsi or usb. Please recompile with CONFIG_USB_STORAGE_DEBUG. Regards Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
