From owner-freebsd-acpi@FreeBSD.ORG Tue Apr 6 06:24:48 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 548E016A4CE for ; Tue, 6 Apr 2004 06:24:48 -0700 (PDT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3F6C43D45 for ; Tue, 6 Apr 2004 06:24:47 -0700 (PDT) (envelope-from marks@dell-laptop.6bone.nl) Received: by postman.ripe.net (Postfix, from userid 8) id C0D904E6BD; Tue, 6 Apr 2004 15:23:34 +0200 (CEST) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id 887964E5DE for ; Tue, 6 Apr 2004 15:23:34 +0200 (CEST) Received: from dell-laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id i36DNYc4024367 for ; Tue, 6 Apr 2004 15:23:34 +0200 Received: (nullmailer pid 22328 invoked by uid 1001); Tue, 06 Apr 2004 13:23:34 -0000 Date: Tue, 6 Apr 2004 15:23:34 +0200 From: Mark Santcroos To: acpi@freebsd.org Message-ID: <20040406132334.GA22310@laptop.6bone.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Status: N 0.004644 / 0.0 / 0.0 / disabled X-RIPE-Signature: dc9da5912b293cec787fda9d264448cb Subject: Important announcement 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, 06 Apr 2004 13:24:48 -0000 een, twee, drie, test! :) From owner-freebsd-acpi@FreeBSD.ORG Tue Apr 6 12:00:47 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 A456D16A4CE for ; Tue, 6 Apr 2004 12:00:47 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 8D6E043D4C for ; Tue, 6 Apr 2004 12:00:47 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 28908 invoked by uid 1000); 6 Apr 2004 19:00:28 -0000 Date: Tue, 6 Apr 2004 12:00:28 -0700 (PDT) From: Nate Lawson To: current@freebsd.org Message-ID: <20040406113717.I28713@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org cc: acpi-jp@jp.freebsd.org Subject: Announcing: freebsd-acpi@ mailing list 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, 06 Apr 2004 19:00:47 -0000 There is a new mailing list for discussing ACPI support in FreeBSD. It is freebsd-acpi@ (or just acpi@). Topics for discussion include new drivers or feature support in acpi, bug reports, and general power management discussions. Subscription info is below... http://lists.freebsd.org/mailman/listinfo/freebsd-acpi acpi-jp@ will continue to exist for Japanese-language discussions about ACPI and the FreeBSD ACPI developers will continue to monitor it. We expect that most discussions will happen on the new list as it is better integrated with related lists (i.e. current@). Thanks, Nate From owner-freebsd-acpi@FreeBSD.ORG Thu Apr 8 11:32:10 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 D3EE216A514 for ; Thu, 8 Apr 2004 11:32:10 -0700 (PDT) Received: from cliffclavin.cs.rpi.edu (cliffclavin.cs.rpi.edu [128.213.1.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 653A443D3F for ; Thu, 8 Apr 2004 11:32:10 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from monica.cs.rpi.edu (root@monica.cs.rpi.edu [128.213.7.2]) i38IW9lE038031 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 8 Apr 2004 14:32:09 -0400 (EDT) Received: from monica.cs.rpi.edu (crossd@localhost [127.0.0.1]) by monica.cs.rpi.edu (8.12.9p2/8.12.6) with ESMTP id i38IW95j052796 for ; Thu, 8 Apr 2004 14:32:09 -0400 (EDT) (envelope-from crossd@monica.cs.rpi.edu) Received: from localhost (crossd@localhost)i38IW9LY052793 for ; Thu, 8 Apr 2004 14:32:09 -0400 (EDT) (envelope-from crossd@monica.cs.rpi.edu) Date: Thu, 8 Apr 2004 14:32:09 -0400 (EDT) From: "David E. Cross" To: freebsd-acpi@freebsd.org Message-ID: <20040408141941.W45013@monica.cs.rpi.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.37 Subject: ACPI,SMP(?), and 5.2.1-RELEASE 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: Thu, 08 Apr 2004 18:32:11 -0000 I recently upgraded my odl ASUS P2B-DS runnig BIOS version 1012 to 5.2.1-RELEASE (from 4.9.1) and noticed that the system is spending 50% of its time in interrupt while idle running any kernel (including GENERIC). When the system is booted without ACPI everything runs correctly and no interrupt load is observed. Additionally on shutting down the kernel messages after disabling ACPI are completely mangled. Like 90% of the time on a "halt" the "System is halted\nSystem is safe to power down or press any key to reboot" is completely missing or mangled to the point of non recognition. When it is visible I sometimes see a message like "Stray irq 2", and recently I got "stray irq 20\n rq 20" (just to give an example of how things are mangled after ACPI shutdown). the "2" bit in the IRQ is consistent whenever I am able to observe it, however I don't have anything in dmesg on irq 2, 12, 20, 21, 22, or 23 (where the IRQs max out according to the IOAPIC line) and I cannot think of anything else that has "2" in the irq number. So why am I not getting stray IRQ errors earlier? Is there any way to tell on a running system which IRQ line is getting spammed and "why"? Any help on this would be greatly appreciated as I would like to run ACPI on this system so that I can do power offs for things like UPS-Battery failure, etc. -- David E. Cross From owner-freebsd-acpi@FreeBSD.ORG Thu Apr 8 17:15:49 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 C10E216A4CE for ; Thu, 8 Apr 2004 17:15:49 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 4229E43D45 for ; Thu, 8 Apr 2004 17:15:49 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 44338 invoked by uid 1000); 9 Apr 2004 00:15:50 -0000 Date: Thu, 8 Apr 2004 17:15:50 -0700 (PDT) From: Nate Lawson To: "David E. Cross" In-Reply-To: <20040408141941.W45013@monica.cs.rpi.edu> Message-ID: <20040408171316.U44332@root.org> References: <20040408141941.W45013@monica.cs.rpi.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@freebsd.org Subject: Re: ACPI,SMP(?), and 5.2.1-RELEASE 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: Fri, 09 Apr 2004 00:15:49 -0000 On Thu, 8 Apr 2004, David E. Cross wrote: > I recently upgraded my odl ASUS P2B-DS runnig BIOS version 1012 to > 5.2.1-RELEASE (from 4.9.1) and noticed that the system is spending 50% of > its time in interrupt while idle running any kernel (including GENERIC). > When the system is booted without ACPI everything runs correctly and no > interrupt load is observed. Send the output of vmstat -i so I can see the interrupt load. Try booting with: hint.apic.0.disabled="1" This is likely an APIC issue if this fixes it. > Additionally on shutting down the kernel messages after disabling ACPI are > completely mangled. Like 90% of the time on a "halt" the "System is > halted\nSystem is safe to power down or press any key to reboot" is > completely missing or mangled to the point of non recognition. When it is > visible I sometimes see a message like "Stray irq 2", and recently I got > "stray irq 20\n rq 20" (just to give an example of how things are > mangled after ACPI shutdown). the "2" bit in the IRQ is consistent > whenever I am able to observe it, however I don't have anything in dmesg > on irq 2, 12, 20, 21, 22, or 23 (where the IRQs max out according to the > IOAPIC line) and I cannot think of anything else that has "2" in the irq > number. So why am I not getting stray IRQ errors earlier? Is there any > way to tell on a running system which IRQ line is getting spammed and > "why"? > > Any help on this would be greatly appreciated as I would like to run ACPI > on this system so that I can do power offs for things like UPS-Battery > failure, etc. This also indicates an APIC problem. jhb@ has a patch that hopefully will be committed to allow disabling irq src overrides. Just for kicks, also reply with the output of "acpidump -t" on your system. -Nate From owner-freebsd-acpi@FreeBSD.ORG Thu Apr 8 19:21:30 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 18E7A16A4CE for ; Thu, 8 Apr 2004 19:21:30 -0700 (PDT) Received: from cliffclavin.cs.rpi.edu (cliffclavin.cs.rpi.edu [128.213.1.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3FEF43D49 for ; Thu, 8 Apr 2004 19:21:29 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from kiki.cs.rpi.edu (kiki.cs.rpi.edu [128.213.50.12]) i392LQlE054516 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Apr 2004 22:21:26 -0400 (EDT) Received: from kiki.cs.rpi.edu (localhost [127.0.0.1]) by kiki.cs.rpi.edu (8.12.9/8.12.6) with ESMTP id i392LQ4F015213; Thu, 8 Apr 2004 22:21:26 -0400 (EDT) (envelope-from crossd@kiki.cs.rpi.edu) Received: from localhost (crossd@localhost)i392LO5C015210; Thu, 8 Apr 2004 22:21:25 -0400 (EDT) (envelope-from crossd@kiki.cs.rpi.edu) Date: Thu, 8 Apr 2004 22:21:23 -0400 (EDT) From: "David E. Cross" To: Nate Lawson In-Reply-To: <20040408171316.U44332@root.org> Message-ID: <20040408213024.T15205@kiki.cs.rpi.edu> References: <20040408141941.W45013@monica.cs.rpi.edu> <20040408171316.U44332@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.37 cc: freebsd-acpi@freebsd.org Subject: Re: ACPI,SMP(?), and 5.2.1-RELEASE 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: Fri, 09 Apr 2004 02:21:30 -0000 On Thu, 8 Apr 2004, Nate Lawson wrote: > On Thu, 8 Apr 2004, David E. Cross wrote: > Send the output of vmstat -i so I can see the interrupt load. interrupt total rate irq6: fdc0 9 0 irq8: rtc 20328 127 irq14: ata0 39 0 irq15: ata1 64 0 irq16: ahc1 407 2 irq17: pcm0 2 0 irq19: xl0 uhci0+ 2373 14 irq20: acpi0 6979146 43893 irq0: clk 15881 99 Total 7018239 44139 (ahc0 isn't shown, but that is on irq19 also, I am assuming that is what the + is for) > Try booting with: > hint.apic.0.disabled="1" > This is likely an APIC issue if this fixes it. > Yup, that fixes it. > This also indicates an APIC problem. jhb@ has a patch that hopefully will > be committed to allow disabling irq src overrides. Just for kicks, also > reply with the output of "acpidump -t" on your system. This is the result of running "acpidump -t" on a system with the APIC disabled: (this is typed by hand unfortunately) /* RSD PTR: OEM=ASUS, ACPI_Rev=1.0x (0) RSDT=0x1fffd000, cksum=119 */ /* RSDT: Length=48, Revision=1, Checksum=182, OEMID=ASUS, OEM Table ID=P2B-DS, OEM Revision=0x58582e32, Creator ID=ASUS, Creator Revision=0x31303030 Entries={ 0x1fffd100, 0x1fffd040, 0x1fffd080 } */ /* FADT: FACS=0x1ffff000, DSDT=0x1fffd180 INT_MODEL=PIC Preferred_PM_Profile=Unspecified (0) SCI_INT=9 SMI_CMD=0xb2, ACPI_ENABLE=0xa1, ACPI_DISABLE=0xa0, S4BIOS_REQ=0x0 PSTATE_CNT=0x0 PM1a_EVT_BLK=0xe400-0xe403 PM1a_CNT_BLK=0xe404-0xe405 PM_TMR_BLK=0xe408-0xe40b GPE0_BLK=0xe40c-0xe40f P_LVL2_LAT=190 us, P_LVL3_LAT=1900 us FLUSH_SIZE=0, FLUSH_STRIDE=0 DUTY_OFFSET=1, DUTY_WIDTH=0 DAY_ALRM=13, MON_ALRM=0, CENTURY=0 IAPC_BOOT_ARCH= Flags={WBINVD,PROC_C1,SLP_BUTTON,RTC_S4} */ /* FACS: Length=64, HwSig=0x00000000, Firm_Wake_Vec=0x00000000 Global_Lock= Flags= Version=0 */ /* DSDT: Length=7645, Revision=1, Checksum=71, OEMID=ASUS, OEM Table ID=P2B-DS, OEM Revision=0x1000, Creator ID=MSFT, Creator Revision=0x1000001 */ /* BOOT: Length=40, Revision=1, Checksum=12, OEMID=ASUS, OEM Table ID=P2B-DS, OEM Revision=0x58582e32, Creator ID=ASUS, Creator Revision=0x31303030 */ /* APIC: Length=92, Revision=1, Checksum=58, OEMID=ASUS, OEM Table ID=P2B-DS, OEM Revision=0x0, Creator ID=, Creator Revision=0x0 Local APIC ADDR=0xfee00000 Flags={PC-AT} Type=IO APIC APIC ID=2 INT BASE=0 ADDR=0x00000000fec00000 Type=INT Override BUS=0 IRQ=0 INTR=2 Flags={Polarity=conforming, Trigger=edge} Type=INT Override BUS=0 IRQ=9 INTR=20 Flags={Polarity=active-hi, Trigger=level} Type=Local APIC ACPI CPU=0 Flags={ENABLED} APIC ID=1 Type=Local APIC ACPI CPU=1 Flags={ENABLED} APIC ID=0 */ A brief glance suggests that this info is the same regardless of the hint.apic.0.disabled flag. Also... hmm "Polartity=active-hi, and level triggered" while on IRQ 20 would certainly explain an interrupt storm, unless some other settings are changed. Is there (was there) any possibility of data-loss because of this. Things look fine, but is there the possibility that something went boom in the background? restoring from backups is "easy" now, but if I continue to do work on and there is something wrong in the background then it could get painful in the future. Is there anything wrong with running with APIC disabled? Should I run with APIC disabled or ACPI disabled? Thank you very much for your time. -- David E. Cross From owner-freebsd-acpi@FreeBSD.ORG Fri Apr 9 10:58: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 2796C16A4CF for ; Fri, 9 Apr 2004 10:58:05 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id D529143D39 for ; Fri, 9 Apr 2004 10:58:04 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 49150 invoked by uid 1000); 9 Apr 2004 17:58:05 -0000 Date: Fri, 9 Apr 2004 10:58:05 -0700 (PDT) From: Nate Lawson To: "Brown, Len" In-Reply-To: Message-ID: <20040409105230.L48723@root.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@freebsd.org Subject: Re: ACPI SCI flags 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: Fri, 09 Apr 2004 17:58:05 -0000 On Fri, 9 Apr 2004, Brown, Len wrote: > Nate, > > I think we finally got the vague part of the ACPI spec > regarding SCI polarity/trigger cleared up. In Linux > as of 2.4.26 and 2.6.5 we now do this: > > PIC mode: > force level/low via ELCR always. > > APIC mode: > no override: > force level/low always > override w/ explicit polarity/trigger: > do exactly what override says > override w/ "compatible" polarity/trigger: > compatible trigger = level > compatible polarity = low > > Of course this makes the SCI a special case WRT > interpreting "compatibility" as compared to other > overrides. Thanks for the concise summary. For an explicit override that is level/high, this appears not to work in some cases. Or it may be the conforming override for irq 2 that is causing the problems. See this message: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=11443+0+current/freebsd-acpi -Nate From owner-freebsd-acpi@FreeBSD.ORG Fri Apr 9 11:13:56 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 EC99D16A4CE; Fri, 9 Apr 2004 11:13:56 -0700 (PDT) Received: from hermes.fm.intel.com (fmr01.intel.com [192.55.52.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7DBF43D1F; Fri, 9 Apr 2004 11:13:56 -0700 (PDT) (envelope-from len.brown@intel.com) Received: from petasus-pilot.fm.intel.com (petasus-pilot.fm.intel.com [10.1.192.44]) 1.15 2004/01/30 18:16:28 root Exp $) with ESMTP id i39IDgHw011526; Fri, 9 Apr 2004 18:13:42 GMT Received: from fmsmsxvs043.fm.intel.com (fmsmsxvs043.fm.intel.com [132.233.42.129]) major-inner.mc,v 1.10 2004/03/01 19:21:36 root Exp $) with SMTP id i39IDWJr018681; Fri, 9 Apr 2004 18:13:48 GMT Received: from fmsmsx331.amr.corp.intel.com ([132.233.42.135]) M2004040911135125223 ; Fri, 09 Apr 2004 11:13:51 -0700 Received: from fmsmsx312.amr.corp.intel.com ([132.233.42.227]) by fmsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 9 Apr 2004 11:13:52 -0700 Received: from hdsmsx401.amr.corp.intel.com ([10.127.2.60]) by fmsmsx312.amr.corp.intel.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 9 Apr 2004 11:13:51 -0700 Received: from hdsmsx402.amr.corp.intel.com ([10.127.2.62]) by hdsmsx401.amr.corp.intel.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 9 Apr 2004 14:13:50 -0400 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Date: Fri, 9 Apr 2004 14:13:50 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ACPI SCI flags Thread-Index: AcQeXD1eIQYJCImoRjOvWqRuvk4LtQAAaXXQ From: "Brown, Len" To: "Nate Lawson" X-OriginalArrivalTime: 09 Apr 2004 18:13:50.0266 (UTC) FILETIME=[688719A0:01C41E5E] X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) cc: freebsd-acpi@freebsd.org Subject: RE: ACPI SCI flags 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: Fri, 09 Apr 2004 18:13:57 -0000 >For an explicit override that is >level/high, this appears not to work in some cases. Or it may be the >conforming override for irq 2 that is causing the problems. See this >message: Is it possible to verify that the APIC RTE 20 is programmed correctly? Also with storms like this, it is possible that the the victim is not the actual cause. Eg. Some other hardware device may be driving IRQ20 below and since ACPI doesn't know how to handle it you get a storm. Eg. IRQ20 is shared between ACPI an another PCI device. I would not expect this to be in any way related to the timer override from 0 to 2, since the timer is working properly. Cheers, -Len ------ interrupt total rate irq6: fdc0 9 0 irq8: rtc 20328 127 irq14: ata0 39 0 irq15: ata1 64 0 irq16: ahc1 407 2 irq17: pcm0 2 0 irq19: xl0 uhci0+ 2373 14 irq20: acpi0 6979146 43893 irq0: clk 15881 99 >