From owner-freebsd-stable@FreeBSD.ORG Fri Mar 28 06:54:16 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 3E603846 for ; Fri, 28 Mar 2014 06:54:16 +0000 (UTC) Received: from mail-ee0-f42.google.com (mail-ee0-f42.google.com [74.125.83.42]) (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 C06342B9 for ; Fri, 28 Mar 2014 06:54:15 +0000 (UTC) Received: by mail-ee0-f42.google.com with SMTP id d17so3694545eek.1 for ; Thu, 27 Mar 2014 23:54:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=N5EFYBfpDI1JiSeVSpOlPq68YgV2G0wiiqnZenw3JC0=; b=aP5fZgWk3VhsN6d0nPMloBqCEZhmSDxOzLZeBIUmGgmUebMgTs24UZbMc3Ug9jHNs+ Z+fP562t3yqbkMe3WwoOEHfq6eDBkH6IWcHNvmgRg1YIp/HQh8tolD7uZCRTPIcvu9LK vVw7ce+XbJsaMkcgWw93BYkS+6/EcpBANsb71H3RsEv+VoPfF9SUMr6NV8wREpDvFtAn +05C5p5C/F176AE3XfboQNMncISU6tSBT+SHbq0WPnH2MNv+0sE4uBzcicbrhslIi0mB P311s3SM4dU4lImfaOvjzQVBxh6H39aDpmOWaaFYN0bTPtDEtb5iWoxZNMm/z5X8nAqC gbKQ== X-Gm-Message-State: ALoCoQlcleWcUku4vX9pQHsI7Rno8f8/8qps4c/h7JJIJPzrqfwZainw+93FGgnNrMHAEDhT3zHY X-Received: by 10.14.214.198 with SMTP id c46mr7753460eep.29.1395989647958; Thu, 27 Mar 2014 23:54:07 -0700 (PDT) Received: from rnote.ddteam.net (208-30-133-95.pool.ukrtel.net. [95.133.30.208]) by mx.google.com with ESMTPSA id u1sm9506273eex.31.2014.03.27.23.54.05 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 27 Mar 2014 23:54:06 -0700 (PDT) Date: Fri, 28 Mar 2014 08:53:40 +0200 From: Aleksandr Rybalko To: Kevin Oberman Subject: Re: Clock issues and crash on resume on 10-Stable r263062M Message-Id: <20140328085340.5395a698.ray@ddteam.net> In-Reply-To: References: <201403181527.17100.jhb@freebsd.org> <20140318234623.61a99182.ray@ddteam.net> <20140319141924.279e3d1bc7d8be7b93470a5d@ddteam.net> <20140327161602.02607ae3a6483bbb984eb367@ddteam.net> X-Mailer: Sylpheed 3.1.2 (GTK+ 2.24.5; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 06:54:16 -0000 On Thu, 27 Mar 2014 17:52:06 -0700 Kevin Oberman wrote: > 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.) it was in r263809 > > -- > R. Kevin Oberman, Network Engineer, Retired > E-mail: rkoberman@gmail.com -- Aleksandr Rybalko