From owner-freebsd-current@FreeBSD.ORG Mon Jun 14 05:22: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 3403516A4CE; Mon, 14 Jun 2004 05:22:53 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9A2143D48; Mon, 14 Jun 2004 05:22:52 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i5E5MVUJ062031; Mon, 14 Jun 2004 00:22:31 -0500 (CDT) (envelope-from dan) Date: Mon, 14 Jun 2004 00:22:31 -0500 From: Dan Nelson To: Nate Lawson Message-ID: <20040614052230.GA3657@dan.emsphone.com> References: <20040612220950.GF15577@freebsd3.cimlogic.com.au> <20040613210504.D16707@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040613210504.D16707@root.org> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: acpi@freebsd.org cc: Robert Watson cc: current@freebsd.org cc: kris@obsecurity.org Subject: Re: ACPI interrupt problems? (Was: HEADS UP: Starting socket locking merge) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jun 2004 05:22:53 -0000 In the last episode (Jun 13), Nate Lawson said: > On Sun, 13 Jun 2004, John Birrell wrote: > > On Sat, Jun 12, 2004 at 05:09:32PM -0400, Robert Watson wrote: > > > As we've had mbuma merged recently, altq, and several other > > > networking 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@. http://lists.freebsd.org/pipermail/freebsd-current/2004-June/028426.html (mid <200406051220.56698.msch@snafu.de> ) has 4 people reporting problems with ACPI and interrupt routing, starting some time after May 22. I still see it on today's kernel. There's also a post by jhb saying he thinks he knows what the problem it. -- Dan Nelson dnelson@allantgroup.com