From owner-freebsd-current@FreeBSD.ORG Tue Feb 11 19:49:34 2014 Return-Path: Delivered-To: freebsd-current@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 57893E6D; Tue, 11 Feb 2014 19:49:34 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2D8F41993; Tue, 11 Feb 2014 19:49:34 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 065A1B981; Tue, 11 Feb 2014 14:49:33 -0500 (EST) From: John Baldwin To: freebsd-current@freebsd.org Subject: Re: newcons comming Date: Tue, 11 Feb 2014 13:04:29 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <20131025151847.2a1b83de93335040797ceaf1@ddteam.net> <20140211155043.6900fe11aaa717f7bca781df@freebsd.org> In-Reply-To: <20140211155043.6900fe11aaa717f7bca781df@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201402111304.29840.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 11 Feb 2014 14:49:33 -0500 (EST) Cc: Aleksandr Rybalko , Adrian Chadd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Tue, 11 Feb 2014 19:49:34 -0000 On Tuesday, February 11, 2014 8:50:43 am Aleksandr Rybalko wrote: > Hi Adrian! > > On Mon, 10 Feb 2014 13:24:18 -0800 > Adrian Chadd wrote: > > > [snip] > > > > My experiences with newcons/drm2: > > > > * suspend/resume occasionally throws up a panic in the softclock code, > > with some vaguely invalid looking newcons timer entry. THis happens > > after it comes out of suspend, after af ew seconds. It sucks and makes > > things rather unusable. > > Are you have some data to investigate who is culprit? > You can try also kernel with syscons, of course console will be black > after kms load, but you still able to input commands. I had this for the first time yesterday. It is the timer used for vt switching. c_lock inside the callout structure for ttyv0 is trashed and points to NULL instead of &Giant. Adrian, you should try setting kern.vt.suspendswitch=0 to see if that helps. -- John Baldwin