LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pascal Terjan <pterjan@mandriva.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.24 regression: pan hanging unkilleable and un-straceable
Date: Sat, 26 Jan 2008 14:27:04 +0000 (UTC) [thread overview]
Message-ID: <loom.20080126T142451-347@post.gmane.org> (raw)
In-Reply-To: <200801270046.26648.nickpiggin@yahoo.com.au>
Nick Piggin <nickpiggin <at> yahoo.com.au> writes:
> On Sunday 27 January 2008 00:29, Frederik Himpe wrote:
> > I just succeeded to reproduce the problem with this patch. Does this
> > smell like an XFS problem?
I got the same issue using ext3
> Possible. Though I think it is more likely to be a bug in the
> new deadlock avoidance code in the generic buffered write path.
> Dang... I wonder why this hasn't come up earlier. It looks like
> pan's use of writev might be tickling it.
>
> How quickly can you reproduce this?
When I was using pan daily one month ago, I got it twice over a week
> Can you use strace to see what the hanging syscall looks like?
I tried last week during 5 hours without luck, I can try again
next prev parent reply other threads:[~2008-01-26 14:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 20:58 Frederik Himpe
2008-01-22 0:05 ` Nick Piggin
2008-01-22 5:03 ` Mike Galbraith
2008-01-22 5:25 ` Nick Piggin
2008-01-22 5:47 ` Mike Galbraith
2008-02-04 14:49 ` Mike Galbraith
2008-02-04 23:02 ` Nick Piggin
2008-01-22 10:38 ` Ingo Molnar
2008-01-24 5:30 ` Valdis.Kletnieks
2008-01-26 13:29 ` Frederik Himpe
2008-01-26 13:46 ` Nick Piggin
2008-01-26 14:27 ` Pascal Terjan [this message]
2008-01-28 1:49 ` Nick Piggin
2008-01-28 1:46 ` Nick Piggin
2008-01-28 18:05 ` Frederik Himpe
2008-01-31 22:45 ` Frederik Himpe
2008-02-02 0:53 ` Nick Piggin
2008-01-22 10:37 ` Ingo Molnar
2008-01-22 23:00 ` Nick Piggin
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=loom.20080126T142451-347@post.gmane.org \
--to=pterjan@mandriva.com \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: 2.6.24 regression: pan hanging unkilleable and un-straceable' \
/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
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).