From: Christoph Hellwig <hch@infradead.org>
To: Luk?? Czerner <lczerner@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: softlockup in xfstests 083
Date: Sat, 8 Dec 2012 07:45:42 -0500 [thread overview]
Message-ID: <20121208124542.GA14814@infradead.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1211261423090.24277@dhcp-1-104.brq.redhat.com>
On Mon, Nov 26, 2012 at 02:30:32PM +0100, Luk?? Czerner wrote:
> I am unable to reproduce the problem even after 70 iteration of 083
> on 3.7.0-rc7. It is not immediately obvious what would block you in
> ext4_ext_remove_space() other reading the extent tree from the disk,
> but it should not take so long, is the trace always the same ?
Hi Lukas,
sorry for the delay.
Been retesting this with the current post-pre8 Linus tree and I can
hit it with a single try, same trace as before.
This is an x86-64 kvm guest, single virtual cpu and 1.5 GB memory on
a virtio disk.
prev parent reply other threads:[~2012-12-08 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 19:36 softlockup in xfstests 083 Christoph Hellwig
2012-11-26 13:30 ` Lukáš Czerner
2012-12-08 12:45 ` Christoph Hellwig [this message]
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=20121208124542.GA14814@infradead.org \
--to=hch@infradead.org \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.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).