Date: Sun, 13 Jun 2004 21:06:19 -0700 (PDT) From: Nate Lawson <nate@root.org> To: John Birrell <jb@cimlogic.com.au> Cc: kris@obsecurity.org Subject: ACPI interrupt problems? (Was: HEADS UP: Starting socket locking merge) Message-ID: <20040613210504.D16707@root.org> In-Reply-To: <20040612220950.GF15577@freebsd3.cimlogic.com.au> References: <Pine.NEB.3.96L.1040612170314.90086R-100000@fledge.watson.org> <20040612220950.GF15577@freebsd3.cimlogic.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040613210504.D16707>