From owner-freebsd-current@FreeBSD.ORG Thu Jun 10 04:55:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2581C16A4CE for ; Thu, 10 Jun 2004 04:55:53 +0000 (GMT) Received: from herbelot.dyndns.org (herbelot.net1.nerim.net [62.212.117.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 146F143D2F for ; Thu, 10 Jun 2004 04:55:52 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from [192.168.2.6] (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.12.11/8.12.10) with ESMTP id i5A4apmi025053; Thu, 10 Jun 2004 06:36:51 +0200 (CEST) From: Thierry Herbelot To: Stephan van Beerschoten Date: Thu, 10 Jun 2004 06:55:42 +0200 User-Agent: KMail/1.6.2 References: <65050.192.168.0.2.1086742730.squirrel@mail.chatcanada.net> <200406092153.04522.thierry@herbelot.com> <20040609202008.GE84791@enigma.whacky.net> In-Reply-To: <20040609202008.GE84791@enigma.whacky.net> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 8bit Message-Id: <200406100655.42464.thierry@herbelot.com> cc: freebsd-current@freebsd.org Subject: Re: cardreader interrupt storm [was : Re: digital camera] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jun 2004 04:55:53 -0000 Le Wednesday 09 June 2004 22:20, Stephan van Beerschoten a écrit : > > No problems with any interrupt storms whatsoever. Let me know if I can help > pinpoint anything somehow. > the interrupt storm only happens when *reading* from the CF : could you just try writing some (preferably large) file, then reading it > > I guess try updating your tree and building a new kernel, simply because my > kernel is somewhat newer then yours and there has been quite some acpi > commits lately. I'll do so as soon as the portupgrade is over ;-) > > /Stephan TfH