Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753640AbbBKQbM (ORCPT ); Wed, 11 Feb 2015 11:31:12 -0500 Received: from mail-wg0-f53.google.com ([74.125.82.53]:44563 "EHLO mail-wg0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752896AbbBKQbK (ORCPT ); Wed, 11 Feb 2015 11:31:10 -0500 From: Enrico Mioso X-Google-Original-From: Enrico Mioso Date: Wed, 11 Feb 2015 17:31:05 +0100 (CET) X-X-Sender: mrkiko@localhost.localdomain To: Alan Stern cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: intensive IO on usb-storage device causing system lock In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1799 Lines: 47 Thank you. If I'll be able I'll try. Thank you again guys. Enrico On Wed, 11 Feb 2015, Alan Stern wrote: > Date: Wed, 11 Feb 2015 16:21:50 > From: Alan Stern > To: Enrico Mioso > Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org > Subject: Re: intensive IO on usb-storage device causing system lock > > On Tue, 10 Feb 2015, Enrico Mioso wrote: > >> Hello guys. >> the problem is still reproducible with final 3.19 kernel - I can confirm it. >> Re-sending the last trace here - don't know if it's available in cxg.de. > > Please stop posting these process traces. They don't help. > > Instead, post a usbmon trace showing what happens around the time when > the problem occurs. If the trace file is quite large (which is likely, > because usbmon can generate a lot of data in a short time), you can > cut out everything up to the last few hundreds of KB before the problem > starts. > >> For those who might not have read the thread - the problem is: after some >> intensive IO to an USB (usb-storage) disk, for a more or less long time, >> depending on the quantity of IO you do, there start to be situations where some >> processes get stuck doing IO, in any case. Not IO to the USB disk, but IO also >> to other devices, like the one where the root partition resides, in my case a >> flash drive. I am using an EEE PC 701. > > That sounds like the problem may lie somewhere other than in the USB > stack. But there's no way to tell without seeing a usbmon trace. > > Alan Stern > > > -- 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/