Date: Tue, 11 Feb 2014 13:04:29 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: Aleksandr Rybalko <ray@freebsd.org>, Adrian Chadd <adrian@freebsd.org> Subject: Re: newcons comming Message-ID: <201402111304.29840.jhb@freebsd.org> In-Reply-To: <20140211155043.6900fe11aaa717f7bca781df@freebsd.org> References: <20131025151847.2a1b83de93335040797ceaf1@ddteam.net> <CAJ-VmokW4hSmNyXSK8f2p3kKwJz3iUr%2BBqzjDB6vywjH65_0SQ@mail.gmail.com> <20140211155043.6900fe11aaa717f7bca781df@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <adrian@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201402111304.29840.jhb>