From: Mugunthan V N <mugunthanvnm@ti.com>
To: Alexander Aring <alex.aring@gmail.com>, <netdev@vger.kernel.org>
Subject: Re: dhcp nfsroot booting failure on bb white
Date: Wed, 12 Aug 2015 14:22:53 +0530 [thread overview]
Message-ID: <55CB0965.9020300@ti.com> (raw)
In-Reply-To: <20150812083629.GA778@omega>
On Wednesday 12 August 2015 02:06 PM, Alexander Aring wrote:
> Hi,
>
> my beaglebone (white edition) fails to boot via dhcp and nfsroot. The
> last messages which I see are:
>
> ...
> [ 2.970593] Sending DHCP requests .
> [ 5.996876] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full -
> flow control off
>
>
> then it stucks forever. I reverted the recently cpsw patches:
>
> 32a7432c0fb8b0117961bdc7ab256667d039de16 ("drivers: net: cpsw: add
> separate napi for tx")
>
> d354eb85d61803e07831b68d1985cd9cfe2f8b59 ("drivers: net: cpsw:
> dual_emac: simplify napi usage")
>
> 870915feabdc3af5f0ebb72d1fcf96bff01837b0 ("drivers: net: cpsw: remove
> disable_irq/enable_irq as irq can be masked from cpsw itself")
>
>
> I did a test after each revert, I finally figured out that after reverting
> the last patch:
>
> 870915feabdc3af5f0ebb72d1fcf96bff01837b0 ("drivers: net: cpsw: remove
> disable_irq/enable_irq as irq can be masked from cpsw itself")
>
> it worked again to boot via dhcp nfsroot.
>
>
> My bootparameters are:
>
> commandline: console=ttyO0,115200n8 console=ttyO0,115200n8 ip=dhcp
> root=/dev/nfs nfsroot=$IP:$NFS_EXPORT,v3,tcp
>
I am already looking into it. Will submit a fix soon. The issue is with
AM335x PG1.0 as there is a errata in CPSW interrupts, PG2.x and other
SoCs are working fine.
Regards
Mugunthan V N
prev parent reply other threads:[~2015-08-12 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 8:36 dhcp nfsroot booting failure on bb white Alexander Aring
2015-08-12 8:52 ` Mugunthan V N [this message]
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=55CB0965.9020300@ti.com \
--to=mugunthanvnm@ti.com \
--cc=alex.aring@gmail.com \
--cc=netdev@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