From owner-acpi-jp@jp.freebsd.org  Fri Nov 23 15:12:32 2001
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id PAA53916;
	Fri, 23 Nov 2001 15:12:32 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from tasogare.imasy.or.jp (root@tasogare.imasy.or.jp [202.227.24.5])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id PAA53911
	for <acpi-jp@jp.freebsd.org>; Fri, 23 Nov 2001 15:12:31 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92])
	(authenticated as iwa with CRAM-MD5)
	by tasogare.imasy.or.jp (8.11.6+3.4W/8.11.6/tasogare) with ESMTP/inet id fAN6CLW11741;
	Fri, 23 Nov 2001 15:12:22 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Date: Fri, 23 Nov 2001 15:12:07 +0900 (JST)
Message-Id: <20011123.151207.122623421.iwasaki@jp.FreeBSD.org>
To: acpi-jp@jp.freebsd.org, coolvibe@hackerheaven.org
From: Mitsuru IWASAKI <iwasaki@jp.freebsd.org>
In-Reply-To: <20011122195603.B17439@laptop.hackerheaven.org>
References: <20011122175136.A17300@laptop.hackerheaven.org>
	<20011123.021832.41628466.iwasaki@jp.FreeBSD.org>
	<20011122195603.B17439@laptop.hackerheaven.org>
X-Mailer: Mew version 2.0 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+010328
X-Sequence: acpi-jp 1491
Subject: [acpi-jp 1491] Re: Weird hang on boot with Compaq Presario
 17XL380 (acpidump included)
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: iwasaki@jp.freebsd.org

Hi,

> > OK, could you get dmesg output in single user mode?
> 
> I managed to get it to boot by using debug.acpi.disable="children" and
> debug.acpi.disable="bus", but that's just as effective as disabling all
> of it together. I tried every subsystem (lid, button, cpu, isa, pci,
> sysresources, ec, thermal) without resorting to disabling bus or
> children, which did not work.

I see.  I added disabling code into acpi_cmbat.c as well, so could you try
it too?

> My dmesg is attached to this mail after booting up with "children"
> disabled. Hope that helps.

Thanks.  There probably are some bugs in ACPI BIOS or ACPI code.
I've made the patch to stop at the end of acpi_cpu_init_throttling()
to review resource setting for devices in console (DDB required).
Could you compare driver's resources in w/ ACPI and w/o?
Any differences?

Thanks

Index: acpi_cpu.c
===================================================================
RCS file: /home/ncvs/src/sys/dev/acpica/acpi_cpu.c,v
retrieving revision 1.8
diff -u -r1.8 acpi_cpu.c
--- acpi_cpu.c	18 Nov 2001 18:12:07 -0000	1.8
+++ acpi_cpu.c	23 Nov 2001 06:01:34 -0000
@@ -293,6 +293,7 @@
     
     printf("acpi_cpu: CPU throttling enabled, %d steps from 100%% to %d.%d%%\n", 
 	   CPU_MAX_SPEED, CPU_SPEED_PRINTABLE(1));
+Debugger(__func__);
 }
 
 /*

