All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8116] New: 2015.05-rc2 raspberrypi2_defconfig network interface not coming up
Date: Sat, 16 May 2015 03:55:50 +0000 (UTC)	[thread overview]
Message-ID: <bug-8116-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=8116

           Summary: 2015.05-rc2 raspberrypi2_defconfig network interface
                    not coming up
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: albert.david at gmail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


in 2015.05-rc2, default configuration of raspberrypi2(raspberrypi2_defconfig)
network interface doesnt show up after boot, but adding a "sleep 1" in
S40network(before line "/sbin/ifup -a") fixes the problem.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2015-05-16  3:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-16  3:55 bugzilla at busybox.net [this message]
2015-05-16  7:03 ` [Buildroot] [Bug 8116] 2015.05-rc2 raspberrypi2_defconfig network interface not coming up bugzilla at busybox.net
2015-05-16 10:58 ` bugzilla at busybox.net
2015-05-16 13:16 ` bugzilla at busybox.net
2015-05-16 13:24 ` bugzilla at busybox.net
2015-05-16 13:33 ` bugzilla at busybox.net
2015-07-07 15:53 ` bugzilla at busybox.net
2015-10-16  9:46 ` bugzilla at busybox.net
2015-10-16 20:00 ` bugzilla at busybox.net
2015-10-16 20:52 ` bugzilla at busybox.net

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=bug-8116-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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.