From owner-freebsd-multimedia Tue Apr 29 16:48:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA18539 for multimedia-outgoing; Tue, 29 Apr 1997 16:48:53 -0700 (PDT) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA18529 for ; Tue, 29 Apr 1997 16:48:50 -0700 (PDT) Received: from ct.picker.com by whqvax.picker.com with SMTP; Tue, 29 Apr 1997 19:47:45 -0400 (EDT) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA29313; Tue, 29 Apr 97 19:47:44 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id TAA28598; Tue, 29 Apr 1997 19:47:19 -0400 Message-Id: <19970429194719.27301@ct.picker.com> Date: Tue, 29 Apr 1997 19:47:19 -0400 From: Randall Hopper To: Amancio Hasty Cc: multimedia@freebsd.org Subject: Re: bt848/fxtv: More info on system freezes References: <19970419141314.20369@ct.picker.com> <199704192128.OAA03885@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199704192128.OAA03885@rah.star-gate.com>; from Amancio Hasty on Sat, Apr 19, 1997 at 02:28:16PM -0700 Sender: owner-multimedia@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Amancio Hasty: |We may have to file a bug report with the X server group to see if we can |get them to help us out. I will be honest with you every day I use |fxtv and I don't get a crash -- once I did get the font corruption and |the system didn't craash however I have not been able to reproduce it. | |My take is that is probably more to do with the PCI chipset. |The "mistery-bit" on the Bt848 is supposed to be a work around for |the Natoma chipset. I still don't know what is supposed to do other |than what I stated. All I am saying is that is difficult to troubleshoot |on my PPRo . Guess that I will have to switch testing to my P100 which |does have a Natoma chipset. Back from the weekend... Interestingly enough, since Mark/my/your latest round of driver mods, I'm not able to hang the X server anymore. Tried hard, but no can do. :-) With the font refresh corruption immediately preceding the lock-ups and the fact that only the X server crashed, sounded like it was most likely X server corruption to me. Given this, I'm inclined to think fxtv or the bt driver might have had a hand, and its since been fixed (as that's all that's changed). I've got a few guesses as to specific changes, but hey!, I'm not gonna complain. Randall