Date: Wed, 20 Feb 2013 14:56:50 -0800 From: Navdeep Parhar <nparhar@gmail.com> To: Konstantin Belousov <kostikbel@gmail.com> Cc: Xin Li <delphij@delphij.net>, FreeBSD Current <freebsd-current@freebsd.org>, d@delphij.net Subject: Re: -CURRENT userland regression Message-ID: <512554B2.3070601@gmail.com> In-Reply-To: <20130220224732.GV2598@kib.kiev.ua> References: <51254ACE.2030100@delphij.net> <51254C7E.9050705@gmail.com> <20130220222518.GT2598@kib.kiev.ua> <51254F33.5060904@gmail.com> <20130220224732.GV2598@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/20/13 14:47, Konstantin Belousov wrote: > On Wed, Feb 20, 2013 at 02:33:23PM -0800, Navdeep Parhar wrote: >> On 02/20/13 14:25, Konstantin Belousov wrote: >>> On Wed, Feb 20, 2013 at 02:21:50PM -0800, 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 :-) >>> >>> How much 'the earlier today' is ? >>> I.e., could you specify some revisions ? >>> >> >> I upgraded from a month old (approx.) head to r247054 and ran into this >> problem. I haven't tried bisecting as I need a running system right now. > > BTW, does the loader fails, or is it the kernel where the problems start > appearing ? > The problem occurs well after the kernel is up and running. The last messages that were readable were from ugen/uhub and ada0. The rest was garbled and the system froze solid something after that. I tried pinging it but it wasn't reachable so this wasn't a case where the console was trashed but system was running. This is amd64 built with clang. I have dual consoles - serial and VGA. FreeBSD trantor 10.0-CURRENT FreeBSD 10.0-CURRENT #26: Wed Feb 20 13:18:48 PST 2013 root@trantor:/usr/obj/usr/src/sys/TOEKTR amd64 Regards, Navdeep
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?512554B2.3070601>