From owner-freebsd-acpi@FreeBSD.ORG Mon Mar 27 09:23:30 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 4FE0116A400; Mon, 27 Mar 2006 09:23:30 +0000 (UTC) (envelope-from fukui.FreeBSD@fanet.net) Received: from mail.fanet.net (home.fanet.net [61.194.26.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id B331243D45; Mon, 27 Mar 2006 09:23:29 +0000 (GMT) (envelope-from fukui.FreeBSD@fanet.net) Received: from mail.fanet.net (user=fukui mech=CRAM-MD5 bits=0) by mail.fanet.net (8.13.5+3.5Wbeta/8.13.5/smtpfeed 1.20) with ESMTP id k2R9NLkc006111; Mon, 27 Mar 2006 18:23:24 +0900 (JST) (envelope-from fukui.FreeBSD@fanet.net) Date: Mon, 27 Mar 2006 18:23:21 +0900 Message-ID: From: Masayuki FUKUI To: nate@root.org In-Reply-To: <44206C20.1060603@root.org> References: <200603210033.k2L0Xorb043252@freefall.freebsd.org> <200603211343.55664.jhb@freebsd.org> <442060E8.2000908@root.org> <44206C20.1060603@root.org> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.6 (=?ISO-2022-JP?B?GyRCNF0yLBsoQg==?=) LIMIT/1.14.9 (=?ISO-2022-JP?B?GyRCRjtMQDt7GyhC?=) APEL/10.6 Emacs/21.4 (i386-mingw-nt5.1.2600) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) Meadow/2.10 (ASAGAO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - =?ISO-2022-JP?B?IhskQjRdGyhC?= =?ISO-2022-JP?B?GyRCMiwbKEIi?=) Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,UNPARSEABLE_RELAY autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 Cc: freebsd-acpi@freebsd.org, bug-followup@freebsd.org Subject: Re: i386/93963: [panic] [patch] ACPI Panic with some ACPI 2.0 PC & cannot boot X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2006 09:23:30 -0000 >>>>> In <44206C20.1060603@root.org> >>>>> Nate Lawson wrote: > I contacted Robert Moore at Intel and he informed us this is fixed in > the 200506 distro of acpi-ca. We have an even newer version in > 7-current, so you can test that also to be sure it fixes your problem. Thank you, Nate-san. I tested it, and 7-current (7.0-CURRENT-SNAP013-i386) could be booted. > Unfortunately, we cannot MFC acpi-ca to 6.x until a known memory leak is > fixed. We'll close this bug once 7-current works for you and we are > able to MFC acpi-ca. I see. PS `acpidump -t' terminates abnormally. |# acpidump -t |/* | RSD PTR: OEM=PTLTD, ACPI_Rev=2.0x (2) | XSDT=0x00000000, length=0, cksum=0 | */ |acpidump: can't map address: Invalid argument From owner-freebsd-acpi@FreeBSD.ORG Mon Mar 27 09:30:24 2006 Return-Path: X-Original-To: freebsd-acpi@hub.freebsd.org Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6083116A426 for ; Mon, 27 Mar 2006 09:30:24 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 631C243D49 for ; Mon, 27 Mar 2006 09:30:23 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k2R9UNTR053972 for ; Mon, 27 Mar 2006 09:30:23 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k2R9UMBj053966; Mon, 27 Mar 2006 09:30:22 GMT (envelope-from gnats) Date: Mon, 27 Mar 2006 09:30:22 GMT Message-Id: <200603270930.k2R9UMBj053966@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: Masayuki FUKUI Cc: Subject: Re: i386/93963: [panic] [patch] ACPI Panic with some ACPI 2.0 PC & cannot boot X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Masayuki FUKUI List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2006 09:30:24 -0000 The following reply was made to PR i386/93963; it has been noted by GNATS. From: Masayuki FUKUI To: nate@root.org Cc: freebsd-acpi@freebsd.org, bug-followup@freebsd.org Subject: Re: i386/93963: [panic] [patch] ACPI Panic with some ACPI 2.0 PC & cannot boot Date: Mon, 27 Mar 2006 18:23:21 +0900 >>>>> In <44206C20.1060603@root.org> >>>>> Nate Lawson wrote: > I contacted Robert Moore at Intel and he informed us this is fixed in > the 200506 distro of acpi-ca. We have an even newer version in > 7-current, so you can test that also to be sure it fixes your problem. Thank you, Nate-san. I tested it, and 7-current (7.0-CURRENT-SNAP013-i386) could be booted. > Unfortunately, we cannot MFC acpi-ca to 6.x until a known memory leak is > fixed. We'll close this bug once 7-current works for you and we are > able to MFC acpi-ca. I see. PS `acpidump -t' terminates abnormally. |# acpidump -t |/* | RSD PTR: OEM=PTLTD, ACPI_Rev=2.0x (2) | XSDT=0x00000000, length=0, cksum=0 | */ |acpidump: can't map address: Invalid argument From owner-freebsd-acpi@FreeBSD.ORG Mon Mar 27 11:02:41 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 C5B4D16A420 for ; Mon, 27 Mar 2006 11:02:41 +0000 (UTC) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2975E43D49 for ; Mon, 27 Mar 2006 11:02:41 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k2RB2ft3062102 for ; Mon, 27 Mar 2006 11:02:41 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k2RB2dGD062096 for freebsd-acpi@freebsd.org; Mon, 27 Mar 2006 11:02:39 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 27 Mar 2006 11:02:39 GMT Message-Id: <200603271102.k2RB2dGD062096@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 Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2006 11:02:41 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2006/03/01] i386/93963 acpi [panic] [patch] ACPI Panic with some ACPI 1 problem 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/17] i386/55661 acpi ACPI suspend/resume problem on ARMADA M70 o [2003/08/20] kern/55822 acpi No ACPI power off with SMP kernel o [2003/08/27] kern/56024 acpi ACPI suspend drains battery while in S3 o [2004/03/09] i386/64002 acpi acpi problem o [2004/05/27] i386/67273 acpi [hang] system hangs with acpi and Xfree o [2004/10/12] i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Arma o [2005/03/21] i386/79080 acpi acpi thermal changes freezes HP nx6110 o [2005/03/21] i386/79081 acpi ACPI suspend/resume not working on HP nx6 o [2005/04/28] i386/80426 acpi [APIC] [panic] 5.4-RC3 still panic when b o [2005/10/17] i386/87568 acpi [ACPI] [REGRESSION] 6.0-STABLE needs ACPI 11 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/05/28] kern/67309 acpi zzz reboot computer (ACPI S3) o [2004/07/29] i386/69750 acpi Boot without ACPI failed on ASUS L5 o [2004/11/11] i386/73822 acpi [request] add thermal support to ACPI o [2004/11/11] kern/73823 acpi [feature request] acpi / power-on by time f [2004/11/17] kern/74030 acpi Unplugging AC causes battery % to stay lo 5 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Mar 27 16:09:49 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 E2E8716A401; Mon, 27 Mar 2006 16:09:49 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2875343D48; Mon, 27 Mar 2006 16:09:49 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k2RG9X4d061929; Mon, 27 Mar 2006 11:09:33 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Mon, 27 Mar 2006 11:01:19 -0500 User-Agent: KMail/1.9.1 References: <200603210033.k2L0Xorb043252@freefall.freebsd.org> <44206C20.1060603@root.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603271101.21466.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1357/Sat Mar 25 16:37:38 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.8 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00, SUBJECT_EXCESS_QP autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: bug-followup@freebsd.org, Masayuki FUKUI Subject: Re: i386/93963: [panic] [patch] ACPI Panic with some ACPI 2.0 PC & cannot boot X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2006 16:09:50 -0000 On Monday 27 March 2006 04:23, Masayuki FUKUI wrote: > >>>>> In <44206C20.1060603@root.org> > >>>>> Nate Lawson wrote: > > I contacted Robert Moore at Intel and he informed us this is fixed in > > the 200506 distro of acpi-ca. We have an even newer version in > > 7-current, so you can test that also to be sure it fixes your problem. > > Thank you, Nate-san. > I tested it, and 7-current (7.0-CURRENT-SNAP013-i386) could be booted. I've just committed the madt patches from this PR, thanks! -- 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 Mar 27 16:10:26 2006 Return-Path: X-Original-To: freebsd-acpi@hub.freebsd.org Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BBA116A427 for ; Mon, 27 Mar 2006 16:10:26 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C92BF43D49 for ; Mon, 27 Mar 2006 16:10:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k2RGAPin087778 for ; Mon, 27 Mar 2006 16:10:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k2RGAPWf087777; Mon, 27 Mar 2006 16:10:25 GMT (envelope-from gnats) Date: Mon, 27 Mar 2006 16:10:25 GMT Message-Id: <200603271610.k2RGAPWf087777@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: John Baldwin Cc: Subject: Re: i386/93963: [panic] [patch] ACPI Panic with some ACPI 2.0 PC & cannot boot X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Baldwin List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2006 16:10:26 -0000 The following reply was made to PR i386/93963; it has been noted by GNATS. From: John Baldwin To: freebsd-acpi@freebsd.org Cc: Masayuki FUKUI , nate@root.org, bug-followup@freebsd.org Subject: Re: i386/93963: [panic] [patch] ACPI Panic with some ACPI 2.0 PC =?iso-8859-1?q?=26=09cannot?= boot Date: Mon, 27 Mar 2006 11:01:19 -0500 On Monday 27 March 2006 04:23, Masayuki FUKUI wrote: > >>>>> In <44206C20.1060603@root.org> > >>>>> Nate Lawson wrote: > > I contacted Robert Moore at Intel and he informed us this is fixed in > > the 200506 distro of acpi-ca. We have an even newer version in > > 7-current, so you can test that also to be sure it fixes your problem. > > Thank you, Nate-san. > I tested it, and 7-current (7.0-CURRENT-SNAP013-i386) could be booted. I've just committed the madt patches from this PR, thanks! -- 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 Mar 27 23:17:06 2006 Return-Path: X-Original-To: freebsd-acpi@FreeBSD.org 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 A6BD016A400 for ; Mon, 27 Mar 2006 23:17:06 +0000 (UTC) (envelope-from bsam@bsam.ru) Received: from mail.kuban.ru (mail.kuban.ru [62.183.66.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4894243D5D for ; Mon, 27 Mar 2006 23:17:04 +0000 (GMT) (envelope-from bsam@bsam.ru) Received: from bsam.ru ([83.239.48.137]) by mail.kuban.ru (8.9.1/8.9.1) with ESMTP id k2RNGiqc006624 for ; Tue, 28 Mar 2006 03:16:54 +0400 (MSD) Received: from bsam by bsam.ru with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FO0wi-000Kqw-Ou for freebsd-acpi@FreeBSD.org; Tue, 28 Mar 2006 03:16:24 +0400 To: freebsd-acpi@FreeBSD.org References: <84395955@ho.ipt.ru> From: Boris Samorodov Date: Tue, 28 Mar 2006 03:16:24 +0400 In-Reply-To: <84395955@ho.ipt.ru> (Boris Samorodov's message of "Mon, 27 Mar 2006 22:30:04 +0400") Message-ID: <62957879@ho.ipt.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: "Boris B. Samorodov" Cc: Subject: Re: 6.1-PRERELEASE: freezing X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2006 23:17:06 -0000 forwarding to acpi@. On Mon, 27 Mar 2006 22:30:04 +0400 Boris Samorodov wrote: > I've had 6.0-STABLE as of jan-2006. Yesterday it was upgraded to > current 6.1-PRERELEASE (tag=RELENG_6). The hardware is HP/Compaq > nx6110 notebook. > After upgrading mashine is freezing under load. After booting the > OS without any actions it's OK for two hours. But after starting of > make buildkernel the mashine freezes. > I run top on ttyv1 (make buildkernel on ttyv2). After aprox. 3-5 > minutes it freezes. I have at kernel config: > options KDB > options KDB_TRACE > options DDB > options DDB_NUMSYM > So pressing then "c", let make buildkernel to > proceed a couple of seconds. And so on. Each command followed by > , "c", unfreezes my notebook for awhile. "Top" shows > only two commands at RUN state: make (cc) and devd. > I launched devd -Dd. There is the result (written many times) after > unfreezing the mashine with the magic keystrokes: > ----- > Processing event '!system=ACPI subsystem=Thermal type=\_TZ_.TZ1_ notify=0x80' > Pushing table > setting system=ACPI > setting subsystem=Thermal > setting type=\_TZ_.TZ1_ Shouldn't it be TZ0? Seems that TZ1 is not used at my machine. ----- hw.acpi.supported_sleep_state: S3 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S3 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 1 hw.acpi.verbose: 1 hw.acpi.reset_video: 1 hw.acpi.cpu.cx_supported: C1/1 C2/2 C3/38 hw.acpi.cpu.cx_lowest: C1 hw.acpi.cpu.cx_usage: 100.00% 0.00% 0.00% hw.acpi.battery.life: 100 hw.acpi.battery.time: -1 hw.acpi.battery.state: 0 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 hw.acpi.acline: 1 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 10 hw.acpi.thermal.tz0.temperature: 47.0C hw.acpi.thermal.tz0.active: 3 hw.acpi.thermal.tz0.passive_cooling: 1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 100.0C hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 102.0C hw.acpi.thermal.tz0._ACx: 80.0C 65.0C 55.0C 40.0C -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz1.temperature: 44.0C hw.acpi.thermal.tz1.active: -1 hw.acpi.thermal.tz1.passive_cooling: 0 hw.acpi.thermal.tz1.thermal_flags: 0 hw.acpi.thermal.tz1._PSV: -1 hw.acpi.thermal.tz1._HOT: -1 hw.acpi.thermal.tz1._CRT: 103.0C hw.acpi.thermal.tz1._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz2.temperature: 30.2C hw.acpi.thermal.tz2.active: -1 hw.acpi.thermal.tz2.passive_cooling: 0 hw.acpi.thermal.tz2.thermal_flags: 0 hw.acpi.thermal.tz2._PSV: 60.0C hw.acpi.thermal.tz2._HOT: -1 hw.acpi.thermal.tz2._CRT: 102.0C hw.acpi.thermal.tz2._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 ----- > setting notify=0x80 > Processing notify event > Testing system=ACPI against ^ACPI > Testing subsystem=Thermal against ^ACAD > Testing system=ACPI against ^ACPI > Testing subsystem=Thermal against ^Thermal > Testing notify=0x80 against ^0xcc > Testing system=ACPI against ^IFNET > Testing system=ACPI against ^IFNET > Popping table > ----- > Booting with ACPI disabled helps as well as kernel.old with it's > modules. > /etc/make.conf: > ----- > KERNCONF?= NX6110 > X_WINDOW_SYSTEM=xorg > OVERRIDE_LINUX_BASE_PORT=fc3 > PERL_VER=5.8.7 > PERL_VERSION=5.8.7 > ----- > What type of debugging should I do to find up what's up? > Thanks. WBR -- Boris B. Samorodov, Research Engineer InPharmTech Co, http://www.ipt.ru Telephone & Internet Service Provider From owner-freebsd-acpi@FreeBSD.ORG Fri Mar 31 01:45:45 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 21A8816A401 for ; Fri, 31 Mar 2006 01:45:45 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F85743D46 for ; Fri, 31 Mar 2006 01:45:44 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (am-productions.biz [69.61.164.22]) (authenticated bits=0) by mail.united-ware.com (8.13.4/8.13.4) with ESMTP id k2V20GqR032896 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 30 Mar 2006 21:00:22 -0500 (EST) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-acpi@freebsd.org Date: Thu, 30 Mar 2006 20:48:36 -0500 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2363661.iik4VSXQtO"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200603302048.43187.mistry.7@osu.edu> X-Spam-Status: No, score=-5.7 required=5.0 tests=ALL_TRUSTED,BAYES_40, MYFREEBSD2 autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mail.united-ware.com X-Virus-Scanned: ClamAV 0.88/1363/Wed Mar 29 15:38:37 2006 on mail.united-ware.com X-Virus-Status: Clean Subject: cpu0: too many short sleeps, backing off to CX X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2006 01:45:45 -0000 --nextPart2363661.iik4VSXQtO Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline This has been bugging me for a while, but now I need it so... When ever I starting to do something CPU intensive on my laptop I get=20 the following on the console and the cs_lowest state changes. cpu0: too many short sleeps, backing off to C2 cpu0: too many short sleeps, backing off to C1 I understand that is for good reasons with normal laptop CPUs. For my=20 Crusoe based system this defeats the whole point of Longrun, which is=20 to do exactly that. Is there a way to prevent this behavior? =2D-=20 Anish Mistry --nextPart2363661.iik4VSXQtO Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBELIp7xqA5ziudZT0RAqliAJwJgvsx9H651NuPIm6mJcIXou9AqACeL0It r2iP6Hy52ebc0Vsp8HuB5G4= =D9J1 -----END PGP SIGNATURE----- --nextPart2363661.iik4VSXQtO-- From owner-freebsd-acpi@FreeBSD.ORG Fri Mar 31 04:46:54 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 C1AB116A400 for ; Fri, 31 Mar 2006 04:46:54 +0000 (UTC) (envelope-from uranus@it.muds.net) Received: from it.muds.net (220-134-153-8.HINET-IP.hinet.net [220.134.153.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D9E243D48 for ; Fri, 31 Mar 2006 04:46:54 +0000 (GMT) (envelope-from uranus@it.muds.net) Received: from localhost (localhost [127.0.0.1]) by it.muds.net (Postfix) with ESMTP id A0C1D2E069 for ; Fri, 31 Mar 2006 12:46:41 +0800 (CST) Received: from it.muds.net ([127.0.0.1]) by localhost (it.muds.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19780-06 for ; Fri, 31 Mar 2006 12:46:41 +0800 (CST) Received: from uranus (uranus [192.168.3.1]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by it.muds.net (Postfix) with ESMTP id 2163B2E063 for ; Fri, 31 Mar 2006 12:46:41 +0800 (CST) Message-ID: <000b01c6547e$16144f00$0201a8c0@uranus> From: "Ling-hua Tseng" To: Date: Fri, 31 Mar 2006 12:46:32 +0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="big5"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Virus-Scanned: amavisd-new with ClamAV at it.muds.net Subject: ASUS V6J with 7.0-CURRENT X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2006 04:46:54 -0000 My notebook is ASUS V6J. 1. I have tried to use acpi_asus.ko but it didn't support ASUS V6J yet. What things I have to provide if someone would like to help me to implement this? Here are my boot messages which related to ACPI: acpi0: on motherboard acpi: bad read from port 0x073 (8) acpi: bad read from port 0x073 (8) acpi: bad read from port 0x073 (8) acpi: bad read from port 0x073 (8) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi: bad write to port 0x080 (8), val 0xaa acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_ec0: port 0x62,0x66 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 2. I enabled the powerd with the flags "-a maximum -b adaptive". The console will be frozen if I removed the AC power. The alt-F1~F7 cannot work on the console after I removing the AC power. When I removed the AC power, I can get the messages: acpi: bad read from port 0x073 (8) cpu0:cpu Cx states c1: Cx sthangedates changed (The second line of the messages are interlaced by two messages.) I can still use ssh to login my system and can use "watch ttyv0" to see the console screen without freezing. This problem is only occured in 7.0-CURRENT (6.1-PRERELEASE can work correctly). 3. I cannot suspend my system by using zzz or acpiconf -s 3. The only message is "kernel: acpi0: device_suspend failed". I have confirmed that my notebook support it by using sysctl: hw.acpi.supported_sleep_state: S1 S3 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 From owner-freebsd-acpi@FreeBSD.ORG Fri Mar 31 22:38:21 2006 Return-Path: X-Original-To: freebsd-acpi@FreeBSD.org 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 DBD5C16A400; Fri, 31 Mar 2006 22:38:21 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7681943D75; Fri, 31 Mar 2006 22:38:19 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id k2VMcFD7045508; Fri, 31 Mar 2006 17:38:15 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-acpi@FreeBSD.org Date: Fri, 31 Mar 2006 17:38:00 -0500 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200603311738.02120.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1364/Thu Mar 30 15:05:50 2006 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: John Baldwin Subject: IBM x336 does not boot with APIC. X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2006 22:38:21 -0000 I tried to install FreeBSD 6.1-BETA4 on IBM x336 and it was not booting. I googled a bit and I found this is known problem for this platform: http://docs.freebsd.org/cgi/mid.cgi?200510061556.55464.jhb To make the system up and running, I had to disable APIC and force keyboard to attach. Of course, I didn't like that. ;-) The first thing I wanted to fix was: acpi0: on motherboard acpi0: [MPSAFE] pci_open(1): mode 1 addr port (0x0cf8) is 0x80000144 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=35908086) acpi_bus_number: root bus has no _BBN, assuming 0 acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR ... I added 'PNP0A08' to pcib_ids in src/sys/dev/acpica/acpi_pcib_acpi.c because this system had this: Scope (\_SB) { Device (PCI0) { Name (_HID, EisaId ("PNP0A08")) Name (_CID, 0x030AD041) ... This ID was added in ACPI 3.0 as 'PCI Express Root Bridge', instead of 'PNP0A03', which is PCI/PCI-X root bridge. However, I got something like this instead: acpi0: could not allocate interrupt ACPI-0210: *** Error: Unable to install System Control Interrupt Handler, AE_ALREADY_EXISTS acpi0: Could not enable ACPI: AE_ALREADY_EXISTS No driver was able to allocate IRQ after this and I am quite puzzled right now. Is it correct thing to do? Why does it break? Why can't I install SCI handler? Jung-uk Kim From owner-freebsd-acpi@FreeBSD.ORG Sat Apr 1 05:50:40 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 4DE7F16A423 for ; Sat, 1 Apr 2006 05:50:40 +0000 (UTC) (envelope-from slipcon@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id D288243D46 for ; Sat, 1 Apr 2006 05:50:39 +0000 (GMT) (envelope-from slipcon@gmail.com) Received: by wproxy.gmail.com with SMTP id 58so328809wri for ; Fri, 31 Mar 2006 21:50:39 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=meC2Hep8tBnbgqsNy6680m+IGwNwa9YdM1x91TVuvBd0PLE7eqEqh9IttV0ff0R5c0xch9sK8FiNJ0PytSC3Wx39KD7MKHGetXmcNrYEAfNWTBl/CNoUkmi8yv/CBIC0J2INcy0maC7k+3Nt4T6ryVMIgVjNae5JewM7hDES13M= Received: by 10.54.113.17 with SMTP id l17mr544323wrc; Fri, 31 Mar 2006 21:43:50 -0800 (PST) Received: by 10.54.83.19 with HTTP; Fri, 31 Mar 2006 21:43:50 -0800 (PST) Message-ID: <580cd3b30603312143o4edc0dd7q667e7e3c578a114c@mail.gmail.com> Date: Sat, 1 Apr 2006 00:43:50 -0500 From: "Scott Lipcon" To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ACPI blacklist - important? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Apr 2006 05:50:40 -0000 Hi, I've got a question, and I have to admit I really don't know much about ACPI, but I'd appreciate any advice. My email server was an Athlon XP running FreeBSD 5.4-STABLE, and the motherboard died. I put the disks in an old machine, which is an ASUS P2D-= B board, dual 350Mhz PII. It panic'ed on boot, saying the ACPI implementatio= n was on the blacklist. I was able to figure out how to disable the blacklis= t check ("set hint.acpi.0.disabled=3D0") and it booted up and seems to be running OK. My question is - what is the side-effect of having this blacklisted ACPI implementation running? My kernel is a single CPU kernel (since my Athlon was only single CPU) so if the lack of SMP has any effect I'd like to know. Specifically, is this setup likely to be stable? I'm certainly planning o= n replacing the Athlon motherboard with a new board/CPU, but I'm going out of town this week and probably wont have time to get replacement parts before = I leave, and I'd really like to have some confidence that my email server wil= l stay up while I'm gone. Any hints? Thanks, Scott From owner-freebsd-acpi@FreeBSD.ORG Sat Apr 1 19:27:33 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 7A22F16A401 for ; Sat, 1 Apr 2006 19:27:33 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm01.prodigy.net (ylpvm01-ext.prodigy.net [207.115.57.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01B5C43D49 for ; Sat, 1 Apr 2006 19:27:30 +0000 (GMT) (envelope-from nate@root.org) Received: from pimout5-ext.prodigy.net (pimout5-int.prodigy.net [207.115.4.21]) by ylpvm01.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id k31JRRag009856 for ; Sat, 1 Apr 2006 14:27:27 -0500 X-ORBL: [71.139.114.10] Received: from [10.0.5.51] (ppp-71-139-114-10.dsl.snfc21.pacbell.net [71.139.114.10]) by pimout5-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id k31JRSPo073240; Sat, 1 Apr 2006 14:27:28 -0500 Message-ID: <442ED3FB.6030904@root.org> Date: Sat, 01 Apr 2006 11:26:51 -0800 From: Nate Lawson User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Scott Lipcon References: <580cd3b30603312143o4edc0dd7q667e7e3c578a114c@mail.gmail.com> In-Reply-To: <580cd3b30603312143o4edc0dd7q667e7e3c578a114c@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: ACPI blacklist - important? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Apr 2006 19:27:33 -0000 Scott Lipcon wrote: > Hi, > > I've got a question, and I have to admit I really don't know much about > ACPI, but I'd appreciate any advice. > > My email server was an Athlon XP running FreeBSD 5.4-STABLE, and the > motherboard died. I put the disks in an old machine, which is an ASUS P2D-B > board, dual 350Mhz PII. It panic'ed on boot, saying the ACPI implementation > was on the blacklist. I was able to figure out how to disable the blacklist > check ("set hint.acpi.0.disabled=0") and it booted up and seems to be > running OK. If you upgrade the BIOS, the message will likely go away. The blacklist check should NOT panic, it should just boot with acpi disabled. So please give the panic message and any associated info (i.e. trap frame). > My question is - what is the side-effect of having this blacklisted ACPI > implementation running? My kernel is a single CPU kernel (since my Athlon > was only single CPU) so if the lack of SMP has any effect I'd like to know. > Specifically, is this setup likely to be stable? I'm certainly planning on > replacing the Athlon motherboard with a new board/CPU, but I'm going out of > town this week and probably wont have time to get replacement parts before I > leave, and I'd really like to have some confidence that my email server will > stay up while I'm gone. Different machines are blacklisted for various reasons. I believe the ASUS P2* series had a bad interrupt routing table, possibly for the SCI. That would mean that it could be unstable with acpi *enabled*. So disabling acpi should be perfectly safe, stable, etc. That's what the blacklist entry is supposed to do. We need to fix the panic problem, so please provide that info when you get a chance. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Sat Apr 1 19:54:33 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 25C7616A422 for ; Sat, 1 Apr 2006 19:54:33 +0000 (UTC) (envelope-from slipcon@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id D737243D6B for ; Sat, 1 Apr 2006 19:54:26 +0000 (GMT) (envelope-from slipcon@gmail.com) Received: by wproxy.gmail.com with SMTP id 58so392955wri for ; Sat, 01 Apr 2006 11:54:26 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=XpagfyJ1iWgZ1a0PWi4ubmVgf5QVq3IfC2aWvKy6WxmYshp9kKRlsbr7rgOJXWNB1zHcRDfkWsVypwkOVJdl1UIVSEiGxWd2+M4wbT0xoBJtHzb8fXh2et83QMlOaFR/G4QBzOFcXYEZAX3ze6T4zxjdcaxSoIJZ3VtbA27DKbM= Received: by 10.54.83.16 with SMTP id g16mr228212wrb; Sat, 01 Apr 2006 11:54:26 -0800 (PST) Received: by 10.54.83.19 with HTTP; Sat, 1 Apr 2006 11:54:26 -0800 (PST) Message-ID: <580cd3b30604011154h3cccb0a4ub5a12a73f2e1756a@mail.gmail.com> Date: Sat, 1 Apr 2006 14:54:26 -0500 From: "Scott Lipcon" To: "Nate Lawson" In-Reply-To: <442ED3FB.6030904@root.org> MIME-Version: 1.0 References: <580cd3b30603312143o4edc0dd7q667e7e3c578a114c@mail.gmail.com> <442ED3FB.6030904@root.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-acpi@freebsd.org Subject: Re: ACPI blacklist - important? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Apr 2006 19:54:33 -0000 On 4/1/06, Nate Lawson wrote: > > Scott Lipcon wrote: > > Hi, > > > > I've got a question, and I have to admit I really don't know much about > > ACPI, but I'd appreciate any advice. > > > > My email server was an Athlon XP running FreeBSD 5.4-STABLE, and the > > motherboard died. I put the disks in an old machine, which is an ASUS > P2D-B > > board, dual 350Mhz PII. It panic'ed on boot, saying the ACPI > implementation > > was on the blacklist. I was able to figure out how to disable the > blacklist > > check ("set hint.acpi.0.disabled=3D0") and it booted up and seems to be > > running OK. > > If you upgrade the BIOS, the message will likely go away. I'm running the 2nd latest BIOS - the board is quite old, and the latest BIOS is 4 years old. The change log doesn't say anything useful. The blacklist check should NOT panic, it should just boot with acpi > disabled. So please give the panic message and any associated info > (i.e. trap frame). I wrote it down so this might not be exactly right, but its close: ACPI APIC table (ASUS P2B D) ACPI Disabled by blacklist. Contact BIOS vendor MADT: ACPI startup failed with AE_ERROR Try disabling either ACPI or apic support. panic. Using MADT but ACPI doesn't work. > My question is - what is the side-effect of having this blacklisted ACPI > > implementation running? My kernel is a single CPU kernel (since my > Athlon > > was only single CPU) so if the lack of SMP has any effect I'd like to > know. > > Specifically, is this setup likely to be stable? I'm certainly > planning on > > replacing the Athlon motherboard with a new board/CPU, but I'm going ou= t > of > > town this week and probably wont have time to get replacement parts > before I > > leave, and I'd really like to have some confidence that my email server > will > > stay up while I'm gone. > > Different machines are blacklisted for various reasons. I believe the > ASUS P2* series had a bad interrupt routing table, possibly for the SCI. > That would mean that it could be unstable with acpi *enabled*. So > disabling acpi should be perfectly safe, stable, etc. That's what the > blacklist entry is supposed to do. We need to fix the panic problem, so > please provide that info when you get a chance. Perhaps this is related then - when I disabled the blacklist check, and it didn't panic, during the boot I get: Timecounter "TSC" frequency 350797176 Hz quality 800 Timecounters tick every 10.000 msec Interrupt storm detected on "irq20: acpi0"; throttling interrupt source Since then, no related messages, and the system seems to be running OK (15 hr uptime). This is a dual CPU board, but since I'm booting it from the disk from my athlon, its a single processor kernel - would that have any affect on its stability? I can provide my kernel config if anyone can suggest changes = - like I said, I most concerned that it stay up for the next two weeks. thanks, Scott