From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 14 04:06:40 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 8B92C16A4CE for ; Mon, 14 Jun 2004 04:06:40 +0000 (GMT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 54F5043D5D for ; Mon, 14 Jun 2004 04:06:40 +0000 (GMT) (envelope-from nate@root.org) Received: (qmail 16741 invoked by uid 1000); 14 Jun 2004 04:06:19 -0000 Date: Sun, 13 Jun 2004 21:06:19 -0700 (PDT) From: Nate Lawson To: John Birrell In-Reply-To: <20040612220950.GF15577@freebsd3.cimlogic.com.au> Message-ID: <20040613210504.D16707@root.org> References: <20040612220950.GF15577@freebsd3.cimlogic.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@FreeBSD.org cc: Robert Watson cc: current@FreeBSD.org cc: kris@obsecurity.org Subject: 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 04:06:40 -0000 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@. -Nate