From owner-freebsd-hackers Fri Apr 9 3:56: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 5CED114D2C; Fri, 9 Apr 1999 03:55:51 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id GAA02375; Fri, 9 Apr 1999 06:54:56 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id GAA18163; Fri, 9 Apr 1999 06:53:38 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id GAA31643; Fri, 9 Apr 1999 06:53:38 -0400 (EDT) Date: Fri, 9 Apr 1999 06:53:38 -0400 (EDT) From: Thomas David Rivers Message-Id: <199904091053.GAA31643@lakes.dignus.com> To: dfr@nlsystems.com, hasty@rah.star-gate.com Subject: Re: Bt848 corruption since upgrading to 3.1. Has DMA code changed? Cc: hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG, roger@cs.strath.ac.uk In-Reply-To: <199904090627.XAA76410@rah.star-gate.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I don't think there is any problem with the bt848 driver on 3.1 if you guys > can't > figure out what is the problem just mail me. Do make sure that your driver > is the correct version for 3.1 . > > In the interrupt routine there is a printf for those having problems just > uncomment it. > > The values printed will give a clue as to what the bt848 is being upset about. > > > > /* printf( " STATUS %x %x %x \n", > dstatus, bktr_status, bt848->risc_count ); > */ > > Amancio > Well - there's some problem.. when I run the TV ap for awhile, the machine will lock up (interestingly enough, sound from the bt848 is still pumping out the of the speakers :-) ) Everything is hung solid. (Ping doesn't answer...) This has been the case since the driver that came out with 2.2.7. (Running in 2.2.5 with whatever driver was there didn't have this problem.) That may not, however, be a problem in the bt848 - but a problem elsewhere (say, X11, the kernel, etc... it could be almost anywhere.) - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message