From owner-acpi-jp@jp.freebsd.org  Sat Nov 24 10:49:16 2001
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id KAA13817;
	Sat, 24 Nov 2001 10:49:16 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from router.hackerheaven.org (qn-213-73-194-201.quicknet.nl [213.73.194.201])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id KAA13811;
	Sat, 24 Nov 2001 10:49:13 +0900 (JST)
	(envelope-from coolvibe@hackerheaven.dyndns.org)
Received: by router.hackerheaven.org (Postfix, from userid 1000)
	id 94C4A1CAA; Sat, 24 Nov 2001 02:48:56 +0100 (CET)
Date: Sat, 24 Nov 2001 02:48:56 +0100
From: Emiel Kollof <coolvibe@hackerheaven.org>
To: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
Cc: acpi-jp@jp.freebsd.org
Message-ID: <20011124024856.A24976@laptop.hackerheaven.org>
References: <20011122175136.A17300@laptop.hackerheaven.org> <20011123.021832.41628466.iwasaki@jp.FreeBSD.org> <20011122195603.B17439@laptop.hackerheaven.org> <20011123.151207.122623421.iwasaki@jp.FreeBSD.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20011123.151207.122623421.iwasaki@jp.FreeBSD.org>
User-Agent: Mutt/1.3.23i
X-Mailer: Mutt 1.3.23i (2001-10-09)
X-Editor: Vim http://www.vim.org/
X-Info: http://www.hackerheaven.org/
X-Info2: http://www.cmdline.org/
X-Info3: http://www.coolvibe.org/
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+010328
X-Sequence: acpi-jp 1496
Subject: [acpi-jp 1496] 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: coolvibe@hackerheaven.org

* Mitsuru IWASAKI (iwasaki@jp.FreeBSD.org) wrote:
> 
> I see.  I added disabling code into acpi_cmbat.c as well, so could you try
> it too?

Didn't come around to it yet, but I'll review and test it.

> 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?

I applied the patch, and it does indeed break into the kernel debugger.
Only, what commands should I enter in there to get the info you want?
Second problem is that this machine has no usable serial line to hook
a serial console into, so I'd have to copy everything by hand (urgh)

But on a more hopeful note, ScrlLock works in the debugger, and I
managed to scroll up to the ACPI initialisation as it boots. Maybe this
will shed more light on it: (NOTE, copied by hand)

acpi0: <PTLTD    RSDT  > on motherboard
Timecounter "ACPI" frequency 3579545 Hz
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
acpi_cpu0: <CPU> on acpi0
acpi_tz0: <thermal zone> on acpi0
acpi_acad0: <AC adapter> on acpi0
acpi_cmbat0: <Control method Battery> on acpi0
acpi_lid0: <Control Method Lid Switch> on acpi0
acpi_button0: <Power Button> on acpi0
acpi_button1: <Sleep Button> on acpi0
acpi_pcib0: <Host-PCI bridge> port 0xcf8-0xcff,0x22 on acpi0
pci0: <PCI bus> on acpi_pcib0
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1

and a stack trace from the debugger:

Debugger("acpi_cpu_init_throttling")
Stopped at      Debugger+0x44: pushl  %ebx
db> trace
Debugger(c057fea2,c057fe60,8,c,5) at Debugger+0x44
acpi_cpu_init_throttling(0,c11494c0,c0583500,1,c11494c0) at acpi_cpu_init_throttling+0x12f
AcpiOSExecuteQueue(c11494c0,1,c0b3da9c,0,c03ca040) at AcpiOsExecuteQueue+0x1c
taskquere_run(c0b3da80,c811dd18,c024b44e,0,c7cfb900) at taskqueue_run+0x6c
taskquere_swi_run(0) at taskqueue_swi_run+0xe
ithread_loop(c0b3da00,c811dd48,c0b3da00,c024b324,0) at ithread_loop+0x12a
fork_exit(c024b324,c0b3da00,c811dd48) at fork_ext+0x58
fork_trampoline() at fork_trampoline+0x8
db>

Hope this helps some more.

Cheers,
Emiel
-- 
Epperson's law:
	When a man says it's a silly, childish game, it's probably
something his wife can beat him at.
