From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754803Ab3AMMJd (ORCPT ); Sun, 13 Jan 2013 07:09:33 -0500 Received: from mail-da0-f41.google.com ([209.85.210.41]:48387 "EHLO mail-da0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754637Ab3AMMJc (ORCPT ); Sun, 13 Jan 2013 07:09:32 -0500 MIME-Version: 1.0 In-Reply-To: References: From: Alex Riesen Date: Sun, 13 Jan 2013 13:09:11 +0100 Message-ID: Subject: Re: USB device cannot be reconnected and khubd "blocked for more than 120 seconds" To: Alan Stern , Jens Axboe Cc: linux-usb@vger.kernel.org, Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jan 12, 2013 at 11:52 PM, Alan Stern wrote: > On Sat, 12 Jan 2013, Alex Riesen wrote: >> Now, who would be interested to handle this kind of misconfiguration ... > > So the whole thing was a false alarm? Yes, almost. What about khubd hanging when machine is shutdown? > Maybe you should report to the block-layer maintainers that it's > possible to mess up the system by building an elevator as a module. > That sounds like the sort of thing they'd be interested to hear. Hi Jens, may I point you at this problem report: http://thread.gmane.org/gmane.linux.kernel/1420814 It is surely a misconfiguration on my part (the used io scheduler configured as a module), but the behavior is somewhat problematic anyway: at least in this case USB storage is essentially locked up. Regards, Alex