From: Trond Myklebust <trondmy@hammerspace.com>
To: "geert@linux-m68k.org" <geert@linux-m68k.org>,
"anemo@mba.ocn.ne.jp" <anemo@mba.ocn.ne.jp>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: Re: NFS/TCP crashes on MIPS/RBTX4927 in v4.20-rcX (bisected)
Date: Wed, 5 Dec 2018 13:45:34 +0000 [thread overview]
Message-ID: <92ce4b8c2b2d53e27ed5bc0e5af3fee4bc17b4dc.camel@hammerspace.com> (raw)
In-Reply-To: <CAMuHMdU9zXXSaPHKvfG3A73h3CTsb9H2RT_gWt-Ne=qQ+HKShQ@mail.gmail.com>
On Wed, 2018-12-05 at 14:41 +0100, Geert Uytterhoeven wrote:
> Hi Nemoto-san,
>
> On Wed, Dec 5, 2018 at 2:11 PM Atsushi Nemoto <anemo@mba.ocn.ne.jp>
> wrote:
> > On Tue, 4 Dec 2018 14:53:07 +0100, Geert Uytterhoeven <
> > geert@linux-m68k.org> wrote:
> > > I found similar crashes in a report from 2006, but of course the
> > > code
> > > has changed too much to apply the solution proposed there
> > > (
> > > https://www.linux-mips.org/archives/linux-mips/2006-09/msg00169.html
> > > ).
> > >
> > > Userland is Debian 8 (the last release supporting "old" MIPS).
> > > My kernel is based on v4.20.0-rc5, but the issue happens with
> > > v4.20-rc1,
> > > too.
> > >
> > > However, I noticed it works in v4.19! Hence I've bisected this,
> > > to commit
> > > 277e4ab7d530bf28 ("SUNRPC: Simplify TCP receive code by switching
> > > to using
> > > iterators").
> > >
> > > Dropping the ",tcp" part from the nfsroot parameter also fixes
> > > the issue.
> > >
> > > Given RBTX4927 is little endian, just like my arm/arm64 boards,
> > > it's probably
> > > not an endianness issue. Sparse didn't show anything suspicious
> > > before/after
> > > the guilty commit.
> > >
> > > Do you have a clue?
> >
> > If it was a cache issue, disabling i-cache or d-cache completely
> > might
> > help understanding the problem. I added TXx9 specific "icdisable"
> > and
> > "dcdisable" kernel options for debugging long ago.
> >
> > I hope these options still works correctly with recent kernel but
> > not
> > sure.
> >
> > Also, disabling i-cache makes your board VERY slow, of course.
>
> Thanks!
>
> When using these options, I do see a slowdown in early boot, but the
> issue
> is still there.
>
> My next guess is an unaligned access not using {get,put}_unaligned(),
> which
> doesn't seem to work on tx4927, but doesn't cause an exception
> neither.
Can you try my linux-next branch on git.linux-nfs.org? It contains a
fixes for a hang that results from the above commit.
git pull git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
Cheers
Trond
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2018-12-05 13:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 13:53 Geert Uytterhoeven
2018-12-05 13:11 ` Atsushi Nemoto
2018-12-05 13:41 ` Geert Uytterhoeven
2018-12-05 13:45 ` Trond Myklebust [this message]
2018-12-05 14:47 ` Geert Uytterhoeven
2018-12-17 14:03 ` Geert Uytterhoeven
2018-12-17 14:51 ` Trond Myklebust
2018-12-17 18:55 ` Geert Uytterhoeven
2018-12-17 19:01 ` Trond Myklebust
2018-12-19 9:56 ` Geert Uytterhoeven
2018-12-07 14:51 ` Atsushi Nemoto
2018-12-07 16:19 ` Geert Uytterhoeven
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=92ce4b8c2b2d53e27ed5bc0e5af3fee4bc17b4dc.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=anemo@mba.ocn.ne.jp \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-nfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®