From owner-freebsd-bugs@FreeBSD.ORG Sat Mar 29 09:40:06 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0D2437B401 for ; Sat, 29 Mar 2003 09:40:06 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 385CF43F75 for ; Sat, 29 Mar 2003 09:40:06 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id h2THe5NS075118 for ; Sat, 29 Mar 2003 09:40:05 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id h2THe5wS075117; Sat, 29 Mar 2003 09:40:05 -0800 (PST) Date: Sat, 29 Mar 2003 09:40:05 -0800 (PST) Message-Id: <200303291740.h2THe5wS075117@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Jens Schweikhardt Subject: Re: kern/48279: Brooktre878 (bktr) may cause freeze X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jens Schweikhardt List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Mar 2003 17:40:38 -0000 The following reply was made to PR kern/48279; it has been noted by GNATS. From: Jens Schweikhardt To: Peter B Cc: GNATS Bug Followup Subject: Re: kern/48279: Brooktre878 (bktr) may cause freeze Date: Sat, 29 Mar 2003 18:03:51 +0100 Peter, On Sat, Mar 29, 2003 at 05:01:11PM +0100, Peter B wrote: # Jens Schweikhardt wrote: # >Synopsis: Brooktre878 (bktr) may cause freeze # > # >State-Changed-From-To: open->feedback # >State-Changed-By: schweikh # >State-Changed-When: Sat Mar 29 06:44:25 PST 2003 # >State-Changed-Why: # >This is a known bug in the interaction of brooktree chips with various # >chipset (IS, VIA, UMC, ALI, and some OPTI). It's OS independent. Please # >refer to http://www.hauppauge.com/html/lockups.htm for a list of issues # >and possibilities on how you *may* resolve them. # # The reason I wonder wheather it's really a hardware issue. I had the same problem. I even swapped the bt848 card for a bt878 card. Then I booted linux on the same system. Same effect: hard freeze (keyboard LEDs don't change) anywhere from 5min to three days after launching fxtv. From all I read on the Hauppauge page, it is a HW incompatibility of the chipset. Which chipset is on your board? If it's anything other than intel, try swapping the board and see if the problem persists. # Is that if I boot # my computer and start XFree86 (4.2.0) and then fxtv *right away* there is no # freezes whatsoever, not even after weeks of uptime and frequent use of fxtv in # all modes. (I'm considering putting ffmpeg in /etc/rc.local) # # However if I boot my computer and start XFree86 (4.2.0) and then start mozilla, # some xterm's, use ssh.. close some xterm's. And after say 5 minutes start fxtv. # Instant freeze.. # # This made me to conclude it's some kind of initialisation error. And that it # might have to do with allocation of resources that will not be properly # allocated at a later time. It might be kernel memory. This is not enough information to make a case either way. The symptom looks very much like a PCI bus lockup, something you can't trigger in software. I'm not saying it must be HW, but after all my efforts and investigations, it's by far the most probable. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped)