From owner-freebsd-acpi@FreeBSD.ORG Sun Apr 15 09:19:25 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 455DE16A406; Sun, 15 Apr 2007 09:19:25 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 1CA7413C44B; Sun, 15 Apr 2007 09:19:25 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (remko@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l3F9JOwa093890; Sun, 15 Apr 2007 09:19:24 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l3F9JO5b093886; Sun, 15 Apr 2007 09:19:24 GMT (envelope-from remko) Date: Sun, 15 Apr 2007 09:19:24 GMT From: Remko Lodder Message-Id: <200704150919.l3F9JO5b093886@freefall.freebsd.org> To: lon_kamikaze@gmx.de, remko@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-acpi@FreeBSD.org Cc: Subject: Re: kern/111591: [Releng_6][i386][acpi_ibm] dev.acpi_ibm.0.events returns I/O error 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, 15 Apr 2007 09:19:25 -0000 Synopsis: [Releng_6][i386][acpi_ibm] dev.acpi_ibm.0.events returns I/O error State-Changed-From-To: closed->open State-Changed-By: remko State-Changed-When: Sun Apr 15 09:18:14 UTC 2007 State-Changed-Why: Reopen (different ticket): reassign to acpi team Responsible-Changed-From-To: freebsd-i386->freebsd-acpi Responsible-Changed-By: remko Responsible-Changed-When: Sun Apr 15 09:18:14 UTC 2007 Responsible-Changed-Why: Reopen (different ticket): reassign to acpi team http://www.freebsd.org/cgi/query-pr.cgi?pr=111591 From owner-freebsd-acpi@FreeBSD.ORG Sun Apr 15 09:30:07 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B35C216A403 for ; Sun, 15 Apr 2007 09:30:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 9A31E13C43E for ; Sun, 15 Apr 2007 09:30:07 +0000 (UTC) (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 l3F9U7jM094632 for ; Sun, 15 Apr 2007 09:30:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l3F9U77c094631; Sun, 15 Apr 2007 09:30:07 GMT (envelope-from gnats) Date: Sun, 15 Apr 2007 09:30:07 GMT Message-Id: <200704150930.l3F9U77c094631@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: "[LoN]Kamikaze" Cc: Subject: Re: i386/111591: [Releng_6][i386][acpi_ibm] dev.acpi_ibm.0.events returns I/O error X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "\[LoN\]Kamikaze" List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Apr 2007 09:30:07 -0000 The following reply was made to PR kern/111591; it has been noted by GNATS. From: "[LoN]Kamikaze" To: Remko Lodder Cc: freebsd-i386@FreeBSD.org, bug-followup@FreeBSD.org Subject: Re: i386/111591: [Releng_6][i386][acpi_ibm] dev.acpi_ibm.0.events returns I/O error Date: Sun, 15 Apr 2007 11:24:13 +0200 Remko Lodder wrote: > Synopsis: [Releng_6][i386][acpi_ibm] dev.acpi_ibm.0.events returns I/O error > > State-Changed-From-To: open->closed > State-Changed-By: remko > State-Changed-When: Sun Apr 15 09:16:55 UTC 2007 > State-Changed-Why: > duplicate of 111590 > > http://www.freebsd.org/cgi/query-pr.cgi?pr=111591 > What does a problem with the acpi_ibm module have to do with psm? I think those are two distinct problems. Other acpi features that are not used through the acpi_ibm module work fine. From owner-freebsd-acpi@FreeBSD.ORG Sun Apr 15 13:20:07 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1CCB116A400 for ; Sun, 15 Apr 2007 13:20:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id BE93213C45B for ; Sun, 15 Apr 2007 13:20:06 +0000 (UTC) (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 l3FDK6Ow011546 for ; Sun, 15 Apr 2007 13:20:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l3FDK6L1011543; Sun, 15 Apr 2007 13:20:06 GMT (envelope-from gnats) Date: Sun, 15 Apr 2007 13:20:06 GMT Message-Id: <200704151320.l3FDK6L1011543@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: Remko Lodder Cc: Subject: Re: i386/111591: [Releng_6][i386][acpi_ibm] dev.acpi_ibm.0.events returns I/O error X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Remko Lodder List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Apr 2007 13:20:07 -0000 The following reply was made to PR kern/111591; it has been noted by GNATS. From: Remko Lodder To: "[LoN]Kamikaze" Cc: freebsd-i386@FreeBSD.org, bug-followup@FreeBSD.org Subject: Re: i386/111591: [Releng_6][i386][acpi_ibm] dev.acpi_ibm.0.events returns I/O error Date: Sun, 15 Apr 2007 15:01:10 +0200 [LoN]Kamikaze wrote: > Remko Lodder wrote: >> Synopsis: [Releng_6][i386][acpi_ibm] dev.acpi_ibm.0.events returns I/O error >> >> State-Changed-From-To: open->closed >> State-Changed-By: remko >> State-Changed-When: Sun Apr 15 09:16:55 UTC 2007 >> State-Changed-Why: >> duplicate of 111590 >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=111591 >> > > What does a problem with the acpi_ibm module have to do with psm? I think those are two distinct problems. Other acpi features that are not used through the acpi_ibm module work fine. As you might have seen this already had been corrected. Thanks for the headsup though, regards, remko -- Kind regards, Remko Lodder ** remko@elvandar.org FreeBSD ** remko@FreeBSD.org /* Quis custodiet ipsos custodes */ From owner-freebsd-acpi@FreeBSD.ORG Sun Apr 15 19:50:07 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7695B16A401 for ; Sun, 15 Apr 2007 19:50:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 2511413C480 for ; Sun, 15 Apr 2007 19:50:07 +0000 (UTC) (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 l3FJo67m059086 for ; Sun, 15 Apr 2007 19:50:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l3FJo6v8059084; Sun, 15 Apr 2007 19:50:06 GMT (envelope-from gnats) Date: Sun, 15 Apr 2007 19:50:06 GMT Message-Id: <200704151950.l3FJo6v8059084@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: "[LoN]Kamikaze" Cc: Subject: Re: i386/111591: [Releng_6][i386][acpi_ibm] dev.acpi_ibm.0.events returns I/O error X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "\[LoN\]Kamikaze" List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Apr 2007 19:50:07 -0000 The following reply was made to PR kern/111591; it has been noted by GNATS. From: "[LoN]Kamikaze" To: remko@FreeBSD.org Cc: freebsd-i386@FreeBSD.org, bug-followup@FreeBSD.org Subject: Re: i386/111591: [Releng_6][i386][acpi_ibm] dev.acpi_ibm.0.events returns I/O error Date: Sun, 15 Apr 2007 21:42:12 +0200 Remko Lodder wrote: > [LoN]Kamikaze wrote: >> Remko Lodder wrote: >>> Synopsis: [Releng_6][i386][acpi_ibm] dev.acpi_ibm.0.events returns >>> I/O error >>> >>> State-Changed-From-To: open->closed >>> State-Changed-By: remko >>> State-Changed-When: Sun Apr 15 09:16:55 UTC 2007 >>> State-Changed-Why: duplicate of 111590 >>> >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=111591 >>> >> >> What does a problem with the acpi_ibm module have to do with psm? I >> think those are two distinct problems. Other acpi features that are >> not used through the acpi_ibm module work fine. > > As you might have seen this already had been corrected. > Thanks for the headsup though, > > regards, > remko I cannot seem to find another PR about this. If it has already been corrected, I suppose these corrections didn't make it into stable, yet. From owner-freebsd-acpi@FreeBSD.ORG Sun Apr 15 21:20:06 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4DA9B16A401 for ; Sun, 15 Apr 2007 21:20:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id EE02A13C448 for ; Sun, 15 Apr 2007 21:20:05 +0000 (UTC) (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 l3FLK5oF065893 for ; Sun, 15 Apr 2007 21:20:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l3FLK5Q3065892; Sun, 15 Apr 2007 21:20:05 GMT (envelope-from gnats) Date: Sun, 15 Apr 2007 21:20:05 GMT Message-Id: <200704152120.l3FLK5Q3065892@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: Remko Lodder Cc: Subject: Re: i386/111591: [Releng_6][i386][acpi_ibm] dev.acpi_ibm.0.events returns I/O error X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Remko Lodder List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Apr 2007 21:20:06 -0000 The following reply was made to PR kern/111591; it has been noted by GNATS. From: Remko Lodder To: "[LoN]Kamikaze" Cc: freebsd-i386@FreeBSD.org, bug-followup@FreeBSD.org Subject: Re: i386/111591: [Releng_6][i386][acpi_ibm] dev.acpi_ibm.0.events returns I/O error Date: Sun, 15 Apr 2007 23:12:13 +0200 [LoN]Kamikaze wrote: > Remko Lodder wrote: >> [LoN]Kamikaze wrote: >>> Remko Lodder wrote: >>>> Synopsis: [Releng_6][i386][acpi_ibm] dev.acpi_ibm.0.events returns >>>> I/O error >>>> >>>> State-Changed-From-To: open->closed >>>> State-Changed-By: remko >>>> State-Changed-When: Sun Apr 15 09:16:55 UTC 2007 >>>> State-Changed-Why: duplicate of 111590 >>>> >>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=111591 >>>> >>> What does a problem with the acpi_ibm module have to do with psm? I >>> think those are two distinct problems. Other acpi features that are >>> not used through the acpi_ibm module work fine. >> As you might have seen this already had been corrected. >> Thanks for the headsup though, >> >> regards, >> remko > > I cannot seem to find another PR about this. If it has already been corrected, I suppose these corrections didn't make it into stable, yet. > I ment that the ticket was reopened and assigned to the proper team. -- Kind regards, Remko Lodder ** remko@elvandar.org FreeBSD ** remko@FreeBSD.org /* Quis custodiet ipsos custodes */ From owner-freebsd-acpi@FreeBSD.ORG Mon Apr 16 05:10:07 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A09F216A401 for ; Mon, 16 Apr 2007 05:10:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 7851413C480 for ; Mon, 16 Apr 2007 05:10:07 +0000 (UTC) (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 l3G5A6cA009430 for ; Mon, 16 Apr 2007 05:10:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l3G5A6jO009429; Mon, 16 Apr 2007 05:10:06 GMT (envelope-from gnats) Date: Mon, 16 Apr 2007 05:10:06 GMT Message-Id: <200704160510.l3G5A6jO009429@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: "[LoN]Kamikaze" Cc: Subject: Re: i386/111591: [Releng_6][i386][acpi_ibm] dev.acpi_ibm.0.events returns I/O error X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "\[LoN\]Kamikaze" List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Apr 2007 05:10:07 -0000 The following reply was made to PR kern/111591; it has been noted by GNATS. From: "[LoN]Kamikaze" To: remko@FreeBSD.org Cc: freebsd-i386@FreeBSD.org, bug-followup@FreeBSD.org Subject: Re: i386/111591: [Releng_6][i386][acpi_ibm] dev.acpi_ibm.0.events returns I/O error Date: Mon, 16 Apr 2007 07:03:15 +0200 Remko Lodder wrote: > I ment that the ticket was reopened and assigned to the proper team. Sorry about that, I'm a bit slow, lately. From owner-freebsd-acpi@FreeBSD.ORG Mon Apr 16 10:01:25 2007 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A971416A4DD for ; Mon, 16 Apr 2007 10:01:25 +0000 (UTC) (envelope-from email@welcomeoffice.emv1.net) Received: from emailer99-225.emv1.net (emailer99-225.emv1.net [84.14.99.225]) by mx1.freebsd.org (Postfix) with ESMTP id 4AEBF13C46A for ; Mon, 16 Apr 2007 10:01:25 +0000 (UTC) (envelope-from email@welcomeoffice.emv1.net) Date: Mon, 16 Apr 2007 11:59:49 +0200 (CEST) From: Welcome Office To: "freebsd-acpi@freebsd.org" Message-ID: <4520581167.1096155.1176717589795@sch3.emv2.com> MIME-Version: 1.0 X-EMV-CampagneId: 1096155$ X-EMV-MemberId: 4520581167$ Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Un avertisseur de radar offert avec votre premiere commande ! X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "clientele@welcomeoffice.com" List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Apr 2007 10:01:25 -0000 WELCOME OFFICE n°1 DU DISCOUNT AUX ENTREPRISES Message invisible, cliquez ici Offre réservée à votre société, Un avertisseur de radar INFORAD V2 offert pour toute première commande supérieure à 400¤ HT ! Le 1er avertisseur de radar légal. Préservez les points de votre permis ! Contient : - le récepteur GPS, - le câble de liaison USB, - 1 adaptateur allume cigare 12/24 Volts, - 2 pastilles velcro, - le manuel d'utilisation - Antenne Magnétique Auto Pour bénéficier de cette offre, rien de plus simple : - connectez vous sur notre site http://as1.emv2.com/I?a=A9X7Cqgr_6nA8TCE66L8vEPjpw - dans la section "Ma commande", inscrivez le code suivant : M16KRADP17 ou copiez-collez le lien suivant dans votre navigateur web http://as1.emv2.com/I?a=A9X7Cqgr_6nA8TCE66L8vEDj2A Bonne journée. L'équipe WELCOME OFFICE From owner-freebsd-acpi@FreeBSD.ORG Mon Apr 16 11:08:15 2007 Return-Path: X-Original-To: freebsd-acpi@FreeBSD.org Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7F89116A406 for ; Mon, 16 Apr 2007 11:08:15 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 57B1013C44C for ; Mon, 16 Apr 2007 11:08:15 +0000 (UTC) (envelope-from owner-bugmaster@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 l3GB8FFT042709 for ; Mon, 16 Apr 2007 11:08:15 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l3GB8DWk042693 for freebsd-acpi@FreeBSD.org; Mon, 16 Apr 2007 11:08:13 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 16 Apr 2007 11:08:13 GMT Message-Id: <200704161108.l3GB8DWk042693@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon 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, 16 Apr 2007 11:08:15 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o i386/54756 acpi ACPI suspend/resume problem on CF-W2 laptop o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 o kern/55822 acpi No ACPI power off with SMP kernel o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/64002 acpi acpi problem o i386/67273 acpi [hang] system hangs with acpi and Xfree o i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Armada 1750 o i386/79080 acpi acpi thermal changes freezes HP nx6110 o i386/79081 acpi ACPI suspend/resume not working on HP nx6110 o kern/104625 acpi ACPI on ASUS A8N-32 SLI/ASUS P4P800 does not show ther o kern/106924 acpi ACPI resume returns g_vfs_done() errors and kernel pan 11 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/67309 acpi zzz reboot computer (ACPI S3) o i386/69750 acpi Boot without ACPI failed on ASUS L5 o kern/73823 acpi [feature request] acpi / power-on by timer support o kern/76950 acpi ACPI wrongly blacklisted on Micron ClientPro 766Xi sys f kern/90871 acpi ACPI problems with ASUS A8N-VM-CSM o kern/97383 acpi Volume buttons on IBM Thinkpad crash system with ACPI o i386/97468 acpi [acpi] ACPI on ASUS A7V hangs on shutdown -p (power of o kern/98171 acpi [acpi] ACPI 1304 / 0501 errors on Acer 5024WLMi Laptop o i386/102343 acpi ACPI error o kern/103365 acpi [acpi] acpi poweroff doesn't work with geli device att o kern/108017 acpi [acpi]: Acer Aspire 5600 o kern/108488 acpi ACPI-1304: *** Error: Method execution failed o kern/108581 acpi sysctl: hw.acpi.cpu.cx_lowest: Invalid argument o kern/108695 acpi [ACPI]: Fatal trap 9: general protection fault when in o kern/109207 acpi ACPI Promlem o kern/111591 acpi [acpi] dev.acpi_ibm.0.events returns I/O error (regres 16 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Apr 16 13:25:48 2007 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C0AC216A419 for ; Mon, 16 Apr 2007 13:25:48 +0000 (UTC) (envelope-from tcheek@pixelfish.com) Received: from mail01.vmatrixmail.com (mail01.vmatrixmail.com [216.219.244.230]) by mx1.freebsd.org (Postfix) with ESMTP id 32B9E13C484 for ; Mon, 16 Apr 2007 13:25:48 +0000 (UTC) (envelope-from tcheek@pixelfish.com) Received: (vmatrix@mail01.vmatrixmail.com) by vmatrixmail.com id S6077501AbXDPNZe for ; Mon, 16 Apr 2007 06:25:34 -0700 To: acpi@freebsd.org MIME-Version: 1.0 X-Mailer: Rich Media Mail V4. Vmatrix, (C) 2003 From: "Tammie Cheek" Sender: "Tammie Cheek" Message-Id: Date: Mon, 16 Apr 2007 06:25:34 -0700 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Technology Industry Moves To Video X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tcheek@pixelfish.com List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Apr 2007 13:25:49 -0000 Greetings!

Are you happy with your results from the Southern California Linux Expo 2007? Did you have what it takes to make the difference between creating excitement and blending in with the competition, between lots of hot leads and a few hard sells ... between success and failure?

Did you have video?

Why video? Video vividly demonstrates the features and benefits of your products. Video captures the praises of your most enthusiastic customers. Video instills interest, reaction and trust. Video sells.

In just 45 days, PixelFish creates marketing videos that become an integral part of your marketing and sales efforts when it streams from your Web site, launches from multimedia email newsletters, plays from CD video brochures and loops from a DVD at your tradeshow booth.

We are PixelFish. We deliver “The Evolution of Video”. And we guarantee results. Click on the videos to the right to see samples of our work.

Contact us today for a free evaluation of your video marketing needs.


Tammie Cheek
PixelFish, Inc.
800.503.3020 x7110
tcheek@pixelfish.com
http://www.pixelfish.com
Interim Video
Empire Stat Group Video
Columbia Healthcare Analytics Video
------------------------------------------------ Unsubscribe to safely remove yourself from this email list, please send email to info@pixelfish.com. Powered by Pixelfish http://www.pixelfish.com From owner-freebsd-acpi@FreeBSD.ORG Tue Apr 17 23:45:40 2007 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 778F016A402 for ; Tue, 17 Apr 2007 23:45:40 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.185]) by mx1.freebsd.org (Postfix) with ESMTP id 0C60413C44B for ; Tue, 17 Apr 2007 23:45:39 +0000 (UTC) (envelope-from grafan@gmail.com) Received: by mu-out-0910.google.com with SMTP id g7so2522052muf for ; Tue, 17 Apr 2007 16:45:38 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=PpfQvzcP7onj9BvjSlHL6WLnxHSJQNn4Gwgizh40cMRiHBsUXfeVGMc/tnSrWT6682g0PANaF7PHpR3dH3uw4F+2N1UkyyMnItVucBfAmKYSh26ncqlfqBlvom9Da7qlV90yrO1boWzov8Bf7caH1VWzx54XyPTRSYZ44ofTibo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=jpvIC7uHU65pOp8LQLiYGIv822WFwppqK25BsZDiIwrSGpnNNX3C3ZuujtsrxQx0zz3Z1DX4DJuKg1JZSKIZBE1b+G9cuDyklUHzteY7vIsmRNCyuMJHjDh9FhWu/WpROzsZC4BKZMt7fsDb4PK0PJtyrh24wHJxPH239GvLWP0= Received: by 10.82.120.14 with SMTP id s14mr1212355buc.1176853538023; Tue, 17 Apr 2007 16:45:38 -0700 (PDT) Received: by 10.82.106.12 with HTTP; Tue, 17 Apr 2007 16:45:37 -0700 (PDT) Message-ID: <6eb82e0704171645n5f7b2ca6h41b41016cdafad24@mail.gmail.com> Date: Wed, 18 Apr 2007 07:45:37 +0800 From: "Rong-en Fan" To: acpi@freebsd.org, mobile@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: acpi_ibm(4): new radio kill switch (readonly) sysctl 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, 17 Apr 2007 23:45:40 -0000 As pointed out by Henrik Brix Andersen, I adds a sysctl entry that shows the status of radio kill switch found on some ThinkPad: http://people.freebsd.org/~rafan/acpi_ibm_killswitch.diff dev.acpi_ibm.0.killswitch = 0 means the switch is off. It seems that no acpi event will be generated when the value changes (actually, my x60 does not generate any events when I presses FN+something). Otherwise, we can hook it in devd.conf and remove wireless driver when kill switch is on... Any comments? Regards, Rong-En Fan From owner-freebsd-acpi@FreeBSD.ORG Wed Apr 18 00:05:29 2007 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 660E416A40A for ; Wed, 18 Apr 2007 00:05:29 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id 1C9CE13C459 for ; Wed, 18 Apr 2007 00:02:42 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 77428 invoked from network); 18 Apr 2007 00:02:44 -0000 Received: from ppp-71-139-34-102.dsl.snfc21.pacbell.net (HELO ?10.0.0.235?) (nate-mail@71.139.34.102) by root.org with ESMTPA; 18 Apr 2007 00:02:44 -0000 Message-ID: <4625601C.9000201@root.org> Date: Tue, 17 Apr 2007 17:02:36 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.7 (X11/20061027) MIME-Version: 1.0 To: Rong-en Fan References: <6eb82e0704171645n5f7b2ca6h41b41016cdafad24@mail.gmail.com> In-Reply-To: <6eb82e0704171645n5f7b2ca6h41b41016cdafad24@mail.gmail.com> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, mobile@freebsd.org Subject: Re: acpi_ibm(4): new radio kill switch (readonly) sysctl 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, 18 Apr 2007 00:05:29 -0000 Rong-en Fan wrote: > As pointed out by Henrik Brix Andersen, I adds a sysctl entry > that shows the status of radio kill switch found on some ThinkPad: > > http://people.freebsd.org/~rafan/acpi_ibm_killswitch.diff > > dev.acpi_ibm.0.killswitch = 0 means the switch is off. It seems that > no acpi event will be generated when the value changes (actually, > my x60 does not generate any events when I presses FN+something). > Otherwise, we can hook it in devd.conf and remove wireless driver when > kill switch is on... > > Any comments? Seems fine to me. But as to the name of the sysctl -- it should be more logical. How about renaming it to dev.acpi_ibm.0.radio_enable and when 1, the radio is enabled? Even if you have to invert the logic of the ACPI method, it would make more sense to users. They don't need to know what's going on under the hood. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Apr 18 02:01:28 2007 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B945816A407; Wed, 18 Apr 2007 02:01:28 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 9282613C4BB; Wed, 18 Apr 2007 02:01:28 +0000 (UTC) (envelope-from sam@errno.com) Received: from [10.0.0.178] ([10.0.0.178]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l3I1dkld043645 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 17 Apr 2007 18:39:47 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <462576E7.9000106@errno.com> Date: Tue, 17 Apr 2007 18:39:51 -0700 From: Sam Leffler Organization: Errno Consulting User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) MIME-Version: 1.0 To: Rong-en Fan References: <6eb82e0704171645n5f7b2ca6h41b41016cdafad24@mail.gmail.com> In-Reply-To: <6eb82e0704171645n5f7b2ca6h41b41016cdafad24@mail.gmail.com> X-Enigmail-Version: 0.94.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, mobile@freebsd.org Subject: Re: acpi_ibm(4): new radio kill switch (readonly) sysctl 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, 18 Apr 2007 02:01:28 -0000 Rong-en Fan wrote: > As pointed out by Henrik Brix Andersen, I adds a sysctl entry > that shows the status of radio kill switch found on some ThinkPad: > > http://people.freebsd.org/~rafan/acpi_ibm_killswitch.diff > > dev.acpi_ibm.0.killswitch = 0 means the switch is off. It seems that > no acpi event will be generated when the value changes (actually, > my x60 does not generate any events when I presses FN+something). > Otherwise, we can hook it in devd.conf and remove wireless driver when > kill switch is on... > > Any comments? If the radio is Atheros-based the kill switch likely generates a GPIO interrupt that the ath driver can catch and use to turn the radio on/off. Sam From owner-freebsd-acpi@FreeBSD.ORG Wed Apr 18 02:26:50 2007 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E716C16A400 for ; Wed, 18 Apr 2007 02:26:50 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.freebsd.org (Postfix) with ESMTP id 1C86813C458 for ; Wed, 18 Apr 2007 02:26:49 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: by ug-out-1314.google.com with SMTP id 71so263648ugh for ; Tue, 17 Apr 2007 19:26:48 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=hL/jZLT5g5XZ1USXSCz3K/2ax19javlkS6AHEU/C+fn1YJdknyb2tQYzyBTB1NxsKHQHQnYcol/ObDe8wJfje9lgg9Z6YhJC/+neUKf5a9J1AZKCqjwJTAjQUz3J3OIRsc+g1KqQgjkLYD89c/P3lDiUzlfbH2hIRC2NPomPjnU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=Cn8TNVoSyGKpYF+hqCHWghvyNVN6S9we1DE1o3RxwjxHMh7eD5Ycw/Wdg+B9G+h2utx2TAqSdZsxfUxc/zbDtRiuOjnLzKp4ivfwYJHDUYHPfoylILECy/J6dQDQjyxx+RKGmptr1usjSHeXW4vec1J70aBjSLOPxV8Mub0Af28= Received: by 10.82.113.6 with SMTP id l6mr401buc.1176861659960; Tue, 17 Apr 2007 19:00:59 -0700 (PDT) Received: by 10.82.175.3 with HTTP; Tue, 17 Apr 2007 19:00:59 -0700 (PDT) Message-ID: <539c60b90704171900u1f00ffd7hd77bc58eb573ae8d@mail.gmail.com> Date: Tue, 17 Apr 2007 19:00:59 -0700 From: "Steve Franks" Sender: bahamasfranks@gmail.com To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Google-Sender-Auth: 3978355453c1ec92 Subject: s3 on asus kills ata? 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, 18 Apr 2007 02:26:51 -0000 The only thing 'special' I have on my system is a gmirror, and it appears to be quite unhappy with suspending. I added lines to rc.suspend to umount the partitions, stop the mirror, and kldunload gmirror, but it still freaks, identically as far as I cen tell whether it is enabled or not, so maybe it's really ata that is the problem, not gmirror. Dmesg output follows, and you can see at the end where I try to suspend, right before gmirror gives the 'provider destroyed' message. Interestingly, after following the acpi.hw.disable_on_poweroff="0" from the handbook, s1 appears to work (although the screen stays in the current state instead of sleeping, but the sleep led does flash and the keyboard is inactive until the sleep button is pressed). Also, I don't know if this is universally the case, but you might put a note in the handbook page for newbies - any time I do an acpiconf -s(x) on any of my machines (the asus server or my brand-new cheapo compaq laptop), I have to follow it with the '&' sign, or else I get a "suspend request: not ready yet" error, and the prompt returns with no suspend. I supose it should be obvious that you cannot suspend if the system is interacting with the user, but it wasn't to me initially, as I didn't know the '&' command/modifier existed until reading about shell scripts a bit. Thanks, all, Steve -- Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-RELEASE #0: Wed Jan 31 21:58:00 MST 2007 steve@aire.franks-development.dyndns.biz:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) CPU 2.53GHz (2532.64-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Features2=0x651d> AMD Features=0x20000800 real memory = 1039859712 (991 MB) avail memory = 991412224 (945 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 5.0 (no driver attached) pcib2: at device 25.0 on pci0 pci2: on pcib2 wi0: port 0xdc00-0xdc7f,0xd880-0xd8bf mem 0xdfeffc00-0xdfefffff irq 16 at device 19.0 on pci2 wi0: using Lucent Technologies, WaveLAN/IEEE wi0: Lucent Firmware: Station (8.72.1) wi0: Ethernet address: 00:60:1d:f0:e4:f9 atapci0: port 0xd800-0xd87f,0xd400-0xd4ff mem 0xdfefe000-0xdfefefff,0xdfec0000-0xdfedffff irq 17 at device 20.0 on pci2 ata2: on atapci0 ata3: on atapci0 ata4: on atapci0 ata5: on atapci0 pci0: at device 27.0 (no driver attached) ohci0: mem 0xdfffc000-0xdfffcfff irq 17 at device 28.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xdfffd000-0xdfffdfff irq 18 at device 28.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ohci2: mem 0xdfffe000-0xdfffefff irq 19 at device 28.2 on pci0 ohci2: [GIANT-LOCKED] usb2: OHCI version 1.0, legacy support usb2: SMM does not respond, resetting usb2: on ohci2 usb2: USB revision 1.0 uhub2: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 3 ports with 3 removable, self powered ehci0: mem 0xdffff800-0xdffff8ff irq 23 at device 28.3 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 3 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: AcerLabs EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 8 ports with 8 removable, self powered isab0: at device 30.0 on pci0 isa0: on isab0 pci0: at device 30.1 (no driver attached) atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 31.0 on pci0 ata0: on atapci1 ata1: on atapci1 acpi_button0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A orm0: at iomem 0xc0000-0xcdfff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ums0: Logitech Trackball, rev 1.10/2.20, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. Timecounter "TSC" frequency 2532635296 Hz quality 800 Timecounters tick every 1.000 msec ad0: 157066MB at ata0-master UDMA133 acd0: DVDR at ata1-master UDMA33 ad4: 152627MB at ata2-master SATA150 ad6: 157066MB at ata3-master SATA150 ad8: 157066MB at ata4-master SATA150 GEOM_MIRROR: Device raincloud created (id=748424551). GEOM_MIRROR: Device raincloud: provider ad4 detected. GEOM_MIRROR: Device raincloud: provider ad6 detected. GEOM_MIRROR: Device raincloud: provider ad6 activated. GEOM_MIRROR: Device raincloud: provider ad4 activated. GEOM_MIRROR: Device raincloud: provider mirror/raincloud launched. GEOM_MIRROR: Device rainstone created (id=985601709). GEOM_MIRROR: Device rainstone: provider ad8 detected. ad10: 152627MB at ata5-master SATA150 GEOM_MIRROR: Force device rainstone start due to timeout. GEOM_MIRROR: Device rainstone: provider ad8 activated. GEOM_MIRROR: Device rainstone: provider mirror/rainstone launched. GEOM_MIRROR: Component ad10 (device rainstone) broken, skipping. GEOM_MIRROR: Cannot add disk ad10 to rainstone (error=22). ...... Trying to mount root from ufs:/dev/ad0s1a GEOM_MIRROR: Device raincloud: provider mirror/raincloud destroyed. GEOM_MIRROR: Device raincloud destroyed. GEOM_MIRROR: Device rainstone: provider mirror/rainstone destroyed. GEOM_MIRROR: Device rainstone destroyed. wi0: link state changed to DOWN ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES DISABLE WCACHE taskqueue timeout - completing request directly ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly ad6: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad6: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad6: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad6: WARNING - SETFEATURES DISABLE WCACHE taskqueue timeout - completing request directly ad6: WARNING - SET_MULTI taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES DISABLE WCACHE taskqueue timeout - completing request directly ad8: WARNING - SET_MULTI taskqueue timeout - completing request directly ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad10: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad10: WARNING - SETFEATURES DISABLE WCACHE taskqueue timeout - completing request directly ad10: WARNING - SET_MULTI taskqueue timeout - completing request directly From owner-freebsd-acpi@FreeBSD.ORG Wed Apr 18 03:55:44 2007 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7CEF716A403 for ; Wed, 18 Apr 2007 03:55:44 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by mx1.freebsd.org (Postfix) with ESMTP id EF69B13C45A for ; Wed, 18 Apr 2007 03:55:43 +0000 (UTC) (envelope-from grafan@gmail.com) Received: by ug-out-1314.google.com with SMTP id 71so272957ugh for ; Tue, 17 Apr 2007 20:55:42 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=IST5yD0sLyy0xEKho7UTee6uf8y+fi+UoURql94jIBz7910lXAbQbMwZj6VRMFQXCUVAPhV+8cqEehRW3zfM0AIxTmklqaGHQOYUS/SEdCf75YYNR7FnY7zX+sa0nQiwoO1ylGe43gkJgRXOY5upc93xel9tTqPkCg+wAcv17IY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Zf5QLSOML031dVrgMCNLGDiNP1E+wBCLtkPAY32ldLyCJUduLJ+8vxwNxAMRYRHoRknhQ1YbWaatGLOyOxUaZzTB38uYaQ4g1fGkv8vzFG77Uifi/l4trJcHFpbf8KvUO9L2DW32JnLAF98O3Cz8As3CT5+Xgvtcs0meRkRi+QA= Received: by 10.82.173.19 with SMTP id v19mr45738bue.1176868542713; Tue, 17 Apr 2007 20:55:42 -0700 (PDT) Received: by 10.82.106.12 with HTTP; Tue, 17 Apr 2007 20:55:42 -0700 (PDT) Message-ID: <6eb82e0704172055l5bddca81t5b7e9e45a297a839@mail.gmail.com> Date: Wed, 18 Apr 2007 11:55:42 +0800 From: "Rong-en Fan" To: acpi@freebsd.org, mobile@freebsd.org In-Reply-To: <4625601C.9000201@root.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6eb82e0704171645n5f7b2ca6h41b41016cdafad24@mail.gmail.com> <4625601C.9000201@root.org> Cc: Subject: Re: acpi_ibm(4): new radio kill switch (readonly) sysctl 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, 18 Apr 2007 03:55:44 -0000 On 4/18/07, Nate Lawson wrote: > Rong-en Fan wrote: > > As pointed out by Henrik Brix Andersen, I adds a sysctl entry > > that shows the status of radio kill switch found on some ThinkPad: > > > > http://people.freebsd.org/~rafan/acpi_ibm_killswitch.diff > > > > dev.acpi_ibm.0.killswitch = 0 means the switch is off. It seems that > > no acpi event will be generated when the value changes (actually, > > my x60 does not generate any events when I presses FN+something). > > Otherwise, we can hook it in devd.conf and remove wireless driver when > > kill switch is on... > > > > Any comments? > > Seems fine to me. But as to the name of the sysctl -- it should be more > logical. How about renaming it to dev.acpi_ibm.0.radio_enable and when > 1, the radio is enabled? Even if you have to invert the logic of the > ACPI method, it would make more sense to users. They don't need to know > what's going on under the hood. Good idea. I updated the patch: http://people.freebsd.org/~rafan/acpi_ibm_radio_switch.diff If you have ThinkPad other than X60, please help test this. Thanks, Rong-En Fan > > -- > Nate > From owner-freebsd-acpi@FreeBSD.ORG Wed Apr 18 05:05:22 2007 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8514116A403 for ; Wed, 18 Apr 2007 05:05:22 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id 6AFE113C459 for ; Wed, 18 Apr 2007 05:05:22 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 10075 invoked from network); 18 Apr 2007 05:05:24 -0000 Received: from ppp-71-139-34-102.dsl.snfc21.pacbell.net (HELO ?10.0.0.235?) (nate-mail@71.139.34.102) by root.org with ESMTPA; 18 Apr 2007 05:05:24 -0000 Message-ID: <4625A70C.1000506@root.org> Date: Tue, 17 Apr 2007 22:05:16 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.7 (X11/20061027) MIME-Version: 1.0 To: Rong-en Fan References: <6eb82e0704171645n5f7b2ca6h41b41016cdafad24@mail.gmail.com> <4625601C.9000201@root.org> <6eb82e0704172055l5bddca81t5b7e9e45a297a839@mail.gmail.com> In-Reply-To: <6eb82e0704172055l5bddca81t5b7e9e45a297a839@mail.gmail.com> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, mobile@freebsd.org Subject: Re: acpi_ibm(4): new radio kill switch (readonly) sysctl 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, 18 Apr 2007 05:05:22 -0000 Rong-en Fan wrote: > On 4/18/07, Nate Lawson wrote: >> Rong-en Fan wrote: >> > As pointed out by Henrik Brix Andersen, I adds a sysctl entry >> > that shows the status of radio kill switch found on some ThinkPad: >> > >> > http://people.freebsd.org/~rafan/acpi_ibm_killswitch.diff >> > >> > dev.acpi_ibm.0.killswitch = 0 means the switch is off. It seems that >> > no acpi event will be generated when the value changes (actually, >> > my x60 does not generate any events when I presses FN+something). >> > Otherwise, we can hook it in devd.conf and remove wireless driver when >> > kill switch is on... >> > >> > Any comments? >> >> Seems fine to me. But as to the name of the sysctl -- it should be more >> logical. How about renaming it to dev.acpi_ibm.0.radio_enable and when >> 1, the radio is enabled? Even if you have to invert the logic of the >> ACPI method, it would make more sense to users. They don't need to know >> what's going on under the hood. > > Good idea. I updated the patch: > > http://people.freebsd.org/~rafan/acpi_ibm_radio_switch.diff > > If you have ThinkPad other than X60, please help test this. This code seems suspect: + case ACPI_IBM_METHOD_RADIO_SWITCH: + acpi_GetInteger(sc->handle, IBM_NAME_RADIO_SWITCH_GET, &val); + sc->radio_switch_state = val; + val = (val != 0); + break; The switch state is set to the return value of the AML method. Then if it is 0, val is set to 0 and if it is 1, val is set to 1. Don't you mean to invert val? If so, this should be sufficient: /* Invert the radio kill switch for the user. */ sc->radio_switch_state = !val; -- Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Apr 18 05:27:29 2007 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B419916A404 for ; Wed, 18 Apr 2007 05:27:29 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.freebsd.org (Postfix) with ESMTP id 4B21E13C458 for ; Wed, 18 Apr 2007 05:27:28 +0000 (UTC) (envelope-from grafan@gmail.com) Received: by ug-out-1314.google.com with SMTP id 71so282185ugh for ; Tue, 17 Apr 2007 22:27:28 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=m9cADchyVj9PKiIzDvMeplzCyJqYQNXYdRxJEDyetLHiPtvsz0Yzja0zuxeGnBz1P/EqcbsLgEinCsWgCZLVkoNtRFtmLv1dbCWu5qz6nY4FFdJSd05wigoD4i+vtLzZpN3A7yHxXp8ATw056vGsy4dXYXhryIpEJjqTeIriyDY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FXMQPPPi8YRWdFnsXvZxAJJXU+6PHzH2XJz4KpOJ32emj1TN7vwHa6BWQevX6CurHzvr8sztGOtBzF+XU++L5ln6nb1xC/BrDcP6+ADOeXPTVm3IzzDHW5kmlTAy3WQpHe2ntsr1KT6O3jBK34kr4B5eKS2u0DuCIUNUYNrJ9S8= Received: by 10.82.158.12 with SMTP id g12mr97937bue.1176874047873; Tue, 17 Apr 2007 22:27:27 -0700 (PDT) Received: by 10.82.106.12 with HTTP; Tue, 17 Apr 2007 22:27:27 -0700 (PDT) Message-ID: <6eb82e0704172227y6c62846l24c9aafab299cb9@mail.gmail.com> Date: Wed, 18 Apr 2007 13:27:27 +0800 From: "Rong-en Fan" To: "Nate Lawson" In-Reply-To: <4625A70C.1000506@root.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6eb82e0704171645n5f7b2ca6h41b41016cdafad24@mail.gmail.com> <4625601C.9000201@root.org> <6eb82e0704172055l5bddca81t5b7e9e45a297a839@mail.gmail.com> <4625A70C.1000506@root.org> Cc: acpi@freebsd.org, mobile@freebsd.org Subject: Re: acpi_ibm(4): new radio kill switch (readonly) sysctl 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, 18 Apr 2007 05:27:29 -0000 On 4/18/07, Nate Lawson wrote: > Rong-en Fan wrote: > > On 4/18/07, Nate Lawson wrote: > >> Rong-en Fan wrote: > >> > As pointed out by Henrik Brix Andersen, I adds a sysctl entry > >> > that shows the status of radio kill switch found on some ThinkPad: > >> > > >> > http://people.freebsd.org/~rafan/acpi_ibm_killswitch.diff > >> > > >> > dev.acpi_ibm.0.killswitch = 0 means the switch is off. It seems that > >> > no acpi event will be generated when the value changes (actually, > >> > my x60 does not generate any events when I presses FN+something). > >> > Otherwise, we can hook it in devd.conf and remove wireless driver when > >> > kill switch is on... > >> > > >> > Any comments? > >> > >> Seems fine to me. But as to the name of the sysctl -- it should be more > >> logical. How about renaming it to dev.acpi_ibm.0.radio_enable and when > >> 1, the radio is enabled? Even if you have to invert the logic of the > >> ACPI method, it would make more sense to users. They don't need to know > >> what's going on under the hood. > > > > Good idea. I updated the patch: > > > > http://people.freebsd.org/~rafan/acpi_ibm_radio_switch.diff > > > > If you have ThinkPad other than X60, please help test this. > > This code seems suspect: > > + case ACPI_IBM_METHOD_RADIO_SWITCH: > + acpi_GetInteger(sc->handle, IBM_NAME_RADIO_SWITCH_GET, &val); > + sc->radio_switch_state = val; > + val = (val != 0); > + break; > > The switch state is set to the return value of the AML method. Then if > it is 0, val is set to 0 and if it is 1, val is set to 1. Don't you > mean to invert val? If so, this should be sufficient: > > /* Invert the radio kill switch for the user. */ > sc->radio_switch_state = !val; Sorry, I update the patch. It should be correct now. Should have morning coffee first :-) Regards, Rong-En Fan > > -- > Nate > From owner-freebsd-acpi@FreeBSD.ORG Wed Apr 18 08:36:50 2007 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1DE1816A401; Wed, 18 Apr 2007 08:36:50 +0000 (UTC) (envelope-from henrik@brixandersen.dk) Received: from solow.pil.dk (relay.pil.dk [195.41.47.164]) by mx1.freebsd.org (Postfix) with ESMTP id D374113C448; Wed, 18 Apr 2007 08:36:49 +0000 (UTC) (envelope-from henrik@brixandersen.dk) Received: from tirith.brixandersen.dk (osgiliath.brixandersen.dk [87.53.223.189]) by solow.pil.dk (Postfix) with ESMTP id 262AE1CC0F3; Wed, 18 Apr 2007 10:19:06 +0200 (CEST) Received: by tirith.brixandersen.dk (Postfix, from userid 1001) id B07E3B897; Wed, 18 Apr 2007 10:19:05 +0200 (CEST) Date: Wed, 18 Apr 2007 10:19:05 +0200 From: Henrik Brix Andersen To: Rong-en Fan Message-ID: <20070418081905.GA42058@tirith.brixandersen.dk> References: <6eb82e0704171645n5f7b2ca6h41b41016cdafad24@mail.gmail.com> <4625601C.9000201@root.org> <6eb82e0704172055l5bddca81t5b7e9e45a297a839@mail.gmail.com> <4625A70C.1000506@root.org> <6eb82e0704172227y6c62846l24c9aafab299cb9@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="d6Gm4EdcadzBjdND" Content-Disposition: inline In-Reply-To: <6eb82e0704172227y6c62846l24c9aafab299cb9@mail.gmail.com> X-PGP-Key: http://www.brixandersen.dk/files/HenrikBrixAndersen.asc User-Agent: Mutt/1.5.15 (2007-04-06) Cc: acpi@freebsd.org, mobile@freebsd.org Subject: Re: acpi_ibm(4): new radio kill switch (readonly) sysctl 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, 18 Apr 2007 08:36:50 -0000 --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Wed, Apr 18, 2007 at 01:27:27PM +0800, Rong-en Fan wrote: > Sorry, I update the patch. It should be correct now. > Should have morning coffee first :-) I can confirm that the updated patch works on my X60s. Regards, Brix --=20 Henrik Brix Andersen --d6Gm4EdcadzBjdND Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: GnuPG signed iD8DBQFGJdR5v+Q4flTiePgRAn7+AJ9vA7dmKN5Q8mn2Io8VA6eoBXSF0ACfWDWZ nPHFjuwOtqfeKL81bxDAtHA= =yi6Q -----END PGP SIGNATURE----- --d6Gm4EdcadzBjdND-- From owner-freebsd-acpi@FreeBSD.ORG Wed Apr 18 08:36:50 2007 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2125716A403; Wed, 18 Apr 2007 08:36:50 +0000 (UTC) (envelope-from henrik@brixandersen.dk) Received: from solow.pil.dk (relay.pil.dk [195.41.47.164]) by mx1.freebsd.org (Postfix) with ESMTP id D35B513C43E; Wed, 18 Apr 2007 08:36:49 +0000 (UTC) (envelope-from henrik@brixandersen.dk) Received: from tirith.brixandersen.dk (osgiliath.brixandersen.dk [87.53.223.189]) by solow.pil.dk (Postfix) with ESMTP id 25DE71CC33A; Wed, 18 Apr 2007 10:20:45 +0200 (CEST) Received: by tirith.brixandersen.dk (Postfix, from userid 1001) id D2060B848; Wed, 18 Apr 2007 10:20:44 +0200 (CEST) Date: Wed, 18 Apr 2007 10:20:44 +0200 From: Henrik Brix Andersen To: Sam Leffler Message-ID: <20070418082044.GB42058@tirith.brixandersen.dk> References: <6eb82e0704171645n5f7b2ca6h41b41016cdafad24@mail.gmail.com> <462576E7.9000106@errno.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TakKZr9L6Hm6aLOc" Content-Disposition: inline In-Reply-To: <462576E7.9000106@errno.com> X-PGP-Key: http://www.brixandersen.dk/files/HenrikBrixAndersen.asc User-Agent: Mutt/1.5.15 (2007-04-06) Cc: acpi@freebsd.org, mobile@freebsd.org Subject: Re: acpi_ibm(4): new radio kill switch (readonly) sysctl 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, 18 Apr 2007 08:36:50 -0000 --TakKZr9L6Hm6aLOc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Sam, On Tue, Apr 17, 2007 at 06:39:51PM -0700, Sam Leffler wrote: > If the radio is Atheros-based the kill switch likely generates a GPIO > interrupt that the ath driver can catch and use to turn the radio on/off. In lack of an ACPI event, that would be neat - any hints on how to test if this is the case? Regards, Brix --=20 Henrik Brix Andersen --TakKZr9L6Hm6aLOc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: GnuPG signed iD8DBQFGJdTcv+Q4flTiePgRAiXsAJ9y4x0e+TFYKBp+tFQkFBTkk1gGswCgp15R BE/966k0xpWDBqICnBkfhVo= =Tpso -----END PGP SIGNATURE----- --TakKZr9L6Hm6aLOc-- From owner-freebsd-acpi@FreeBSD.ORG Thu Apr 19 05:23:12 2007 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8F55716A476 for ; Thu, 19 Apr 2007 05:23:12 +0000 (UTC) (envelope-from DFaulkner@bytecraft.com.au) Received: from bcmelmx.bytecraft.au.com (bcmelmx.bytecraft.au.com [203.39.118.2]) by mx1.freebsd.org (Postfix) with ESMTP id AAB0013C4C9 for ; Thu, 19 Apr 2007 05:23:11 +0000 (UTC) (envelope-from DFaulkner@bytecraft.com.au) Received: from svmarshal2.bytecraft.internal (svmarshal2.bytecraft.internal [10.0.0.3]) by bcmelmx.bytecraft.au.com (8.12.11/8.12.11) with ESMTP id l3J4okxK086192 for ; Thu, 19 Apr 2007 14:50:46 +1000 (EST) (envelope-from DFaulkner@bytecraft.com.au) Received: from svmailmel.bytecraft.internal (Not Verified[10.0.0.24]) by svmarshal2.bytecraft.internal with MailMarshal (v6, 1, 4, 441) id ; Thu, 19 Apr 2007 14:50:45 +1000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Thu, 19 Apr 2007 14:50:45 +1000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FreeBSD Install Problem - QUAD CPU Thread-Index: AceCPkpS3rOwDwBCQMSJMdiwpidydg== From: "David Faulkner" To: Subject: FreeBSD Install Problem - QUAD CPU 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: Thu, 19 Apr 2007 05:23:12 -0000 Hi All, Have just signed up to this group to see if someone can help me out. Our server details are as follows. Server: IBM X3850 (88633SM) QUAD CPU: 40K2522 HDD X 6: 40K1051 IBM ServeRAID 8i: 39R8729 We are attempting to install FreeBSD 6.2-RELEASE onto this machine and are running into a problem getting the operating system to work happily with the QUAD CPU arrangement. We seem to be having issues getting the machine to boot with the 4 processors, receiving the following message "panic: madt_probe_cpus_handler: CPU ID 38 Too High" So to bypass this we disabled ACPI on boot. This allowed us to get past the CPU error and continue to boot, however a little ways down the track we noticed things like the ethernet adapater not getting picked up, and the big problem - none of the disks getting recognised - obviously posing a serious install problem!. We have since tried a few things, one of which was removing all but one of the CPU's. If we do this, and boot with ACPI enabled, all is totally fine. All disks are found, and I receive no CPU panic error. So it appears to me that by disabling ACPI in an attempt to bypass the QUAD CPU problem, we are causing another issue behind the scenes. The root of the problem now appears to be, that if we have anything over 1 CPU, directly after the kernel is loaded (when booting from the CD to try and install), we receive the error message "panic: madt_probe_cpus_handler: CPU ID 38 Too High". The moment a second CPU to the machine....it bombs out. Any help is warmly accepted. Cheers Dave --------------------------------------------------------------- The information transmitted in this e-mail is for the exclusive use of the intended addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material.=20 E-mails may not be secure, may contain computer viruses and may be corrupted in transmission. Please carefully check this e-mail (and any attachment) accordingly. No warranties are given and no liability is accepted for any loss or damage caused by such matters. --------------------------------------------------------------- ### This e-mail message has been scanned for Viruses by Bytecraft ### From owner-freebsd-acpi@FreeBSD.ORG Thu Apr 19 06:01:46 2007 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 81C3016A40A for ; Thu, 19 Apr 2007 06:01:46 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id 6A61C13C4BC for ; Thu, 19 Apr 2007 06:01:46 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 61865 invoked from network); 19 Apr 2007 06:01:48 -0000 Received: from ppp-71-139-34-102.dsl.snfc21.pacbell.net (HELO ?10.0.0.235?) (nate-mail@71.139.34.102) by root.org with ESMTPA; 19 Apr 2007 06:01:48 -0000 Message-ID: <462705C4.7050505@root.org> Date: Wed, 18 Apr 2007 23:01:40 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.7 (X11/20061027) MIME-Version: 1.0 To: David Faulkner References: In-Reply-To: X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: FreeBSD Install Problem - QUAD CPU 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: Thu, 19 Apr 2007 06:01:46 -0000 David Faulkner wrote: > Hi All, > > Have just signed up to this group to see if someone can help me out. > > Our server details are as follows. > > Server: IBM X3850 (88633SM) > QUAD CPU: 40K2522 > HDD X 6: 40K1051 > IBM ServeRAID 8i: 39R8729 > > We are attempting to install FreeBSD 6.2-RELEASE onto this machine and > are running into a problem getting the operating system to work happily > with the QUAD CPU arrangement. > > We seem to be having issues getting the machine to boot with the 4 > processors, receiving the following message > > "panic: madt_probe_cpus_handler: CPU ID 38 Too High" > > So to bypass this we disabled ACPI on boot. This allowed us to get past > the CPU error and continue to boot, however a little ways down the track > we noticed things like the ethernet adapater not getting picked up, and > the big problem - none of the disks getting recognised - obviously > posing a serious install problem!. > > We have since tried a few things, one of which was removing all but one > of the CPU's. If we do this, and boot with ACPI enabled, all is totally > fine. All disks are found, and I receive no CPU panic error. > > So it appears to me that by disabling ACPI in an attempt to bypass the > QUAD CPU problem, we are causing another issue behind the scenes. > > The root of the problem now appears to be, that if we have anything over > 1 CPU, directly after the kernel is loaded (when booting from the CD to > try and install), we receive the error message "panic: > madt_probe_cpus_handler: CPU ID 38 Too High". The moment a second CPU to > the machine....it bombs out. > > Any help is warmly accepted. Please post a URL to your ASL please: acpidump -dt | gzip -c9 > x3850.asl.gz -- Nate From owner-freebsd-acpi@FreeBSD.ORG Thu Apr 19 11:08:09 2007 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C0FD916A402 for ; Thu, 19 Apr 2007 11:08:09 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from smtp807.mail.ird.yahoo.com (smtp807.mail.ird.yahoo.com [217.146.188.67]) by mx1.freebsd.org (Postfix) with SMTP id 0E34013C45B for ; Thu, 19 Apr 2007 11:08:08 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: (qmail 59240 invoked from network); 19 Apr 2007 10:41:26 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btinternet.com; h=Received:X-YMail-OSG:From:To:Subject:Date:User-Agent:MIME-Version:Content-Type:Message-Id; b=uFvZTyc4Y71YpgXlsDMd3oK9IXhoe/TDxn5HUoWidlatWwA0eTsVvkksGbKM+3wjMnVZSn0BdjsV+W27/kj7qjw7wVGW5CrmIf03xgq3Dq2lZk04beHGbLYcYSUCW7AUu13BxcuWC3GTJvJy6JqFCO8gwzuw9tn/QClkLvmN4zY= ; Received: from unknown (HELO w2fzz0vc03.aah-go-on.com) (thomas.sparrevohn@btinternet.com@81.156.124.220 with login) by smtp807.mail.ird.yahoo.com with SMTP; 19 Apr 2007 10:41:26 -0000 X-YMail-OSG: FUss86EVM1nXcj3SzIwwcYLXns5qs8noy80pVdOt5Agvu7Q8 From: Thomas Sparrevohn To: freebsd-acpi@freebsd.org Date: Thu, 19 Apr 2007 11:41:23 +0100 User-Agent: KMail/1.9.6 MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_Td0JG50Ab1VSD2I" Message-Id: <200704191141.23799.Thomas.Sparrevohn@btinternet.com> X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Allocations Errors 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: Thu, 19 Apr 2007 11:08:09 -0000 --Boundary-00=_Td0JG50Ab1VSD2I Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi When I boot the system I get the following 3 errors acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, f00000 (3) failed acpi0: reservation of 1000000, 9edbcc00 (3) failed I don't what it means or whether it does any harm - S3 and S1 states does not seem to work when I try with acpiconf -s1 and -s3 but that does not surprise me as "shutdown -p" does not work either --Boundary-00=_Td0JG50Ab1VSD2I-- From owner-freebsd-acpi@FreeBSD.ORG Thu Apr 19 15:46:45 2007 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 72EB916A404 for ; Thu, 19 Apr 2007 15:46:45 +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 8779913C483 for ; Thu, 19 Apr 2007 15:46:44 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l3JFkbCa009009; Thu, 19 Apr 2007 11:46:37 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Thu, 19 Apr 2007 11:24:42 -0400 User-Agent: KMail/1.9.6 References: <462705C4.7050505@root.org> In-Reply-To: <462705C4.7050505@root.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200704191124.42978.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 19 Apr 2007 11:46:37 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/3130/Thu Apr 19 11:31:36 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: David Faulkner Subject: Re: FreeBSD Install Problem - QUAD CPU 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: Thu, 19 Apr 2007 15:46:45 -0000 On Thursday 19 April 2007 02:01:40 am Nate Lawson wrote: > David Faulkner wrote: > > Hi All, > > > > Have just signed up to this group to see if someone can help me out. > > > > Our server details are as follows. > > > > Server: IBM X3850 (88633SM) > > QUAD CPU: 40K2522 > > HDD X 6: 40K1051 > > IBM ServeRAID 8i: 39R8729 > > > > We are attempting to install FreeBSD 6.2-RELEASE onto this machine and > > are running into a problem getting the operating system to work happily > > with the QUAD CPU arrangement. > > > > We seem to be having issues getting the machine to boot with the 4 > > processors, receiving the following message > > > > "panic: madt_probe_cpus_handler: CPU ID 38 Too High" > > > > So to bypass this we disabled ACPI on boot. This allowed us to get past > > the CPU error and continue to boot, however a little ways down the track > > we noticed things like the ethernet adapater not getting picked up, and > > the big problem - none of the disks getting recognised - obviously > > posing a serious install problem!. > > > > We have since tried a few things, one of which was removing all but one > > of the CPU's. If we do this, and boot with ACPI enabled, all is totally > > fine. All disks are found, and I receive no CPU panic error. > > > > So it appears to me that by disabling ACPI in an attempt to bypass the > > QUAD CPU problem, we are causing another issue behind the scenes. > > > > The root of the problem now appears to be, that if we have anything over > > 1 CPU, directly after the kernel is loaded (when booting from the CD to > > try and install), we receive the error message "panic: > > madt_probe_cpus_handler: CPU ID 38 Too High". The moment a second CPU to > > the machine....it bombs out. > > > > Any help is warmly accepted. > > Please post a URL to your ASL please: > acpidump -dt | gzip -c9 > x3850.asl.gz He has a CPU with an APIC ID of 38 apparently. At the top of /sys/i386/acpica/madt.c, try changing NLAPICS (poor name now, should be MAX_LAPIC_ID) to 64 instead of 32. -- John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Thu Apr 19 15:46:45 2007 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8C5E116A406 for ; Thu, 19 Apr 2007 15:46:45 +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 C64B413C4C1 for ; Thu, 19 Apr 2007 15:46:44 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l3JFkbCb009009; Thu, 19 Apr 2007 11:46:39 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Thu, 19 Apr 2007 11:25:26 -0400 User-Agent: KMail/1.9.6 References: <200704191141.23799.Thomas.Sparrevohn@btinternet.com> In-Reply-To: <200704191141.23799.Thomas.Sparrevohn@btinternet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200704191125.26484.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 19 Apr 2007 11:46:40 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/3130/Thu Apr 19 11:31:36 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Subject: Re: Allocations Errors 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: Thu, 19 Apr 2007 15:46:45 -0000 On Thursday 19 April 2007 06:41:23 am Thomas Sparrevohn wrote: > Hi > > When I boot the system I get the following 3 errors > > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, f00000 (3) failed > acpi0: reservation of 1000000, 9edbcc00 (3) failed > > I don't what it means or whether it does any harm - > > S3 and S1 states does not seem to work when I try > with acpiconf -s1 and -s3 but that does not surprise > me as "shutdown -p" does not work either On recent current? Try disabling the 'ram0' device via 'hint.ram.0.disabled=1' -- John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Thu Apr 19 16:12:16 2007 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E4D1716A402 for ; Thu, 19 Apr 2007 16:12:16 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from smtp803.mail.ird.yahoo.com (smtp803.mail.ird.yahoo.com [217.146.188.63]) by mx1.freebsd.org (Postfix) with SMTP id 4076413C448 for ; Thu, 19 Apr 2007 16:12:16 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: (qmail 27694 invoked from network); 19 Apr 2007 16:12:15 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btinternet.com; h=Received:X-YMail-OSG:Reply-To:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language; b=j3snZE6Gf8h5QDYGYyd03tj3r8FKGONdCC15veb5y5ldx/ks5324kbp3MCU5d9dAJvaKascY2jly0R1kGpbpyuZAqn1VnLDLB/mkrj7NDqrmqzrC76O8zEFuC2HDeRSPY8XMPlf9IDpKWbHxuHjPUtjK7Ssf8X/32NXIuud3hv8= ; Received: from unknown (HELO w2fzz0vc03) (thomas.sparrevohn@btinternet.com@81.156.124.220 with login) by smtp803.mail.ird.yahoo.com with SMTP; 19 Apr 2007 16:12:14 -0000 X-YMail-OSG: o9PzkW0VM1ljcekT3ScVPE9SWoboJlGOfK4udX3ZFvtunwTw85Jnbp5hrfHUXyo2cJhP8EZ9kg-- From: "Thomas Sparrevohn" To: "'John Baldwin'" , References: <200704191141.23799.Thomas.Sparrevohn@btinternet.com> <200704191125.26484.jhb@freebsd.org> In-Reply-To: <200704191125.26484.jhb@freebsd.org> Date: Thu, 19 Apr 2007 17:12:12 +0100 Message-ID: <007d01c7829d$7e2615d0$7a724170$@Sparrevohn@btinternet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AceCme2GKq+0duEpR7WP1zN9/vv3fwAA4CgQ Content-Language: en-gb Cc: Subject: RE: Allocations Errors X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Thomas.Sparrevohn@btinternet.com List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Apr 2007 16:12:17 -0000 On current - Cvsup today - I try > -----Original Message----- > From: John Baldwin [mailto:jhb@freebsd.org] > Sent: 19 April 2007 16:25 > To: freebsd-acpi@freebsd.org > Cc: Thomas Sparrevohn > Subject: Re: Allocations Errors > > On Thursday 19 April 2007 06:41:23 am Thomas Sparrevohn wrote: > > Hi > > > > When I boot the system I get the following 3 errors > > > > acpi0: on motherboard > > acpi0: [ITHREAD] > > acpi0: Power Button (fixed) > > acpi0: reservation of 0, a0000 (3) failed > > acpi0: reservation of 100000, f00000 (3) failed > > acpi0: reservation of 1000000, 9edbcc00 (3) failed > > > > I don't what it means or whether it does any harm - > > > > S3 and S1 states does not seem to work when I try > > with acpiconf -s1 and -s3 but that does not surprise > > me as "shutdown -p" does not work either > > On recent current? Try disabling the 'ram0' device > via 'hint.ram.0.disabled=1' > > -- > John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Fri Apr 20 14:09:08 2007 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5F5CF16A404 for ; Fri, 20 Apr 2007 14:09:08 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from smtp814.mail.ird.yahoo.com (smtp814.mail.ird.yahoo.com [217.146.188.74]) by mx1.freebsd.org (Postfix) with SMTP id C82F913C44B for ; Fri, 20 Apr 2007 14:09:07 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: (qmail 98918 invoked from network); 20 Apr 2007 14:09:06 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btinternet.com; h=Received:X-YMail-OSG:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id; b=uMJ8IS8qbG0JqiK99ldnq0Zidi3lHMhitk4U0nPUgVVpUV+60bEKLgHyN3Zg6/O2uh4J7TrSj+JZWttTgrbPoMmNGFLZdwLQHl5dViWUAFonwdD05yB6G33+yk9I7c5HpMJLurZ5gnyMyUXleKH+VmW4DfuFCY5Q27BXcofMGFI= ; Received: from unknown (HELO w2fzz0vc03.aah-go-on.com) (thomas.sparrevohn@btinternet.com@81.156.124.220 with login) by smtp814.mail.ird.yahoo.com with SMTP; 20 Apr 2007 14:09:06 -0000 X-YMail-OSG: 0eL.5boVM1mQBTKVBiozy2he_OxUECwa2jc9p5K8m.JPumz8eycmpD5cYv.4u02LS0ulU8MzdQ-- From: Thomas Sparrevohn To: freebsd-acpi@freebsd.org Date: Fri, 20 Apr 2007 15:09:03 +0100 User-Agent: KMail/1.9.6 References: <200704191141.23799.Thomas.Sparrevohn@btinternet.com> <200704191125.26484.jhb@freebsd.org> <007d01c7829d$7e2615d0$7a724170$@Sparrevohn@btinternet.com> In-Reply-To: <007d01c7829d$7e2615d0$7a724170$@Sparrevohn@btinternet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200704201509.04361.Thomas.Sparrevohn@btinternet.com> Cc: Subject: Re: Allocations Errors 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, 20 Apr 2007 14:09:08 -0000 On Thursday 19 April 2007 17:12:12 Thomas Sparrevohn wrote: > On current - Cvsup today - I try > > > > On recent current? Try disabling the 'ram0' device > > via 'hint.ram.0.disabled=1' > > After a more systematic testing it looks like Disabling nvidia.ko is a prereq for anthing to work - Its a well know problem All tests was conducted with setting hw.acpi.osname="Windows 2001" S1 State Testing S1 state - S1 state seems to work apart from the video card not turning off when the system enters S1 state pressing the "wakeup/power combined" button brings the system back to life but it blanks out the monitor Visual identification on the power/sleep button shows S1 - e.g Blinks faster than S3 Halting the system with S5 actually shuts off the system Tested with hw.acpi.reset_video but it did no make any difference S3 State Testing S3 state - System enters S3 state with no other logged messages than Apr 20 13:48:22 w2fzz0vc03 kernel: ACPI set debug layer 'ACPI_ALL_COMPONENTS ACP I_ALL_DRIVERS' level 'ACPI_LV_VERBOSE' Apr 20 13:50:00 w2fzz0vc03 acpi: suspend at 20070420 13:50:00 Pressing the power/wakeup button reboots the system with no additional log messages I single short depression of the power button immediate initiates S5 state rather than S3 no matter how short the depression is Visual indicators shows S3 state "slow" blink S3 state leaves the disks in dirty state S5 State acpiconf -s 5 initiates shutdown but never actually powerdown the system - however mostly after a S1 state it does enter S5 state Does anybody have any other suggestions for what to do now? From owner-freebsd-acpi@FreeBSD.ORG Sat Apr 21 10:57:13 2007 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6BF6116A400 for ; Sat, 21 Apr 2007 10:57:13 +0000 (UTC) (envelope-from dikshie@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.239]) by mx1.freebsd.org (Postfix) with ESMTP id 309C013C43E for ; Sat, 21 Apr 2007 10:57:13 +0000 (UTC) (envelope-from dikshie@gmail.com) Received: by nz-out-0506.google.com with SMTP id r28so961066nza for ; Sat, 21 Apr 2007 03:57:12 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=pFYcoTCpR2AXY89OfhaKqsoI7m2/abaWxcUicsVdo6IoEv5VZ3p7SduuKglC8lwdoIu5rXjIEIpGPaSaRFcnwE6yFPFR9ZqZ2Z3aEb7z9sTw7+kz0dGzOxUY9F6huVypZsPlUPExlfoLaM1TZ0v7qpQN0gaBeKsNguoDPZ99dvQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=EUcUXem+H6hKaJBcEbVng6de3+OydlxO2NbQUK4SMfsjPSxWrutoK2poOR5E0OEGH6QiAvJSSmbdeWOIXBEsT+w+2zRSQzvkEB5fRGpSD2FhjYywu2PhEP7C3IRMv3l7OyQ01sgOb0zu/HS9Uz/HQTeE3Y8EOilE/5RVRpsd1P8= Received: by 10.65.239.14 with SMTP id q14mr7781922qbr.1177151427746; Sat, 21 Apr 2007 03:30:27 -0700 (PDT) Received: by 10.65.59.3 with HTTP; Sat, 21 Apr 2007 03:30:27 -0700 (PDT) Message-ID: <910e60e80704210330m5c6dd076ub4d06caef5f998c@mail.gmail.com> Date: Sat, 21 Apr 2007 19:30:27 +0900 From: dikshie To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: acpi problem 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, 21 Apr 2007 10:57:13 -0000 Hi, I got following panic message related to ACPI on -CURRENT: http://www.sfc.wide.ad.jp/~dikshie/panic/panic.jpg kernel built on April 21, 15:09:18 JST regards, -- -dikshie- From owner-freebsd-acpi@FreeBSD.ORG Sat Apr 21 13:59:35 2007 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A8BF816A404 for ; Sat, 21 Apr 2007 13:59:35 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id 7B71613C468 for ; Sat, 21 Apr 2007 13:59:35 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 13605 invoked from network); 21 Apr 2007 13:59:35 -0000 Received: from ppp-71-139-34-102.dsl.snfc21.pacbell.net (HELO ?10.0.0.235?) (nate-mail@71.139.34.102) by root.org with ESMTPA; 21 Apr 2007 13:59:35 -0000 Message-ID: <462A18C1.8020400@root.org> Date: Sat, 21 Apr 2007 06:59:29 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.7 (X11/20061027) MIME-Version: 1.0 To: dikshie References: <910e60e80704210330m5c6dd076ub4d06caef5f998c@mail.gmail.com> In-Reply-To: <910e60e80704210330m5c6dd076ub4d06caef5f998c@mail.gmail.com> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: acpi problem 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, 21 Apr 2007 13:59:35 -0000 dikshie wrote: > Hi, > I got following panic message related to ACPI on -CURRENT: > http://www.sfc.wide.ad.jp/~dikshie/panic/panic.jpg > kernel built on April 21, 15:09:18 JST > > regards, This problem is known and can be avoided by disabling WITNESS until it's fixed. -- Nate