From owner-freebsd-stable@FreeBSD.ORG Wed Apr 18 01:19:39 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0C30E106566B; Wed, 18 Apr 2012 01:19:39 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mx.nsu.ru (r2b9.nsu.ru [212.192.164.39]) by mx1.freebsd.org (Postfix) with ESMTP id A1B158FC08; Wed, 18 Apr 2012 01:19:38 +0000 (UTC) Received: from regency.nsu.ru ([193.124.210.26]) by mx.nsu.ru with esmtp (Exim 4.69) (envelope-from ) id 1SKJXj-0007fA-1F; Wed, 18 Apr 2012 08:18:47 +0700 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.14.2/8.14.2) with ESMTP id q3I1LcWN012697; Wed, 18 Apr 2012 08:21:38 +0700 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.14.2/8.14.2/Submit) id q3I1LHlt012676; Wed, 18 Apr 2012 08:21:17 +0700 (NOVT) (envelope-from danfe) Date: Wed, 18 Apr 2012 08:21:16 +0700 From: Alexey Dokuchaev To: John Baldwin Message-ID: <20120418012116.GA11023@regency.nsu.ru> References: <20120416042645.GA53074@regency.nsu.ru> <20120416070646.GA78414@regency.nsu.ru> <4F8BD14D.8050206@rdtc.ru> <201204170840.37631.jhb@freebsd.org> <20120417144643.GB70796@regency.nsu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120417144643.GB70796@regency.nsu.ru> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org, Eugene Grosbein Subject: Re: RELENG_8 kernel as of Apr 14 does not boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Apr 2012 01:19:39 -0000 On Tue, Apr 17, 2012 at 09:46:43PM +0700, Alexey Dokuchaev wrote: > I've just tried to zzz/resume several times in a row with latest 8.x > kernel with io/mem compiled in. Maybe I am speaking too fast, but guess > what: keyboard works now, network service are accessible, bluetooth mouse > works, etc. Unbelievable. My stupid "nodevice" gimmick prevented me from > having working resume, LOL. Alas, fresh reboot -- and it all as bad as before. Need to debug more... ./danfe