From owner-freebsd-stable@FreeBSD.ORG Wed Mar 19 15:54:43 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0D262D95; Wed, 19 Mar 2014 15:54:43 +0000 (UTC) Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C2D7FA20; Wed, 19 Mar 2014 15:54:42 +0000 (UTC) Received: by mail-pb0-f47.google.com with SMTP id up15so9044895pbc.6 for ; Wed, 19 Mar 2014 08:54:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=xuIIcP9hG1B1LXePVeWdeb7ndsny8tBACLk1tS4t6RE=; b=zPF+GI75cYu59nB+dA2yiOu2uNl6weddHcC8XDFAWoj7CKP4t7A2iwGsjeJQj0H/vy JkC6Ny9gy2tsIzcqazA3/aO8sVa7FjaiCmnczRV8gilFKQ2t+zY7Ho+je4SdcXt6vqXE QugJ2H9COXtqpGebg7ZFNKQ3ZV8T0L7ChIB5SaKLTfrvMr2MAVaOeCLMx22Zc/4ORanb E7Fi5WRNJg8dmy8a+J6TSO2xh7TI0qZ5htXQi347S/GIWBeKrwuI27gp+uREp47FWX0D RuDTxoXlr7beJC2s4jru5C1WX7/FqECF5WtKtH7XLsraHAlP/r8FjLgHHPL/TPewDact l/9g== MIME-Version: 1.0 X-Received: by 10.66.156.137 with SMTP id we9mr41370053pab.30.1395244482405; Wed, 19 Mar 2014 08:54:42 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.66.0.164 with HTTP; Wed, 19 Mar 2014 08:54:42 -0700 (PDT) In-Reply-To: <20140319141924.279e3d1bc7d8be7b93470a5d@ddteam.net> References: <201403181527.17100.jhb@freebsd.org> <20140318234623.61a99182.ray@ddteam.net> <20140319141924.279e3d1bc7d8be7b93470a5d@ddteam.net> Date: Wed, 19 Mar 2014 08:54:42 -0700 X-Google-Sender-Auth: dvQKsauiTBLRH0nQCFux46GVCfs Message-ID: Subject: Re: Clock issues and crash on resume on 10-Stable r263062M From: Kevin Oberman To: Aleksandr Rybalko Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: Adrian Chadd , FreeBSD-STABLE Mailing List , Aleksandr Rybalko , John Baldwin X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Mar 2014 15:54:43 -0000 On Wed, Mar 19, 2014 at 5:19 AM, Aleksandr Rybalko wrote: > On Tue, 18 Mar 2014 21:07:57 -0700 > Adrian Chadd 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