linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Paul Collins <paul@burly.ondioline.org>
Cc: Neil Brown <neilb@suse.de>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	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 00:36:37 +1000	[thread overview]
Message-ID: <1217860597.12535.2.camel@localhost> (raw)
In-Reply-To: <87y73dcd60.fsf@burly.wgtn.ondioline.org>

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

On Mon, 2008-08-04 at 22:00 +1200, Paul Collins wrote:
> Paul Collins <paul@burly.ondioline.org> writes:
> 
> > Neil Brown <neilb@suse.de> writes:
> >> Could you try removing the 'static' declaration for nfsd_acceptable
> >> and recompile?
> >> Or maybe try a different compiler?
> >
> > I will give these a try this evening.
> 
> I built myself a nice new cross compiler:
> 
>         powerpc-linux-gnu-gcc-4.1 (GCC) 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)
> 
> and rebuilt 94ad374a0751f40d25e22e036c37f7263569d24c.  Running that on
> the server and 2.6.26 on the client, I got yet another Oops.  This one
> locked the machine up pretty good, so all I have is a picture:
> 
> http://ondioline.org/~paul/DSCN1608.JPG

Wow.

Can you try building a kernel on the server? ie. not over NFS.

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-08-04 14:36 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 [this message]
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
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=1217860597.12535.2.camel@localhost \
    --to=michael@ellerman.id.au \
    --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 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).