From owner-freebsd-acpi@FreeBSD.ORG Sun Jun 13 00:06:28 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 A5E7016A4CE for ; Sun, 13 Jun 2004 00:06:28 +0000 (GMT) Received: from ylpvm01.prodigy.net (ylpvm01-ext.prodigy.net [207.115.57.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3F4143D58 for ; Sun, 13 Jun 2004 00:06:27 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (adsl-63-207-60-35.dsl.lsan03.pacbell.net [63.207.60.35])i5D069nI001993 for ; Sat, 12 Jun 2004 20:06:09 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D16CF52684; Sat, 12 Jun 2004 17:06:09 -0700 (PDT) X-Original-To: kkenn@localhost Delivered-To: kkenn@localhost.obsecurity.org Received: from localhost (localhost [127.0.0.1]) by obsecurity.dyndns.org (Postfix) with ESMTP id B15D7516EB for ; Sat, 12 Jun 2004 15:17:08 -0700 (PDT) Delivered-To: kris@freebsd.org Received: from localhost [127.0.0.1] by localhost with POP3 (fetchmail-6.2.4) for kkenn@localhost (single-drop); Sat, 12 Jun 2004 15:17:08 -0700 (PDT) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 61B6916A51C; Sat, 12 Jun 2004 22:15:16 +0000 (GMT) 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 5A2EF16A4CE; Sat, 12 Jun 2004 22:11:09 +0000 (GMT) Received: from freebsd3.cimlogic.com.au (adsl-20-121.swiftdsl.com.au [218.214.20.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D1BC43D45; Sat, 12 Jun 2004 22:11:03 +0000 (GMT) (envelope-from jb@cimlogic.com.au) Received: by freebsd3.cimlogic.com.au (Postfix, from userid 102) id BBF9A6AA57; Sun, 13 Jun 2004 08:09:50 +1000 (EST) Date: Sun, 13 Jun 2004 08:09:50 +1000 From: John Birrell To: Robert Watson Message-ID: <20040612220950.GF15577@freebsd3.cimlogic.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Sender: owner-freebsd-current@FreeBSD.org Errors-To: owner-freebsd-current@FreeBSD.org X-UIDL: eo_!!/SH!!lRO"!WFB!! X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=0.17.5 Resent-From: kris@obsecurity.org Resent-Date: Sat, 12 Jun 2004 17:06:07 -0700 Resent-To: acpi@FreeBSD.org Resent-Message-Id: <20040613000609.D16CF52684@obsecurity.dyndns.org> cc: current@FreeBSD.org Subject: Re: HEADS UP: Starting socket locking merge X-BeenThere: freebsd-acpi@freebsd.org List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jun 2004 00:06:28 -0000 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. -- John Birrell _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-acpi@FreeBSD.ORG Sun Jun 13 22:54: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 5DB5D16A4CE for ; Sun, 13 Jun 2004 22:54:35 +0000 (GMT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 2B00C43D48 for ; Sun, 13 Jun 2004 22:54:35 +0000 (GMT) (envelope-from nate@root.org) Received: (qmail 15563 invoked by uid 1000); 13 Jun 2004 22:54:04 -0000 Date: Sun, 13 Jun 2004 15:54:04 -0700 (PDT) From: Nate Lawson To: Ariff Abdullah In-Reply-To: <20040613064351.44f05257.skywizard@MyBSD.org.my> Message-ID: <20040613155339.Q15532@root.org> References: <20040613064351.44f05257.skywizard@MyBSD.org.my> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@FreeBSD.org cc: freebsd-current@FreeBSD.org Subject: Re: MSI 6712 KT4AV asl/dsdt acpi + floppy hack 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: Sun, 13 Jun 2004 22:54:35 -0000 I just committed code changing the sysresource behavior. It should work without your trick. Please cvsup and test. -Nate On Sun, 13 Jun 2004, Ariff Abdullah wrote: > Those with MSI 6712 KT4AV motherboard plagued with floppy controller > disability can try this to *re*enable your controller back. The trick > is to move 0x03F0 resource out of SYSR , and put it under FDC0. Take a > look at http://staff.mybsd.org.my/skywizard/FreeBSD/msi_acpi/ . > > Perhaps other simmilar cases can be cured using this trick. Good luck. > > -- > > Ariff Abdullah > MyBSD > > http://www.MyBSD.org.my (IPv6/IPv4) > http://staff.MyBSD.org.my (IPv6/IPv4) > http://tomoyo.MyBSD.org.my (IPv6/IPv4) > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" > From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 14 04:05:25 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 CE55B16A4CE for ; Mon, 14 Jun 2004 04:05:25 +0000 (GMT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id A341943D58 for ; Mon, 14 Jun 2004 04:05:25 +0000 (GMT) (envelope-from nate@root.org) Received: (qmail 16713 invoked by uid 1000); 14 Jun 2004 04:04:55 -0000 Date: Sun, 13 Jun 2004 21:04:55 -0700 (PDT) From: Nate Lawson To: Ariff Abdullah In-Reply-To: <20040613155339.Q15532@root.org> Message-ID: <20040613210341.V16707@root.org> References: <20040613064351.44f05257.skywizard@MyBSD.org.my> <20040613155339.Q15532@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@FreeBSD.org cc: freebsd-current@FreeBSD.org Subject: Re: MSI 6712 KT4AV asl/dsdt acpi + floppy hack 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:05:25 -0000 Another way to see if this was a sysresource problem is to add this to your loader.conf and reboot: debug.acpi.disable="sysresource" -Nate On Sun, 13 Jun 2004, Nate Lawson wrote: > I just committed code changing the sysresource behavior. It should work > without your trick. Please cvsup and test. > > -Nate > > On Sun, 13 Jun 2004, Ariff Abdullah wrote: > > Those with MSI 6712 KT4AV motherboard plagued with floppy controller > > disability can try this to *re*enable your controller back. The trick > > is to move 0x03F0 resource out of SYSR , and put it under FDC0. Take a > > look at http://staff.mybsd.org.my/skywizard/FreeBSD/msi_acpi/ . > > > > Perhaps other simmilar cases can be cured using this trick. Good luck. > > > > -- > > > > Ariff Abdullah > > MyBSD > > > > http://www.MyBSD.org.my (IPv6/IPv4) > > http://staff.MyBSD.org.my (IPv6/IPv4) > > http://tomoyo.MyBSD.org.my (IPv6/IPv4) > > _______________________________________________ > > freebsd-acpi@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" > 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 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----- From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 14 05:14:46 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 AA23216A4CE for ; Mon, 14 Jun 2004 05:14:46 +0000 (GMT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 7665243D2D for ; Mon, 14 Jun 2004 05:14:46 +0000 (GMT) (envelope-from nate@root.org) Received: (qmail 17099 invoked by uid 1000); 14 Jun 2004 05:14:17 -0000 Date: Sun, 13 Jun 2004 22:14:17 -0700 (PDT) From: Nate Lawson To: Daniel O'Connor In-Reply-To: <200406141433.42584.doconnor@gsoft.com.au> Message-ID: <20040613221018.C17008@root.org> References: <20040613210504.D16707@root.org> <200406141433.42584.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org 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 05:14:46 -0000 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. -Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 14 05:22:53 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 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: John Birrell cc: kris@obsecurity.org 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: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 From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 14 05:51:59 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 6761A16A4CE; Mon, 14 Jun 2004 05:51:59 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E69F43D31; Mon, 14 Jun 2004 05:51:58 +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 i5E5pidv036405; Mon, 14 Jun 2004 15:21:44 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Nate Lawson Date: Mon, 14 Jun 2004 15:21:34 +0930 User-Agent: KMail/1.6.2 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: quoted-printable Message-Id: <200406141521.40645.doconnor@gsoft.com.au> X-Spam-Score: -4.9 () CARRIAGE_RETURNS,IN_REP_TO,MIME_LONG_LINE_QP,PGP_SIGNATURE,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_01_02,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: acpi@freebsd.org cc: freebsd-current@freebsd.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:51:59 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 14 Jun 2004 14:44, Nate Lawson wrote: > > 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=3D2053288+0+archive/2004/cvs= =2Dall >/20040530.cvs-all OK, that appears to revert to the old behaviour WRT IRQs so it works :) > 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. Agreed. Having a work around while it's being thrased out is nice though :) Thanks. =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) iD8DBQFAzTzs5ZPcIHs/zowRAn8tAJ49COLDDARWywm7k8BGrFcbsqVeWACePUDc jP/EYMQy3zZ9pzTwoTTQafg=3D =3DUfHq =2D----END PGP SIGNATURE----- From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 14 11:01:46 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 7257716A4D0 for ; Mon, 14 Jun 2004 11:01:46 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B41A43D31 for ; Mon, 14 Jun 2004 11:01:46 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i5EB1W3n072496 for ; Mon, 14 Jun 2004 11:01:32 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i5EB1WNN072490 for freebsd-acpi@freebsd.org; Mon, 14 Jun 2004 11:01:32 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 14 Jun 2004 11:01:32 GMT Message-Id: <200406141101.i5EB1WNN072490@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-acpi@FreeBSD.org Subject: Current problem reports assigned to you 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 11:01:46 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/09/10] kern/56659 acpi ACPI trouble on IBM ThinkPad X31 f [2004/01/31] kern/62194 acpi kern/acpi: Unable to map IRQ on device cb 2 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/07/22] i386/54756 acpi ACPI suspend/resume problem on CF-W2 lapt o [2003/08/20] kern/55822 acpi No ACPI power off with SMP kernel o [2003/12/17] i386/60317 acpi FreeBSD 5.2rc1 doesn't boot with ACPI ena 3 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/08/11] i386/55473 acpi Mouse broken on some AWARD BIOS with ACPI o [2004/03/17] misc/64365 acpi ACPI problems o [2004/05/28] kern/67309 acpi zzz reboot computer (ACPI S3) 3 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 14 13:08: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 14CD616A4CE; Mon, 14 Jun 2004 13:08:35 +0000 (GMT) Received: from tomoyo.MyBSD.org.my (duke.void.net.my [202.157.186.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26EBA43D45; Mon, 14 Jun 2004 13:08:34 +0000 (GMT) (envelope-from skywizard@MyBSD.org.my) Received: from kasumi.MyBSD.org.my (unknown [219.94.60.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tomoyo.MyBSD.org.my (Postfix) with ESMTP id BFA016CC1F; Mon, 14 Jun 2004 21:09:32 +0800 (MYT) Date: Mon, 14 Jun 2004 21:08:24 +0800 From: Ariff Abdullah To: Nate Lawson Message-Id: <20040614210824.4cad9fb8.skywizard@MyBSD.org.my> In-Reply-To: <20040613155339.Q15532@root.org> References: <20040613064351.44f05257.skywizard@MyBSD.org.my> <20040613155339.Q15532@root.org> Organization: MyBSD X-Mailer: /usr/local/lib/ruby/1.8/net/smtp.rb Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-acpi@FreeBSD.org cc: freebsd-current@FreeBSD.org Subject: Re: MSI 6712 KT4AV asl/dsdt acpi + floppy hack 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 13:08:35 -0000 On Sun, 13 Jun 2004 15:54:04 -0700 (PDT) Nate Lawson wrote: > I just committed code changing the sysresource behavior. It should > work without your trick. Please cvsup and test. > > -Nate > > On Sun, 13 Jun 2004, Ariff Abdullah wrote: > > Those with MSI 6712 KT4AV motherboard plagued with floppy > > controller disability can try this to *re*enable your controller > > back. The trick is to move 0x03F0 resource out of SYSR , and put > > it under FDC0. Take a look at > > http://staff.mybsd.org.my/skywizard/FreeBSD/msi_acpi/ . > > > > Perhaps other simmilar cases can be cured using this trick. Good > > luck. > > I'm afraid the result still the same (done with update/buildworld). My various dmesg messages: http://staff.mybsd.org.my/skywizard/FreeBSD/msi_acpi/ 1) normal boot - dmesg.normal * Failed to detect at all. 2) debug.acpi.disabled="sysresource" (debug.acpi.disable yields nothing) - dmesg.disabled_sysresource * few attempts, detected on isa0 3) my dsdt hack - dmesg.dsdt * detected, on acpi0 -- Ariff Abdullah MyBSD http://www.MyBSD.org.my (IPv6/IPv4) http://staff.MyBSD.org.my (IPv6/IPv4) http://tomoyo.MyBSD.org.my (IPv6/IPv4) From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 14 15:12:23 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 F0D5016A4CF for ; Mon, 14 Jun 2004 15:12:23 +0000 (GMT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id BB7BB43D49 for ; Mon, 14 Jun 2004 15:12:23 +0000 (GMT) (envelope-from nate@root.org) Received: (qmail 20122 invoked by uid 1000); 14 Jun 2004 15:11:29 -0000 Date: Mon, 14 Jun 2004 08:11:29 -0700 (PDT) From: Nate Lawson To: Ariff Abdullah In-Reply-To: <20040614210824.4cad9fb8.skywizard@MyBSD.org.my> Message-ID: <20040614080620.S20092@root.org> References: <20040613064351.44f05257.skywizard@MyBSD.org.my> <20040614210824.4cad9fb8.skywizard@MyBSD.org.my> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@FreeBSD.org cc: freebsd-current@FreeBSD.org Subject: Re: MSI 6712 KT4AV asl/dsdt acpi + floppy hack 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 15:12:24 -0000 On Mon, 14 Jun 2004, Ariff Abdullah wrote: > On Sun, 13 Jun 2004 15:54:04 -0700 (PDT) > Nate Lawson wrote: > > I just committed code changing the sysresource behavior. It should > > work without your trick. Please cvsup and test. > > > > On Sun, 13 Jun 2004, Ariff Abdullah wrote: > > > Those with MSI 6712 KT4AV motherboard plagued with floppy > > > controller disability can try this to *re*enable your controller > > > back. The trick is to move 0x03F0 resource out of SYSR , and put > > > it under FDC0. Take a look at > > > http://staff.mybsd.org.my/skywizard/FreeBSD/msi_acpi/ . > > > > > > Perhaps other simmilar cases can be cured using this trick. Good > > > luck. > > > > > I'm afraid the result still the same (done with update/buildworld). My > various dmesg messages: Yes, sorry. My commit would fix the case where it was under SYSR (system resource) _and_ FDC0.CRS (floppy current resources) but it turns out to be missing there, as you found. Try seeing how it works for you with just adding the 0x03F0 line under FDC0 and not deleting it from SYSR. (I just want to be sure my resource code works for you, this is not a final fix.) I'll look into what might be done with PRS and SRS for this device. > http://staff.mybsd.org.my/skywizard/FreeBSD/msi_acpi/ > > 1) normal boot > - dmesg.normal > * Failed to detect at all. > > 2) debug.acpi.disabled="sysresource" (debug.acpi.disable yields > nothing) > - dmesg.disabled_sysresource > * few attempts, detected on isa0 > > 3) my dsdt hack > - dmesg.dsdt > * detected, on acpi0 -Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 14 17:09:55 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 BA58016A4CE; Mon, 14 Jun 2004 17:09:55 +0000 (GMT) Received: from tomoyo.MyBSD.org.my (duke.void.net.my [202.157.186.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3790343D58; Mon, 14 Jun 2004 17:09:47 +0000 (GMT) (envelope-from skywizard@MyBSD.org.my) Received: from kasumi.MyBSD.org.my (unknown [219.94.60.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tomoyo.MyBSD.org.my (Postfix) with ESMTP id BAF136CC8D; Tue, 15 Jun 2004 01:10:50 +0800 (MYT) Date: Tue, 15 Jun 2004 01:09:41 +0800 From: Ariff Abdullah To: Nate Lawson Message-Id: <20040615010941.43fd7f49.skywizard@MyBSD.org.my> In-Reply-To: <20040614080620.S20092@root.org> References: <20040613064351.44f05257.skywizard@MyBSD.org.my> <20040614210824.4cad9fb8.skywizard@MyBSD.org.my> <20040614080620.S20092@root.org> Organization: MyBSD X-Mailer: /usr/local/lib/ruby/1.8/net/smtp.rb Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-acpi@FreeBSD.org cc: freebsd-current@FreeBSD.org Subject: Re: MSI 6712 KT4AV asl/dsdt acpi + floppy hack 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:09:55 -0000 On Mon, 14 Jun 2004 08:11:29 -0700 (PDT) Nate Lawson wrote: > On Mon, 14 Jun 2004, Ariff Abdullah wrote: > > On Sun, 13 Jun 2004 15:54:04 -0700 (PDT) > > Nate Lawson wrote: > > > I just committed code changing the sysresource behavior. It > > > should work without your trick. Please cvsup and test. > > > > > > On Sun, 13 Jun 2004, Ariff Abdullah wrote: > > > > Those with MSI 6712 KT4AV motherboard plagued with floppy > > > > controller disability can try this to *re*enable your > > > > controller back. The trick is to move 0x03F0 resource out of > > > > SYSR , and put it under FDC0. Take a look at > > > > http://staff.mybsd.org.my/skywizard/FreeBSD/msi_acpi/ . > > > > > > > > Perhaps other simmilar cases can be cured using this trick. > > > > Good luck. > > > > > > > > I'm afraid the result still the same (done with > > update/buildworld). My various dmesg messages: > > Yes, sorry. My commit would fix the case where it was under SYSR > (system resource) _and_ FDC0.CRS (floppy current resources) but it > turns out to be missing there, as you found. Try seeing how it > works for you with just adding the 0x03F0 line under FDC0 and not > deleting it from SYSR. (I just want to be sure my resource code > works for you, this is not a final fix.) Looks perfect, without removing from SYSR and simply add the missing resource under FDC0.CRS *only*. > > I'll look into what might be done with PRS and SRS for this device. > I don't have to touch PRS/SRS, though it's look a little bit fishy, or perhaps the parser already did his job fixing it. -- Ariff Abdullah MyBSD http://www.MyBSD.org.my (IPv6/IPv4) http://staff.MyBSD.org.my (IPv6/IPv4) http://tomoyo.MyBSD.org.my (IPv6/IPv4) 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 763D316A4CE 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 5024F43D31 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 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 From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 15 05:23:05 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 77C6816A4CF for ; Tue, 15 Jun 2004 05:23:05 +0000 (GMT) Received: from mail.daemonspace.com (dns3.freebsd.org.cn [61.129.66.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id A79C343D41 for ; Tue, 15 Jun 2004 05:23:01 +0000 (GMT) (envelope-from delphij@frontfree.net) Received: (qmail 71933 invoked by uid 0); 15 Jun 2004 05:21:58 -0000 Received: from unknown (HELO beastie.frontfree.net) (218.107.145.7) by mail.daemonspace.com with SMTP; 15 Jun 2004 05:21:58 -0000 Received: from localhost (localhost.frontfree.net [127.0.0.1]) by beastie.frontfree.net (Postfix) with ESMTP id C67C811F8E; Tue, 15 Jun 2004 13:22:33 +0800 (CST) Received: from beastie.frontfree.net ([127.0.0.1]) by localhost (beastie.frontfree.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00916-02; Tue, 15 Jun 2004 13:22:32 +0800 (CST) Received: by beastie.frontfree.net (Postfix, from userid 1001) id 45E441184F; Tue, 15 Jun 2004 13:22:30 +0800 (CST) Date: Tue, 15 Jun 2004 13:22:29 +0800 From: Xin LI To: acpi@FreeBSD.org, current@FreeBSD.org Message-ID: <20040615052229.GA2249@frontfree.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-GPG-key-ID/Fingerprint: 0xCAEEB8C0 / 43B8 B703 B8DD 0231 B333 DC28 39FB 93A0 CAEE B8C0 X-GPG-Public-Key: http://www.delphij.net/delphij.asc X-Operating-System: FreeBSD beastie.frontfree.net 5.2-delphij FreeBSD 5.2-delphij #66: Tue Jun 15 11:25:44 CST 2004 root@beastie.frontfree.net:/usr/obj/usr/src/sys/BEASTIE i386 X-URL: http://www.delphij.net X-By: delphij@beastie.frontfree.net X-Location: Beijing, China X-Virus-Scanned: by amavisd-new at frontfree.net Subject: [backtrace] kernel dump when shutting down 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: Tue, 15 Jun 2004 05:23:05 -0000 --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello folks, I got a strange problem when having HTT enabled on a P4 2.8E processor. When rebooting the system, after the disk sync and the system is going to restart, it crashes and generates a crashdump. Strangely, the panic message seems to be corrupted. The kernel was built on fresh cvsup'ed code. I have did some local modifications, however, the crash persists no matter whether I have applied my modifications. Here is the backtrace: (kgdb) beastie# gdb -k kernel.debug /var/crash/vmcore.4 GNU gdb 5.2.1 (FreeBSD) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-undermydesk-freebsd"... panic: blockable sleep lock (sleep mutex) process lock @ /usr/src/sys/kern/= kern_sig.c:1510 panic messages: --- panic: blockable sleep lock (sleep mutex) process lock @ /usr/src/sys/kern/= kern_sig.c:1510 cpuid =3D 1;=20 boot() called on cpu#1 Uptime: 14m26s Dumping 1007 MB ad2: timeout waiting for write DRQad2: timeout waiting for write DRQad2: ti= meout waiting for write DRQad2: timeout waiting for write DRQad2: timeout w= aiting for write DRQ 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 = 256 272 288 304 320 336 352 368 384 400 416 432 448 464 480 496 512 528 544= 560 576 592 608 624 640 656 672 688 704 720 736 752 768 784 800 816 832 84= 8 864 880 896 912spin lock witness lock held by 0xc1e2b420 for > 5 seconds 928 944 960 976 992 --- #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:236 236 dumping++; (kgdb) bt full #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:236 No locals. #1 0xc0500256 in runq_choose (rq=3D0x0) at /usr/src/sys/kern/kern_switch.c= :583 ke =3D (struct kse *) 0x0 #2 0xc050b25a in kseq_choose (kseq=3D0xc1e29800) at /usr/src/sys/kern/sche= d_ule.c:783 ke =3D (struct kse *) 0xc1e2b420 swap =3D (struct runq *) 0xc1e2980c #3 0xc050c364 in sched_choose () at /usr/src/sys/kern/sched_ule.c:347 kseq =3D (struct kseq *) 0xc06c4970 ke =3D (struct kse *) 0xc1e2f780 The system works just fine when HTT is disabled. Kernel configuration is: # # BEASTIE -- Customized kernel configuration file for FreeBSD/i386 # # $Phantasm$ machine i386 cpu I686_CPU ident BEASTIE # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=3D-g # Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options INET # InterNETworking options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_DIRHASH # Improve performance on big directories options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=3D0 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options PFIL_HOOKS # pfil(9) framework # Debugging for use in -current options DDB # Enable the kernel debugger options INVARIANTS # Enable calls of extra sanity checking options INVARIANT_SUPPORT # Extra sanity checks of internal structures, re= quired by INVARIANTS options WITNESS # Enable checks to detect deadlocks and cycles options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel device apic # I/O APIC device isa device eisa device pci # ATA and ATAPI devices device ata device atadisk # ATA disk drives options ATA_STATIC_ID # Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Floating point support - do not disable. device npx # Add suspend/resume support for the i8254. device pmtimer # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # Pseudo devices - the number indicates how many units to allocate. device random # Entropy device device loop # Network loopback device ether # Ethernet support device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter #makeoptions CONF_CFLAGS=3D-fno-builtin #options MAXDSIZ=3D(1024UL*1024*1024) #options MAXSSIZ=3D(128UL*1024*1024) #options DFLDSIZ=3D(1024UL*1024*1024) options INCLUDE_CONFIG_FILE #options ADAPTIVE_MUTEXES #options MUTEX_NOINLINE options IPSEC options IPSEC_ESP device pf device pflog device pfsync options MROUTING options PIM options IPDIVERT options IPSTEALTH options RANDOM_IP_ID options ACCEPT_FILTER_DATA options ACCEPT_FILTER_HTTP options ZERO_COPY_SOCKETS #options HZ=3D100 #options PPS_SYNC device green_saver device crypto device cryptodev device rndtest device hifn device ubsec options PANIC_REBOOT_WAIT_TIME=3D0 #options PERFMON #options DEVICE_POLLING options AUTO_EOI_1 device acpi options DDB_UNATTENDED #options DDB_TRACE options NULLFS options FDESCFS The system used to crash before sync'ing disks. It seems that Nate's recent commit has removed that crash. More information available upon request. Cheers, --=20 Xin LI http://www.delphij.net/ See complete headers for GPG key and other information. --TB36FDmn/VVEgNH/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAzoeVOfuToMruuMARAj5RAJ0R+qCGErvrT+M/eqObGumnN/RItgCeJPWH +VsbSXCS8KxlIqAEgBGwPz8= =Kgn5 -----END PGP SIGNATURE----- --TB36FDmn/VVEgNH/-- From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 15 06:31:13 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 9755C16A4CE; Tue, 15 Jun 2004 06:31:13 +0000 (GMT) Received: from expert.ukrtel.net (expert.ukrtel.net [195.5.6.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53EF743D1D; Tue, 15 Jun 2004 06:31:12 +0000 (GMT) (envelope-from astesin@ukrtelecom.net) Received: from hoexc010.ho.ukrtelecom.net (doctor.ukrtel.net [195.5.37.134]) by expert.ukrtel.net (Netscape Messaging Server 3.5) with ESMTP id AAA3ABD; Tue, 15 Jun 2004 09:29:36 +0300 Received: by hoexc010.ukrtelecom.net with Internet Mail Service (5.5.2653.19) id ; Tue, 15 Jun 2004 09:31:09 +0300 Message-ID: <1152675CA9EDD71187130002B3CE5ADA08A6F449@hoexc010.ukrtelecom.net> From: astesin@ukrtelecom.net To: freebsd-acpi@FreeBSD.org, freebsd-current@FreeBSD.org Date: Tue, 15 Jun 2004 09:31:08 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="koi8-r" Subject: Intel S875WP1-E mothterboard and -CURRENT 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: Tue, 15 Jun 2004 06:31:13 -0000 Hello all, w/CURRENT as of 20040614 at a box built around Intel S875WP1-E motherboard (the one equipped with Promise SATA RAID0+1) and the new (Prescott kernel) P-IV 3.0 strange things do happen. Installed just yesterday on the brand-new box and when I say `reboot' it syncs discs Ok, than from time to time (not every time) after shutting down ACPI it not even panics (sometimes panics, sometimes - not) and freeses with very strange appearance on the console screen - like bytes in text mode video memory are randomly swapped making screen unreadable. Tried to catch this into debugger but with no luck. Any clues? What to to to diagnose this? How can I help to locate the bug? Thanks, Andrew From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 15 09:22:55 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 B7DDC16A4DA; Tue, 15 Jun 2004 09:22:55 +0000 (GMT) Received: from expert.ukrtel.net (expert.ukrtel.net [195.5.6.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FC6D43D2F; Tue, 15 Jun 2004 09:22:54 +0000 (GMT) (envelope-from astesin@ukrtelecom.net) Received: from hoexc010.ho.ukrtelecom.net (doctor.ukrtel.net [195.5.37.134]) by expert.ukrtel.net (Netscape Messaging Server 3.5) with ESMTP id AAAA2; Tue, 15 Jun 2004 12:20:59 +0300 Received: by hoexc010.ukrtelecom.net with Internet Mail Service (5.5.2653.19) id ; Tue, 15 Jun 2004 12:22:34 +0300 Message-ID: <1152675CA9EDD71187130002B3CE5ADA08A6F4F7@hoexc010.ukrtelecom.net> From: astesin@ukrtelecom.net To: delphij@frontfree.net, acpi@FreeBSD.org, current@FreeBSD.org Date: Tue, 15 Jun 2004 12:22:34 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="koi8-r" Subject: HA: [backtrace] kernel dump when shutting down 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: Tue, 15 Jun 2004 09:22:56 -0000 Hello Xin, > I got a strange problem when having HTT enabled on a P4 2.8E > processor. When rebooting the system, after the disk sync and > the system is going to restart, it crashes and generates a > crashdump. Strangely, the panic message seems to be corrupted. That's exactly what I'm seeing on P4 3.0E (yes, also `E') and Intel S875WP1-E motherboard ftp://download.intel.com/support/motherboards/server/s875wp1-e/tps.pdf , but it even doesn't do crashdump, just freeses. And not each time but maybe 3-4 of 5 reboots. BTW running `halt' instead of reboot worked. Sorry I didn't had time this night to try a kernel with debugging. > The system used to crash before sync'ing disks. It seems that > Nate's recent commit has removed that crash. More information > available upon request. Exactly. 5.2.1-R and -CURRENT of late May were also tested, they were crashing before syncing discs, 20040614 -CURRENT crashes (freeses) after syncing. People say that on older P4 CPUs (Northwood core) that do not have this problem, only on `E'-s (??? Strange enough). WBR, Andrew From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 15 12:24:45 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 2387816A4CF for ; Tue, 15 Jun 2004 12:24:45 +0000 (GMT) Received: from mail.FreeBSD.org.cn (dns3.freebsd.org.cn [61.129.66.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2515843D2F for ; Tue, 15 Jun 2004 12:24:43 +0000 (GMT) (envelope-from delphij@frontfree.net) Received: (qmail 8606 invoked by uid 0); 15 Jun 2004 12:23:18 -0000 Received: from unknown (HELO beastie.frontfree.net) (218.107.145.7) by mail.FreeBSD.org.cn with AES256-SHA encrypted SMTP; 15 Jun 2004 12:23:18 -0000 Received: from localhost (localhost.frontfree.net [127.0.0.1]) by beastie.frontfree.net (Postfix) with ESMTP id D9870121A3; Tue, 15 Jun 2004 19:55:51 +0800 (CST) Received: from beastie.frontfree.net ([127.0.0.1]) by localhost (beastie.frontfree.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01196-09; Tue, 15 Jun 2004 19:55:50 +0800 (CST) Received: by beastie.frontfree.net (Postfix, from userid 1001) id EEB70121A0; Tue, 15 Jun 2004 19:55:48 +0800 (CST) Date: Tue, 15 Jun 2004 19:55:48 +0800 From: Xin LI To: astesin@ukrtelecom.net Message-ID: <20040615115548.GA1250@frontfree.net> References: <1152675CA9EDD71187130002B3CE5ADA08A6F4F7@hoexc010.ukrtelecom.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ibTvN161/egqYuK8" Content-Disposition: inline In-Reply-To: <1152675CA9EDD71187130002B3CE5ADA08A6F4F7@hoexc010.ukrtelecom.net> User-Agent: Mutt/1.4.2.1i X-GPG-key-ID/Fingerprint: 0xCAEEB8C0 / 43B8 B703 B8DD 0231 B333 DC28 39FB 93A0 CAEE B8C0 X-GPG-Public-Key: http://www.delphij.net/delphij.asc X-Operating-System: FreeBSD beastie.frontfree.net 5.2-delphij FreeBSD 5.2-delphij #66: Tue Jun 15 11:25:44 CST 2004 root@beastie.frontfree.net:/usr/obj/usr/src/sys/BEASTIE i386 X-URL: http://www.delphij.net X-By: delphij@beastie.frontfree.net X-Location: Beijing, China X-Virus-Scanned: by amavisd-new at frontfree.net cc: acpi@FreeBSD.org cc: current@FreeBSD.org Subject: Re: HA: [backtrace] kernel dump when shutting down 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: Tue, 15 Jun 2004 12:24:45 -0000 --ibTvN161/egqYuK8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 15, 2004 at 12:22:34PM +0300, astesin@ukrtelecom.net wrote: > Hello Xin, >=20 > > I got a strange problem when having HTT enabled on a P4 2.8E=20 > > processor. When rebooting the system, after the disk sync and=20 > > the system is going to restart, it crashes and generates a=20 > > crashdump. Strangely, the panic message seems to be corrupted. >=20 > That's exactly what I'm seeing on P4 3.0E (yes, also `E') and Intel > S875WP1-E motherboard > ftp://download.intel.com/support/motherboards/server/s875wp1-e/tps.pdf , = but > it even doesn't do crashdump, just freeses. And not each time but maybe 3= -4 > of 5 reboots. BTW running `halt' instead of reboot worked. Sorry I didn't > had time this night to try a kernel with debugging. Ah... Yes, I'm using Intel motherboard too, however, with a different chipset. Are you sure that the system is actually frozen? In my case, nothing appeared in console, however, pressing Ctrl+C will reboot immediately, which is the behavior when system is dumping core. In addition, I have successfully obtained crashdump. The backtrace itself seemed to be meaningless. I thought there might be some locking problem within the shutdown code. I will do some experiments after my competitive examination for bachelor's degree tomorrow. > > The system used to crash before sync'ing disks. It seems that=20 > > Nate's recent commit has removed that crash. More information=20 > > available upon request. >=20 > Exactly. 5.2.1-R and -CURRENT of late May were also tested, they were > crashing before syncing discs, 20040614 -CURRENT crashes (freeses) after > syncing. >=20 > People say that on older P4 CPUs (Northwood core) that do not have this > problem, only on `E'-s (??? Strange enough). Exactly. The P4 box at my lab does work correctly. Let's check the developers' manual from Intel and we may find something useful :-) Cheers, --=20 Xin LI http://www.delphij.net/ See complete headers for GPG key and other information. --ibTvN161/egqYuK8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAzuPEOfuToMruuMARAvMUAKCLTzTZUY0CYr8NglinRXLz5upjewCfbRC9 l6DMj0Ewag/huAFnTbsl8DA= =MxtJ -----END PGP SIGNATURE----- --ibTvN161/egqYuK8-- From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 15 17:31:14 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 C583616A4CE for ; Tue, 15 Jun 2004 17:31:14 +0000 (GMT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 8B98743D60 for ; Tue, 15 Jun 2004 17:31:14 +0000 (GMT) (envelope-from nate@root.org) Received: (qmail 27833 invoked by uid 1000); 15 Jun 2004 17:30:44 -0000 Date: Tue, 15 Jun 2004 10:30:44 -0700 (PDT) From: Nate Lawson To: arch@freebsd.org, acpi@freebsd.org Message-ID: <20040615102506.F27810@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: ACPI mpsafe patch 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: Tue, 15 Jun 2004 17:31:14 -0000 I've gone through this carefully and have tested it a lot and it appears ready for mainstream testing. I'm especially interested in SMP testing, with and without WITNESS. Run the following script on your system to test it (start 2 or 3 of these): #!/bin/sh sysctl hw.acpi.thermal.polling_rate=1 sysctl hw.acpi.battery.info_expire=1 while [ 1 ]; do apm sysctl hw.acpi done While that's going, use the system normally, suspend/resume, etc. The few parts that aren't done are acpi_video, acpi_asus, and acpi_toshiba. Once I finish these and a couple nits, I'll provide a final patch for testing as well as fix any problems found. http://www.root.org/~nate/freebsd/acpi_mpsafe.diff.gz Thanks, -Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 15 17:55:26 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 7C61A16A506; Tue, 15 Jun 2004 17:55:26 +0000 (GMT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D9FF43D53; Tue, 15 Jun 2004 17:55:25 +0000 (GMT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Tue, 15 Jun 2004 13:55:17 -0400 Message-ID: From: Don Bowman To: "'current@freebsd.org'" , "'acpi@freebsd.org'" Date: Tue, 15 Jun 2004 13:55:13 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C45301.E8603B70" Subject: acpi interrupt storm when disabling, IPI hang 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: Tue, 15 Jun 2004 17:55:26 -0000 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C45301.E8603B70 Content-Type: text/plain; charset="iso-8859-1" When i run 'acpiconf -d', i get an interrupt storm on irq9... vmstat -i shows ~1000/s. Jun 15 13:41:33 cdata kernel: Interrupt storm detected on "irq9: acpi0"; throttling interrupt source when i try to re-enable, i get an error: # acpiconf -e acpi0: interrupt handler already installed ACPI-0210: *** Error: Unable to install System Control Interrupt Handler, AE_ALREADY_EXISTS acpiconf: enable failed: Device not configured # System is a Supermicro X5DPE motherboard, dual 2.8GHz Xeon, 533MHz FSB, Intel e7501 chipset. # sysctl hw.acpi hw.acpi.supported_sleep_state: S1 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 0 hw.acpi.verbose: 0 hw.acpi.disable_on_poweroff: 0 hw.acpi.reset_video: 1 hw.acpi.cpu.cx_supported: C1/0 hw.acpi.cpu.cx_lowest: C1 hw.acpi.cpu.cx_usage: 99% The system will not boot 5.x if acpi is disabled. It will run 4.x without trouble tho. I am currently debugging a problem where 2 of the processors are in acpi_cpu_c1, 1 is in idle, and 1 calls smp_tlb_shootdown, but the IPI to one of the other processors never completes, so it hangs. I have a core file from this state. (kgdb) printStack2 0xed09acdc : 0xa10cc483 : 0xf689c3c9 : 0xe800768d : 0xb808c483 : 0xe90cc483 (kgdb) printStack2 0xed09dcd8 : 0x5590c3c9 : 0x0000d4e9 : 0xf689c3c9 : 0xe800768d : 0xb808c483 : 0xe90cc483 (kgdb) printStack2 0xed0a0cd8 : 0x5590c3c9 : 0x0000d4e9 : 0xf689c3c9 : 0xe800768d : 0xb808c483 : 0xe90cc483 (kgdb) printStack2 0xeec7dc3c : 0x0128978b : 0x000350e9 : 0x6404c483 : 0x8d04c483 : 0x5bf8658d : 0x8d04c483 : 0xc483f689 : 0xeb04c483 : 0xb808c483 : 0xe90cc483 Sometimes that last one is like: #7 0xc068e066 in smp_tlb_shootdown (vector=246, addr1=0, addr2=0) at machine/cpufunc.h:305 #8 0xc068e1d0 in smp_invlpg_range (addr1=3876638720, addr2=3876769792) at /usr/src/sys/i386/i386/mp_machdep.c:1030 #9 0xc0690643 in pmap_invalidate_range (pmap=0xc077dd80, sva=3876638720, eva=3876769792) at /usr/src/sys/i386/i386/pmap.c:640 #10 0xc0690be0 in pmap_qenter (sva=3876638720, m=0xde548600, count=0) at /usr/src/sys/i386/i386/pmap.c:958 #11 0xc058aca3 in cluster_rbuild (vp=0xc83db104, filesize=1073741824, lbn=40844, blkno=241691456, size=16384, run=8, fbp=0x0) at /usr/src/sys/kern/vfs_cluster.c:508 #12 0xc058a3a8 in cluster_read (vp=0xc83db104, filesize=1073741824, lblkno=40844, size=16384, cred=0x0, totread=8192, seqcount=127, bpp=0x0) at /usr/src/sys/kern/vfs_cluster.c:263 #13 0xc063dc4a in ffs_read (ap=0x0) at /usr/src/sys/ufs/ffs/ffs_vnops.c:441 #14 0xc059e325 in vn_read (fp=0xc5a02198, uio=0xf53c1c88, active_cred=0xc59f6280, flags=0, td=0xc6645e70) at vnode_if.h:398 #15 0xc05655bc in dofileread (td=0xc6645e70, fp=0xc5a02198, fd=23, buf=0x706b40c0, nbyte=8192, offset=0, flags=0) at /usr/src/sys/sys/file.h:233 #16 0xc0565467 in read (td=0xc6645e70, uap=0xf53c1d14) at /usr/src/sys/kern/sys_generic.c:107 #17 0xc06956f7 in syscall (frame= {tf_fs = 138149935, tf_es = 138149935, tf_ds = -1078001617, tf_edi = 81682, tf_esi = 137404728, tf_ebp = -1077946040, tf_isp = -180609676, tf_ebx = 608, tf_edx = 23, tf_ecx = 137834496, tf_eax = 3, tf_trapno = 22, tf_err = 2, tf_eip = 1749868123, tf_cs = 31, tf_eflags = 582, tf_esp = -1077946068, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1004 #18 0x684cde5b in ?? () (kgdb) disass acpi_cpu_c1 Dump of assembler code for function acpi_cpu_c1: 0xc084cc44 : push %ebp 0xc084cc45 : mov %esp,%ebp 0xc084cc47 : sti 0xc084cc48 : hlt 0xc084cc49 : leave 0xc084cc4a : ret 0xc084cc4b : nop End of assembler dump. (kgdb) disass acpi_cpu_idle Dump of assembler code for function acpi_cpu_idle: 0xc084caa0 : push %ebp ... 0xc084cb4f : cltd 0xc084cb50 : idivl 0xc0753f0c 0xc084cb56 : mov %eax,0x9c(%esi) 0xc084cb5c : call 0xc084cc44 0xc084cb61 : jmp 0xc084cc3a 0xc084cb66 : mov %esi,%esi 0xc084cb68 : cmpl $0x3,0x4(%edi) 0xc084cb6c : jne 0xc084cb88 ------_=_NextPart_000_01C45301.E8603B70 Content-Type: application/octet-stream; name="dmesg.boot" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="dmesg.boot" Copyright (c) 1992-2004 The FreeBSD Project.=0A= Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, = 1994=0A= The Regents of the University of California. All rights reserved.=0A= FreeBSD 5.2-CURRENT #10: Thu Jun 10 08:54:08 EDT 2004=0A= root@cdata.sandvine.com:/usr/obj/usr/src/sys/CDATA=0A= Preloaded elf kernel "/boot/kernel/kernel" at 0xc086b000.=0A= Preloaded elf module "/boot/kernel/acpi.ko" at 0xc086b30c.=0A= ACPI APIC Table: =0A= Timecounter "i8254" frequency 1193182 Hz quality 0=0A= CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2799.22-MHz 686-class CPU)=0A= Origin =3D "GenuineIntel" Id =3D 0xf27 Stepping =3D 7=0A= = Features=3D0xbfebfbff=0A= Hyperthreading: 2 logical CPUs=0A= real memory =3D 4026007552 (3839 MB)=0A= avail memory =3D 3940634624 (3758 MB)=0A= FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs=0A= cpu0 (BSP): APIC ID: 0=0A= cpu1 (AP): APIC ID: 1=0A= cpu2 (AP): APIC ID: 6=0A= cpu3 (AP): APIC ID: 7=0A= Pentium 4 TCC support enabled, current performance 100%=0A= ioapic0 irqs 0-23 on motherboard=0A= ioapic1 irqs 24-47 on motherboard=0A= ioapic2 irqs 48-71 on motherboard=0A= ioapic3 irqs 72-95 on motherboard=0A= ioapic4 irqs 96-119 on motherboard=0A= random: =0A= Pentium Pro MTRR support enabled=0A= npx0: [FAST]=0A= npx0: on motherboard=0A= npx0: INT 16 interface=0A= acpi0: on motherboard=0A= acpi0: [GIANT-LOCKED]=0A= pcibios: BIOS version 2.10=0A= acpi0: Power Button (fixed)=0A= Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000=0A= acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on = acpi0=0A= cpu0: on acpi0=0A= cpu1: on acpi0=0A= cpu2: on acpi0=0A= cpu3: on acpi0=0A= pcib0: port 0xcf8-0xcff on acpi0=0A= pci0: on pcib0=0A= pci0: at device 0.1 (no driver attached)=0A= pcib1: at device 2.0 on pci0=0A= pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.HLB_ - = AE_NOT_FOUND=0A= pci1: on pcib1=0A= pci1: at device 28.0 (no driver = attached)=0A= pcib2: at device 29.0 on pci1=0A= pci2: on pcib2=0A= pci1: at device 30.0 (no driver = attached)=0A= pcib3: at device 31.0 on pci1=0A= pci3: on pcib3=0A= em0: port = 0x3000-0x303f mem 0xf4200000-0xf421ffff irq 28 at device 2.0 on pci3=0A= em0: [GIANT-LOCKED]=0A= em0: Ethernet address: 00:30:48:2a:a0:1c=0A= em0: Speed:N/A Duplex:N/A=0A= em1: port = 0x3040-0x307f mem 0xf4220000-0xf423ffff irq 29 at device 2.1 on pci3=0A= em1: [GIANT-LOCKED]=0A= em1: Ethernet address: 00:30:48:2a:a0:1d=0A= em1: Speed:N/A Duplex:N/A=0A= pci0: at device 2.1 (no driver attached)=0A= pcib4: at device 3.0 on pci0=0A= pcib4: could not get PCI interrupt routing table for \\_SB_.PCI0.HLC_ - = AE_NOT_FOUND=0A= pci4: on pcib4=0A= pci4: at device 28.0 (no driver = attached)=0A= pcib5: at device 29.0 on pci4=0A= pci5: on pcib5=0A= aac0: mem 0xf8000000-0xfbffffff irq 96 at = device 1.0 on pci5=0A= aac0: [FAST]=0A= aac0: i960RX 100MHz, 48MB cache memory, optional battery present=0A= aac0: Kernel 4.0-0, Build 6011, S/N ba8ff3=0A= aac0: Supported = Options=3D1f7e=0A= aacp0: on aac0=0A= aacp1: on aac0=0A= pci4: at device 30.0 (no driver = attached)=0A= pcib6: at device 31.0 on pci4=0A= pci6: on pcib6=0A= pci0: at device 3.1 (no driver attached)=0A= uhci0: port = 0x2000-0x201f irq 16 at device 29.0 on pci0=0A= uhci0: [GIANT-LOCKED]=0A= usb0: on uhci0=0A= usb0: USB revision 1.0=0A= uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1=0A= uhub0: 2 ports with 2 removable, self powered=0A= uhci1: port = 0x2020-0x203f irq 19 at device 29.1 on pci0=0A= uhci1: [GIANT-LOCKED]=0A= usb1: on uhci1=0A= usb1: USB revision 1.0=0A= uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1=0A= uhub1: 2 ports with 2 removable, self powered=0A= uhci2: port = 0x2040-0x205f irq 18 at device 29.2 on pci0=0A= uhci2: [GIANT-LOCKED]=0A= usb2: on uhci2=0A= usb2: USB revision 1.0=0A= uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1=0A= uhub2: 2 ports with 2 removable, self powered=0A= pcib7: at device 30.0 on pci0=0A= pci7: on pcib7=0A= pci7: at device 1.0 (no driver attached)=0A= isab0: at device 31.0 on pci0=0A= isa0: on isab0=0A= atapci0: port = 0x2080-0x208f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on = pci0=0A= ata0: at 0x1f0 irq 14 on atapci0=0A= ata1: at 0x170 irq 15 on atapci0=0A= ichsmb0: port 0x1100-0x111f irq = 17 at device 31.3 on pci0=0A= ichsmb0: [GIANT-LOCKED]=0A= smbus0: on ichsmb0=0A= smb0: on smbus0=0A= acpi_button0: on acpi0=0A= atkbdc0: port 0x64,0x60 irq 1 on acpi0=0A= atkbd0: flags 0x1 irq 1 on atkbdc0=0A= kbd0 at atkbd0=0A= atkbd0: [GIANT-LOCKED]=0A= sio0 port 0x3f8-0x3ff irq 4 on acpi0=0A= sio0: type 16550A, console=0A= sio1 port 0x2f8-0x2ff irq 3 on acpi0=0A= sio1: type 16550A=0A= fdc0: port = 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0=0A= fdc0: FIFO enabled, 8 bytes threshold=0A= orm0: