From owner-freebsd-current@FreeBSD.ORG Wed Mar 4 23:16:56 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E40F8E92 for ; Wed, 4 Mar 2015 23:16:56 +0000 (UTC) Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A4E52187 for ; Wed, 4 Mar 2015 23:16:56 +0000 (UTC) Received: by igdh15 with SMTP id h15so41268287igd.3 for ; Wed, 04 Mar 2015 15:16:56 -0800 (PST) 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=erhUQNPlvBNrkiqEv7BLM1/lghbX1rPduUn3SW/0bXE=; b=lfXSDVP0E+HuAp1jkn3RWPTxYcsrChh0yqfgSslCZCqs3iXxmvlhCagZ0ikHgLXhw4 FphjRGWQ6Ote0mbm0SN64PvqZwqnBDcFsw/S5r48qYbLMCX2DxF0XDa1WSlyqs7xV1Yc eNcGoKnkxZFLkqRpfMM3djK3NHWWLriCsfs1mgcNCCKfTC/6gJKDqTPdldblRLyGUWFD aOZNUBceAtltDxe8gjsBKcFnygjxMODCZZu201j9J2yDzd5kaOpUoRgc7aqeI4a48Vpu tNh6xegI+kZL/Ne8h1pOroccK6NSn2vb+YOoloHFaSwVW1VNVqU8Wz9XPbD2z1AI2nS3 RiOA== MIME-Version: 1.0 X-Received: by 10.50.30.202 with SMTP id u10mr42189621igh.35.1425511015807; Wed, 04 Mar 2015 15:16:55 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.107.174.86 with HTTP; Wed, 4 Mar 2015 15:16:55 -0800 (PST) In-Reply-To: <20150304184757.3679a5b5@rsbsd.rsb> References: <20150227183143.708a0656@rsbsd.rsb> <20150227195346.78dbbca9@rsbsd.rsb> <20150304184757.3679a5b5@rsbsd.rsb> Date: Wed, 4 Mar 2015 15:16:55 -0800 X-Google-Sender-Auth: L9hZI2svC9nUrPX4fn852zO8Sj8 Message-ID: Subject: Re: system failure: cannot kill webkit-gtk3 if using dumbell/radeon From: Kevin Oberman To: Beeblebrox Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Mar 2015 23:16:57 -0000 On Wed, Mar 4, 2015 at 8:47 AM, Beeblebrox wrote: > Hi. > > Sorry for the delay to get back to you (including your private emails). > Not a problem, those were various reports left to your judgment as to > their significance. Better to provide more information rather than less. > > slim failure: Traced to dbus start failure at bootup. Slim now starts, > after manual start of dbus. > GDM failure: Starts, but after taking a long time. I'll send Koop the log > files from my recent attempt. > > > You mentioned "ghost text" with nano in vt(4). Could you please file > > a bug in Bugzilla with a picture of what you get? Please join a dmesg > too. > I can confirm this is still an issue. I'll try to get to it at the soonest. > > > the unkillable processes are interesting. If you can reproduce > I really don't know how it came about, so no promises. The most > interesting part of that error however, was the behaviour of vt(4). The > problem is not only unkillable processes, but TTY freeze when doing an > unrelated action to the locked process. I mean, nano or top have nothing to > do with webkit-gtk3, yet caused TTY freeze (due to GPU lock-up I ignorantly > presume) > > > the flickering you see with some applications/desktop environments > This is really serious. It has lessened, but not gone away. > Additionally, I started to get a "sticky mouse" problem some time ago > and I'm inclined to agree with HPS' assessment that "drm2.ko graphics > driver has some hard spinning loops" ( > http://freebsd.1045724.n5.nabble.com/Some-unresolved-but-important-X-org-problems-td5987904.html > ) > Have not had the hardware to test with different GPU unfortunately. > > Regards. > > This sounds a lot like another rcorder issue. If you run "rcorder /etc/rc.d/* /usr/locl/rtc/rc.d/* > /dev/null", do you get errors... particularly circular dependencies? I know that webcamd and dbus have a problem. These are very dangerous as the behavior when they occur is undefined, very unstable and can easily result in daemons failing to start. They are also a real pain to track down. Most often just looking at "REQUIRES" and "BEFORE" statements is not very useful. Note that reports of "no providers" are warnings and often normal and expected. -- Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com