From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paul Collins <paul@burly.ondioline.org>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Neil Brown <neilb@suse.de>,
nfsv4@linux-nfs.org, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org
Subject: Re: nfsd, v4: oops in find_acceptable_alias, ppc32 Linux, post-2.6.27-rc1
Date: Tue, 05 Aug 2008 17:16:58 +1000 [thread overview]
Message-ID: <1217920618.24157.161.camel@pasglop> (raw)
In-Reply-To: <871w145ar3.fsf@burly.wgtn.ondioline.org>
On Tue, 2008-08-05 at 16:47 +1200, Paul Collins wrote:
> It's about four years old. It was in storage for about six months and I
> got it repaired a few weeks ago (display cable and inverter). The sort
> of crazy crap I've been reporting certainly smacks of memory corruption.
> But on the other hand, 2.6.25 (Debian's) and 2.6.26 (my own) have been
> trouble-free.
Any chance you can bisect the problem ?
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paul Collins <paul@burly.ondioline.org>
Cc: michael@ellerman.id.au, "J. Bruce Fields" <bfields@fieldses.org>,
Neil Brown <neilb@suse.de>,
nfsv4@linux-nfs.org, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org
Subject: Re: nfsd, v4: oops in find_acceptable_alias, ppc32 Linux, post-2.6.27-rc1
Date: Tue, 05 Aug 2008 17:16:58 +1000 [thread overview]
Message-ID: <1217920618.24157.161.camel@pasglop> (raw)
In-Reply-To: <871w145ar3.fsf@burly.wgtn.ondioline.org>
On Tue, 2008-08-05 at 16:47 +1200, Paul Collins wrote:
> It's about four years old. It was in storage for about six months and I
> got it repaired a few weeks ago (display cable and inverter). The sort
> of crazy crap I've been reporting certainly smacks of memory corruption.
> But on the other hand, 2.6.25 (Debian's) and 2.6.26 (my own) have been
> trouble-free.
Any chance you can bisect the problem ?
Cheers,
Ben.
next prev parent reply other threads:[~2008-08-05 7:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 12:03 nfsd, v4: oops in find_acceptable_alias, ppc32 Linux, post-2.6.27-rc1 Paul Collins
2008-08-02 18:45 ` J. Bruce Fields
2008-08-02 22:36 ` Paul Collins
2008-08-02 22:36 ` Paul Collins
2008-08-03 6:47 ` Paul Collins
2008-08-03 6:47 ` Paul Collins
2008-08-03 12:09 ` Neil Brown
2008-08-03 12:25 ` Paul Collins
2008-08-04 4:08 ` Neil Brown
2008-08-04 5:11 ` Paul Collins
2008-08-04 10:00 ` Paul Collins
2008-08-04 14:36 ` Michael Ellerman
2008-08-04 14:36 ` Michael Ellerman
2008-08-04 20:51 ` Paul Collins
2008-08-04 20:51 ` Paul Collins
2008-08-04 20:59 ` J. Bruce Fields
2008-08-04 20:59 ` J. Bruce Fields
2008-08-05 0:16 ` Michael Ellerman
2008-08-05 0:16 ` Michael Ellerman
2008-08-05 3:43 ` Paul Collins
2008-08-05 3:43 ` Paul Collins
2008-08-05 4:34 ` Michael Ellerman
2008-08-05 4:34 ` Michael Ellerman
2008-08-05 4:47 ` Paul Collins
2008-08-05 4:47 ` Paul Collins
2008-08-05 7:16 ` Benjamin Herrenschmidt [this message]
2008-08-05 7:16 ` Benjamin Herrenschmidt
2008-08-06 6:29 ` Benjamin Herrenschmidt
2008-08-25 20:12 ` Bill Davidsen
2008-08-25 20:12 ` Bill Davidsen
2008-08-05 9:43 ` Paul Collins
2008-08-05 9:43 ` Paul Collins
2008-08-05 11:53 ` Michael Ellerman
2008-08-05 11:53 ` Michael Ellerman
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=1217920618.24157.161.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=neilb@suse.de \
--cc=nfsv4@linux-nfs.org \
--cc=paul@burly.ondioline.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 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.