All of lore.kernel.org
 help / color / mirror / Atom feed
From: Iordan Iordanov <iordan@cdf.toronto.edu>
To: dujun <dujun@perabytes.com>
Cc: "Neil Brown" <neilb@suse.de>,
	"Mathias Burén" <mathias.buren@gmail.com>,
	linux-raid@vger.kernel.org, "CDF Admin" <admin@cdf.toronto.edu>
Subject: Re: raid related kernel hang in 2.6.36
Date: Thu, 10 Feb 2011 11:28:24 -0500	[thread overview]
Message-ID: <4D541228.2090700@cdf.toronto.edu> (raw)
In-Reply-To: <1290654763.5416.31.camel@dujun.perabytes.com>

Hi Neil,

We are currently using 2.6.36 on a production machine running mdadm, and 
this morning we experienced a very similar issue, but we didn't have the 
LOCKUP_DETECTOR config options set, so there was absolutely no output. 
We also experienced this on a non-production test platform a few days 
ago (same hardware and software as our production machine).

Has this bug been diagnosed/resolved? If so, past which kernel version? 
If not, can you suggest some recourse for us, like perhaps moving back 
to 2.6.35 for our production server, and moving up to the latest stable 
on our test platform, and enabling the LOCKUP_DETECTOR options?

Is this bug totally reproducible Du Jun? If so, should I just try what 
you outlined in your previous message?

Many thanks,
Iordan Iordanov


  reply	other threads:[~2011-02-10 16:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-24 13:48 raid related kernel hang in 2.6.36 Du Jun
2010-11-24 14:19 ` Mathias Burén
2010-11-24 14:34   ` Du Jun
2010-11-24 20:01     ` Neil Brown
2010-11-24 21:15       ` Carlos Carvalho
2010-11-25  3:12       ` dujun
2011-02-10 16:28         ` Iordan Iordanov [this message]
2011-02-11 15:52           ` Iordan Iordanov

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=4D541228.2090700@cdf.toronto.edu \
    --to=iordan@cdf.toronto.edu \
    --cc=admin@cdf.toronto.edu \
    --cc=dujun@perabytes.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mathias.buren@gmail.com \
    --cc=neilb@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.