Date: Wed, 19 Mar 2014 08:54:42 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Aleksandr Rybalko <ray@ddteam.net> Cc: Adrian Chadd <adrian@freebsd.org>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>, Aleksandr Rybalko <ray@freebsd.org>, John Baldwin <jhb@freebsd.org> Subject: Re: Clock issues and crash on resume on 10-Stable r263062M Message-ID: <CAN6yY1uUuEytGS_TOWfxS92JLmYkJ6%2Badrx1zEbPGHoOJwdLJA@mail.gmail.com> In-Reply-To: <20140319141924.279e3d1bc7d8be7b93470a5d@ddteam.net> References: <CAN6yY1seOSacdXY3RKOgEdY_v%2BzD=vqMAfnsXH96Ft8w%2BOoJew@mail.gmail.com> <201403181527.17100.jhb@freebsd.org> <CAN6yY1tGaEwQ9cxii9F6ub2c=UD-wdrDRKT_LtZsBrGyDb%2B0nw@mail.gmail.com> <20140318234623.61a99182.ray@ddteam.net> <CAJ-VmondROfMX=7A7FCsr_e=vV75phnsnDz7TG0K6UhX6a=R7A@mail.gmail.com> <20140319141924.279e3d1bc7d8be7b93470a5d@ddteam.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1uUuEytGS_TOWfxS92JLmYkJ6%2Badrx1zEbPGHoOJwdLJA>