On Sun, 14 Jun 2009, Eric Lammerts wrote:<snip>There is something strange going on with tun devices:
First you see the ip, then you don't...
I traced it back to this commit:
$ git-bisect bad
05f54c13cd0c33694eec39a265475c5d6cf223cf is first bad commit
commit 05f54c13cd0c33694eec39a265475c5d6cf223cf
Author: Hugh Dickins <hugh@xxxxxxxxxxx>
Date: Thu Apr 16 21:55:29 2009 +0100
Revert "kobject: don't block for each kobject_uevent".
If I take 2.6.30 and revert that commit, the problem goes away.
I'm mortified! But it's rather odd, that's just a straight reversion
of an earlier, clearly buggy commit: I guess you have some other issue,
which reverting to a wait here now uncovers.
One likely workaround: I suspect your .config says something like
CONFIG_UEVENT_HELPER_PATH=/sbin/hotplug, but you've no /sbin/hotplug?
Please try changing that to CONFIG_UEVENT_HELPER_PATH="", and see if
the problem comes up with that resulting kernel.