From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 14 17:16: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 A047516A4CF for ; Mon, 14 Jun 2004 17:16:40 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 850CD43D31 for ; Mon, 14 Jun 2004 17:16:40 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 24270 invoked from network); 14 Jun 2004 17:15:53 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 14 Jun 2004 17:15:53 -0000 Received: from 10.50.41.233 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i5EHFgEQ057461; Mon, 14 Jun 2004 13:15:42 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Mon, 14 Jun 2004 13:16:37 -0400 User-Agent: KMail/1.6 References: <200406141433.42584.doconnor@gsoft.com.au> <20040613221018.C17008@root.org> In-Reply-To: <20040613221018.C17008@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406141316.37293.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: acpi@FreeBSD.org cc: Daniel O'Connor cc: freebsd-current@FreeBSD.org cc: John Birrell Subject: Re: ACPI interrupt problems? (Was: HEADS UP: Starting socketlocking 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 17:16:40 -0000 On Monday 14 June 2004 01:14 am, Nate Lawson wrote: > On Mon, 14 Jun 2004, Daniel O'Connor wrote: > > On Mon, 14 Jun 2004 13:36, Nate Lawson wrote: > > > > 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) > > Have you isolated it further? Try backing out rev 1.15 of > acpi_pci_link.c, referenced by this email (click on link for a patch): > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=2053288+0+archive/2004/cvs-all >/20040530.cvs-all > > I do believe John is working on this. A temporary backout might be in > order but I'll let him decide on that. Either way, the right direction > for this stuff is to keep moving forward and this commit was definitely a > step that way. It can be backed out for now I guess. Basically, the code doesn't work at all with regards to routing virgin interrupts and this change just exposed that. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org