All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] NFS-root boot problem
Date: Tue, 30 Jun 2020 19:43:30 +0200	[thread overview]
Message-ID: <20200630194330.554815c0@windsurf> (raw)
In-Reply-To: <CAOiXNkBxAvePRB5zCCcPdyyBarM_4w_8hvc15nWhuK=15W6ptg@mail.gmail.com>

On Tue, 30 Jun 2020 19:23:30 +0200
Andrey Nechypurenko <andreynech@gmail.com> wrote:

> [    8.349831] stm32-dwmac 5800a000.ethernet eth0: Link is Up -
> 1Gbps/Full - flow control rx/tx
> [    8.369852] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> [    8.399809] Sending DHCP requests ., OK
> [    8.445835] IP-Config: Got DHCP answer from 192.168.10.1, my
> address is 192.168.10.2
> [    8.459285] IP-Config: Complete:
> [    8.464607]      device=eth0, hwaddr=00:80:e1:42:63:27,
> ipaddr=192.168.10.2, mask=255.255.255.0, gw=192.168.10.1
> [    8.480546]      host=devboard, domain=dev.local, nis-domain=(none)
> [    8.492540]      bootserver=192.168.10.1, rootserver=192.168.10.1,
> rootpath=/srv/nfs/rootfs,wsize=1024,rsize=1024,v3
> [    8.492546]      nameserver0=8.8.8.8
> [    8.515305] ALSA device list:
> [    8.520550]   No soundcards found.
> [    8.569520] VFS: Mounted root (nfs filesystem) on device 0:16.
> [    8.583574] devtmpfs: mounted
> [    8.590867] Freeing unused kernel memory: 1024K
> [    8.630042] Run /sbin/init as init process
> Starting syslogd: OK
> Starting klogd: OK
> Running sysctl: OK
> Initializing random number generator: OK
> Saving random seed: OK
> Starting rpcbind: OK
> Starting network: ip: RTNETLINK answers: File exists
> udhcpc: started, v1.31.1
> [   19.379804] nfs: server 192.168.10.1 not responding, still trying
> [   28.199820] nfs: server 192.168.10.1 not responding, still trying

When your DHCP client in userspace runs, it turns the network interface
down, and because you're doing root-over-NFS, this means you're cutting
the tree branch on which you're sitting!

Disable your DHCP client in userspace will solve your problem.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-06-30 17:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30 17:23 [Buildroot] NFS-root boot problem Andrey Nechypurenko
2020-06-30 17:43 ` Thomas Petazzoni [this message]
2020-07-01  8:18   ` Andrey Nechypurenko

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=20200630194330.554815c0@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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.