From: Jan Kara <jack@suse.cz>
To: Marcus Sundman <marcus@hibox.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Debugging system freezes on filesystem writes
Date: Thu, 1 Nov 2012 20:01:19 +0100 [thread overview]
Message-ID: <20121101190119.GA27294@quack.suse.cz> (raw)
In-Reply-To: <508DB432.2030208@hibox.fi>
On Mon 29-10-12 00:39:46, Marcus Sundman wrote:
Hello,
> I have a big problem with the system freezing and would appreciate
> any help on debugging this and pinpointing where exactly the problem
> is, so it could be fixed.
>
> So, whenever I write to the disk the system comes to a crawl or
> freezes altogether. This happens even when the writing processes are
> running on nice '19' and ionice 'idle'. (E.g. a 10 second compile
> could freeze the system for several minutes, rendering the computer
> pretty much unusable for anything interesting.)
>
> Here you can see a 20 second gap even in superhigh priority:
> # nice -n -20 ionice -c1 iostat -t -m -d -x 1 > http://pastebin.com/j5qnh2VV
>
> I'm currently running 3.5.0-17-lowlatency on the ZenBook UX31E,
> using the NOOP I/O scheduler on the SanDisk SSD U100. The chipset
> seems to be Intel QS67. I've had this same problem on 3.2.0 generic
> and lowlatency kernels.
These are Ubuntu kernels. Any chance to reproduce the issue with vanilla
kernels - i.e. kernels without any Ubuntu patches? Also when you speak of
system freezing - can you e.g. type to terminal while the system is frozen?
Or is it just that running commands freezes? And how much free memory do
you have while the system is frozen? Finally, can you trigger the freeze by
something simpler than compilation - e.g. does
dd if=/dev/zero of=/tmp bs=1M
trigger the freeze as well?
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2012-11-01 19:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 22:39 Debugging system freezes on filesystem writes Marcus Sundman
2012-11-01 19:01 ` Jan Kara [this message]
2012-11-02 2:19 ` Marcus Sundman
2012-11-07 16:17 ` Jan Kara
2012-11-08 23:41 ` Marcus Sundman
2012-11-09 13:12 ` Marcus Sundman
2012-11-13 13:51 ` Jan Kara
2012-11-16 1:11 ` Marcus Sundman
2012-11-21 23:30 ` Jan Kara
2012-11-27 16:14 ` Marcus Sundman
2012-12-05 15:32 ` Jan Kara
2013-02-20 8:42 ` Marcus Sundman
2013-02-20 11:40 ` Marcus Sundman
2013-02-22 20:51 ` Jan Kara
2013-02-22 23:27 ` Marcus Sundman
2013-02-24 0:12 ` Dave Chinner
2013-02-24 1:20 ` Theodore Ts'o
2013-02-26 18:41 ` Marcus Sundman
2013-02-26 22:17 ` Theodore Ts'o
2013-02-26 23:17 ` Jan Kara
2013-09-12 12:57 ` Marcus Sundman
2013-09-12 13:10 ` Jan Kara
2013-09-12 13:47 ` Marcus Sundman
2013-09-12 14:39 ` Jan Kara
2013-09-12 15:08 ` Marcus Sundman
2013-09-12 16:35 ` Jan Kara
2013-09-12 17:59 ` Marcus Sundman
2013-09-12 20:46 ` Jan Kara
2013-09-13 6:35 ` Marcus Sundman
2013-09-13 20:54 ` Jan Kara
2013-09-14 2:41 ` Theodore Ts'o
2013-09-15 19:19 ` Marcus Sundman
2013-09-16 0:06 ` Theodore Ts'o
2013-02-25 13:05 ` Jan Kara
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=20121101190119.GA27294@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus@hibox.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.