From owner-freebsd-stable@FreeBSD.ORG Sun Oct 27 06:11:47 2013 Return-Path: Delivered-To: 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 ESMTP id 5568EBB8 for ; Sun, 27 Oct 2013 06:11:47 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pb0-x22b.google.com (mail-pb0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2B48328A8 for ; Sun, 27 Oct 2013 06:11:47 +0000 (UTC) Received: by mail-pb0-f43.google.com with SMTP id md4so670367pbc.30 for ; Sat, 26 Oct 2013 23:11:46 -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=bjCsgX83iis3iVM9bVQHiqShjq7S/V/TyIO4uHR8+E4=; b=1KPWErrVccDeqDCkJRGHgUjClohumun1GA0IebHO1rPQz5xtUNhc2rQEX3dx2j5kPn Ietv4H62n2qAnwlhRsKlHUZ/lmWMPjLJkVI1fH11K8pOpwHDjvm4LuU76wp1NhfxCHCn /YJjNLmsFdRxn9Q2hXVEpEI8i9fCQPLWNnq5lDrVrz9gXHgiSTiwtAUVK1ImI3ujnfGC TfxpdoIqz8aPKDy0lVMHrSLnsfGEdMq3gd5lDiUiJ8OxWmvAJfFf7vcn9iW3sILC2de5 JOGo9GEEGrpy7MKjBKr3RbxqXvqwaV7hqFsPtCpwZMpiVnjXvW/qlq9ZUcXChIH2S7Ma mluA== MIME-Version: 1.0 X-Received: by 10.66.146.199 with SMTP id te7mr19270983pab.106.1382854306806; Sat, 26 Oct 2013 23:11:46 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.67.23.101 with HTTP; Sat, 26 Oct 2013 23:11:46 -0700 (PDT) In-Reply-To: References: <20131027011829.GA98327@lyxys.ka.sub.org> Date: Sat, 26 Oct 2013 23:11:46 -0700 X-Google-Sender-Auth: x8gTNqj81k-6KiiePnhid3mfNHc Message-ID: Subject: Re: x11 hangs unkillable on 10.0-BETA1 From: Kevin Oberman To: "illoai@gmail.com" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Oct 2013 06:11:47 -0000 On Sat, Oct 26, 2013 at 10:23 PM, illoai@gmail.com wrote= : > On 27 October 2013 01:10, Kevin Oberman wrote: > > On Sat, Oct 26, 2013 at 9:31 PM, illoai@gmail.com > wrote: > >> > >> On 26 October 2013 21:18, Wolfgang Zenker > >> wrote: > >> > Testing 10.0-BETA1 on an old IBM T42p Laptop, after a while Xorg > starts > >> > to use 100% CPU, stops to update the screen and does not accept any > >> > input anymore. I can still work from remote via ssh; top shows Xorg > >> > using > >> > up 100% CPU most of the time. Trying to kill or even kill -9 the Xor= g > >> > process does not result in an error message but fails to terminate t= he > >> > process. > >> > > >> > What information would be helpful to debug this? > >> > > >> > >> Screams of the tormented? Basically, I debug [X] by disabling > >> features until it doesn't lock up, & then I use those settings until > >> it causes lockups (from updates). > >> > >> mplayer would reliably lock Xorg if I used (or allowed) vo=3Dsdl > >> or higher (gl, gl2, whatever). vo=3Dx11 a) never locks up xorg & > >> 4) doesn't allow resizing of windows to scale the player. Oh f'well. > >> > >> Summary: > >> Xorg on FreeBSD is a crap shoot based on your card. IIRC a T42 > >> is one of those terrible i915 or something video cards. Ugh. > > > > > > I am surprised by this. I have a T42 with the Intel 3000 graphics card > and > > it has worked quite well for me. I use mplayer, vlc, and (primarily) > xine on > > it. I use the default video output device for all. I thought the defau= lt > > was Xv, but I could well be wrong. It's been working for me on stable f= or > > well over a year. I started using it when kib made patches available, > but I > > have been running the committed version. > > > > Just to confirm, you have WITH_NEW_XORG=3DYES and WITH_KMS=3DYES in > > /etc/make.conf and have built all X ports and the kernel with these > options. > > No*, AMD, but I've had my fill of Intel naughtiness lo many years ago. > I've essentially defaulted to the equivalent of VESA, given the horrors > that lie within the realms of DRM & DRI & GL. > > The problem is manifold, but no matter what the Xorg (& FBSD DRM) > driver writers do, the hardware manufacturers move to weirder & odder > methods of displaying (or desplaying, if you're trying to follow allonge > in mi=C3=BEle =C3=A6nglisc) your graphical content. Oddly enough, they s= eem > to have a rather short turnaround on their Windows=E2=84=A2 drivers. > > > Anyway, don't trust new technology, unless it directly benefits you, > & even then, don't trust it. > > *None of those settings, but how does that affect your situation? > > If you have AMD and are running 9, you can't use WITH_KMS (only supports Intel) and probably don't want WITH_NEW_XORG as it won't work with newer AMD graphics. If you are running 10, you want WITH_NEW_XORG, the fairly current Xorg code. It requires the option because X.org dropped support for a lot of older GPUs. You can try WITH_NEW_XORG and see how well it works with your AMD system. 10 also brings KMS support for AMD GPUs. I have none, so I can't say how well it works. I forgot that the kernel is now always built to support KMS, so it's only the X ports that require a re-build. --=20 R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com