From owner-freebsd-current@FreeBSD.ORG  Sun Nov  8 13:31:03 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id BDCD81065679;
	Sun,  8 Nov 2009 13:31:03 +0000 (UTC)
	(envelope-from hselasky@c2i.net)
Received: from swip.net (mailfe10.tele2.se [212.247.155.33])
	by mx1.freebsd.org (Postfix) with ESMTP id 230A58FC17;
	Sun,  8 Nov 2009 13:31:02 +0000 (UTC)
X-Cloudmark-Score: 0.000000 []
X-Cloudmark-Analysis: v=1.0 c=1 a=RERtC8nhXGhYvIZhK0yWrQ==:17
	a=gtfo_z9B48n2ptGh-pUA:9 a=1Ik2Ak7zZt177asXVowkbeJSBDcA:4
Received: from [90.149.203.35] (account mc467741@c2i.net HELO
	laptop.adsl.tele2.no)
	by mailfe10.swip.net (CommuniGate Pro SMTP 5.2.16)
	with ESMTPA id 1147897675; Sun, 08 Nov 2009 14:31:01 +0100
From: Hans Petter Selasky <hselasky@c2i.net>
To: Alexander Nedotsukov <bland@freebsd.org>
Date: Sun, 8 Nov 2009 14:32:22 +0100
User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; )
References: <202969100caf7f0bb8098572b0dad622@mail>
	<200911070109.28595.hselasky@c2i.net>
	<D75328A3-1C22-4277-987C-4B633DAF948E@freebsd.org>
In-Reply-To: <D75328A3-1C22-4277-987C-4B633DAF948E@freebsd.org>
X-Face: (%<A9p';5>:6u[ldzJ`0qjD7sCkfdMmD*RxpO<
	=?iso-8859-1?q?Q0yAl=7E=3F=60=27F=3FjDVb=5DE6TQ7=27=23h-VlLs=7Dk/=0A=09?=(yxg(p!IL.`#ng"%`BMrham7%UK,}VH\wUOm=^>wEEQ+KWt[{J#x6ow~JO:,zwp.(t;
	@ =?iso-8859-1?q?Aq=0A=09=3A4=3A=26nFCgDb8=5B3oIeTb=5E=27?=",;
	u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200911081432.24072.hselasky@c2i.net>
Cc: freebsd-current@freebsd.org, Andrew Thompson <thompsa@freebsd.org>
Subject: Re: umass problem.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Nov 2009 13:31:03 -0000

On Sunday 08 November 2009 14:24:39 Alexander Nedotsukov wrote:
> Just curious, is there is no way to detect lost interrupt in new usb  
> stack quickly or check in the old one was not correct anyway?

Hi,

The check might not be correct, because new jobs can be queued immediately 
after the interrupt, and in that case it is not correct to check of the number 
of jobs is zero.

--HPS