From owner-freebsd-acpi@FreeBSD.ORG Sun Mar 19 10:54:04 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 2F75716A401 for ; Sun, 19 Mar 2006 10:54:04 +0000 (UTC) (envelope-from acpi@dino.sk) Received: from bsd.dino.sk (bsd.dino.sk [213.215.72.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8820643D49 for ; Sun, 19 Mar 2006 10:54:02 +0000 (GMT) (envelope-from acpi@dino.sk) Received: from lex ([213.215.74.194]) (AUTH: PLAIN milan, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by bsd.dino.sk with esmtp; Sun, 19 Mar 2006 11:54:34 +0100 id 00000040.441D386A.0001303F From: Milan Obuch To: freebsd-acpi@freebsd.org Date: Sun, 19 Mar 2006 11:53:37 +0100 User-Agent: KMail/1.8.3 References: <200603061009.03933.acpi@dino.sk> In-Reply-To: <200603061009.03933.acpi@dino.sk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603191153.40326.acpi@dino.sk> Subject: Re: Trouble with ACPI on my TabletPC TC1000 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: Sun, 19 Mar 2006 10:54:04 -0000 On Monday 06 March 2006 10:09, Milan Obuch wrote: > Hi, > I would like to get some help to solve my problem with ACPI on TC1000. With > freshly cvsupped -current it does not boot with ACPI enabled. I collected > some info as mentioned in FreeBSD handbook for ACPI debugging, available at > http://www.dino.sk. > There are basically two sets of files - 5.5-PRERELEASE with working ACPI > and 7.0-CURRENT with broken ACPI. No info is included from 6.x version, > however, I did test it once or twice and it fails just like -current. > As there are some parts enhanced in -current and TC1000 has better hardware > support there I would like to get this corrected, but I am not yet able to > do it alone. > Regards, > Milan I did some work in the mean time, 6.1-BETA3 installed and works with ACPI. System updated to 6.1-PRERELEASE (I think) and works well. With one brute hack even 7.0-CURRENT works with ACPI - original error, panic: acpi_pci_update_device: deleting alive child acpi_sysresource1 can be removed by commenting first part of acpi_pci_update_device function in dev/acpica/acpi_pci.c file - code conditionally evaluated when child != NULL. After commenting it out system boots with ACPI and works. I would like to get some hints on what to look for, so I can at least understand why this code fails, what should it be doing. I have no knowledge on ACPI code, so any hint is appreciated. Regards, Milan From owner-freebsd-acpi@FreeBSD.ORG Mon Mar 20 11:02:34 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 CC9C416A400 for ; Mon, 20 Mar 2006 11:02:34 +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 8F54943D46 for ; Mon, 20 Mar 2006 11:02:34 +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 k2KB2Yuh082384 for ; Mon, 20 Mar 2006 11:02:34 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k2KB2XjR082377 for freebsd-acpi@freebsd.org; Mon, 20 Mar 2006 11:02:33 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 20 Mar 2006 11:02:33 GMT Message-Id: <200603201102.k2KB2XjR082377@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, 20 Mar 2006 11:02:34 -0000 Current FreeBSD problem reports Critical problems 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 20 17:18:46 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 1CA2416A400 for ; Mon, 20 Mar 2006 17:18:46 +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 66D9D43D8D for ; Mon, 20 Mar 2006 17:18:27 +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 k2KHIJvV097319; Mon, 20 Mar 2006 12:18:21 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Mon, 20 Mar 2006 11:33:17 -0500 User-Agent: KMail/1.9.1 References: <200603061009.03933.acpi@dino.sk> <200603191153.40326.acpi@dino.sk> In-Reply-To: <200603191153.40326.acpi@dino.sk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603201133.19361.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1345/Mon Mar 20 07:03:16 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.6 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Subject: Re: Trouble with ACPI on my TabletPC TC1000 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, 20 Mar 2006 17:18:46 -0000 On Sunday 19 March 2006 05:53, Milan Obuch wrote: > On Monday 06 March 2006 10:09, Milan Obuch wrote: > > Hi, > > I would like to get some help to solve my problem with ACPI on TC1000. With > > freshly cvsupped -current it does not boot with ACPI enabled. I collected > > some info as mentioned in FreeBSD handbook for ACPI debugging, available at > > http://www.dino.sk. > > There are basically two sets of files - 5.5-PRERELEASE with working ACPI > > and 7.0-CURRENT with broken ACPI. No info is included from 6.x version, > > however, I did test it once or twice and it fails just like -current. > > As there are some parts enhanced in -current and TC1000 has better hardware > > support there I would like to get this corrected, but I am not yet able to > > do it alone. > > Regards, > > Milan > > I did some work in the mean time, 6.1-BETA3 installed and works with ACPI. > System updated to 6.1-PRERELEASE (I think) and works well. > With one brute hack even 7.0-CURRENT works with ACPI - original error, panic: > acpi_pci_update_device: deleting alive child acpi_sysresource1 can be removed > by commenting first part of acpi_pci_update_device function in > dev/acpica/acpi_pci.c file - code conditionally evaluated when child != NULL. > After commenting it out system boots with ACPI and works. > I would like to get some hints on what to look for, so I can at least > understand why this code fails, what should it be doing. I have no knowledge > on ACPI code, so any hint is appreciated. I'd like to see a copy of your asl. This is the first I've heard of an ACPI system resource device being a PCI device. -- 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 20 17:51:35 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 5547C16A400; Mon, 20 Mar 2006 17:51:35 +0000 (UTC) (envelope-from acpi@dino.sk) Received: from bsd.dino.sk (bsd.dino.sk [213.215.72.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03AED43D69; Mon, 20 Mar 2006 17:51:33 +0000 (GMT) (envelope-from acpi@dino.sk) Received: from lex ([213.215.74.194]) (AUTH: PLAIN milan, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by bsd.dino.sk with esmtp; Mon, 20 Mar 2006 18:52:13 +0100 id 00000042.441EEBCD.0000416F From: Milan Obuch To: freebsd-acpi@freebsd.org Date: Mon, 20 Mar 2006 18:50:44 +0100 User-Agent: KMail/1.8.3 References: <200603061009.03933.acpi@dino.sk> <200603191153.40326.acpi@dino.sk> <200603201133.19361.jhb@freebsd.org> In-Reply-To: <200603201133.19361.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603201850.51441.acpi@dino.sk> Cc: Subject: Re: Trouble with ACPI on my TabletPC TC1000 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, 20 Mar 2006 17:51:35 -0000 On Monday 20 March 2006 17:33, John Baldwin wrote: > On Sunday 19 March 2006 05:53, Milan Obuch wrote: > > On Monday 06 March 2006 10:09, Milan Obuch wrote: > > > Hi, > > > I would like to get some help to solve my problem with ACPI on TC1000. > > > With freshly cvsupped -current it does not boot with ACPI enabled. I > > > collected some info as mentioned in FreeBSD handbook for ACPI > > > debugging, available at http://www.dino.sk. > > > There are basically two sets of files - 5.5-PRERELEASE with working > > > ACPI and 7.0-CURRENT with broken ACPI. No info is included from 6.x > > > version, however, I did test it once or twice and it fails just like > > > -current. As there are some parts enhanced in -current and TC1000 has > > > better hardware support there I would like to get this corrected, but I > > > am not yet able to do it alone. > > > Regards, > > > Milan > > > > I did some work in the mean time, 6.1-BETA3 installed and works with > > ACPI. System updated to 6.1-PRERELEASE (I think) and works well. > > With one brute hack even 7.0-CURRENT works with ACPI - original error, > > panic: acpi_pci_update_device: deleting alive child acpi_sysresource1 can > > be removed by commenting first part of acpi_pci_update_device function in > > dev/acpica/acpi_pci.c file - code conditionally evaluated when child != > > NULL. After commenting it out system boots with ACPI and works. > > I would like to get some hints on what to look for, so I can at least > > understand why this code fails, what should it be doing. I have no > > knowledge on ACPI code, so any hint is appreciated. > > I'd like to see a copy of your asl. This is the first I've heard of an > ACPI system resource device being a PCI device. Do you mean output of acpidump -d -t? Posted on my page, download full text version... If anything else is useful/interesting, just drop a line and I will try to find that info, test a patch... anything. Regards, Milan From owner-freebsd-acpi@FreeBSD.ORG Mon Mar 20 18:50:04 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 5D2E316A423 for ; Mon, 20 Mar 2006 18:50:04 +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 8A1DC43D5C for ; Mon, 20 Mar 2006 18:50:03 +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 k2KIntCT000958; Mon, 20 Mar 2006 13:49:58 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Milan Obuch Date: Mon, 20 Mar 2006 13:49:37 -0500 User-Agent: KMail/1.9.1 References: <200603061009.03933.acpi@dino.sk> <200603201133.19361.jhb@freebsd.org> <200603201850.51441.acpi@dino.sk> In-Reply-To: <200603201850.51441.acpi@dino.sk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603201349.39308.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1345/Mon Mar 20 07:03:16 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.6 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-acpi@freebsd.org Subject: Re: Trouble with ACPI on my TabletPC TC1000 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, 20 Mar 2006 18:50:04 -0000 On Monday 20 March 2006 12:50, Milan Obuch wrote: > On Monday 20 March 2006 17:33, John Baldwin wrote: > > On Sunday 19 March 2006 05:53, Milan Obuch wrote: > > > On Monday 06 March 2006 10:09, Milan Obuch wrote: > > > > Hi, > > > > I would like to get some help to solve my problem with ACPI on TC1000. > > > > With freshly cvsupped -current it does not boot with ACPI enabled. I > > > > collected some info as mentioned in FreeBSD handbook for ACPI > > > > debugging, available at http://www.dino.sk. > > > > There are basically two sets of files - 5.5-PRERELEASE with working > > > > ACPI and 7.0-CURRENT with broken ACPI. No info is included from 6.x > > > > version, however, I did test it once or twice and it fails just like > > > > -current. As there are some parts enhanced in -current and TC1000 has > > > > better hardware support there I would like to get this corrected, but I > > > > am not yet able to do it alone. > > > > Regards, > > > > Milan > > > > > > I did some work in the mean time, 6.1-BETA3 installed and works with > > > ACPI. System updated to 6.1-PRERELEASE (I think) and works well. > > > With one brute hack even 7.0-CURRENT works with ACPI - original error, > > > panic: acpi_pci_update_device: deleting alive child acpi_sysresource1 can > > > be removed by commenting first part of acpi_pci_update_device function in > > > dev/acpica/acpi_pci.c file - code conditionally evaluated when child != > > > NULL. After commenting it out system boots with ACPI and works. > > > I would like to get some hints on what to look for, so I can at least > > > understand why this code fails, what should it be doing. I have no > > > knowledge on ACPI code, so any hint is appreciated. > > > > I'd like to see a copy of your asl. This is the first I've heard of an > > ACPI system resource device being a PCI device. > > Do you mean output of acpidump -d -t? Posted on my page, download full text > version... If anything else is useful/interesting, just drop a line and I > will try to find that info, test a patch... anything. This is a really retarded motherboard. It claims to have two PCI-ISA bridges and the second PCI-ISA bridge also claims to be a system resource. I can give you a patch for your system though. Try http://www.FreeBSD.org/~jhb/patches/tc1000.patch -- 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 Mar 21 00:33:50 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 781E616A41F; Tue, 21 Mar 2006 00:33:50 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 366AD43D46; Tue, 21 Mar 2006 00:33:50 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k2L0Xo2u043256; Tue, 21 Mar 2006 00:33:50 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k2L0Xorb043252; Tue, 21 Mar 2006 00:33:50 GMT (envelope-from linimon) Date: Tue, 21 Mar 2006 00:33:50 GMT From: Mark Linimon Message-Id: <200603210033.k2L0Xorb043252@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-acpi@FreeBSD.org 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 List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Mar 2006 00:33:50 -0000 Synopsis: [panic] [patch] ACPI Panic with some ACPI 2.0 PC & cannot boot Responsible-Changed-From-To: freebsd-i386->freebsd-acpi Responsible-Changed-By: linimon Responsible-Changed-When: Tue Mar 21 00:31:09 UTC 2006 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=93963 From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 21 05:25:35 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 67D7316A41F for ; Tue, 21 Mar 2006 05:25:35 +0000 (UTC) (envelope-from Mark_Andrews@isc.org) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0711043D45 for ; Tue, 21 Mar 2006 05:25:35 +0000 (GMT) (envelope-from Mark_Andrews@isc.org) Received: from drugs.dv.isc.org (localhost.isc.org [IPv6:::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by farside.isc.org (Postfix) with ESMTP id F16A4E606F for ; Tue, 21 Mar 2006 05:25:32 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.13.4/8.13.4) with ESMTP id k2L5PSis001981 for ; Tue, 21 Mar 2006 16:25:28 +1100 (EST) (envelope-from marka@drugs.dv.isc.org) Resent-Message-Id: <200603210525.k2L5PSis001981@drugs.dv.isc.org> Message-Id: <200603210525.k2L5PSis001981@drugs.dv.isc.org> To: freebsd-acpi@freebsd.org From: Mark Andrews Date: Tue, 21 Mar 2006 11:58:48 +1100 Sender: Mark_Andrews@isc.org Resent-To: freebsd-acpi@freebsd.org Resent-Date: Tue, 21 Mar 2006 16:25:28 +1100 Resent-From: Mark Andrews Subject: DELL D610 lid and backlight 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: Tue, 21 Mar 2006 05:25:35 -0000 I have a problem if I enable acpi on my dell d610. The backlight goes off and doesn't come back on if the lid is closed. This is independent of whether debug.acpi.disabled="lid" is set or not. Below are two boot sequences. The first is without debug.acpi.disabled="lid", the second with it. In both cases I was able to shutdown by blindly issuing "shutdown -r now". I have also tried to force a suspend by pressing the the standby key and letting it return. The machine appears to suspend by examining the power led but the backlight doesn't come on when it comes out of suspend and it is a bit hard to tell what has happened. Mark Mar 21 11:14:07 drugs syslogd: kernel boot file is /boot/kernel/kernel Mar 21 11:14:07 drugs kernel: Copyright (c) 1992-2006 The FreeBSD Project. Mar 21 11:14:07 drugs kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Mar 21 11:14:07 drugs kernel: The Regents of the University of California. All rights reserved. Mar 21 11:14:07 drugs kernel: FreeBSD 6.1-PRERELEASE #1: Sat Mar 18 01:49:32 EST 2006 Mar 21 11:14:07 drugs kernel: marka@drugs.dv.isc.org:/usr/obj/usr/src/sys/DRUGS Mar 21 11:14:07 drugs kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Mar 21 11:14:07 drugs kernel: CPU: Intel(R) Pentium(R) M processor 1.73GHz (1729.12-MHz 686-class CPU) Mar 21 11:14:07 drugs kernel: Origin = "GenuineIntel" Id = 0x6d8 Stepping = 8 Mar 21 11:14:07 drugs kernel: Features=0xafe9fbff Mar 21 11:14:07 drugs kernel: Features2=0x180 Mar 21 11:14:07 drugs kernel: AMD Features=0x100000 Mar 21 11:14:07 drugs kernel: real memory = 1065160704 (1015 MB) Mar 21 11:14:07 drugs kernel: avail memory = 1033383936 (985 MB) Mar 21 11:14:07 drugs kernel: ACPI APIC Table: Mar 21 11:14:07 drugs kernel: ioapic0: Changing APIC ID to 1 Mar 21 11:14:07 drugs kernel: ioapic0 irqs 0-23 on motherboard Mar 21 11:14:07 drugs kernel: wlan: mac acl policy registered Mar 21 11:14:07 drugs kernel: npx0: [FAST] Mar 21 11:14:07 drugs kernel: npx0: on motherboard Mar 21 11:14:07 drugs kernel: npx0: INT 16 interface Mar 21 11:14:07 drugs kernel: acpi0: on motherboard Mar 21 11:14:07 drugs kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 Mar 21 11:14:07 drugs kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 Mar 21 11:14:07 drugs kernel: cpu0: on acpi0 Mar 21 11:14:07 drugs kernel: acpi_throttle0: on cpu0 Mar 21 11:14:07 drugs kernel: acpi_acad0: on acpi0 Mar 21 11:14:07 drugs kernel: battery0: on acpi0 Mar 21 11:14:07 drugs kernel: battery1: on acpi0 Mar 21 11:14:07 drugs kernel: acpi_lid0: on acpi0 Mar 21 11:14:07 drugs kernel: acpi_button0: on acpi0 Mar 21 11:14:07 drugs kernel: acpi_button1: on acpi0 Mar 21 11:14:07 drugs kernel: pcib0: port 0xcf8-0xcff on acpi0 Mar 21 11:14:07 drugs kernel: pci0: on pcib0 Mar 21 11:14:07 drugs kernel: agp0: port 0xec38-0xec3f mem 0xdff00000-0xdff7ffff,0xc0000000-0xcfffffff,0xdfec0000-0xdfefffff irq 16 at device 2.0 on pci0 Mar 21 11:14:07 drugs kernel: agp0: detected 7932k stolen memory Mar 21 11:14:07 drugs kernel: agp0: aperture size is 256M Mar 21 11:14:07 drugs kernel: pci0: at device 2.1 (no driver attached) Mar 21 11:14:07 drugs kernel: pcib1: at device 28.0 on pci0 Mar 21 11:14:07 drugs kernel: pci2: on pcib1 Mar 21 11:14:07 drugs kernel: bge0: mem 0xdfdf0000-0xdfdfffff irq 16 at device 0.0 on pci2 Mar 21 11:14:07 drugs kernel: miibus0: on bge0 Mar 21 11:14:07 drugs kernel: brgphy0: on miibus0 Mar 21 11:14:07 drugs kernel: brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto Mar 21 11:14:07 drugs kernel: bge0: Ethernet address: 00:14:22:d9:fb:dc Mar 21 11:14:07 drugs kernel: uhci0: port 0xbf80-0xbf9f irq 16 at device 29.0 on pci0 Mar 21 11:14:07 drugs kernel: uhci0: [GIANT-LOCKED] Mar 21 11:14:07 drugs kernel: usb0: on uhci0 Mar 21 11:14:07 drugs kernel: usb0: USB revision 1.0 Mar 21 11:14:07 drugs kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Mar 21 11:14:07 drugs kernel: uhub0: 2 ports with 2 removable, self powered Mar 21 11:14:07 drugs kernel: uhci1: port 0xbf60-0xbf7f irq 17 at device 29.1 on pci0 Mar 21 11:14:07 drugs kernel: uhci1: [GIANT-LOCKED] Mar 21 11:14:07 drugs kernel: usb1: on uhci1 Mar 21 11:14:07 drugs kernel: usb1: USB revision 1.0 Mar 21 11:14:07 drugs kernel: uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Mar 21 11:14:07 drugs kernel: uhub1: 2 ports with 2 removable, self powered Mar 21 11:14:07 drugs kernel: uhci2: port 0xbf40-0xbf5f irq 18 at device 29.2 on pci0 Mar 21 11:14:07 drugs kernel: uhci2: [GIANT-LOCKED] Mar 21 11:14:07 drugs kernel: usb2: on uhci2 Mar 21 11:14:07 drugs kernel: usb2: USB revision 1.0 Mar 21 11:14:07 drugs kernel: uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Mar 21 11:14:07 drugs kernel: uhub2: 2 ports with 2 removable, self powered Mar 21 11:14:07 drugs kernel: uhci3: port 0xbf20-0xbf3f irq 19 at device 29.3 on pci0 Mar 21 11:14:07 drugs kernel: uhci3: [GIANT-LOCKED] Mar 21 11:14:07 drugs kernel: usb3: on uhci3 Mar 21 11:14:07 drugs kernel: usb3: USB revision 1.0 Mar 21 11:14:07 drugs kernel: uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Mar 21 11:14:07 drugs kernel: uhub3: 2 ports with 2 removable, self powered Mar 21 11:14:07 drugs kernel: ehci0: mem 0xffa80800-0xffa80bff irq 16 at device 29.7 on pci0 Mar 21 11:14:07 drugs kernel: ehci0: [GIANT-LOCKED] Mar 21 11:14:07 drugs kernel: usb4: EHCI version 1.0 Mar 21 11:14:07 drugs kernel: usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 Mar 21 11:14:07 drugs kernel: usb4: on ehci0 Mar 21 11:14:07 drugs kernel: usb4: USB revision 2.0 Mar 21 11:14:07 drugs kernel: uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 Mar 21 11:14:07 drugs kernel: uhub4: 8 ports with 8 removable, self powered Mar 21 11:14:07 drugs kernel: pcib2: at device 30.0 on pci0 Mar 21 11:14:07 drugs kernel: pci3: on pcib2 Mar 21 11:14:07 drugs kernel: cbb0: at device 1.0 on pci3 Mar 21 11:14:07 drugs kernel: cardbus0: on cbb0 Mar 21 11:14:07 drugs kernel: pccard0: <16-bit PCCard bus> on cbb0 Mar 21 11:14:07 drugs kernel: pci3: at device 1.5 (no driver attached) Mar 21 11:14:07 drugs kernel: iwi0: mem 0xdfcff000-0xdfcfffff irq 17 at device 3.0 on pci3 Mar 21 11:14:07 drugs kernel: iwi0: Ethernet address: 00:16:6f:46:b7:5d Mar 21 11:14:07 drugs kernel: pcm0: port 0xed00-0xedff,0xec40-0xec7f mem 0xdfebfe00-0xdfebffff,0xdfebfd00-0xdfebfdff irq 16 at device 30.2 on pci0 Mar 21 11:14:07 drugs kernel: pcm0: Mar 21 11:14:07 drugs kernel: pci0: at device 30.3 (no driver attached) Mar 21 11:14:07 drugs kernel: isab0: at device 31.0 on pci0 Mar 21 11:14:07 drugs kernel: isa0: on isab0 Mar 21 11:14:07 drugs kernel: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xbfa0-0xbfaf irq 17 at device 31.2 on pci0 Mar 21 11:14:07 drugs kernel: atapci0: failed to enable memory mapping! Mar 21 11:14:07 drugs kernel: ata0: on atapci0 Mar 21 11:14:07 drugs kernel: ata1: on atapci0 Mar 21 11:14:07 drugs kernel: acpi_tz0: on acpi0 Mar 21 11:14:07 drugs kernel: atkbdc0: port 0x60,0x64,0x62,0x66 irq 1 on acpi0 Mar 21 11:14:07 drugs kernel: atkbd0: irq 1 on atkbdc0 Mar 21 11:14:07 drugs kernel: kbd0 at atkbd0 Mar 21 11:14:07 drugs kernel: atkbd0: [GIANT-LOCKED] Mar 21 11:14:07 drugs kernel: psm0: irq 12 on atkbdc0 Mar 21 11:14:07 drugs kernel: psm0: [GIANT-LOCKED] Mar 21 11:14:07 drugs kernel: psm0: model GlidePoint, device ID 0 Mar 21 11:14:07 drugs kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Mar 21 11:14:07 drugs kernel: sio0: type 16550A Mar 21 11:14:07 drugs kernel: ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 1 on acpi0 Mar 21 11:14:07 drugs kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Mar 21 11:14:07 drugs kernel: ppc0: FIFO with 16/16/8 bytes threshold Mar 21 11:14:07 drugs kernel: ppbus0: on ppc0 Mar 21 11:14:07 drugs kernel: ppi0: on ppbus0 Mar 21 11:14:07 drugs kernel: plip0: on ppbus0 Mar 21 11:14:07 drugs kernel: lpt0: on ppbus0 Mar 21 11:14:07 drugs kernel: lpt0: Interrupt-driven port Mar 21 11:14:07 drugs kernel: pmtimer0 on isa0 Mar 21 11:14:07 drugs kernel: orm0: at iomem 0xc0000-0xcf7ff,0xcf800-0xcffff on isa0 Mar 21 11:14:07 drugs kernel: sc0: at flags 0x100 on isa0 Mar 21 11:14:07 drugs kernel: sc0: VGA <16 virtual consoles, flags=0x300> Mar 21 11:14:07 drugs kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 Mar 21 11:14:07 drugs kernel: sio1: port may not be enabled Mar 21 11:14:07 drugs kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Mar 21 11:14:07 drugs kernel: Timecounter "TSC" frequency 1729121298 Hz quality 800 Mar 21 11:14:07 drugs kernel: Timecounters tick every 1.000 msec Mar 21 11:14:07 drugs kernel: acpi_acad0: acline initialization start Mar 21 11:14:07 drugs kernel: battery0: battery initialization start Mar 21 11:14:07 drugs kernel: acpi_acad0: On Line Mar 21 11:14:07 drugs kernel: acpi_acad0: acline initialization done, tried 1 times Mar 21 11:14:07 drugs kernel: battery1: battery initialization start Mar 21 11:14:07 drugs kernel: battery0: battery initialization done, tried 1 times Mar 21 11:14:07 drugs kernel: ad0: 95396MB at ata0-master UDMA100 Mar 21 11:14:07 drugs kernel: acd0: CDRW at ata1-master UDMA33 Mar 21 11:14:07 drugs kernel: Trying to mount root from ufs:/dev/ad0s4a Mar 21 11:14:07 drugs kernel: ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding enabled, default to deny, logging disabled Mar 21 11:14:07 drugs named[463]: starting BIND 9.4.0a4 -m record -t /var/named -u bind Mar 21 11:14:07 drugs named[463]: command channel listening on 127.0.0.1#953 Mar 21 11:14:07 drugs named[463]: command channel listening on ::1#953 Mar 21 11:14:07 drugs named[463]: running Mar 21 11:14:22 drugs named[463]: client 127.0.0.1#60646: RFC 1918 response from Internet for 1.0.53.10.in-addr.arpa Mar 21 11:14:22 drugs named[463]: client 127.0.0.1#52985: RFC 1918 response from Internet for 2.0.53.10.in-addr.arpa Mar 21 11:14:22 drugs named[463]: client 127.0.0.1#64899: RFC 1918 response from Internet for 3.0.53.10.in-addr.arpa Mar 21 11:14:22 drugs named[463]: client 127.0.0.1#52450: RFC 1918 response from Internet for 4.0.53.10.in-addr.arpa Mar 21 11:14:22 drugs named[463]: client 127.0.0.1#50823: RFC 1918 response from Internet for 5.0.53.10.in-addr.arpa Mar 21 11:14:22 drugs named[463]: client 127.0.0.1#51024: RFC 1918 response from Internet for 6.0.53.10.in-addr.arpa Mar 21 11:14:33 drugs login: ROOT LOGIN (root) ON ttyv0 Mar 21 11:14:48 drugs kernel: battery1: battery initialization failed, giving up Mar 21 11:15:00 drugs kernel: acpi_lid0: Lid closed Mar 21 11:15:02 drugs kernel: acpi_lid0: Lid opened Mar 21 11:15:08 drugs kernel: acpi_lid0: Lid closed Mar 21 11:15:12 drugs kernel: acpi_lid0: Lid opened Mar 21 11:15:17 drugs reboot: rebooted by root Mar 21 11:15:17 drugs syslogd: exiting on signal 15 Mar 21 11:16:32 drugs syslogd: kernel boot file is /boot/kernel/kernel Mar 21 11:16:32 drugs kernel: Copyright (c) 1992-2006 The FreeBSD Project. Mar 21 11:16:32 drugs kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Mar 21 11:16:32 drugs kernel: The Regents of the University of California. All rights reserved. Mar 21 11:16:32 drugs kernel: FreeBSD 6.1-PRERELEASE #1: Sat Mar 18 01:49:32 EST 2006 Mar 21 11:16:32 drugs kernel: marka@drugs.dv.isc.org:/usr/obj/usr/src/sys/DRUGS Mar 21 11:16:32 drugs kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Mar 21 11:16:32 drugs kernel: CPU: Intel(R) Pentium(R) M processor 1.73GHz (1729.12-MHz 686-class CPU) Mar 21 11:16:32 drugs kernel: Origin = "GenuineIntel" Id = 0x6d8 Stepping = 8 Mar 21 11:16:32 drugs kernel: Features=0xafe9fbff Mar 21 11:16:32 drugs kernel: Features2=0x180 Mar 21 11:16:32 drugs kernel: AMD Features=0x100000 Mar 21 11:16:32 drugs kernel: real memory = 1065160704 (1015 MB) Mar 21 11:16:32 drugs kernel: avail memory = 1033383936 (985 MB) Mar 21 11:16:32 drugs kernel: ACPI APIC Table: Mar 21 11:16:32 drugs kernel: ioapic0: Changing APIC ID to 1 Mar 21 11:16:32 drugs kernel: ioapic0 irqs 0-23 on motherboard Mar 21 11:16:32 drugs kernel: wlan: mac acl policy registered Mar 21 11:16:32 drugs kernel: npx0: [FAST] Mar 21 11:16:32 drugs kernel: npx0: on motherboard Mar 21 11:16:32 drugs kernel: npx0: INT 16 interface Mar 21 11:16:32 drugs kernel: acpi0: on motherboard Mar 21 11:16:32 drugs kernel: Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 Mar 21 11:16:32 drugs kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 Mar 21 11:16:32 drugs kernel: cpu0: on acpi0 Mar 21 11:16:32 drugs kernel: acpi_throttle0: on cpu0 Mar 21 11:16:32 drugs kernel: acpi_acad0: on acpi0 Mar 21 11:16:32 drugs kernel: battery0: on acpi0 Mar 21 11:16:32 drugs kernel: battery1: on acpi0 Mar 21 11:16:32 drugs kernel: acpi_lid0: on acpi0 Mar 21 11:16:32 drugs kernel: acpi_button0: on acpi0 Mar 21 11:16:32 drugs kernel: acpi_button1: on acpi0 Mar 21 11:16:32 drugs kernel: pcib0: port 0xcf8-0xcff on acpi0 Mar 21 11:16:32 drugs kernel: pci0: on pcib0 Mar 21 11:16:32 drugs kernel: agp0: port 0xec38-0xec3f mem 0xdff00000-0xdff7ffff,0xc0000000-0xcfffffff,0xdfec0000-0xdfefffff irq 16 at device 2.0 on pci0 Mar 21 11:16:32 drugs kernel: agp0: detected 7932k stolen memory Mar 21 11:16:32 drugs kernel: agp0: aperture size is 256M Mar 21 11:16:32 drugs kernel: pci0: at device 2.1 (no driver attached) Mar 21 11:16:32 drugs kernel: pcib1: at device 28.0 on pci0 Mar 21 11:16:32 drugs kernel: pci2: on pcib1 Mar 21 11:16:32 drugs kernel: bge0: mem 0xdfdf0000-0xdfdfffff irq 16 at device 0.0 on pci2 Mar 21 11:16:32 drugs kernel: miibus0: on bge0 Mar 21 11:16:32 drugs kernel: brgphy0: on miibus0 Mar 21 11:16:32 drugs kernel: brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto Mar 21 11:16:32 drugs kernel: bge0: Ethernet address: 00:14:22:d9:fb:dc Mar 21 11:16:32 drugs kernel: uhci0: port 0xbf80-0xbf9f irq 16 at device 29.0 on pci0 Mar 21 11:16:32 drugs kernel: uhci0: [GIANT-LOCKED] Mar 21 11:16:32 drugs kernel: usb0: on uhci0 Mar 21 11:16:32 drugs kernel: usb0: USB revision 1.0 Mar 21 11:16:32 drugs kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Mar 21 11:16:32 drugs kernel: uhub0: 2 ports with 2 removable, self powered Mar 21 11:16:32 drugs kernel: uhci1: port 0xbf60-0xbf7f irq 17 at device 29.1 on pci0 Mar 21 11:16:32 drugs kernel: uhci1: [GIANT-LOCKED] Mar 21 11:16:32 drugs kernel: usb1: on uhci1 Mar 21 11:16:32 drugs kernel: usb1: USB revision 1.0 Mar 21 11:16:32 drugs kernel: uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Mar 21 11:16:32 drugs kernel: uhub1: 2 ports with 2 removable, self powered Mar 21 11:16:32 drugs kernel: uhci2: port 0xbf40-0xbf5f irq 18 at device 29.2 on pci0 Mar 21 11:16:32 drugs kernel: uhci2: [GIANT-LOCKED] Mar 21 11:16:32 drugs kernel: usb2: on uhci2 Mar 21 11:16:32 drugs kernel: usb2: USB revision 1.0 Mar 21 11:16:32 drugs kernel: uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Mar 21 11:16:32 drugs kernel: uhub2: 2 ports with 2 removable, self powered Mar 21 11:16:32 drugs kernel: uhci3: port 0xbf20-0xbf3f irq 19 at device 29.3 on pci0 Mar 21 11:16:32 drugs kernel: uhci3: [GIANT-LOCKED] Mar 21 11:16:32 drugs kernel: usb3: on uhci3 Mar 21 11:16:32 drugs kernel: usb3: USB revision 1.0 Mar 21 11:16:32 drugs kernel: uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Mar 21 11:16:32 drugs kernel: uhub3: 2 ports with 2 removable, self powered Mar 21 11:16:32 drugs kernel: ehci0: mem 0xffa80800-0xffa80bff irq 16 at device 29.7 on pci0 Mar 21 11:16:32 drugs kernel: ehci0: [GIANT-LOCKED] Mar 21 11:16:32 drugs kernel: usb4: EHCI version 1.0 Mar 21 11:16:32 drugs kernel: usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 Mar 21 11:16:32 drugs kernel: usb4: on ehci0 Mar 21 11:16:32 drugs kernel: usb4: USB revision 2.0 Mar 21 11:16:32 drugs kernel: uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 Mar 21 11:16:32 drugs kernel: uhub4: 8 ports with 8 removable, self powered Mar 21 11:16:32 drugs kernel: pcib2: at device 30.0 on pci0 Mar 21 11:16:32 drugs kernel: pci3: on pcib2 Mar 21 11:16:32 drugs kernel: cbb0: at device 1.0 on pci3 Mar 21 11:16:32 drugs kernel: cardbus0: on cbb0 Mar 21 11:16:32 drugs kernel: pccard0: <16-bit PCCard bus> on cbb0 Mar 21 11:16:32 drugs kernel: pci3: at device 1.5 (no driver attached) Mar 21 11:16:32 drugs kernel: iwi0: mem 0xdfcff000-0xdfcfffff irq 17 at device 3.0 on pci3 Mar 21 11:16:32 drugs kernel: iwi0: Ethernet address: 00:16:6f:46:b7:5d Mar 21 11:16:32 drugs kernel: pcm0: port 0xed00-0xedff,0xec40-0xec7f mem 0xdfebfe00-0xdfebffff,0xdfebfd00-0xdfebfdff irq 16 at device 30.2 on pci0 Mar 21 11:16:32 drugs kernel: pcm0: Mar 21 11:16:32 drugs kernel: pci0: at device 30.3 (no driver attached) Mar 21 11:16:32 drugs kernel: isab0: at device 31.0 on pci0 Mar 21 11:16:32 drugs kernel: isa0: on isab0 Mar 21 11:16:32 drugs kernel: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xbfa0-0xbfaf irq 17 at device 31.2 on pci0 Mar 21 11:16:32 drugs kernel: atapci0: failed to enable memory mapping! Mar 21 11:16:32 drugs kernel: ata0: on atapci0 Mar 21 11:16:32 drugs kernel: ata1: on atapci0 Mar 21 11:16:32 drugs kernel: acpi_tz0: on acpi0 Mar 21 11:16:32 drugs kernel: atkbdc0: port 0x60,0x64,0x62,0x66 irq 1 on acpi0 Mar 21 11:16:32 drugs kernel: atkbd0: irq 1 on atkbdc0 Mar 21 11:16:32 drugs kernel: kbd0 at atkbd0 Mar 21 11:16:32 drugs kernel: atkbd0: [GIANT-LOCKED] Mar 21 11:16:32 drugs kernel: psm0: irq 12 on atkbdc0 Mar 21 11:16:32 drugs kernel: psm0: [GIANT-LOCKED] Mar 21 11:16:32 drugs kernel: psm0: model GlidePoint, device ID 0 Mar 21 11:16:32 drugs kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Mar 21 11:16:32 drugs kernel: sio0: type 16550A Mar 21 11:16:32 drugs kernel: ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 1 on acpi0 Mar 21 11:16:32 drugs kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Mar 21 11:16:32 drugs kernel: ppc0: FIFO with 16/16/8 bytes threshold Mar 21 11:16:32 drugs kernel: ppbus0: on ppc0 Mar 21 11:16:32 drugs kernel: ppi0: on ppbus0 Mar 21 11:16:32 drugs kernel: plip0: on ppbus0 Mar 21 11:16:32 drugs kernel: lpt0: on ppbus0 Mar 21 11:16:32 drugs kernel: lpt0: Interrupt-driven port Mar 21 11:16:32 drugs kernel: pmtimer0 on isa0 Mar 21 11:16:32 drugs kernel: orm0: at iomem 0xc0000-0xcf7ff,0xcf800-0xcffff on isa0 Mar 21 11:16:32 drugs kernel: sc0: at flags 0x100 on isa0 Mar 21 11:16:32 drugs kernel: sc0: VGA <16 virtual consoles, flags=0x300> Mar 21 11:16:32 drugs kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 Mar 21 11:16:32 drugs kernel: sio1: port may not be enabled Mar 21 11:16:32 drugs kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Mar 21 11:16:32 drugs kernel: Timecounter "TSC" frequency 1729120496 Hz quality 800 Mar 21 11:16:32 drugs kernel: Timecounters tick every 1.000 msec Mar 21 11:16:32 drugs kernel: acpi_acad0: acline initialization start Mar 21 11:16:32 drugs kernel: battery0: battery initialization start Mar 21 11:16:32 drugs kernel: acpi_acad0: On Line Mar 21 11:16:32 drugs kernel: acpi_acad0: acline initialization done, tried 1 times Mar 21 11:16:32 drugs kernel: battery1: battery initialization start Mar 21 11:16:32 drugs kernel: battery0: battery initialization done, tried 1 times Mar 21 11:16:32 drugs kernel: ad0: 95396MB at ata0-master UDMA100 Mar 21 11:16:32 drugs kernel: acd0: CDRW at ata1-master UDMA33 Mar 21 11:16:32 drugs kernel: Trying to mount root from ufs:/dev/ad0s4a Mar 21 11:16:32 drugs kernel: ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding enabled, default to deny, logging disabled Mar 21 11:16:32 drugs named[463]: starting BIND 9.4.0a4 -m record -t /var/named -u bind Mar 21 11:16:32 drugs named[463]: command channel listening on 127.0.0.1#953 Mar 21 11:16:32 drugs named[463]: command channel listening on ::1#953 Mar 21 11:16:32 drugs named[463]: running Mar 21 11:16:51 drugs named[463]: client 127.0.0.1#52985: RFC 1918 response from Internet for 1.0.53.10.in-addr.arpa Mar 21 11:16:52 drugs named[463]: client 127.0.0.1#64899: RFC 1918 response from Internet for 2.0.53.10.in-addr.arpa Mar 21 11:16:54 drugs named[463]: client 127.0.0.1#52450: RFC 1918 response from Internet for 3.0.53.10.in-addr.arpa Mar 21 11:16:54 drugs named[463]: client 127.0.0.1#50823: RFC 1918 response from Internet for 4.0.53.10.in-addr.arpa Mar 21 11:16:54 drugs named[463]: client 127.0.0.1#51024: RFC 1918 response from Internet for 5.0.53.10.in-addr.arpa Mar 21 11:16:54 drugs named[463]: client 127.0.0.1#50345: RFC 1918 response from Internet for 6.0.53.10.in-addr.arpa Mar 21 11:17:02 drugs login: 1 LOGIN FAILURE ON ttyv0 Mar 21 11:17:07 drugs kernel: battery1: battery initialization failed, giving up Mar 21 11:17:10 drugs login: ROOT LOGIN (root) ON ttyv0 Mar 21 11:17:39 drugs reboot: rebooted by root Mar 21 11:17:39 drugs syslogd: exiting on signal 15 -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 21 06:00: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 E47AD16A41F; Tue, 21 Mar 2006 06:00:40 +0000 (UTC) (envelope-from acpi@dino.sk) Received: from bsd.dino.sk (bsd.dino.sk [213.215.72.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4564043D4C; Tue, 21 Mar 2006 06:00:39 +0000 (GMT) (envelope-from acpi@dino.sk) Received: from lex ([213.215.74.194]) (AUTH: PLAIN milan, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by bsd.dino.sk with esmtp; Tue, 21 Mar 2006 07:01:23 +0100 id 00000098.441F96B3.0000765E From: Milan Obuch To: freebsd-acpi@freebsd.org Date: Tue, 21 Mar 2006 07:00:12 +0100 User-Agent: KMail/1.8.3 References: <200603061009.03933.acpi@dino.sk> <200603201850.51441.acpi@dino.sk> <200603201349.39308.jhb@freebsd.org> In-Reply-To: <200603201349.39308.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603210700.18673.acpi@dino.sk> Cc: Subject: Re: Trouble with ACPI on my TabletPC TC1000 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: Tue, 21 Mar 2006 06:00:41 -0000 On Monday 20 March 2006 19:49, you wrote: > On Monday 20 March 2006 12:50, Milan Obuch wrote: > > On Monday 20 March 2006 17:33, John Baldwin wrote: ... > > > I'd like to see a copy of your asl. This is the first I've heard of an > > > ACPI system resource device being a PCI device. > > > > Do you mean output of acpidump -d -t? Posted on my page, download full > > text version... If anything else is useful/interesting, just drop a line > > and I will try to find that info, test a patch... anything. > > This is a really retarded motherboard. It claims to have two PCI-ISA > bridges and the second PCI-ISA bridge also claims to be a system resource. > I can give you a patch for your system though. Try > http://www.FreeBSD.org/~jhb/patches/tc1000.patch This patch works - system boots fine. Only issue seen was 'suspend request ignored - not ready yet' yesterday, but not (yet) today, when pressing on/off button (maybe designed as suspend/resume button). I would like to put this patch on my page, too - any objection? On the other side, from the VT82C686B datasheet it looks like I need a driver for this system resource, which should be PCI function 4 - output from pciconf -lv related to this is isab1@pci0:7:4: class=0x060100 card=0x00b50e11 chip=0x30571106 rev=0x40 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82C686A/B ACPI Power Management Controller' class = bridge subclass = PCI-ISA Any idea on this, apart from writing new driver? How could I find info on this device from asl? I do not understand this, yet... Regards, Milan From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 21 08:13:48 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 35D5E16A401 for ; Tue, 21 Mar 2006 08:13:48 +0000 (UTC) (envelope-from markd@kermodei.org) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 925FB43D48 for ; Tue, 21 Mar 2006 08:13:47 +0000 (GMT) (envelope-from markd@kermodei.org) Received: from pimout7-ext.prodigy.net (pimout7-int.prodigy.net [207.115.4.147]) by ylpvm15.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id k2L8DnYA019956 for ; Tue, 21 Mar 2006 03:13:50 -0500 X-ORBL: [67.123.80.209] Received: from osprey.kermodei.org (osprey.kermodei.org [67.123.80.209]) by pimout7-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id k2L8DfD1115680; Tue, 21 Mar 2006 03:13:41 -0500 Received: from localhost (osprey.kermodei.org [127.0.0.1]) by osprey.kermodei.org (Postfix) with ESMTP id 34E0B5C55; Tue, 21 Mar 2006 00:13:49 -0800 (PST) Received: from osprey.kermodei.org ([127.0.0.1]) by localhost (osprey.kermodei.org [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id 21789-03; Tue, 21 Mar 2006 00:13:47 -0800 (PST) Received: by osprey.kermodei.org (Postfix, from userid 1000) id AE4AF5C4F; Tue, 21 Mar 2006 00:13:47 -0800 (PST) From: Mark Diekhans MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17439.46523.576483.319302@osprey.kermodei.org> Date: Tue, 21 Mar 2006 00:13:47 -0800 To: Mark Andrews In-Reply-To: <200603210525.k2L5PSis001981@drugs.dv.isc.org> References: <200603210525.k2L5PSis001981@drugs.dv.isc.org> X-Mailer: VM 7.19 under Emacs 21.3.1 Cc: freebsd-acpi@freebsd.org Subject: Re: DELL D610 lid and backlight 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: Tue, 21 Mar 2006 08:13:48 -0000 Mark Andrews writes: > I have a problem if I enable acpi on my dell d610. The backlight > goes off and doesn't come back on if the lid is closed. This is > independent of whether debug.acpi.disabled="lid" is set or not. For the Dell X1, enable acpi_video in loader.conf: /boot/loader.conf with: acpi_video_load="YES" add this to /etc/devd.conf: # lid open/close events notify 10 { match "system" "ACPI"; match "subsystem" "Lid"; action "/etc/rc.lid $notify"; }; /etc/rc.lid is: #!/bin/sh # deal with lid switch events if [ x$1 = x0x00 ]; then logger -t Lid Closed at `date` sysctl hw.acpi.video.out0.active=0 else logger -t Lid Opened at `date` sysctl hw.acpi.video.out0.active=1 fi From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 21 14:04:28 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 356D016A41F for ; Tue, 21 Mar 2006 14:04:28 +0000 (UTC) (envelope-from Mark_Andrews@isc.org) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 017E843D45 for ; Tue, 21 Mar 2006 14:04:26 +0000 (GMT) (envelope-from Mark_Andrews@isc.org) Received: from drugs.dv.isc.org (localhost.isc.org [IPv6:::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by farside.isc.org (Postfix) with ESMTP id C305AE60EB for ; Tue, 21 Mar 2006 14:04:26 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.13.4/8.13.4) with ESMTP id k2LDDdKr001086; Wed, 22 Mar 2006 00:13:41 +1100 (EST) (envelope-from marka@drugs.dv.isc.org) Message-Id: <200603211313.k2LDDdKr001086@drugs.dv.isc.org> To: Mark Diekhans From: Mark Andrews In-reply-to: Your message of "Tue, 21 Mar 2006 00:13:47 -0800." <17439.46523.576483.319302@osprey.kermodei.org> Date: Wed, 22 Mar 2006 00:13:39 +1100 Sender: Mark_Andrews@isc.org Cc: freebsd-acpi@freebsd.org Subject: Re: DELL D610 lid and backlight 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: Tue, 21 Mar 2006 14:04:28 -0000 > Mark Andrews writes: > > I have a problem if I enable acpi on my dell d610. The backlight > > goes off and doesn't come back on if the lid is closed. This is > > independent of whether debug.acpi.disabled="lid" is set or not. > > For the Dell X1, > > enable acpi_video in loader.conf: /boot/loader.conf with: > acpi_video_load="YES" > > add this to /etc/devd.conf: > > # lid open/close events > notify 10 { > match "system" "ACPI"; > match "subsystem" "Lid"; > action "/etc/rc.lid $notify"; > }; > > /etc/rc.lid is: > > #!/bin/sh > # deal with lid switch events > > if [ x$1 = x0x00 ]; then > logger -t Lid Closed at `date` > sysctl hw.acpi.video.out0.active=0 > else > logger -t Lid Opened at `date` > sysctl hw.acpi.video.out0.active=1 > fi Thanks. That helped. I've got "shutdown -p now" back now as well. The back light was more important than power management so I had disabled acpi between between sessions. Standby still has the same symptoms. I added hw.acpi.video.out0.active=1 to sysctl.conf in case it was rebooting so it would restore the back light on the way up. This doesn't appear to be the case. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 21 14:10:27 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 21A8116A400 for ; Tue, 21 Mar 2006 14:10:27 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DD4B43D5D for ; Tue, 21 Mar 2006 14:10:26 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k2LEAPh9024856; Tue, 21 Mar 2006 08:10:25 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <44200951.204@centtech.com> Date: Tue, 21 Mar 2006 08:10:25 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060112) MIME-Version: 1.0 To: Mark Andrews References: <200603211313.k2LDDdKr001086@drugs.dv.isc.org> In-Reply-To: <200603211313.k2LDDdKr001086@drugs.dv.isc.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1346/Tue Mar 21 03:03:02 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-acpi@freebsd.org Subject: Re: DELL D610 lid and backlight 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: Tue, 21 Mar 2006 14:10:27 -0000 Mark Andrews wrote: >> Mark Andrews writes: >> >>> I have a problem if I enable acpi on my dell d610. The backlight >>> goes off and doesn't come back on if the lid is closed. This is >>> independent of whether debug.acpi.disabled="lid" is set or not. >>> >> For the Dell X1, >> >> enable acpi_video in loader.conf: /boot/loader.conf with: >> acpi_video_load="YES" >> >> add this to /etc/devd.conf: >> >> # lid open/close events >> notify 10 { >> match "system" "ACPI"; >> match "subsystem" "Lid"; >> action "/etc/rc.lid $notify"; >> }; >> >> /etc/rc.lid is: >> >> #!/bin/sh >> # deal with lid switch events >> >> if [ x$1 = x0x00 ]; then >> logger -t Lid Closed at `date` >> sysctl hw.acpi.video.out0.active=0 >> else >> logger -t Lid Opened at `date` >> sysctl hw.acpi.video.out0.active=1 >> fi >> > > Thanks. That helped. I've got "shutdown -p now" back now as > well. The back light was more important than power management > so I had disabled acpi between between sessions. > > Standby still has the same symptoms. I added > hw.acpi.video.out0.active=1 to sysctl.conf in case it was rebooting > so it would restore the back light on the way up. This doesn't > appear to be the case. > If you have debugging enabled - it might be going into the debugger. Check caps lock - does it work? If so, try doing a 'call doadump' and hit enter - does the hd run for a while? If it does, when it stops running, type 'restart' and maybe it will reboot. On my D810 (which is the same system as the D610 I believe), I can get it to suspend, but resuming makes the system boot up like it had been turned off. I have these settings in /etc/sysctl.conf: hw.acpi.lid_switch_state=NONE debug.cpufreq.lowest=500 hw.acpi.video.lcd0.active=1 hw.acpi.video.crt0.active=1 And have played with these two settings: #hw.acpi.reset_video=1 #hw.syscons.sc_no_suspend_vtswitch=1 I also have this in /boot/loader.conf, but can't recall why: hw.apic.enable_extint=1 Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 21 19:14:05 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 3F72B16A423; Tue, 21 Mar 2006 19:14:05 +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 9927543D45; Tue, 21 Mar 2006 19:14:02 +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 k2LJE1OI011221; Tue, 21 Mar 2006 14:14:01 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Tue, 21 Mar 2006 13:43:52 -0500 User-Agent: KMail/1.9.1 References: <200603210033.k2L0Xorb043252@freefall.freebsd.org> In-Reply-To: <200603210033.k2L0Xorb043252@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603211343.55664.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1347/Tue Mar 21 11:35:25 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.6 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-i386@freebsd.org, Mark Linimon 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: Tue, 21 Mar 2006 19:14:05 -0000 On Monday 20 March 2006 19:33, Mark Linimon wrote: > Synopsis: [panic] [patch] ACPI Panic with some ACPI 2.0 PC & cannot boot > > Responsible-Changed-From-To: freebsd-i386->freebsd-acpi > Responsible-Changed-By: linimon > Responsible-Changed-When: Tue Mar 21 00:31:09 UTC 2006 > Responsible-Changed-Why: > Over to maintainer(s). > > http://www.freebsd.org/cgi/query-pr.cgi?pr=93963 The patch basically forces the use of ACPI 1.0 tables if the ACPI 2.0 table pointer is NULL. This is really just more BIOS brain damage. Most of the patch is to Intel's ACPI-CA code, so we need to see what they think about this workaround. -- 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 Mar 21 20:24: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 5125716A400; Tue, 21 Mar 2006 20:24:54 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB9EF43D58; Tue, 21 Mar 2006 20:24:45 +0000 (GMT) (envelope-from nate@root.org) Received: from pimout7-ext.prodigy.net (pimout7-int.prodigy.net [207.115.4.147]) by ylpvm15.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id k2LKOkYC004490; Tue, 21 Mar 2006 15:24:46 -0500 X-ORBL: [67.119.74.222] Received: from [10.0.0.53] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by pimout7-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id k2LKOaZA168712; Tue, 21 Mar 2006 15:24:41 -0500 Message-ID: <442060E8.2000908@root.org> Date: Tue, 21 Mar 2006 12:24:08 -0800 From: Nate Lawson User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: fukui.FreeBSD@fanet.net References: <200603210033.k2L0Xorb043252@freefall.freebsd.org> <200603211343.55664.jhb@freebsd.org> In-Reply-To: <200603211343.55664.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Tue, 21 Mar 2006 20:24:54 -0000 John Baldwin wrote: > On Monday 20 March 2006 19:33, Mark Linimon wrote: >> Synopsis: [panic] [patch] ACPI Panic with some ACPI 2.0 PC & cannot boot >> >> Responsible-Changed-From-To: freebsd-i386->freebsd-acpi >> Responsible-Changed-By: linimon >> Responsible-Changed-When: Tue Mar 21 00:31:09 UTC 2006 >> Responsible-Changed-Why: >> Over to maintainer(s). >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=93963 > > The patch basically forces the use of ACPI 1.0 tables if the ACPI 2.0 table > pointer is NULL. This is really just more BIOS brain damage. Most of the > patch is to Intel's ACPI-CA code, so we need to see what they think about > this workaround. Fukui-san, Would you please submit the output of acpidump -t to the PR? This would help us understand the RSDT and XSDT on your machine. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 21 20:30:31 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 A4F7016A4C9 for ; Tue, 21 Mar 2006 20:30:31 +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 3051443D46 for ; Tue, 21 Mar 2006 20:30:31 +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 k2LKUVuS031013 for ; Tue, 21 Mar 2006 20:30:31 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k2LKUVIw031012; Tue, 21 Mar 2006 20:30:31 GMT (envelope-from gnats) Date: Tue, 21 Mar 2006 20:30:31 GMT Message-Id: <200603212030.k2LKUVIw031012@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: Nate Lawson 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: Nate Lawson List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Mar 2006 20:30:31 -0000 The following reply was made to PR i386/93963; it has been noted by GNATS. From: Nate Lawson To: fukui.FreeBSD@fanet.net 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: Tue, 21 Mar 2006 12:24:08 -0800 John Baldwin wrote: > On Monday 20 March 2006 19:33, Mark Linimon wrote: >> Synopsis: [panic] [patch] ACPI Panic with some ACPI 2.0 PC & cannot boot >> >> Responsible-Changed-From-To: freebsd-i386->freebsd-acpi >> Responsible-Changed-By: linimon >> Responsible-Changed-When: Tue Mar 21 00:31:09 UTC 2006 >> Responsible-Changed-Why: >> Over to maintainer(s). >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=93963 > > The patch basically forces the use of ACPI 1.0 tables if the ACPI 2.0 table > pointer is NULL. This is really just more BIOS brain damage. Most of the > patch is to Intel's ACPI-CA code, so we need to see what they think about > this workaround. Fukui-san, Would you please submit the output of acpidump -t to the PR? This would help us understand the RSDT and XSDT on your machine. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 21 21:12:36 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 3CDE616A401; Tue, 21 Mar 2006 21:12:36 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm43.prodigy.net (ylpvm43-ext.prodigy.net [207.115.57.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA6AD43D46; Tue, 21 Mar 2006 21:12:35 +0000 (GMT) (envelope-from nate@root.org) Received: from pimout5-ext.prodigy.net (pimout5-int.prodigy.net [207.115.4.21]) by ylpvm43.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id k2LLCcBf009143; Tue, 21 Mar 2006 16:12:38 -0500 X-ORBL: [67.119.74.222] Received: from [10.0.0.53] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by pimout5-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id k2LLCSDB013658; Tue, 21 Mar 2006 16:12:33 -0500 Message-ID: <44206C20.1060603@root.org> Date: Tue, 21 Mar 2006 13:12:00 -0800 From: Nate Lawson User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: fukui.FreeBSD@fanet.net References: <200603210033.k2L0Xorb043252@freefall.freebsd.org> <200603211343.55664.jhb@freebsd.org> <442060E8.2000908@root.org> In-Reply-To: <442060E8.2000908@root.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Tue, 21 Mar 2006 21:12:36 -0000 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. 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. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 21 21:20:13 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 75B6C16A422 for ; Tue, 21 Mar 2006 21:20:13 +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 B2D1743D46 for ; Tue, 21 Mar 2006 21:20:12 +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 k2LLKCMS034102 for ; Tue, 21 Mar 2006 21:20:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k2LLKCsd034101; Tue, 21 Mar 2006 21:20:12 GMT (envelope-from gnats) Date: Tue, 21 Mar 2006 21:20:12 GMT Message-Id: <200603212120.k2LLKCsd034101@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: Nate Lawson 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: Nate Lawson List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Mar 2006 21:20:13 -0000 The following reply was made to PR i386/93963; it has been noted by GNATS. From: Nate Lawson To: fukui.FreeBSD@fanet.net 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: Tue, 21 Mar 2006 13:12:00 -0800 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. 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. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Mar 22 08:08:22 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 639BF16A420 for ; Wed, 22 Mar 2006 08:08:22 +0000 (UTC) (envelope-from acpi@dino.sk) Received: from bsd.dino.sk (bsd.dino.sk [213.215.72.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98C6143D53 for ; Wed, 22 Mar 2006 08:08:20 +0000 (GMT) (envelope-from acpi@dino.sk) Received: from lex ([213.215.74.194]) (AUTH: PLAIN milan, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by bsd.dino.sk with esmtp; Wed, 22 Mar 2006 09:09:11 +0100 id 000000AA.44210627.0000F74A From: Milan Obuch To: freebsd-acpi@freebsd.org Date: Wed, 22 Mar 2006 09:08:03 +0100 User-Agent: KMail/1.8.3 References: <200603061009.03933.acpi@dino.sk> <200603201349.39308.jhb@freebsd.org> <200603210700.18673.acpi@dino.sk> In-Reply-To: <200603210700.18673.acpi@dino.sk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603220908.05065.acpi@dino.sk> Subject: Re: Trouble with ACPI on my TabletPC TC1000 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: Wed, 22 Mar 2006 08:08:22 -0000 On Tuesday 21 March 2006 07:00, Milan Obuch wrote: ... > > This is a really retarded motherboard. It claims to have two PCI-ISA > > bridges and the second PCI-ISA bridge also claims to be a system > > resource. I can give you a patch for your system though. Try > > http://www.FreeBSD.org/~jhb/patches/tc1000.patch > > This patch works - system boots fine. Only issue seen was 'suspend request > ignored - not ready yet' yesterday, but not (yet) today, when pressing > on/off button (maybe designed as suspend/resume button). I would like to > put this patch on my page, too - any objection? > > On the other side, from the VT82C686B datasheet it looks like I need a > driver for this system resource, which should be PCI function 4 - output > from pciconf -lv related to this is > > isab1@pci0:7:4: class=0x060100 card=0x00b50e11 chip=0x30571106 rev=0x40 > hdr=0x00 > vendor = 'VIA Technologies Inc' > device = 'VT82C686A/B ACPI Power Management Controller' > class = bridge > subclass = PCI-ISA > > Any idea on this, apart from writing new driver? > How could I find info on this device from asl? I do not understand this, > yet... > Huh, somewhat blind - viapm_load="YES" in loader.conf was it. What is weird 'kldload viapm' does not work - but I understand isab is already attached so nothing else could work. I will try a patch for this issue, later. Still, hints how to understand my asl are more than welcome... Regards, Milan -- Please reply to the mailing list only. This address is filtered.