From owner-freebsd-stable@FreeBSD.ORG Fri Mar 28 00:52:07 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 1EBF5514; Fri, 28 Mar 2014 00:52:07 +0000 (UTC) Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D1C8369; Fri, 28 Mar 2014 00:52:06 +0000 (UTC) Received: by mail-pa0-f51.google.com with SMTP id kq14so4266775pab.10 for ; Thu, 27 Mar 2014 17:52:06 -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=nQbpuLxtg9ohM/fsZfN4qXQB/e+jtvKEFwn3uDUhll0=; b=a4XJPbIMBiJ40UH52rDYaRAwW3aU88Yxzi09LtT8+kqQQmINRbTDYGUJf0f5ES2MK6 EAOFPrIu4BtzVxqEt5aIA/boqh8N2HzsJ8g3x/TmwYirQ36hhHaPIN8mU/csek9e9Hgl o5WceyGmX/KPy4p6py4MfFPiLF/apKMQHdnwbBZxbh2ywqudi/JFp7WLb1493U3aex0Q kCqqcBQY4sVKNCeMXmBXSCUQIyQCmCd6W+H61lH+JmtY57qVqdk9vjJ1zQiFEaFVT59O iom+yH2FKe3NynUaIUPniIL/qBVl+kTqwaLeS9Q3JaV+i5se5BxOXWQYfcKda1ct+qtv 1OiQ== MIME-Version: 1.0 X-Received: by 10.66.156.137 with SMTP id we9mr5250147pab.30.1395967926456; Thu, 27 Mar 2014 17:52:06 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.66.0.164 with HTTP; Thu, 27 Mar 2014 17:52:06 -0700 (PDT) In-Reply-To: <20140327161602.02607ae3a6483bbb984eb367@ddteam.net> References: <201403181527.17100.jhb@freebsd.org> <20140318234623.61a99182.ray@ddteam.net> <20140319141924.279e3d1bc7d8be7b93470a5d@ddteam.net> <20140327161602.02607ae3a6483bbb984eb367@ddteam.net> Date: Thu, 27 Mar 2014 17:52:06 -0700 X-Google-Sender-Auth: OjZVKmOn6DSpPTF5e8XiM9AgEO4 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: Fri, 28 Mar 2014 00:52:07 -0000 On Thu, Mar 27, 2014 at 7:16 AM, Aleksandr Rybalko wrote: > On Wed, 19 Mar 2014 08:54:42 -0700 > Kevin Oberman wrote: > > > 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 > > 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 > 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.) -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com