From: "Petr Titěra" <P.Titera@century.cz>
To: Mike Galbraith <efault@gmx.de>
Cc: Norbert Preining <preining@logic.at>,
Ulrich Lukas <stellplatz-nr.13a@datenparkplatz.de>,
linux-kernel@vger.kernel.org
Subject: Re: complete IO hang since a few kernel revision
Date: Sat, 10 Oct 2009 21:06:58 +0200 [thread overview]
Message-ID: <4AD0DB52.20800@century.cz> (raw)
In-Reply-To: <1254815060.8758.14.camel@marge.simson.net>
Mike Galbraith napsal(a):
> On Tue, 2009-10-06 at 16:16 +0900, Norbert Preining wrote:
>
>> On Tue, 06 Oct 2009, Mike Galbraith wrote:
>>
>>> I've tried unsuccessfully to reproduce this behavior.
>>>
>>> Since it doesn't appear to be something readily reproducible, more
>>> information and/or some digging on your part may be needed.
>>>
>> Hm, how could I do that? I am fine with compiling some strange
>> kernel options, or running some debugging task, but I don't have
>> and netconsole or serial console available.
>>
>
> Locating when it started for you would be valuable, even if it's not
> pin-pointed such as a git bisection could do. A bisection is the best
> bet to nail it down, but can be quite time consuming.
>
>
I see something similar here. Processes just get stuck in
balance_dirty_pages for infinite time. It helps if, when process is
stuck another process generates some dirty pages. Unfotunately last
kernel I'm prety sure everything worked is 2.6.31-rc9-tip-01355-ge035e96
(yes its x86 -tip kernel). I'm building new kernel now.
Petr
> One thing you can try is to drop to a non-gui shell, and see it the
> symptom is reproducible without the GUI. If it is, poke SysRq-W while
> things are thoroughly jammed up, and post the output+config here.
>
> -Mike
>
> --
> 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/
>
>
> __________ Informace od ESET Smart Security, verze databaze 4496 (20091010) __________
>
> Tuto zpravu proveril ESET Smart Security.
>
> http://www.eset.cz
>
>
>
__________ Informace od ESET Smart Security, verze databaze 4496 (20091010) __________
Tuto zpravu proveril ESET Smart Security.
http://www.eset.cz
next prev parent reply other threads:[~2009-10-10 19:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 1:16 complete IO hang since a few kernel revision Norbert Preining
2009-10-05 2:57 ` Ulrich Lukas
2009-10-05 8:33 ` Norbert Preining
2009-10-06 2:00 ` Robert Hancock
2009-10-06 2:05 ` Norbert Preining
2009-10-06 7:11 ` Mike Galbraith
2009-10-06 7:16 ` Norbert Preining
2009-10-06 7:44 ` Mike Galbraith
2009-10-10 19:06 ` Petr Titěra [this message]
2009-11-18 7:56 ` Linux 2.6.31 - very swap-happy with plenty of free RAM Dan Merillat
2009-11-18 15:22 ` Rik van Riel
2009-11-18 15:48 ` Norbert Preining
2009-11-19 14:36 ` KOSAKI Motohiro
2009-11-25 23:13 ` Dan Merillat
2009-11-26 1:54 ` Rik van Riel
2009-12-03 4:16 ` Dan Merillat
2009-12-07 20:49 ` Dan Merillat
2009-12-09 20:48 ` Henrique de Moraes Holschuh
2009-12-09 21:18 ` Rik van Riel
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=4AD0DB52.20800@century.cz \
--to=p.titera@century.cz \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=preining@logic.at \
--cc=stellplatz-nr.13a@datenparkplatz.de \
/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).