Messages in this thread | | | Date | Fri, 23 Sep 2005 23:16:42 +1000 (EST) | From | Srihari Vijayaraghavan <> | Subject | [PROBLEM] USB Storage & D state processes |
| |
Hardware: Athlon 64 VIA K8T 800
Software: FC4 2.6.14-rc2 (vanilla)
Few usb-storage process are stuck in D state: usb-storage D 000000000000000a 0 8176 1 8250 3455 (L-TLB) ffff8100121bfe08 0000000000000046 000000000000026b ffff81002ec8d870 ffff81002a47c750 ffffffff802f2750 ffff8100121bfe38 0000000000000046 00000000000000c1 ffffffff803e6110 Call Trace:<ffffffff802f2750>{thread_return+0} <ffffffff802f2bba>{wait_for_completion+154} <ffffffff8012ecd0>{default_wake_function+0} <ffffffff80145dd0>{kthread_stop+128} <ffffffff88001635>{:scsi_mod:scsi_host_dev_release+69} <ffffffff801dd8a1>{kobject_cleanup+97} <ffffffff801dd900>{kobject_release+0} <ffffffff801de0f0>{kref_put+96} <ffffffff882401a4>{:usb_storage:usb_stor_control_thread+500} <ffffffff8010f3b6>{child_rip+8} <ffffffff8823ffb0>{:usb_storage:usb_stor_control_thread+0} <ffffffff8010f3ae>{child_rip+0}
usb-storage D 000000000000000a 0 9569 1 16314 8250 (L-TLB) ffff81000fdcfda8 0000000000000046 0000000000000233 ffff81000b5315f0 ffff810037b14910 ffffffff8823ec40 ffffffff8012ecd0 0000000000100100 0000000000200200 ffffffff803544b0 Call Trace:<ffffffff8823ec40>{:usb_storage:usb_stor_msg_common+336} <ffffffff8012ecd0>{default_wake_function+0} <ffffffff802f355e>{__down+222} <ffffffff8012ecd0>{default_wake_function+0} <ffffffff802f31f3>{__down_failed+53} <ffffffff880015f0>{:scsi_mod:scsi_host_dev_release+0} <ffffffff801460d1>{.text.lock.kthread+5} <ffffffff88001635>{:scsi_mod:scsi_host_dev_release+69} <ffffffff801dd8a1>{kobject_cleanup+97} <ffffffff801dd900>{kobject_release+0} <ffffffff801de0f0>{kref_put+96} <ffffffff882401a4>{:usb_storage:usb_stor_control_thread+500} <ffffffff8010f3b6>{child_rip+8} <ffffffff8823ffb0>{:usb_storage:usb_stor_control_thread+0} <ffffffff8010f3ae>{child_rip+0} usb-storage D 000000000000000a 0 16314 1 9569 (L-TLB) ffff81000d32dda8 0000000000000046 000000000000027e ffff81000b530850 ffff81002a47d4f0 ffffffff8823ec40 0000000000000000 ffff81000d32c000 ffff81000b530f20 ffffffff803544b0 Call Trace:<ffffffff8823ec40>{:usb_storage:usb_stor_msg_common+336} <ffffffff802f355e>{__down+222} <ffffffff8012ecd0>{default_wake_function+0} <ffffffff802f31f3>{__down_failed+53} <ffffffff880015f0>{:scsi_mod:scsi_host_dev_release+0} <ffffffff801460d1>{.text.lock.kthread+5} <ffffffff88001635>{:scsi_mod:scsi_host_dev_release+69} <ffffffff801dd8a1>{kobject_cleanup+97} <ffffffff801dd900>{kobject_release+0} <ffffffff801de0f0>{kref_put+96} <ffffffff882401a4>{:usb_storage:usb_stor_control_thread+500} <ffffffff8010f3b6>{child_rip+8} <ffffffff8823ffb0>{:usb_storage:usb_stor_control_thread+0} <ffffffff8010f3ae>{child_rip+0}
Yum is in the middle of updating the system, & I think it's stuck due to these problems. If possible I'd love to avoid any reboots/restarts etc., so that yum may complete its job :-(.
I have nothing mounted through usb storage ATM, though I must have had something earlier today.
Thanks Hari
Send instant messages to your online friends http://au.messenger.yahoo.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |