From: "Franklin S Cooper Jr." <fcooper@ti.com>
To: samanthakumar@google.com, willemb@google.com,
edumazet@google.com, tony@atomide.com, mugunthanvnm@ti.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, kuznet@ms2.inr.ac.ru, jmorris@namei.org,
yoshfuji@linux-ipv6.org, kaber@trash.net, nsekhar@ti.com,
linux-omap@vger.kernel.org
Subject: Boot failure when using NFS on OMAP based evms
Date: Wed, 6 Apr 2016 18:12:42 -0500 [thread overview]
Message-ID: <570597EA.3040902@ti.com> (raw)
Hi All,
Currently linux-next is failing to boot via NFS on my AM335x GP evm,
AM437x GP evm and Beagle X15. I bisected the problem down to the commit
"udp: remove headers from UDP packets before queueing".
I had to revert the following three commits to get things working again:
e6afc8ace6dd5cef5e812f26c72579da8806f5ac
udp: remove headers from UDP packets before queueing
627d2d6b550094d88f9e518e15967e7bf906ebbf
udp: enable MSG_PEEK at non-zero offset
b9bb53f3836f4eb2bdeb3447be11042bd29c2408
sock: convert sk_peek_offset functions to WRITE_ONCE
I'm using omap2plus_defconfig for my config.
Below bootlogs are from my AM335x GP evm:
Working
http://pastebin.ubuntu.com/15661989/ (Linux-next 3 patches reverted)
Failing
http://pastebin.ubuntu.com/15661318/ (Linux-next)
WARNING: multiple messages have this Message-ID (diff)
From: "Franklin S Cooper Jr." <fcooper@ti.com>
To: <samanthakumar@google.com>, <willemb@google.com>,
<edumazet@google.com>, <tony@atomide.com>, <mugunthanvnm@ti.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<davem@davemloft.net>, <kuznet@ms2.inr.ac.ru>,
<jmorris@namei.org>, <yoshfuji@linux-ipv6.org>, <kaber@trash.net>,
<nsekhar@ti.com>, <linux-omap@vger.kernel.org>
Subject: Boot failure when using NFS on OMAP based evms
Date: Wed, 6 Apr 2016 18:12:42 -0500 [thread overview]
Message-ID: <570597EA.3040902@ti.com> (raw)
Hi All,
Currently linux-next is failing to boot via NFS on my AM335x GP evm,
AM437x GP evm and Beagle X15. I bisected the problem down to the commit
"udp: remove headers from UDP packets before queueing".
I had to revert the following three commits to get things working again:
e6afc8ace6dd5cef5e812f26c72579da8806f5ac
udp: remove headers from UDP packets before queueing
627d2d6b550094d88f9e518e15967e7bf906ebbf
udp: enable MSG_PEEK at non-zero offset
b9bb53f3836f4eb2bdeb3447be11042bd29c2408
sock: convert sk_peek_offset functions to WRITE_ONCE
I'm using omap2plus_defconfig for my config.
Below bootlogs are from my AM335x GP evm:
Working
http://pastebin.ubuntu.com/15661989/ (Linux-next 3 patches reverted)
Failing
http://pastebin.ubuntu.com/15661318/ (Linux-next)
next reply other threads:[~2016-04-06 23:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 23:12 Franklin S Cooper Jr. [this message]
2016-04-06 23:12 ` Boot failure when using NFS on OMAP based evms Franklin S Cooper Jr.
2016-04-07 2:22 ` Willem de Bruijn
2016-04-07 14:36 ` Franklin S Cooper Jr.
2016-04-07 14:36 ` Franklin S Cooper Jr.
2016-04-07 14:39 ` Willem de Bruijn
2016-04-07 15:52 ` Willem de Bruijn
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=570597EA.3040902@ti.com \
--to=fcooper@ti.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=samanthakumar@google.com \
--cc=tony@atomide.com \
--cc=willemb@google.com \
--cc=yoshfuji@linux-ipv6.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.