From: Trond Myklebust <trondmy@hammerspace.com>
To: "bfields@fieldses.org" <bfields@fieldses.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"daniel@zonque.org" <daniel@zonque.org>,
"jlayton@kernel.org" <jlayton@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 5.1.0-rc4: Oops in __rpc_execute() when trying to boot from NFS
Date: Mon, 8 Apr 2019 18:51:43 +0000 [thread overview]
Message-ID: <ce6d2388a9214f95cc38de5ec225cba26cf63b0d.camel@hammerspace.com> (raw)
In-Reply-To: <0412f79c-61a8-bfa4-26ce-1083a59d31e8@zonque.org>
On Mon, 2019-04-08 at 19:01 +0200, Daniel Mack wrote:
> Hi,
>
> I'm seeing the Oops below when trying to boot 5.1.0-rc4 on an ARM
> PXA3xx
> platform. v5.0 did not show this effect with the same cmdline.
>
> Relevant bits from the config are:
>
> CONFIG_NFS_FS=y
> CONFIG_NFS_V2=y
> CONFIG_NFS_V3=y
> # CONFIG_NFS_V3_ACL is not set
> # CONFIG_NFS_V4 is not set
> # CONFIG_NFS_SWAP is not set
> CONFIG_ROOT_NFS=y
> CONFIG_NFS_FSCACHE=y
> # CONFIG_NFSD is not set
> CONFIG_NFS_COMMON=y
>
> Anything else I can provide? I could bisect the issue if that helps.
>
Please do bisect if that is at all practical. I'm having trouble
interpreting this Oops.
Thanks!
Trond
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2019-04-08 18:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 17:01 5.1.0-rc4: Oops in __rpc_execute() when trying to boot from NFS Daniel Mack
2019-04-08 18:51 ` Trond Myklebust [this message]
2019-04-09 16:25 ` Daniel Mack
2019-04-09 16:55 ` Trond Myklebust
2019-04-09 17:54 ` Daniel Mack
2019-04-11 19:50 ` Trond Myklebust
2019-04-12 5:57 ` Daniel Mack
2019-04-12 13:34 ` Trond Myklebust
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=ce6d2388a9214f95cc38de5ec225cba26cf63b0d.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=bfields@fieldses.org \
--cc=daniel@zonque.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@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