From: Andrew Morton <akpm@linux-foundation.org>
To: avillaci@ceibo.fiec.espol.edu.ec
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, linux-mm@kvack.org
Subject: Re: [Bugme-new] [Bug 31142] New: Large write to USB stick freezes unrelated tasks for a long time
Date: Tue, 15 Mar 2011 13:53:34 -0700 [thread overview]
Message-ID: <20110315135334.36e29414.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-31142-10286@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Tue, 15 Mar 2011 15:55:52 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=31142
>
> Summary: Large write to USB stick freezes unrelated tasks for a
> long time
> Product: IO/Storage
> Version: 2.5
> Kernel Version: 2.6.38-rc8
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Block Layer
> AssignedTo: axboe@kernel.dk
> ReportedBy: avillaci@ceibo.fiec.espol.edu.ec
> Regression: No
>
>
> Created an attachment (id=50902)
> --> (https://bugzilla.kernel.org/attachment.cgi?id=50902)
> kernel backtraces from hung Eclipse task while writing to usb stick
>
> System is Fedora 14 x86_64 with 4 GB RAM, running vanilla kernel 2.6.38-rc8.
>
> I have a USB 2.0 high-speed memory stick with around 7.5 GB of space. Whenenver
> I write a large amount of data (several GBs of files) through any means (cp,
> nautilus GUI, etc), I notice some large applications that I consider unrelated
> to the I/O operation (Firefox web browser, Thunderbird email viewer, Eclipse
> IDE) may randomly freeze whenever I try to interact with them. I use Compiz,
> and I notice the apps getting grayed out, but I have also seen the freeze
> happening with Metacity and Gnome-shell, so I believe the window manager is
> irrelevant. Sometimes other smaller tasks (gnome-terminal, gedit) also freeze.
> For Eclipse, the hang also cause a series of kernel backtraces, attached to
> this report. The hang usually lasts for several tens of seconds, and may freeze
> and unfreeze several times while the file copying to USB takes place. All of
> the hung applications unfreeze themselves after write activity (as seen from
> the LED in the memory stick) ceases.
>
> Reproducibility: always (with sufficiently large bulk write)
> To reproduce:
> 1) have an usb stick with several GB of free space, with any filesystem (tried
> vfat and udf)
> 2) prepare several gb of files to copy from hard disk to usb stick
> 3) start large application (firefox, eclipse, or thunderbird)
> 4) check that application is responsive before file copy starts
> 5) insert usb stick and (auto)mount it. Previously started app is still
> responsive.
> 6) start file copy to usb stick with any command
> 7) attempt to interact with chosen application during the entirety of the file
> write
> Expected result: I/O to usb stick takes place in background, unrelated apps
> continue to be responsive in foreground.
> Actual result: some large tasks freeze for tens of seconds while write takes
> place.
>
> Feel free to reassign this bug to a different category. It involves I/O, block,
> USB, and mmap.
rofl, will we ever fix this.
Please enable sysrq and do a sysrq-w when the tasks are blocked so we
can find where things are getting stuck. Please avoid email client
wordwrapping when sending us the sysrq output.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2011-03-15 20:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-31142-10286@https.bugzilla.kernel.org/>
2011-03-15 20:53 ` Andrew Morton [this message]
2011-03-15 22:53 ` [Bugme-new] [Bug 31142] New: Large write to USB stick freezes unrelated tasks for a long time Alex Villacís Lasso
2011-03-15 23:19 ` Andrew Morton
2011-03-16 15:25 ` Alex Villacís Lasso
2011-03-16 22:02 ` Andrew Morton
2011-03-17 21:27 ` Alex Villacís Lasso
2011-03-17 21:47 ` Andrew Morton
2011-03-17 22:11 ` Alex Villacís Lasso
2011-03-17 22:25 ` Andrew Morton
2011-03-18 11:13 ` Mel Gorman
2011-03-18 12:26 ` Andrea Arcangeli
2011-03-18 18:05 ` Alex Villacís Lasso
2011-03-19 13:46 ` Mel Gorman
2011-03-19 16:04 ` Alex Villacís Lasso
2011-03-19 23:51 ` Andrea Arcangeli
2011-03-21 9:41 ` Mel Gorman
2011-03-21 13:48 ` Andrea Arcangeli
2011-03-21 15:22 ` Alex Villacís Lasso
2011-03-21 15:36 ` Alex Villacís Lasso
2011-03-21 15:40 ` Andrea Arcangeli
2011-03-21 16:37 ` Mel Gorman
2011-03-21 17:05 ` Alex Villacís Lasso
2011-03-21 20:16 ` Andrea Arcangeli
2011-03-21 23:35 ` Alex Villacís Lasso
2011-03-22 11:20 ` Mel Gorman
2011-03-22 15:03 ` Andrea Arcangeli
2011-03-22 20:34 ` Alex Villacís Lasso
2011-03-22 21:40 ` Andrea Arcangeli
2011-03-23 0:37 ` Andrea Arcangeli
2011-03-23 16:51 ` Alex Villacís Lasso
2011-04-04 15:37 ` Alex Villacís Lasso
2011-04-08 19:09 ` Andrea Arcangeli
2011-04-08 20:06 ` Alex Villacís Lasso
2011-04-12 16:27 ` Alex Villacís Lasso
2011-04-14 17:25 ` Alex Villacís Lasso
2011-04-14 17:37 ` Andrea Arcangeli
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=20110315135334.36e29414.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=avillaci@ceibo.fiec.espol.edu.ec \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-mm@kvack.org \
/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;
as well as URLs for NNTP newsgroup(s).