From: Mark Salter <msalter-H+wXaHxf7aLQT0dZR+AlfA@public•gmane.org>
To: Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public•gmane.org
Cc: linux-next <linux-next-u79uwXL29TY76Z2rM5mHXA@public•gmane.org>,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public•gmane.org
Subject: nfs root problem in linux-next
Date: Mon, 25 Jun 2012 16:26:45 -0400 [thread overview]
Message-ID: <1340656006.20557.30.camel@deneb.redhat.com> (raw)
As of Friday's linux-next I've been unable to successfully boot using an
nfs root with a c6x board. I bisected it to this patch:
commit cc3b296fd9a01c9e654bcb9373af70dd6e32fb24
Author: Trond Myklebust <Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public•gmane.org>
Date: Thu Jun 21 14:53:10 2012 -0400
SUNRPC: Clean up xdr_read_pages and xdr_enter_page
I placed "good-boot" and "bad-boot" packet capture files at:
http://people.redhat.com/~msalter/linux-next/
The only difference in the kernels used is the above patch. The
bad-boot mounted the nfs root but was unable to find the init
file which caused a panic. The nfsroot= parameter uses v3,tcp
flags and the server side is running rhel6.
I'm not at all familiar with the nfs code, but can help with
testing or providing any addtional info needed.
--Mark
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public•gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2012-06-25 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 20:26 Mark Salter [this message]
[not found] ` <1340656006.20557.30.camel-PDpCo7skNiwAicBL8TP8PQ@public.gmane.org>
2012-06-25 23:14 ` nfs root problem in linux-next Myklebust, Trond
[not found] ` <1340666049.4362.9.camel-SyLVLa/KEI9HwK5hSS5vWB2eb7JE58TQ@public.gmane.org>
2012-06-26 3:17 ` Mark Salter
2012-06-29 13:55 ` Myklebust, Trond
2012-06-29 14:48 ` Mark Salter
2012-06-29 14:53 ` Fengguang Wu
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=1340656006.20557.30.camel@deneb.redhat.com \
--to=msalter-h+wxahxf7alqt0dzr+alfa@public$(echo .)gmane.org \
--cc=Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public$(echo .)gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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