From owner-freebsd-current@FreeBSD.ORG Sat Jun 11 17:19:35 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ABCED1065672 for ; Sat, 11 Jun 2011 17:19:35 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 581E78FC0C for ; Sat, 11 Jun 2011 17:19:34 +0000 (UTC) Received: by vxc34 with SMTP id 34so4128061vxc.13 for ; Sat, 11 Jun 2011 10:19:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=m3AK3GyoLdCSNpKL4UB657CIwqxjmpgYLQaeKUDFGbw=; b=x5RSCCp69Y6XoheDquGzf8EAWKLRlLr7WZOu17A46ySbSvv3omnhxzkE5JBeeTPyZQ G2L3zIhVnzdiF6VXIacvonXyo1UmL0VY/WWEpinY24k8KkXJ+43xAwN3efolgzWwLW/V l+x3bqVA/70/ps0UV2oukihNXghol9JMWzaNM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=kk7KdRdJt9l+vMFlxiMEycDsDDwi37nd6D0udyvw3boDnLYfV7d/Ds0GrwPS/6/qtK wOPYY3p9jJcvg4Tzn+yPRLsMtOYi4klN8mGkR/InhhZ7e0Jh5KXGMd+qATYxHDAW/Vip SHJmSb8UNxW1mADpfTgrpKKVbpSm6X+Mib1UQ= MIME-Version: 1.0 Received: by 10.220.177.9 with SMTP id bg9mr1291027vcb.93.1307812774306; Sat, 11 Jun 2011 10:19:34 -0700 (PDT) Received: by 10.220.189.202 with HTTP; Sat, 11 Jun 2011 10:19:34 -0700 (PDT) In-Reply-To: References: <6D37AF86-9C14-4824-96CA-55C86497DECD@lists.zabbadoz.net> <4434466E-F4B0-47B1-98BF-80E4E495AA4C@lists.zabbadoz.net> <66750835-22BE-4F95-8940-567D74BC0488@lists.zabbadoz.net> <828CAE62-9C52-40EF-9C6B-A412645DB347@gmail.com> <96924B71-E657-460A-B274-BB38DCA5713A@lists.zabbadoz.net> Date: Sat, 11 Jun 2011 10:19:34 -0700 Message-ID: From: Garrett Cooper To: "Bjoern A. Zeeb" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Current Subject: Re: IPv4 broken on r222048 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2011 17:19:35 -0000 On Wed, Jun 8, 2011 at 9:33 PM, Garrett Cooper wrote: > On Wed, Jun 8, 2011 at 9:31 AM, Bjoern A. Zeeb > wrote: >> >> On Jun 8, 2011, at 4:25 PM, Garrett Cooper wrote: >> >>> On Jun 8, 2011, at 9:07 AM, "Bjoern A. Zeeb" wrote: >>> >>>> On Jun 7, 2011, at 6:15 PM, Garrett Cooper wrote: >>>> >>>>>> I think I just found a good "recovery" idea -- I should disable the >>>>>> features with rescue builds. =A0That should give one a working >>>>>> /rescue/ifconfig in all cases and should be sufficient to recover? >>>>> >>>>> =A0That would be a good backup plan so people could at least avoid >>>>> painting themselves into a corner by accident. >>>> >>>> Can you confirm that >>>> http://people.freebsd.org/~bz/20110608-02-ifconfig-rescue.diff >>>> would work for you? >>>> >>>> One will still be screwed if doing it remotely without serial console = or >>>> keyb access, but with that there should be a way to recover. =A0Note t= hat >>>> the rc scripts also check the AF to be present and will not configure = them >>>> if not. >>> >>> Will do when I get back home. I rebuilt world and kernel a few times, r= einstalled, and I'm still running into the same issues (kern.features.inet = is missing), so something is really funky with the system. >>> >>> I'll look at my last buildkernel log, an if that doesn't turn up anythi= ng helpful try building GENERIC tonight and boot it to see what happens.. >>> >>> I'll let you know how the patch goes.. >> >> check with strings if you can find a __kern_features_inet > > =A0 =A0Is that the right string to look for? All I found was > sysctl__kern_features_children (despite the fact that I do actually > have OIDs hanging off of kern.features). > =A0 =A0BTW, objdump -x /boot/kernel/kernel | grep __kern_features_ turned > up a lot more data, but unfortunately inet isn't one of the missing > pieces between strings and objdump -x :/.. > =A0 =A0I checked opt_global.h and opt_inet.h and #define INET 1 is > present in opt_inet.h at least.. Nothing apparently fishy in the > buildkernel log either... but why isn't it pulling in headers from -I@ > or ${KERNBUILDDIR} (!). Also, why is /sys/conf/*.mk blantantly > ignoring my CFLAGS (I hardcoded /usr/obj/usr/src/sys/FALLOUT just for > kicks and it was clearly omitted from the cc calls I saw)?? I haven't > dug down that deep yet, but it would be interesting if someone knew > the answer to that question offhand. > =A0 =A0Just for grins I put... > > #ifndef INET > #error "you lose!" > #endif > > =A0 =A0... in in_proto.c and it didn't bail. So obviously it thinks it > has INET support. > =A0 =A0Time to try GENERIC. A fresh tree exhibited the problem as well with my custom KERNCONF (which has INET and INET6 support compiled in), whereas GENERIC with the same src.conf doesn't. I diff reduced my custom KERNCONF a bit with GENERIC and it's still not working (I stripped a bunch of unneeded drivers out of the configuration and load a handful as modules, e.g. aio, if_re, linux*), and still ran into problems. I wiped out /boot/$INSTKERNNAME and /boot/kernel (for some reason the symlink I setup wasn't there.. hmm). So I'll need to dig through the installkernel target in a bit to figure out why things weren't sane. Overall, this case is now closed. I'll post more findings in another thread when I find out why stuff was broken, if it wasn't a trivial PEBKAC issue. Thanks, -Garrett