From owner-freebsd-multimedia Thu Mar 27 17:47:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA11185 for multimedia-outgoing; Thu, 27 Mar 1997 17:47:14 -0800 (PST) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA11173 for ; Thu, 27 Mar 1997 17:47:09 -0800 (PST) Received: from ct.picker.com by whqvax.picker.com with SMTP; Thu, 27 Mar 1997 20:46:22 -0500 (EST) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA28396; Thu, 27 Mar 97 20:46:12 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id UAA09928; Thu, 27 Mar 1997 20:46:11 -0500 Message-Id: <19970327204611.40929@ct.picker.com> Date: Thu, 27 Mar 1997 20:46:11 -0500 From: Randall Hopper To: Steve Passe Cc: Thomas Arnold , multimedia@FreeBSD.ORG Subject: Re: bt848 driver for this week References: <199703252136.OAA28951@Ilsa.StevesCafe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.65 In-Reply-To: <199703252136.OAA28951@Ilsa.StevesCafe.com>; from Steve Passe on Tue, Mar 25, 1997 at 02:36:28PM -0700 Sender: owner-multimedia@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Steve Passe: |in -current "man tsleep", no idea whether it is in 2.2 Sure is. /usr/src/sys/kern/kern_synch.c w/ man page. I get the same error as I mentioned last weekend when doing CAP_SINGLEs on 2.2-GAMMA w/ the 970322 driver: |bktr0: ioctl: tsleep error -1 2c0f24 |bktr0: ioctl: tsleep error -1 1000f24 |bktr0: ioctl: tsleep error -1 1000754 |bktr0: ioctl: tsleep error -1 2c0754 |bktr0: ioctl: tsleep error -1 1000624 |bktr0: ioctl: tsleep error -1 2c0624 | | error=tsleep((caddr_t)bktr, METPRI, "capturing", hz); | |Since this is an ERESTART error (METPRI has PCATCH), is the right fix for |this to change this line to: | | while ((error=tsleep((caddr_t)bktr, METPRI, "capturing", hz)) == ERESTART) ; I don't know what the right fix is, but I can tell you it isn't that simple. :-) By experiment, the above is one easy way to lock your machine solid. I hadn't had a chance to dig into it further. |Sounds like this may be related to my seeing the video not capture both |frames on a CAP_SINGLE. Randall