From: NeilBrown <neilb@suse.de>
To: "fibreraid@gmail.com" <fibreraid@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>, linux-xfs@vger.kernel.org
Subject: Re: md 3.2.1 and xfs kernel panic on Linux 2.6.38
Date: Thu, 16 Jun 2011 12:26:52 +1000 [thread overview]
Message-ID: <20110616122652.428ac545@notabene.brown> (raw)
In-Reply-To: <20110616115531.298328f2@notabene.brown>
On Thu, 16 Jun 2011 11:55:31 +1000 NeilBrown <neilb@suse.de> wrote:
> Hmmm... maybe we are missing the wakeup call. I can find where we wake-up
> anyone waiting for an overlapping read request to complete, but I cannot find
> where we wake-up someone waiting for when an overlapping write request
> completes. That should probably go in handle_stripe_clean_event.
On second thoughts, I can find where it is handled correctly for an
overlapping write request.
So I'm not stumped again.
I tried looking at a disassembly listing of make_request to confirm which
'schedule' call it was, but when I disassemble make_request it is about 1700
bytes long where as you trace show:
make_request+0x138/0x3d0
That it is 0x3d0 long, or about 900 bytes. That is odd.
Can you get a disassembly to show me?
e.g.
gdb raid456.ko
disassemble make_request
Thanks,
NeilBrown
>
> Do you have the system still hanging in this state? If not, can you get it
> back into this state easily?
> If so, you can force a wakeup with the magic incantation:
>
> cat /sys/block/mdXX/md/suspend_lo > /sys/block/mdXX/md/suspend_lo
>
> (with 'XX' suitably substituted).
>
> If that makes a difference, then I know I am on the right track
>
> Thanks,
> NeilBrown
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-06-16 2:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-12 18:50 md 3.2.1 and xfs kernel panic on Linux 2.6.38 fibreraid
2011-06-16 1:55 ` NeilBrown
2011-06-16 2:26 ` NeilBrown [this message]
2011-06-16 5:50 ` Stan Hoeppner
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=20110616122652.428ac545@notabene.brown \
--to=neilb@suse.de \
--cc=fibreraid@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=linux-xfs@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).