Re: Clock issues and crash on resume on 10-Stable r263062M

On Thu, Mar 27, 2014 at 11:53 PM, Aleksandr Rybalko <ray@ddteam.net> wrote:

> On Thu, 27 Mar 2014 17:52:06 -0700
> Kevin Oberman <rkoberman@gmail.com> wrote:
>
> > On Thu, Mar 27, 2014 at 7:16 AM, Aleksandr Rybalko <ray@ddteam.net>
> > wrote:
> >
> > > On Wed, 19 Mar 2014 08:54:42 -0700
> > > Kevin Oberman <rkoberman@gmail.com> wrote:
> > >
> > > > On Wed, Mar 19, 2014 at 5:19 AM, Aleksandr Rybalko
> > > > <ray@ddteam.net>
> > > wrote:
> > > >
> > > > > On Tue, 18 Mar 2014 21:07:57 -0700
> > > > > Adrian Chadd <adrian@freebsd.org> wrote:
> > > > >
> > > > > > Well, changing the default is cool, but there's still some
> > > > > > odd bug there that could do with chasing down. :)
> > > > >
> > > > > Sorry, I currently can't work on investigation why GIANT lock
> > > > > is NULL sometime on resume. (IIRC it happen because I use
> > > > > callout_init w/o mtx, so callout try to lock using GIANT)
> > > > >
> > > > > But I will glad to get any help on that :)
> > > > >
> > > > >
> > > > Turned off vt switch and found a couple issues:
> > > >
> > > > 1. Audio was muted  (by pressing the mute button) when I
> > > > suspended the system. The suspend operation caused the system to
> > > > beep. When I resumed,
> > > it
> > > > did so again and I noticed that the audio was no longer muted.
> > > > This can
> > > be
> > > > an issue when in a meeting or in some other place where a loud
> > > > noise is
> > > not
> > > > desirable, but my be an issue with the Lenovo BIOS or EC.
> > > >
> > > > 2. When the system is resumed, the display is not refreshed and
> > > > is full
> > > of
> > > > artifacts.I moved to another desktop and back (I use gnome2) and
> > > > fixed everything except the panel which never gets redrawn. This
> > > > is possibly
> > > an X
> > > > issue (Intel 3000 graphics) or something with the KMS handling of
> > > > a
> > > resume.
> > > >
> > > > Probably neither of these is really a vt(4) issue, though, an I
> > > > really do appreciate having a working vty system after starting X.
> > > > --
> > > > R. Kevin Oberman, Network Engineer, Retired
> > > > E-mail: rkoberman@gmail.com
> > >
> > > Kevin,
> > >
> > > I was already describe possible culprits of Xorg screen puzzling
> > > after resume, there is two possible candidates:
> > > 1. mishandling of system PM events by Xorg.
> > > 2. something wrong inside drm2+drm/kms drivers.
> > >
> > > but things #1 in your list points more to mishandling of PM events.
> > >
> > > btw, crash with suspendswitch=1 looks like fixed :)
> > >
> > > Thanks!
> > >
> > > WBW
> > > --
> > > Aleksandr Rybalko <ray@ddteam.net>
> > >
> >
> >
> > Thanks for getting this running.
> >
> > FWIW, I realized that switching to a vty and back to X takes care of
> > he messed up display. Do you know when the crash was fixed? I am
> > running r263692 and it still crashes. (Typo in sysctl.conf.)
>
> it was in r263809
>
> >
> > --
> > R. Kevin Oberman, Network Engineer, Retired
> > E-mail: rkoberman@gmail.com
>

Missed it by THAT much! (Possibly humor only recognized in American
culture.) Guess I need to rebuild my kernel!

Thanks again! It's great to have vtys back.

By the way, is there a way to increase the size of the scrollback buffer?

--
> Aleksandr Rybalko <ray@ddteam.net>
>

-- 
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkoberman@gmail.com
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"