mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Enrico Mioso <mrkiko.rs@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: intensive IO on usb-storage device causing system lock
Date: Wed, 11 Feb 2015 17:31:05 +0100 (CET)	[thread overview]
Message-ID: <alpine.LNX.2.03.1502111730450.4336@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1502111018180.1100-100000@iolanthe.rowland.org>

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 <stern@rowland.harvard.edu>
> To: Enrico Mioso <mrkiko.rs@gmail.com>
> 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
>
>
>

  reply	other threads:[~2015-02-11 16:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44L0.1502031300480.1130-100000@iolanthe.rowland.org>
2015-02-10 12:18 ` Enrico Mioso
2015-02-11 15:21   ` Alan Stern
2015-02-11 16:31     ` Enrico Mioso [this message]
2015-02-11 10:00 ` Enrico Mioso

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=alpine.LNX.2.03.1502111730450.4336@gmail.com \
    --to=mrkiko.rs@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome