From owner-freebsd-current@FreeBSD.ORG Thu Feb 21 15:50:11 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 C3B08FF8 for ; Thu, 21 Feb 2013 15:50:11 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id A2FA7F40 for ; Thu, 21 Feb 2013 15:50:11 +0000 (UTC) Received: from pakbsde14.localnet (unknown [38.105.238.108]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 1F069B911; Thu, 21 Feb 2013 10:50:11 -0500 (EST) From: John Baldwin To: freebsd-current@freebsd.org, Xin Li Subject: Re: -CURRENT userland regression Date: Thu, 21 Feb 2013 10:31:31 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <51254ACE.2030100@delphij.net> <51254C7E.9050705@gmail.com> In-Reply-To: <51254C7E.9050705@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201302211031.31599.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 21 Feb 2013 10:50:11 -0500 (EST) Cc: 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 15:50:11 -0000 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? -- John Baldwin