Re: newcons comming

From: John Baldwin <jhb_at_freebsd.org>
Date: Tue, 11 Feb 2014 13:04:29 -0500
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_at_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
Received on Tue Feb 11 2014 - 18:49:34 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:46 UTC