From owner-freebsd-ports-bugs@FreeBSD.ORG Tue Jul 8 01:30:11 2003 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2409837B401 for ; Tue, 8 Jul 2003 01:30:11 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 217E143FBD for ; Tue, 8 Jul 2003 01:30:10 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h688U9Up047885 for ; Tue, 8 Jul 2003 01:30:09 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h688U98b047884; Tue, 8 Jul 2003 01:30:09 -0700 (PDT) Resent-Date: Tue, 8 Jul 2003 01:30:09 -0700 (PDT) Resent-Message-Id: <200307080830.h688U98b047884@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-ports-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, jimd@siu.edu Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5E9637B401 for ; Tue, 8 Jul 2003 01:23:13 -0700 (PDT) Received: from 255-202.ip.ll.net (255-202.ip.ll.net [209.131.255.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 269C843FB1 for ; Tue, 8 Jul 2003 01:23:12 -0700 (PDT) (envelope-from jimd_NOSPAM@siu.edu) Received: from 255-202.ip.ll.net (localhost [127.0.0.1]) by freebsd2.localnet10 (8.12.9/8.12.9) with ESMTP id h688MXa9001614; Tue, 8 Jul 2003 03:22:37 -0500 (CDT) (envelope-from jimd_NOSPAM@siu.edu) Message-Id: <200307080822.h688MXa9001614@freebsd2.localnet10> Date: Tue, 8 Jul 2003 03:22:33 -0500 (CDT) From: jimd_NOSPAM@siu.edu To: FreeBSD-gnats-submit@FreeBSD.org cc: freebsd-gfx-bugs@nvidia.com Subject: ports/54209: FBSD-1.0-4365 nVidia driver (port) locks up in Wolfenstein Enemy Territory X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jimd@siu.edu List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2003 08:30:11 -0000 >Number: 54209 >Category: ports >Synopsis: FBSD-1.0-4365 nVidia driver (port) locks up in Wolfenstein Enemy Territory >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jul 08 01:30:09 PDT 2003 >Closed-Date: >Last-Modified: >Originator: none >Release: FreeBSD 5.1-RELEASE i386 >Organization: >Environment: System: FreeBSD 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Tue Jun 24 22:44:46 CDT 2003 x@freebsd2.localnet10:/usr/src/sys/i386/compile/XSYSTEM i386 XFree86-Server-4.3.0_8 XFree86-clients-4.3.0_2 XFree86-libraries-4.3.0_5 linux_base-7.1_5 ET 2.55 linux-i386 May 27 2003 (under FreeBSD-1.0-3203 nvidia driver): GL_VENDOR: NVIDIA Corporation GL_RENDERER: GeForce4 Ti 4600/PCI/SSE2 GL_VERSION: 1.3.1 NVIDIA 32.03 /etc/sysctl.conf: hw.nvidia.registry.EnableAGPSBA=1 hw.nvidia.registry.EnableAGPFW=1 >Description: Using the FreeBSD-1.0-4265 nvidia driver. Normal video operations don't present any problems, so far. Wolfenstien Enemy Territory basic video operations don't present any problems. When playing a game and the player's character is killed, the screen locks up for at least as long as the "kill recycle time" - sometimes longer. The screen graphic is frozen but the sound may be repeating through a small segment (such as beeping). In most cases, game action and video operation is restored once the character has been "restored". Sometimes the game action and video display does not "reset" and X-windows must be aborted. Occassionally, the system will have to be "cold-booted" when you cannot "break out of" X. Restoring the previous FreeBSD-1.0-3203 nvidia driver restores normal Enemy Territory function when the character is "killed". Only one video lockup was encountered after going from 3203 to 4265 and back to 3203. Previous usage of Enemy Territory under 3203 did not exhibit any such behaviour. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: