From: Mike Galbraith <efault@gmx.de>
To: Norbert Preining <preining@logic.at>
Cc: Ulrich Lukas <stellplatz-nr.13a@datenparkplatz.de>,
linux-kernel@vger.kernel.org
Subject: Re: complete IO hang since a few kernel revision
Date: Tue, 06 Oct 2009 09:44:20 +0200 [thread overview]
Message-ID: <1254815060.8758.14.camel@marge.simson.net> (raw)
In-Reply-To: <20091006071609.GB21772@gandalf.dynalias.org>
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.
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
next prev parent reply other threads:[~2009-10-06 7:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 1:16 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 [this message]
2009-10-10 19:06 ` Petr Titěra
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=1254815060.8758.14.camel@marge.simson.net \
--to=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
Powered by JetHome