From owner-freebsd-current@FreeBSD.ORG Thu Feb 21 17:51:37 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0E895E06; Thu, 21 Feb 2013 17:51:37 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from hammer.pct.niksun.com (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 835FBAE6; Thu, 21 Feb 2013 17:51:36 +0000 (UTC) Message-ID: <51265E39.2070109@FreeBSD.org> Date: Thu, 21 Feb 2013 12:49:45 -0500 From: Jung-uk Kim User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130220 Thunderbird/17.0.3 MIME-Version: 1.0 To: John Baldwin Subject: Re: -CURRENT userland regression References: <51254ACE.2030100@delphij.net> <51254C7E.9050705@gmail.com> <201302211031.31599.jhb@freebsd.org> In-Reply-To: <201302211031.31599.jhb@freebsd.org> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Xin Li , Navdeep Parhar X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Thu, 21 Feb 2013 17:51:37 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-02-21 10:31:31 -0500, John Baldwin wrote: > On Wednesday, February 20, 2013 5:21:50 pm Navdeep Parhar wrote: >> On 02/20/13 14:14, Xin Li wrote: >>> Hi, >>> >>> It seems that fresh -HEAD would give an unusable kernel that >>> overwrites screen buffer in a way making it impossible to >>> debug. Using an old world source to do 'make buildworld >>> buildkernel' results in a (mostly: I have some strange USB >>> issue right now and still looking for the cause) usable >>> kernel. >>> >>> For now my known good combination is world 246858 with kernel >>> 247057. I'm still trying to find out which revision have broke >>> the stuff. >> >> I ran into this earlier today. Selecting "safe mode" in the boot >> loader menu seems to work around the problem on my system. Now I >> will not reboot until I see a fix for this in head :-) > > "safe mode" toggles a few different things IIRC, can you narrow it > down to a single setting? kern.smp.disabled=1 Jung-uk Kim -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJRJl45AAoJECXpabHZMqHO/I0IALhqfW2uSY+IoCOvtSN7eQGM IRmzRiFtoz7sXb5OiNlHjwZdRcQR4t6656EUyItDjr3XbXvnGaNL/nk+B9moSgSi NmHpEWQ4yNTJKYUAnvw4NGHKkiOpmNsrAA5i8EEQQesQGuwke0eYaeHMb5R5Wvsu lyWTB0ZH1XV8VehvTir3vo7MWaGjYYp8l09YpaDUYTpn364Fx+jBgsG5qKWdrHMn l/TwMLmWB6Mij2K8+FeS9PIijFKhaTh2s5xa1/xX3vFuR0mhMfNm7OfadXy1KKsL YcTm4Q0QYDkfoxwoS6+AWKVk1LMrF8vah8kHalKp5JCtNv3p1jr5RupalYI9zgo= =1D9R -----END PGP SIGNATURE-----