From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 14 05:04:35 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6773716A4CE; Mon, 14 Jun 2004 05:04:35 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DEC143D39; Mon, 14 Jun 2004 05:04:32 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id i5E53iVR035708; Mon, 14 Jun 2004 14:33:45 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Mon, 14 Jun 2004 14:33:42 +0930 User-Agent: KMail/1.6.2 References: <20040612220950.GF15577@freebsd3.cimlogic.com.au> <20040613210504.D16707@root.org> In-Reply-To: <20040613210504.D16707@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200406141433.42584.doconnor@gsoft.com.au> X-Spam-Score: -4.9 () CARRIAGE_RETURNS,IN_REP_TO,PGP_SIGNATURE,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_02_03,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: current@freebsd.org cc: acpi@freebsd.org cc: Robert Watson cc: kris@obsecurity.org cc: John Birrell Subject: Re: ACPI interrupt problems? (Was: HEADS UP: Starting socket locking merge) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jun 2004 05:04:35 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 14 Jun 2004 13:36, Nate Lawson wrote: > > > changes in addition to this, I'd ask people be particularly diligent = in > > > reporting new poor behavior in the network stack. Because we've also > > > seen several fixes along the way, I'd also ask you make sure you're > > > up-to-date. > > > > That's difficult for those of us who are affected by the ACPI interrupt > > allocation problems. If ACPI isn't going to be fixed soon (it's been 2 > > weeks already), then the last commits should be backed. > > It would help if you'd point out the email message with this problem and > what commits caused it. I'm not aware of any new interrupt problems and > haven't seen email about it on acpi@. I don't know which commit but I believe John Baldwin is working on a fix. The problem occurs between 02:30 29/05/2004 UTC and 04:00 29/05/2004 UTC. (ie code from the former works, code from the later doesn't) The problem exhibits itself as bfe0 watchdog timeouts (on my system anyway) =2D --=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAzTGu5ZPcIHs/zowRAnQ2AJ4v7shFOdu0NEdNxPUcelLI60QHLgCgjlsA xdSHMSR/EzUT1Ra3r25GaAc=3D =3D6I3m =2D----END PGP SIGNATURE-----