Date: Sat, 24 Nov 2001 14:35:13 +0900 From: Takanori Watanabe <takawata@shidahara1.planet.sci.kobe-u.ac.jp> To: Andy Sparrow <spadger@best.com> Cc: acpi-jp@jp.freebsd.org, hackers@freebsd.org Subject: Re: ACPI causes immediate reboot? Message-ID: <200111240535.OAA81688@shidahara1.planet.sci.kobe-u.ac.jp> In-Reply-To: Your message of "Fri, 23 Nov 2001 21:11:09 PST." <20011124051109.593EE3E31@CRWdog.demon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20011124051109.593EE3E31@CRWdog.demon.co.uk>, Andy Sparrow wrote:
>
>Hi.
>
>Using ACPI in -CURRENT from yesterday causes an (almost) immediate reboot on
>an HP Omnibook 6100. Here's the longest dmesg I've seen from this:
>
>Copyright (c) 1992-2001 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 5.0-CURRENT #1: Sat Nov 24 18:38:34 PST 2001
> root@tureg.geek4food.org:/home/Current/src/sys/i386/compile/test
>Preloaded elf kernel "/boot/kernel/kernel" at 0xc04a0000.
>Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04a00b4.
>Calibrating clock(s) ... TSC clock: 1129541023 Hz, i8254 clock: 1193151 Hz
>CLK_USE_I8254_CALIBRATION not specified - using default frequency
>Timecounter "i8254" frequency 1193182 Hz
>CLK_USE_TSC_CALIBRATION not specified - using old calibration method
>Timecounter "TSC" frequency 1129577046 Hz
>CPU: Pentium III/Pentium III Xeon/Celeron (1129.58-MHz 686-class CPU)
> Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1
> Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,
>P
>AT,PSE36,MMX,FXSR,SSE>
>real memory = 267780096 (261504K bytes)
>Physical memory chunk(s):
>0x00001000 - 0x0009efff, 647168 bytes (158 pages)
>0x004c7000 - 0x0ff57fff, 262737920 bytes (64145 pages)
>avail memory = 255885312 (249888K bytes)
>bios32: Found BIOS32 Service Directtwork setup:
>pcibios: PCI BIOS ICAST> mtu 16384
>pnpbios: Entry = f0000:a2e4 Rev = 1.0
>pnpbios: Event flag at 4b4
>Other BIOS signatures found:
>null: <null device, zero device>
>random: <entropy source>
>mem: <118>Routing daemons:
>pci_open(1): modogd
>pci_cfgchecknal network daemons:
Hmmm, then try making acpi module with
% make -DACPI_DEBUG
then
set
debug.acpi.debugger=init
and
debug.acpi.debugger=table
in kernel loader and see it reaches to the debugger.
If it reaches both point, add Debugger("ACPI"); to applopliate point, like
acpi_identify, acpi_probe, acpi_attach .
If you like, please send me DSDT dump and ASL produ with acpidump.
>Using 'unset acpi_load' or disabling ACPI in device.hints & then later kldload
>ing ACPI gives these messages:
>
>Bold:
>
>acpi_alloc_wakeup_handler: unable to allocate wake memory
>module_register_init: MOD_LOAD (nexus/acpi, c01eb598, 0xc17bcafc) error 1
>pccbb0: <TI1420 PCI-CardBus Bridge> at device 5.0 on pci2
>pccbb0: Could not map register memory
>device_probe_and_attach: pccbb0 attach returned 12
>pccbb0: <TI1420 PCI-CardBus Bridge> at device 5.1 on pci2
>pccbb0: Could not map register memory
>device_probe_and_attach: pccbb0 attach returned 12
>
>Dim:
>
>Nov 24 19:40:48 tureg /boot/kernel/kernel: acpi_alloc_wakeup_handler: unable t
>o allocate wake memory
>Nov 24 19:40:48 tureg /boot/kernel/kernel: module_register_init: MOD_LOAD (nex
>us/acpi, c01eb598, 0xc17bcafc) error 1
>Nov 24 19:40:48 tureg /boot/kernel/kernel: pccbb0: <TI1420 PCI-CardBus Bridge>
> at device 5.0 on pci2
>Nov 24 19:40:48 tureg /boot/kernel/kernel: pccbb0: Could not map register memo
>ry
>Nov 24 19:40:48 tureg /boot/kernel/kernel: device_probe_and_attach: pccbb0 att
>ach returned 12
Don't load acpi module via kldload(8). ACPI requires early boottime
initialization and device tree recognition will be deplicated.
ACPI module is intended to load by kernel loader. This will make
it easier to switch acpi mode kernel and regacy mode.
Takanori Watanabe
<a href="http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html">;
Public Key</a>
Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200111240535.OAA81688>