From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Alexander Graf <agraf@suse.de>,
anton@samba.org, LKML List <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] nfsd crashing with 3.6.0-rc7 on PowerPC
Date: Wed, 03 Oct 2012 14:22:46 +1000 [thread overview]
Message-ID: <1349238166.3847.38.camel@pasglop> (raw)
In-Reply-To: <20121002214327.GA29218@linux.vnet.ibm.com>
On Tue, 2012-10-02 at 14:43 -0700, Nishanth Aravamudan wrote:
>
> Started looking into this. If your suspicion were accurate, wouldn't
> the
> bisection have stopped at 0e4bc95d87394364f408627067238453830bdbf3
> ("powerpc/iommu: Reduce spinlock coverage in iommu_alloc and
> iommu_free")?
>
> Alex, the error is reproducible, right? Does it go away by reverting
> that commit against mainline? Just trying to narrow down my focus.
My suspiction is, I'm afraid, a real bug but not that bug since it would
only happen on U3 and this is an U4 machine ... so we have two bugs, one
of them still unidentified.
Cleaning up the CC list for now...
Cheers,
Ben.
prev parent reply other threads:[~2012-10-03 4:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 1:55 [REGRESSION] nfsd crashing with 3.6.0-rc7 on PowerPC Alexander Graf
2012-09-28 2:04 ` Linus Torvalds
2012-09-28 2:19 ` Alexander Graf
2012-09-28 15:10 ` J. Bruce Fields
2012-09-28 15:34 ` Alexander Graf
2012-10-01 14:03 ` Alexander Graf
2012-10-01 15:21 ` J. Bruce Fields
2012-10-02 0:58 ` Benjamin Herrenschmidt
2012-10-02 21:43 ` Nishanth Aravamudan
2012-10-02 21:47 ` Alexander Graf
2012-10-02 22:17 ` Nishanth Aravamudan
2012-10-02 22:31 ` Alexander Graf
2012-10-04 0:26 ` Anton Blanchard
2012-10-04 4:57 ` [PATCH] powerpc/iommu: Fix multiple issues with IOMMU pools code Anton Blanchard
2012-10-04 10:54 ` Alexander Graf
2012-10-03 4:22 ` Benjamin Herrenschmidt [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=1349238166.3847.38.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=agraf@suse.de \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nacc@linux.vnet.ibm.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).