From: Alan Stern <firstname.lastname@example.org> To: Steven Rostedt <email@example.com> Cc: LKML <firstname.lastname@example.org>, <email@example.com>, <firstname.lastname@example.org>, Jens Axboe <email@example.com>, Greg Kroah-Hartman <firstname.lastname@example.org> Subject: Re: Lockup on USB and block devices Date: Tue, 1 Oct 2019 14:31:46 -0400 (EDT) [thread overview] Message-ID: <Pine.LNX.4.44L0.email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Tue, 1 Oct 2019, Steven Rostedt wrote: > Not sure who to blame, but my server locked up when upgraded (accessing > volume group information), and echoing in "w" into sysrq-trigger showed > a bit of information. > > First, looking at my dmesg I see that my usb-storage is hung up, for > whatever reason. Thus, this could be the source of all issues. > > > [5434447.145737] INFO: task usb-storage:32246 blocked for more than 120 seconds. > [5434447.145740] Not tainted 5.2.4-custom #4 > > (BTW, I was upgrading to my 5.2.17 kernel when this happened) > > [5434447.145741] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > [5434447.145743] usb-storage D 0 32246 2 0x80004000 > [5434447.145745] Call Trace: > [5434447.145749] ? __schedule+0x1e8/0x600 > [5434447.145752] schedule+0x29/0x90 > [5434447.145755] schedule_timeout+0x208/0x300 > [5434447.145765] ? usb_hcd_submit_urb+0xbe/0xb90 [usbcore] > [5434447.145773] ? usb_alloc_urb+0x23/0x70 [usbcore] > [5434447.145782] ? usb_sg_init+0x92/0x2b0 [usbcore] > [5434447.145791] ? usb_hcd_submit_urb+0xbe/0xb90 [usbcore] > [5434447.145795] ? __switch_to_asm+0x34/0x70 > [5434447.145798] wait_for_completion+0x111/0x180 > [5434447.145800] ? wake_up_q+0x70/0x70 > [5434447.145809] usb_sg_wait+0xfa/0x150 [usbcore] > [5434447.145814] usb_stor_bulk_transfer_sglist.part.4+0x64/0xb0 [usb_storage] > [5434447.145818] usb_stor_bulk_srb+0x49/0x80 [usb_storage] > [5434447.145821] usb_stor_Bulk_transport+0x167/0x3e0 [usb_storage] > [5434447.145824] ? schedule+0x29/0x90 > [5434447.145828] ? usb_stor_disconnect+0xb0/0xb0 [usb_storage] > [5434447.145832] usb_stor_invoke_transport+0x3a/0x4e0 [usb_storage] > [5434447.145835] ? wait_for_completion_interruptible+0x12d/0x1d0 > [5434447.145837] ? wake_up_q+0x70/0x70 > [5434447.145841] usb_stor_control_thread+0x1c5/0x270 [usb_storage] > [5434447.145845] kthread+0x116/0x130 > [5434447.145847] ? kthread_create_worker_on_cpu+0x70/0x70 > [5434447.145851] ret_from_fork+0x35/0x40 It looks like a problem with your xHCI USB host controller. Normally a usb-storage transfer would be aborted after 90 seconds. But if the host controller (or its driver) isn't working right, and the abort never completes, you end up with a situation like this -- usb-storage and the higher SCSI and block layers waiting indefinitely for an event that won't occur. In theory, unplugging the USB mass-storage device would unblock everything (unless xhci-hcd is too badly wedged). But of course, doing that is likely to mess up whatever you were working on. Alan Stern
next prev parent reply other threads:[~2019-10-01 18:31 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-01 17:44 Steven Rostedt 2019-10-01 18:31 ` Alan Stern [this message] 2019-10-14 11:59 ` Oliver Neukum 2019-10-14 15:13 ` Alan Stern 2019-10-14 10:56 ` Oliver Neukum
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=Pine.LNX.4.44L0.email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Lockup on USB and block devices' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).