From: Bill Davidsen <davidsen@tmr.com>
To: Paul Collins <paul@burly.ondioline.org>
Cc: michael@ellerman.id.au, linuxppc-dev@ozlabs.org,
nfsv4@linux-nfs.org, linux-kernel@vger.kernel.org
Subject: Re: nfsd, v4: oops in find_acceptable_alias, ppc32 Linux, post-2.6.27-rc1
Date: Mon, 25 Aug 2008 16:12:53 -0400 [thread overview]
Message-ID: <48B31245.4040505@tmr.com> (raw)
In-Reply-To: <871w145ar3.fsf@burly.wgtn.ondioline.org>
Paul Collins wrote:
> Michael Ellerman <michael@ellerman.id.au> writes:
>> Also, how old is the machine? Any chance you're just seeing random
>> memory corruption?
>
> 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.
>
While it is possible that the new kernel tickles a hardware bug and all
the old ones don't, I would put my $ on the kernel being the issue.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2008-08-30 18:35 UTC|newest]
Thread overview: 21+ 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-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 20:51 ` Paul Collins
2008-08-04 20:59 ` J. Bruce Fields
2008-08-05 0:16 ` Michael Ellerman
2008-08-05 3:43 ` Paul Collins
2008-08-05 4:34 ` Michael Ellerman
2008-08-05 4:47 ` Paul Collins
2008-08-05 7:16 ` Benjamin Herrenschmidt
2008-08-06 6:29 ` Benjamin Herrenschmidt
2008-08-25 20:12 ` Bill Davidsen [this message]
2008-08-05 9:43 ` Paul Collins
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=48B31245.4040505@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--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 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).