init-ifupdown: adjust priority of networking to fix system freeze problem
authorChen Qi <Qi.Chen@windriver.com>
Thu, 12 Dec 2013 08:38:04 +0000 (16:38 +0800)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Sat, 14 Dec 2013 09:11:19 +0000 (09:11 +0000)
commit05c1a96591ce41c1f8dffc115d1c1db7b24e0ed7
treef241e2894fee7e1b4e326e08e062304fa7d0b4b7
parent74b5048d1c0d2c3185362231c741f6301b55ea08
init-ifupdown: adjust priority of networking to fix system freeze problem

On mpc8315e, a system freeze is encountered at system boot time if
connman and init-ifupdown are installed.

The error message before the freeze is:
    "ip: RTNETLINK answers: File exists"

This problem is introduced by the following commit.
    dc80eea sysvinit: fix problem in switching runlevels

Part of the above commit is to make the networking init script run
at runlevel 2 3 4 5 instead of runlevel S. However, after the change,
networking is run after connman. And this causes the problem stated
above.

Make networking run first when entering runlevel 2 3 4 5, so that we
don't break things.

[YOCTO #5651]

(From OE-Core rev: d518892d38ac399c091ff509a9fd90fc00d71224)

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/recipes-core/init-ifupdown/init-ifupdown_1.0.bb