From: Eric Lammerts <eric@lammerts.org>
To: Hugh Dickins <hugh.dickins@tiscali.co.uk>
Cc: kernel list <linux-kernel@vger.kernel.org>,
gregkh@suse.de, netdev@vger.kernel.org
Subject: Re: 2.6.30: tun losing ip
Date: Sun, 14 Jun 2009 14:36:10 -0400 [thread overview]
Message-ID: <4A35431A.50507@lammerts.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0906141015130.11221@sister.anvils>
On 06/14/2009 05:28 AM, Hugh Dickins wrote:
> On Sun, 14 Jun 2009, Eric Lammerts wrote:
>> There is something strange going on with tun devices:
<snip>
>> 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@veritas.com>
>> 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.
Actually I do have an /sbin/hotplug, with I now noticed has some old
script stuff behind it that starts a udhcpc... aarrrgh. I removed it and
the problem's gone.
Apologies for wasting your time.
Eric
prev parent reply other threads:[~2009-06-14 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 5:18 2.6.30: tun losing ip Eric Lammerts
2009-06-14 9:28 ` Hugh Dickins
2009-06-14 18:36 ` Eric Lammerts [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=4A35431A.50507@lammerts.org \
--to=eric@lammerts.org \
--cc=gregkh@suse.de \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-kernel@vger.kernel.org \
--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 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.