From owner-freebsd-stable@FreeBSD.ORG Sun Oct 27 18:03:00 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 8BE84D74 for ; Sun, 27 Oct 2013 18:03:00 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6242B241E for ; Sun, 27 Oct 2013 18:03:00 +0000 (UTC) Received: by mail-pd0-f171.google.com with SMTP id w10so4234027pde.30 for ; Sun, 27 Oct 2013 11:03:00 -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=/hYGJXuZkvEQ4OfGPhK4BxuTQAXPdnG7RqNpYUxn2CE=; b=Mb1u1zw8sGIQ+aVJPSn6fgs5wSMfwPm2N6Z76UwAS6sGi5vQX612koXBkxPdDjtLYr 1NsP80LuMl+8Tc4YD7YpRJJ35aiWhGz1s5b28ZiLdGs1tbdRbEqQJdtIOD/HZDZsQNhK vjCVmlTEOTJC0QKvbFb558CL16jHtFwUeJrgDnsLxtaFhrTcL4YP8PXCD7rvqdRuLNBF yO0V6HNn02rYeOPm2Kv1Zsl+OlKVltiGiUryIUA58GQx+HMGuP/5YBxg/NfwXlqPhkby tRpjW7QLo82+qsaXmw6knS1XegCVRniE7lHV+Q69I9dPJDdJAPFXpHw53IHNUit5dSOR sG9g== MIME-Version: 1.0 X-Received: by 10.68.172.66 with SMTP id ba2mr12285150pbc.92.1382896979980; Sun, 27 Oct 2013 11:02:59 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.67.23.101 with HTTP; Sun, 27 Oct 2013 11:02:59 -0700 (PDT) In-Reply-To: <20131027090624.GA13421@lyxys.ka.sub.org> References: <20131027011829.GA98327@lyxys.ka.sub.org> <20131027090624.GA13421@lyxys.ka.sub.org> Date: Sun, 27 Oct 2013 11:02:59 -0700 X-Google-Sender-Auth: ias9xyqvFwXRUaO74-GjMt1W0NU Message-ID: Subject: Re: x11 hangs unkillable on 10.0-BETA1 From: Kevin Oberman To: Wolfgang Zenker Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "stable@freebsd.org" , "illoai@gmail.com" 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 18:03:00 -0000 On Sun, Oct 27, 2013 at 2:06 AM, Wolfgang Zenker wrote: > * Kevin Oberman [131027 06:10]: > > 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 Xorg > >>> process does not result in an error message but fails to terminate the > >>> process. > > >> [..] > >> 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. > > This is a pre-Lenovo T42p and X identifies the graphics card as an > [AMD/ATI] RV350/M10 GL [Mobility FireGL T2] rev 128 > > > 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 > > 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=YES and WITH_KMS=YES in > > /etc/make.conf and have built all X ports and the kernel with these > options. > > So far I have not tried WITH_NEW_XORG=YES, beause AFAIR that would not > allow me to switch back to console after starting X11. > No, WITH_NEW_XORG has nothing to do with this. It's KMS on Intel graphics that prevents getting a vty after X is started. Well. actually is is th display of vty that fails. You can still type commands and they are executed. You can, for example, restart X (startx). NEW_XORG is mostly the new MESA code that no linger supports older version of may cards. What results would be on your RV350, I can't say. Once you go to 10, you can build WITH_GALIUM and, hopefully shortly after that newcons will be ready and the problem of returning to console mode will be over. That said, I am not sure whether KMS support will make any difference on your system. I do recommend starting without an xorg.conf file. It almost always works at a basic level. Then, if that works, with or without WITH_NEW_XORG=YES, you can add "extras" like optional fonts, or additional modules. Mine is pretty short. > The last line in the Xorg.0.log of the failed session was > [mi] EQ overflowing. The server is probably stuck in an infinite loop. > so I might give WITH_NEW_XORG=YES a try. > > Wolfgang > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com