Hello everyone, I am new to this and english is not my native language, so I hope you can forgive if I make mistakes. I am using Ubuntu 12.04 LTS with the latest updates. Kernel version is 3.2.0-38-generic. When I attach my new USB 2.0 enclosure with a built in 3TB Seagte HDD, it simply cant be accessed. There is a new block device /dev/sdb, but any try to access it, for example with fdisk or mount, will cause the process to hang. If I boot up with the enclosure attached, the boot process will even stop or hang until I detach it. I have found these patches https://patchwork.kernel.org/patch/1192871/ https://patchwork.kernel.org/patch/1144701/ and see, that there might be a problem with USB enclosures (which have an internal adapter to sata) and big HDDs. Although those patches try to solve the problem, in my case it persists, even when using a latest 3.2-kernel. Now I give you some additional detail information, what happens when the drive is attached: dmesg: "[ 8077.484051] usb 1-6: new high-speed USB device number 7 using ehci_hcd [ 8077.621998] scsi3 : usb-storage 1-6:1.0 [ 8078.642103] scsi 3:0:0:0: Direct-Access ST3000DM 001-1CH166 PQ: 0 ANSI: 5 [ 8078.646865] sd 3:0:0:0: Attached scsi generic sg1 type 0 [ 8078.647315] sd 3:0:0:0: [sdb] Very big device. Trying to use READCAPACITY(16). [ 8078.647689] sd 3:0:0:0: [sdb] 5860532995 512-byte logical blocks: (3.00TB/2.72 TiB) [ 8078.648561] sd 3:0:0:0: [sdb] Write Protect is off [ 8078.648567] sd 3:0:0:0: [sdb] Mode Sense: 28 00 00 00 [ 8078.649310] sd 3:0:0:0: [sdb] No Caching mode page present [ 8078.649315] sd 3:0:0:0: [sdb] Assuming drive cache: write through [ 8078.650059] sd 3:0:0:0: [sdb] Very big device. Trying to use READCAPACITY(16). [ 8078.651933] sd 3:0:0:0: [sdb] No Caching mode page present [ 8078.651937] sd 3:0:0:0: [sdb] Assuming drive cache: write through" lsusb: "Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 046d:c30a Logitech, Inc. iTouch Composite Bus 003 Device 002: ID 045e:0047 Microsoft Corp. IntelliMouse Explorer 3.0 Bus 001 Device 007: ID 152d:2509 JMicron Technology Corp. / JMicron USATechnology Corp. JMS539 SuperSpeed SATA II 3.0G Bridge" When then trying to access the device, for example with sudo fdisk -l /dev/sdb nothing, happens and I need to kill the process. Afterwards I get with dmesg: "[ 8280.424033] INFO: task kworker/u:0:5 blocked for more than 120 seconds. [ 8280.424039] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables thismessage. [ 8280.424043] kworker/u:0 D df489c68 0 5 2 0x00000000 [ 8280.424050] df489c88 00000046 dbf9ac00 df489c68 c1284fbf c17cc020 c18e63c0c18e63c0 [ 8280.424058] f52db01d 00000758 dfbe53c0 df47b2c0 c897b2c0 dbf9ac00 df489c60c1162510 [ 8280.424065] 00000000 00000010 00000001 0000000f c181eb80 df489c88 c107457b26ddba6b [ 8280.424073] Call Trace: [ 8280.424086] [<c1284fbf>] ? submit_bio+0x6f/0x100 [ 8280.424097] [<c1162510>] ? bio_alloc_bioset+0x40/0xc0 [ 8280.424105] [<c107457b>] ? ktime_get_ts+0xeb/0x120 [ 8280.424116] [<c1574805>] schedule+0x35/0x50 [ 8280.424120] [<c1574898>] io_schedule+0x78/0xb0 [ 8280.424128] [<c10e68ad>] sleep_on_page+0xd/0x20 [ 8280.424133] [<c1574e47>] __wait_on_bit_lock+0x47/0x90 [ 8280.424137] [<c10e68a0>] ? __lock_page+0x80/0x80 [ 8280.424142] [<c10e6898>] __lock_page+0x78/0x80 [ 8280.424148] [<c106a1d0>] ? autoremove_wake_function+0x50/0x50 [ 8280.424153] [<c10e76a7>] do_read_cache_page+0x137/0x160 [ 8280.424158] [<c1163560>] ? blkdev_write_begin+0x40/0x40 [ 8280.424163] [<c10e7724>] read_cache_page_async+0x24/0x30 [ 8280.424167] [<c10e7747>] read_cache_page+0x17/0x30 [ 8280.424171] [<c1163560>] ? blkdev_write_begin+0x40/0x40 [ 8280.424177] [<c118c8b6>] read_dev_sector+0x36/0x90 [ 8280.424181] [<c118d940>] ? invalidate_partitions+0xa0/0xa0 [ 8280.424185] [<c118d99b>] adfspart_check_ICS+0x5b/0x270 [ 8280.424193] [<c12a43c8>] ? vsnprintf+0x2c8/0x390 [ 8280.424197] [<c12a44ea>] ? snprintf+0x1a/0x20 [ 8280.424201] [<c118d940>] ? invalidate_partitions+0xa0/0xa0 [ 8280.424206] [<c118cf81>] check_partition+0xe1/0x1e0 [ 8280.424210] [<c118d61a>] rescan_partitions+0x9a/0x320 [ 8280.424218] [<c136ffa4>] ? __pm_runtime_resume+0x54/0x80 [ 8280.424224] [<c1397633>] ? scsi_autopm_get_device+0x23/0x60 [ 8280.424229] [<c15761dd>] ? _raw_spin_lock+0xd/0x10 [ 8280.424233] [<c1164777>] __blkdev_get+0x327/0x400 [ 8280.424237] [<c1164897>] blkdev_get+0x47/0x180 [ 8280.424246] [<c13631b4>] ? put_device+0x14/0x20 [ 8280.424254] [<c128d171>] register_disk+0x131/0x150 [ 8280.424258] [<c128c352>] ? blk_register_region+0x32/0x40 [ 8280.424263] [<c128ba70>] ? disk_map_sector_rcu+0xc0/0xc0 [ 8280.424267] [<c128d237>] add_disk+0xa7/0x210 [ 8280.424272] [<c128ba70>] ? disk_map_sector_rcu+0xc0/0xc0 [ 8280.424276] [<c128c180>] ? get_disk+0xa0/0xa0 [ 8280.424282] [<c139c51f>] sd_probe_async+0xff/0x1b0 [ 8280.424288] [<c1027418>] ? default_spin_lock_flags+0x8/0x10 [ 8280.424293] [<c1071319>] async_run_entry_fn+0x69/0x170 [ 8280.424300] [<c1064f0a>] ? destroy_worker+0x6a/0xa0 [ 8280.424305] [<c1065041>] process_one_work+0x101/0x3a0 [ 8280.424309] [<c1065815>] ? maybe_create_worker+0x15/0xe0 [ 8280.424314] [<c1064f1e>] ? destroy_worker+0x7e/0xa0 [ 8280.424318] [<c10712b0>] ? async_schedule+0x20/0x20 [ 8280.424323] [<c1065b14>] worker_thread+0x124/0x2d0 [ 8280.424327] [<c10659f0>] ? manage_workers.isra.29+0x110/0x110 [ 8280.424331] [<c106996d>] kthread+0x6d/0x80 [ 8280.424335] [<c1069900>] ? flush_kthread_worker+0x80/0x80 [ 8280.424341] [<c157dafe>] kernel_thread_helper+0x6/0x10" This seems like a kernel related problem to me, I hope I am adressing the right people with this. The device is working properly when using another operating system which is not based on Linux, you know which one I mean. ;) This is all I have to say for now. I hope you can find what is going wrong there. If you need additional information, ask and I will give it to you. Again, if I made mistakes by posting this report or forgot something, please be lenient toward me. Michael PS: I will add a usbmon log later, like Mr. Stern wanted me to. -- 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
