From owner-freebsd-bugs@FreeBSD.ORG Sat Mar 12 01:50:08 2005 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D803C16A4CE for ; Sat, 12 Mar 2005 01:50:08 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48E7443D2D for ; Sat, 12 Mar 2005 01:50:08 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j2C1o8b9072257 for ; Sat, 12 Mar 2005 01:50:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j2C1o8ks072255; Sat, 12 Mar 2005 01:50:08 GMT (envelope-from gnats) Date: Sat, 12 Mar 2005 01:50:08 GMT Message-Id: <200503120150.j2C1o8ks072255@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: rjohns44@comcast.net Subject: Re: kern/77805: Boot hangs with ACPI enabled X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: rjohns44@comcast.net List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Mar 2005 01:50:09 -0000 The following reply was made to PR kern/77805; it has been noted by GNATS. From: rjohns44@comcast.net To: freebsd-gnats-submit@FreeBSD.org, rjohns44@comcast.net, freebsd-acpi@freebsd.org, kris@obsecurity.org Cc: Subject: Re: kern/77805: Boot hangs with ACPI enabled Date: Sat, 12 Mar 2005 01:45:32 +0000 --NextPart_Webmail_9m3u9jl4l_22141_1110591932_0 Content-Type: text/plain Content-Transfer-Encoding: 8bit Per the handbook, tried adding the following statement to /boot/loader.conf: debug.acpi.disabled=cpu This removed the "boot-hangs-during-startup" issue, but does point to a bug in the cpu portion of the ACPI. It seems to be have been overlooked in the correspondence on this issue, but this DID NOT OCCUR in 5.0-Release, 5.1-Release, 5.2-Release, 5.2.1-Release, 5.3-Release. It only happened when I upgraded to 5.3-Stable around 2/18/2005. On Sat, 2005-02-26 at 19:05 -0800, Nate Lawson wrote: > Ron Johnson wrote: > > Any help would be appreciated! dmesg output and ASL are in the bug > > report. > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=77805 > > > > With ACPI enabled, boot fails at "hw.acpi.cpu.cx_lowest: C1 -> C3". This > > statement is not in sysctl.conf or loader.conf and appears to be changed > > automatically. No issue in all previous 5.X versions. 5.3-STABLE > > downloaded from CVS on 2/19/2005 around 3pm EST. > > You want to change the performance/economy settings in rc.conf. Man 5 > rc.conf > > The defaults were changed between 5.2.1 and 5.3: > > src/etc/defaults/rc.conf:revision 1.206 > date: 2004/05/29 04:52:37; author: njl; state: Exp; lines: +1 -1 > Throw the switch and enable use of the lowest idle states while online in > addition to offline. This can be overridden in /etc/rc.conf if it causes > trouble although this has been stable since 2003/12. > > I have no idea why C3 is unstable on your machine. Please try > overriding this with something like this and see if it helps: > > performance_cx_state=HIGH > economy_cx_state=HIGH > It didn't help. Still hangs at the same point. It did output new error messages below. Feb 27 18:08:13 armada kernel: ACPI-0361: *** Error: Thread 29 cannot release Mutex [MUT0] acquired by thread 8 Feb 27 18:08:13 armada kernel: ACPI-1304: *** Error: Method execution failed [\_SB_.PCI0.PIB_.EC0_.SMRD] (Node 0xc14653e0), AE_AML_NOT_OWNER Feb 27 18:08:13 armada kernel: ACPI-1304: *** Error: Method execution failed [\_SB_.BAT1.UPBI] (Node 0xc13ab2c0), AE_AML_NOT_OWNER Feb 27 18:08:13 armada kernel: ACPI-1304: *** Error: Method execution failed [\_SB_.BAT1.SEBI] (Node 0xc13ab200), AE_AML_NOT_OWNER Feb 27 18:08:13 armada kernel: ACPI-1304: *** Error: Method execution failed [\_TZ_.THRM._TMP] (Node 0xc13ab8a0), AE_AML_NOT_OWNER Feb 27 18:08:13 armada kernel: acpi: suspend request ignored (not ready yet) Feb 27 18:08:16 armada last message repeated 5 times Feb 27 18:08:16 armada syslogd: exiting on signal 15 This does seem similar to the "Laptop and ACPI" thread http://lists.freebsd.org/pipermail/freebsd-acpi/2005-March/001325.html. Although my clock speed is reported correctly without ACPI. --NextPart_Webmail_9m3u9jl4l_22141_1110591932_0 Content-Type: text/html Content-Transfer-Encoding: 8bit
Per the handbook, tried adding the following statement to /boot/loader.conf:
debug.acpi.disabled=cpu
 
This removed the "boot-hangs-during-startup" issue, but does point to a bug in the cpu portion of the ACPI. It seems to be have been overlooked in the correspondence on this issue, but this DID NOT OCCUR in 5.0-Release, 5.1-Release, 5.2-Release, 5.2.1-Release, 5.3-Release. It only happened when I upgraded to 5.3-Stable around 2/18/2005.
 
On Sat, 2005-02-26 at 19:05 -0800, Nate Lawson wrote:

> Ron Johnson wrote:
> > Any help would be appreciated! dmesg output and ASL are in the bug
> > report.
> >
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=77805
> >
> > With ACPI enabled, boot fails at "hw.acpi.cpu.cx_lowest: C1 -> C3". This
> > statement is not in sysctl.conf or loader.conf and appears to be changed
> > automatically. No issue in all previous 5.X versions. 5.3-STABLE
> > downloaded from CVS on 2/19/2005 around 3pm EST.
>
> You want to change the performance/economy settings in rc.conf.  Man 5
> rc.conf
>
> The defaults were changed between 5.2.1 and 5.3:
>
> src/etc/defaults/rc.c on f:revision 1.206
> date: 2004/05/29 04:52:37;  author: njl;  state: Exp;  lines: +1 -1
> Throw the switch and enable use of the lowest idle states while online in
> addition to offline.  This can be overridden in /etc/rc.conf if it causes
> trouble although this has been stable since 2003/12.
>
> I have no idea why C3 is unstable on your machine.  Please try
> overriding this with somethin g like this and see if it helps:
>
> performance_cx_state=HIGH
> economy_cx_state=HIGH
>

It didn't help. Still hangs at the same point. It did output new error
messages below.

Feb 27 18:08:13 armada kernel: ACPI-0361: *** Error: Thread 29 cannot
release Mutex [MUT0] acquired by thread 8
Feb 27 18:08:13 armada kernel: ACPI-1304: *** Error: Method execution
failed [\_SB_.PCI0.PIB_.EC0_.SMRD] (N ode 0xc14653e0), AE_AML_NOT_OWNER
Feb 27 18:08:13 armada kernel: ACPI-1304: *** Error: Method execution
failed [\_SB_.BAT1.UPBI] (Node 0xc13ab2c0), AE_AML_NOT_OWNER
Feb 27 18:08:13 armada kernel: ACPI-1304: *** Error: Method execution
failed [\_SB_.BAT1.SEBI] (Node 0xc13ab200), AE_AML_NOT_OWNER
Feb 27 18:08:13 armada kernel: ACPI-1304: *** Error: Method execution
failed [\_TZ_.THRM._TMP] (Node 0xc13ab8a0), AE_AML_NOT_OWNER
Feb 27 18:08:13 armada kernel: acpi: suspend request ignored ( not ready
yet)
Feb 27 18:08:16 armada last message repeated 5 times
Feb 27 18:08:16 armada syslogd: exiting on signal 15

This does seem similar to the "Laptop and ACPI" thread
http://lists.freebsd.org/pipermail/freebsd-acpi/2005-March/001325.html.
Although my clock speed is reported correctly without ACPI.
--NextPart_Webmail_9m3u9jl4l_22141_1110591932_0--