From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
Andrew Morton <akpm@linux-foundation.org>,
pbadari@gmail.com
Subject: Re: [BUG] 2.6.25-rc5-mm1 kernel panic with "Exception: 501 " on powerpc
Date: Thu, 13 Mar 2008 18:32:10 +0530 [thread overview]
Message-ID: <47D925D2.9050003@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080312223300.GE613@parisc-linux.org>
Matthew Wilcox wrote:
> On Thu, Mar 13, 2008 at 09:26:09AM +1100, Michael Ellerman wrote:
>> down() looks OK, but there's still a spin_lock_irq() in __down_common(),
>> although I don't know if it makes sense for us to be in __down() at that
>> stage.
>
> The spin_lock_irq in __down_common is correct. We're going to schedule(),
> so we spin_unlock_irq() to save us passing the flags into the helper
> function. If we had interrupts disabled on entry, there's an Aieee
> for that.
>
Hi All,
Sorry for all the noise made :-(, something wrong in the test setup from my end,
the kernel was 2.6.25-rc3-mm1 not 2.6.25-rc5-mm1. This bug is not seen in the
2.6.25-rc5-mm1 kernel.
--
Thanks & Regards,
Kamalesh Babulal,
next prev parent reply other threads:[~2008-03-13 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080311011434.ad8c8d7d.akpm@linux-foundation.org>
2008-03-12 12:55 ` [BUG] 2.6.25-rc5-mm1 kernel panic with "Exception: 501 " on powerpc Kamalesh Babulal
2008-03-12 17:46 ` Andrew Morton
2008-03-12 17:51 ` Matthew Wilcox
2008-03-12 22:26 ` Michael Ellerman
2008-03-12 22:33 ` Matthew Wilcox
2008-03-13 13:02 ` Kamalesh Babulal [this message]
2008-03-12 20:40 ` Benjamin Herrenschmidt
2008-03-12 18:14 ` Badari Pulavarty
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=47D925D2.9050003@linux.vnet.ibm.com \
--to=kamalesh@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=matthew@wil.cx \
--cc=pbadari@gmail.com \
/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).