From owner-freebsd-stable@FreeBSD.ORG Thu May 22 15:49:51 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1544DC09 for ; Thu, 22 May 2014 15:49:51 +0000 (UTC) Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173]) by mx1.freebsd.org (Postfix) with ESMTP id C24A12F60 for ; Thu, 22 May 2014 15:49:50 +0000 (UTC) Received: from lowell-desk.lan (lowell-desk.lan [172.30.250.41]) by be-well.ilk.org (Postfix) with ESMTP id E2B9033C48 for ; Thu, 22 May 2014 11:49:38 -0400 (EDT) Received: by lowell-desk.lan (Postfix, from userid 1147) id 15FF93984E; Thu, 22 May 2014 11:49:36 -0400 (EDT) From: Lowell Gilbert Cc: freebsd-stable@freebsd.org Subject: Re: strange svn problem on FreeBSD 10 STABLE References: <20140522144628.72655b16@X220.alogt.com> Reply-To: freebsd-stable@freebsd.org Date: Thu, 22 May 2014 11:49:36 -0400 In-Reply-To: <20140522144628.72655b16@X220.alogt.com> (Erich Dollansky's message of "Thu, 22 May 2014 14:46:28 +0800") Message-ID: <44fvk1q0dr.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2014 15:49:51 -0000 Erich Dollansky writes: > Hi, > > I ran svn and get this as a result: > > Updating the source tree. > Updating '/usr/src': > At revision 266536. > > So, it all should be fine. > > When I compile then the kernel, I will get this: > > -------------------------------------------------------------- >>>> Kernel build for X220 started on Thu May 22 14:41:52 WITA 2014 > -------------------------------------------------------------- > ===> X220 > mkdir -p /usr/obj/usr/src/sys > > -------------------------------------------------------------- >>>> stage 1: configuring the kernel > -------------------------------------------------------------- > cd /usr/src/sys/amd64/conf; > PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/legacy/bin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin > config -d /usr/obj/usr/src/sys/X220 /usr/src/sys/amd64/conf/X220 > WARNING: duplicate option `NEW_PCIB' encountered. WARNING: duplicate > option `GEOM_PART_BSD' encountered. WARNING: duplicate option > `GEOM_PART_MBR' encountered. WARNING: duplicate option `GEOM_PART_EBR' > encountered. WARNING: duplicate option `GEOM_PART_EBR_COMPAT' > encountered. WARNING: duplicate option `DEV_ISA' encountered. WARNING: > duplicate device `isa' encountered. WARNING: duplicate option `DEV_MEM' > encountered. WARNING: duplicate device `mem' encountered. > WARNING: duplicate option `DEV_IO' encountered. > WARNING: duplicate device `io' encountered. > config: Error: device "vt" is unknown > config: Error: device "vt_vga" is unknown > config: 2 errors > *** Error code 1 > > Stop. > make[1]: stopped in /usr/src > *** Error code 1 > > Stop. > make: stopped in /usr/src > > There was a kernel with VT enabled installed on this machine. Ok, I > could imagine where the warnings come from but why is VT not part of > the latest revision? > > Is there a problem with my local copy? There have been some > interruptions during the download. Vaguely possible. However, my guess would be that you've changed the branch you're pulling the sources from, or the kernel configuration, or both. The vt driver is fairly new, so you need a reasonably recent 10.x or higher source tree to have it available. So: my advice. (1) check what you have for sources: "svn info" will tell you, and "svn status" will tell you if you have changed any files in the tree. Look at the output carefully for hints of problems. If svn reports problems with its database, try "svn cleanup". (2) If your svn tree isn't tracking the branch that you intend to, fix that. It looks like stable/10 or mainline head are good targets for using the vt console device right now, although I may well be wrong on that. (3) Try building the GENERIC and VT kernels rather than your custom kernel. If they build, then your custom kernel configuration is the problem, and you can either reconfigure that or just use one of the standard ones you just built. If they don't build, you will at least get much clearer indications of the problem. [Don't use -j with the make command.] (4) Make sure you're following the recommended upgrade path. I probably could have been a lot more help if you'd included the output of "uname -a" and "svn info" in your message. And your kernel configuration file, although even better than that would be trying the GENERIC configuration and showing the results of that. Good luck.