linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Andreas Friedrich Berendsen <afberendsen@gmail.com>,
	linux-ext4@vger.kernel.org
Subject: Re: possible ext4 race situation freezing linux
Date: Tue, 24 Feb 2009 09:38:17 -0600	[thread overview]
Message-ID: <49A41469.6090604@redhat.com> (raw)
In-Reply-To: <20090224141749.GC5482@mit.edu>

Theodore Tso wrote:
> On Wed, Feb 25, 2009 at 01:22:22AM +1300, Andreas Friedrich Berendsen wrote:
>> Kernel version: 2.26.28.7
>> efs2progs version: 1.41.4
>> arch: x86_64 (amd)
>>
>> I made this test four times and the results  were the same: linux
>> freezes and becomes unresponsive. Only solution is to reset the box. I
>> do not know if the problem is with the USB devices sub-subsystem or a
>> possible ext4 race condition.
> 
> Can you use alt-sysrq to get some stack traces or a register dump out,
> so we can see where the kernel is hanging?
> 
>       	      	    	       	  - Ted

alt-sysrq-w would be a good place to start (just in case you're not
familiar w/ the sysrq keys)

It'd also be great to test w/ 2.6.29, as a deadlock was fixed there
recently (it's on its way to .28.x too AFAIK)

Thanks,

-Eric

  reply	other threads:[~2009-02-24 15:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24 12:22 possible ext4 race situation freezing linux Andreas Friedrich Berendsen
2009-02-24 14:17 ` Theodore Tso
2009-02-24 15:38   ` Eric Sandeen [this message]
2009-02-24 17:03     ` Andreas Friedrich Berendsen
2009-02-24 17:30       ` Theodore Tso
2009-03-04  6:42         ` Andreas Friedrich Berendsen
2009-03-04  6:56           ` Eric Sandeen
2009-03-04  8:03             ` Andreas Friedrich Berendsen
2009-03-06 19:21               ` Andreas Friedrich Berendsen

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=49A41469.6090604@redhat.com \
    --to=sandeen@redhat.com \
    --cc=afberendsen@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).