From owner-freebsd-stable@FreeBSD.ORG Mon Oct 2 04:37:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7FE016A403 for ; Mon, 2 Oct 2006 04:37:38 +0000 (UTC) (envelope-from verbo.solo@sbcglobal.net) Received: from smtp106.plus.mail.re2.yahoo.com (smtp106.plus.mail.re2.yahoo.com [206.190.53.31]) by mx1.FreeBSD.org (Postfix) with SMTP id 45C3F43D49 for ; Mon, 2 Oct 2006 04:37:38 +0000 (GMT) (envelope-from verbo.solo@sbcglobal.net) Received: (qmail 4498 invoked from network); 2 Oct 2006 04:37:37 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Received:Subject:From:To:Content-Type:Date:Message-Id:Mime-Version:X-Mailer:Content-Transfer-Encoding; b=Az3EGT63JF9QMOSMWvSNYO8JsvDKUxJpXn1IH9lOYR5GBnvAwFtycLhFx3vOdIW3fjiFlr3Mfj+Zr4ac3T8xFim65wbE8KH3kATgrNWvG1mNG/S9v+EQ1fV4ayp+UH0IY0rQMDiaGY3d2T+kt53j3YBmQW3SzCbjygQzMaJNNWY= ; Received: from unknown (HELO elbereth.gateway.2wire.net) (verbo.solo@sbcglobal.net@69.152.90.113 with plain) by smtp106.plus.mail.re2.yahoo.com with SMTP; 2 Oct 2006 04:37:37 -0000 From: "Charles P. Schaum" To: "freebsd-stable@freebsd.org" Content-Type: text/plain Date: Sun, 01 Oct 2006 23:37:36 -0500 Message-Id: <1159763856.71287.24.camel@elbereth.gateway.2wire.net> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: DRM/DRI in STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2006 04:37:38 -0000 Hi, Just had a question about DRI/DRM using the Intel i915 module on an 845G. Using fullscreen modes that have a resolution different from the display at startup can cause the xserver to halt and restart. This actually happened more under 6.1 STABLE than 6.2-PRE. After building world I can usually go for about a day or so without this behavior appearing. Then it will occur and, after the first occurrance, it will generally have that behavior until a subsequent rebuilding of world. I usually avoid this by modifying games so that they either run in a window or use the default resolution, so there's an easy workaround. I was just curious if I were doing something dumb or if that's just life right now. Charles See below: I had been getting messages under 6.1-STABLE like: Sep 21 05:09:07 elbereth kernel: Warning: pid 3307 used static ldt allocation. Sep 21 05:09:07 elbereth kernel: See the i386_set_ldt man page for more info Sep 21 05:11:52 elbereth kernel: error: [drm:pid3311:drm_close] *ERROR* can't find authenticator... But after rebuilding world/kernel to 6.2-PRE (STABLE) these have largely disappeared - and I still am using the same apps. About the only thing I see currently are some errors generated when recording a CD via GNOME (atapicam) which have no effect on my getting a good CD and therefore which I ignore. Today's messages were: Oct 1 07:47:59 elbereth kernel: pid 59648 (typesconfig), uid 0: exited on signal 11 (core dumped) Oct 1 07:47:59 elbereth kernel: pid 59649 (typesconfig), uid 0: exited on signal 11 (core dumped) Oct 1 20:39:16 elbereth kernel: pid 811 (Xorg), uid 0: exited on signal 6 (core dumped) Oct 1 20:39:22 elbereth gdm[804]: Error reinitilizing server Oct 1 20:39:55 elbereth login: ROOT LOGIN (root) ON ttyv0 Oct 1 21:16:24 elbereth cupsd: Unable to read configuration file '/usr/local/etc/cups/cupsd.conf' - exiting! Oct 1 21:16:24 elbereth syslogd: /dev/:0: No such file or directory Oct 1 21:17:40 elbereth sudo: charles : TTY=ttyp2 ; PWD=/home/charles ; USER=root ; COMMAND=/usr/local/sbin/cupsd Oct 1 22:48:42 elbereth kernel: pid 23581 (typesconfig), uid 0: exited on signal 11 (core dumped) Oct 1 22:48:42 elbereth kernel: pid 23582 (typesconfig), uid 0: exited on signal 11 (core dumped) The X log really did not indicate anything unusual, save that the server crashed: (II) 3rd Button detected: disabling emulate3Button (II) I810(0): Setting refresh with VBE 3 method. (II) I810(0): Display plane A is enabled and connected to Pipe A. (II) I810(0): Enabling plane A. (II) I810(0): Display plane A is now enabled and connected to Pipe A. (II) I810(0): PIPEACONF is 0x80000000 (II) I810(0): Mode bandwidth is 47 Mpixel/s (II) I810(0): maxBandwidth is 640 Mbyte/s, pipe bandwidths are 252 Mbyte/s, 0 Mbyte/s *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Fatal server error: Caught signal 11. Server aborting Please consult the The X.Org Foundation support at http://wiki.X.Org for help. Please also check the log file at "/var/log/Xorg.0.log" for additional information. (WW) I810(0): Successfully set original devices (WW) I810(0): Setting the original video mode instead of restoring the saved state (WW) I810(0): Extended BIOS function 0x5f05 failed. (II) I810(0): BIOS call 0x5f05 not supported, setting refresh with VBE 3 method. (II) I810(0): xf86UnbindGARTMemory: unbind key 9 (II) I810(0): xf86UnbindGARTMemory: unbind key 1 (II) I810(0): xf86UnbindGARTMemory: unbind key 2 (II) I810(0): xf86UnbindGARTMemory: unbind key 4 (II) I810(0): xf86UnbindGARTMemory: unbind key 3 (II) I810(0): xf86UnbindGARTMemory: unbind key 5 (II) I810(0): xf86UnbindGARTMemory: unbind key 6 (II) I810(0): xf86UnbindGARTMemory: unbind key 7 (II) I810(0): xf86UnbindGARTMemory: unbind key 8 (WW) I810(0): Successfully set original devices (2)