From: "BERTRAND Joël" <joel.bertrand@systella.fr>
To: sparclinux@vger.kernel.org
Subject: Re: NFS Oopses on SPARC64?
Date: Tue, 09 Jan 2007 13:23:05 +0000 [thread overview]
Message-ID: <45A39739.2010809@systella.fr> (raw)
In-Reply-To: <200701091315.l09DFl1B006228@laptop13.inf.utfsm.cl>
Horst H. von Brand a écrit :
Hello,
> I've got Oopses with high(ish?) NFS load (compiling stuff on my x86_64 on
> my automounted home from SPARC64) with vanilla 2.6.19.1 and 2.6.20-rc4
> (didn't do any such madness before, and not in between). Reported as 7795
> and 7796 in bugzilla.kernel.org. Aurora Corona on a SPARC Station Ultra 1,
> up to date.
>
> Has anybody else seen something like this? This machine has had random NFS
> and hang problems, which I didn't have the time to investigate further then.
> I attributed them to the (all too common) brownouts here.
I have reported in this mailing list the same bug. I have an U60/SMP
with several raid volumes and 1 GB of main memory that currently runs
with official 2.6.19.1. It's NFS randomly hangs with an Oops. I have
tried kernel-nfsd (v3 and v4), same result. But user-nfsd works fine for
me (very slow, but without any oops). I never see any hang trouble (only
with sparc32).
Remark : older kernel work fine and the same kernel built for i386 or
K8 works fine too. I have tried to build 2.6.19.1 with gcc-3.4 and
gcc-4.1, same result, nfs oppses, but not in the same routine.
> I've set up things so I can disassemble/regenerate the .s for the stuff
> referenced in the Oops, but I'd rather not (my knowledge of SPARC assembly
> is almost non-existent). Any clues/pointers?
No...
Regards,
JKB
next prev parent reply other threads:[~2007-01-09 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 13:15 NFS Oopses on SPARC64? Horst H. von Brand
2007-01-09 13:23 ` BERTRAND Joël [this message]
2007-01-09 15:56 ` Horst H. von Brand
2007-01-10 23:27 ` David Miller
2007-01-11 8:18 ` BERTRAND Joël
2007-01-11 9:28 ` David Miller
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=45A39739.2010809@systella.fr \
--to=joel.bertrand@systella.fr \
--cc=sparclinux@vger.kernel.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.