Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 Mar 2014 11:41:48 +0200
From:      Aleksandr Rybalko <ray@freebsd.org>
To:        John Baldwin <jhb@freebsd.org>
Cc:        svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org
Subject:   Re: svn commit: r263321 - head/sys/dev/vt
Message-ID:  <20140327114148.3368cea00ad2a0994315c5b0@freebsd.org>
In-Reply-To: <201403191453.47690.jhb@freebsd.org>
References:  <201403182222.s2IMMmOM081929@svn.freebsd.org> <201403191453.47690.jhb@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 19 Mar 2014 14:53:47 -0400
John Baldwin <jhb@freebsd.org> wrote:

> On Tuesday, March 18, 2014 6:22:48 pm Aleksandr Rybalko wrote:
> > Author: ray
> > Date: Tue Mar 18 22:22:47 2014
> > New Revision: 263321
> > URL: http://svnweb.freebsd.org/changeset/base/263321
> > 
> > Log:
> >   Switch kern.vt.suspendswitch to 0 by default (disabled).
> >   kern.vt.suspendswitch - sysctl/tunable which enable switch to VT0 before going
> >   to suspend and switch back after resume.
> >   
> >   MFC after:	7 days
> 
> I think it is fine to change the default, but I'm not certain that this fixes
> the panics on resume.  So far no one has reported back that this did fix them
> after I suggested it.  It would be good to fix the panics as well if possible.
> The last time I looked at it in detail, it seemed like the callout for only
> ttyv0 had been zero'd.  Other ttyv timers used in switching still had the correct
> contents.
> 
> -- 
> John Baldwin

Yeah, thanks for pointing on it. Your hint about ttyv0 point to the
difference between ttyv0 and others. Window structure for VT1 defined
statically for early stage drivers (like vt_vga), so I forget to
initialize callout for that window :)

Now it was fixed by r263809.

And since we still have problem with puzzling Xorg screen after
suspend/resume - I will revert this commit.

My research on that problem (puzzling Xorg screen) point on two
possible problems:
1. maybe Xorg lack of APM module, or it is broken somehow.
2. maybe problem in drm2, so Xorg's framebuffer rearranged by drm2, but
Xorg don't know about that.

Many thanks!

WBW
-- 
Aleksandr Rybalko <ray@freebsd.org>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140327114148.3368cea00ad2a0994315c5b0>