From owner-freebsd-current@FreeBSD.ORG  Tue Dec 20 08:38:54 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35])
	by hub.freebsd.org (Postfix) with ESMTP id 11D52106566C;
	Tue, 20 Dec 2011 08:38:54 +0000 (UTC)
	(envelope-from dougb@FreeBSD.org)
Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org
	[IPv6:2001:4f8:fff6::36])
	by mx2.freebsd.org (Postfix) with ESMTP id 829FD14DA52;
	Tue, 20 Dec 2011 08:38:53 +0000 (UTC)
Message-ID: <4EF0499D.4070000@FreeBSD.org>
Date: Tue, 20 Dec 2011 00:38:53 -0800
From: Doug Barton <dougb@FreeBSD.org>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:8.0) Gecko/20111110 Thunderbird/8.0
MIME-Version: 1.0
To: Dimitry Andric <dim@FreeBSD.org>
References: <4EEF0124.4000902@FreeBSD.org> <4EEF3B22.8010401@FreeBSD.org>
In-Reply-To: <4EEF3B22.8010401@FreeBSD.org>
X-Enigmail-Version: undefined
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-current <freebsd-current@FreeBSD.org>
Subject: Re: r228700 can't dhclient em0
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Dec 2011 08:38:54 -0000

On 12/19/2011 05:24, Dimitry Andric wrote:
> On 2011-12-19 10:17, Doug Barton wrote:
>> I updated to r228700 from 228122 and dhclient exits immediately saying
>> that em0 doesn't exist. However ifconfig seems to disagree:
>>
>>
>> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>  metric 0 mtu
>> 1500
>>
>> options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
>>
>>          ether 00:24:e8:30:10:9b
>>          nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>>          media: Ethernet autoselect (100baseTX<full-duplex>)
>>          status: active
>> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST>  metric 0 mtu 16384
>>          options=3<RXCSUM,TXCSUM>
>>          nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
>>
>>
>> Interestingly, some of the options are different in that version, vs.
>> the working version:
>>
>> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>  metric 0 mtu
>> 1500
>>     options=219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC>
>>
>>     ether 00:24:e8:30:10:9b
>>     inet 172.17.198.245 netmask 0xffff0000 broadcast 172.17.255.255
>>     nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>>     media: Ethernet autoselect (100baseTX<full-duplex>)
>>     status: active
> 
> I saw this too, when my kernel and userland were out of sync (e.g. just
> after installing a new kernel, and before installworld).  I suspect it
> is caused by the changes in r228571, which cause old ifconfig and
> dhclient to not recognize any interfaces.  I'm not 100% sure though...

I tried replacing both ifconfig and dhclient with the versions that were
built along with the new kernel, and that didn't work.

The traditional (and documented) upgrade process for many years has been
to boot the new kernel, make sure it's Ok, then update world. Obviously
something different is needed this time, so it needs an UPDATING entry
(assuming that all this is not just a bug).


Doug

-- 

		[^L]

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/