From owner-freebsd-stable@FreeBSD.ORG Sun Oct 27 05:23:03 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EA4E876C for ; Sun, 27 Oct 2013 05:23:02 +0000 (UTC) (envelope-from illoai@gmail.com) Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8787526D5 for ; Sun, 27 Oct 2013 05:23:02 +0000 (UTC) Received: by mail-we0-f169.google.com with SMTP id q58so5417343wes.28 for ; Sat, 26 Oct 2013 22:23:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=HhEdF9hR1FYkTHIkSGz5DwwFtG0b9aM2prhdZZ/EF/U=; b=uoSYbozxRr0zh8DfLqYAs5TF4ioR69zMoRO7zTvKCsbggG83ln8wsxs3kNDy+skw8E mQ1knXlHW7+8Y4rCdTHQ6mGPNAnI/yds0fUX59K97zDSMV1ASJDFS2IL8nRlaQuyi8RR K6T+cB9qTP9XM8zbMRqqVLbqLDc4GYSM8SzVw7l7KRQ3yylxnlCROmMYqs+L3HD6GET1 1+/6Q+sWl61a6/g1cbwd9U4W51aR7ohHqmexiOOhOV/R9HDTy//WsEJNfuPwdS22DIv7 mmtV3qSFj/NPnp9YWlYmp69EQJt8lZGLDlxzWffII8A4ElbyKlyaB8YwxTQbkyx3y0S8 sw7g== MIME-Version: 1.0 X-Received: by 10.180.212.51 with SMTP id nh19mr2180151wic.52.1382851381007; Sat, 26 Oct 2013 22:23:01 -0700 (PDT) Received: by 10.216.245.5 with HTTP; Sat, 26 Oct 2013 22:23:00 -0700 (PDT) In-Reply-To: References: <20131027011829.GA98327@lyxys.ka.sub.org> Date: Sun, 27 Oct 2013 01:23:00 -0400 Message-ID: Subject: Re: x11 hangs unkillable on 10.0-BETA1 From: "illoai@gmail.com" To: Kevin Oberman Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 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 05:23:03 -0000 On 27 October 2013 01:10, Kevin Oberman wrote: > On Sat, Oct 26, 2013 at 9:31 PM, illoai@gmail.com wrot= e: >> >> On 26 October 2013 21:18, Wolfgang Zenker >> wrote: >> > Testing 10.0-BETA1 on an old IBM T42p Laptop, after a while Xorg start= s >> > 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 Xorg >> > process does not result in an error message but fails to terminate the >> > 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 an= d > 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 default > was Xv, but I could well be wrong. It's been working for me on stable for > 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 optio= ns. 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=FEle =E6nglisc) your graphical content. Oddly enough, they seem to have a rather short turnaround on their Windows=99 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? --=20 --