Hi, > If that's the cause, it's probably a double down of the host scan > semaphore somewhere in the code. alt-sysrq-t should work in this case, > can you get a stack trace of the blocked process? Good idea, I wonder why the IO isnt completing. Anton [c0000000004945fc] schedule+0x63c/0xf70 [c0000000004954c8] wait_for_completion+0xb8/0x140 [c0000000002a3800] blk_execute_rq+0xb0/0x120 [c000000000338a98] scsi_execute+0xf8/0x150 [c000000000338bc0] scsi_execute_req+0xd0/0x140 [c00000000033bce4] scsi_probe_and_add_lun+0x204/0x9f0 [c00000000033cfc4] __scsi_scan_target+0x164/0x4f0 [c00000000033d430] scsi_scan_channel+0xe0/0x120 [c00000000033d598] scsi_scan_host_selected+0x128/0x1d0 [c000000000361c20] ibmvscsi_probe+0x270/0x400 [c0000000000367fc] vio_bus_probe+0x7c/0x90 [c000000000299a78] driver_probe_device+0x98/0x160 [c000000000299ce8] __driver_attach+0xa8/0xd0 [c000000000298938] bus_for_each_dev+0x88/0xe0 [c000000000299738] driver_attach+0x28/0x40 [c000000000299074] bus_add_driver+0xc4/0x200 [c00000000029a1cc] driver_register+0x5c/0x80 [c0000000000365b0] vio_register_driver+0x50/0x70 [c000000000565bac] ibmvscsi_module_init+0x1c/0x40 - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
