From owner-freebsd-current@FreeBSD.ORG Fri Dec 12 00:50:38 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4D0116A4CE for ; Fri, 12 Dec 2003 00:50:38 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FDBD43D5D for ; Fri, 12 Dec 2003 00:50:05 -0800 (PST) (envelope-from gwk@rahn-koltermann.de) Received: from [212.227.126.202] (helo=mrvnet.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1AUizq-0006n4-00; Fri, 12 Dec 2003 09:50:02 +0100 Received: from [172.23.4.143] (helo=config16.kundenserver.de) by mrvnet.kundenserver.de with esmtp (Exim 3.35 #1) id 1AUizq-0007ZP-00; Fri, 12 Dec 2003 09:50:02 +0100 Received: from www-data by config16.kundenserver.de with local (Exim 3.35 #1 (Debian)) id 1AUizp-00069i-00; Fri, 12 Dec 2003 09:50:01 +0100 To: =?iso-8859-1?Q?Nate_Lawson?= From: Message-Id: <27942123$10712179493fd97d1d12a418.73468379@config16.schlund.de> X-Binford: 6100 (more power) X-Originating-From: 27942123 X-Mailer: Webmail X-Routing: DE X-Received: from config16 by 213.148.149.130 with HTTP id 27942123 for nate@root.org; Fri, 12 Dec 2003 09:48:01 +0100 Content-Type: text/plain; charset="iso-8859-1" Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Priority: 3 Date: Fri, 12 Dec 2003 09:48:01 +0100 X-Provags-ID: kundenserver.de abuse@kundenserver.de ident:@172.23.4.143 cc: freebsd-current@freebsd.org cc: acpi-jp@jp.FreeBSD.org cc: =?iso-8859-1?Q? Georg-W=2E_Koltermann ?= Subject: Re: Re: [acpi-jp 2879] 5.1R: page fault from AcpiNsMapHandleToNode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 08:50:39 -0000 Nate Lawson schrieb am 12.12.2003, 02:15:30: > There are different ways of turning on the fan. acpi_thermal switches > them on based on the _ACx objects, which is what caused the panic. So the > fan being turned on by the BIOS or through some other mechanism won't > trigger the fault. We can also lower the value at which acpi_thermal does > the switch or just manually turn it on. Output from sysctl hw.acpi would > help. hw.acpi.supported_sleep_state: S3 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: S1 hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 0 hw.acpi.s4bios: 1 hw.acpi.verbose: 0 hw.acpi.disable_on_poweroff: 1 hw.acpi.cpu.max_speed: 8 hw.acpi.cpu.current_speed: 8 hw.acpi.cpu.performance_speed: 8 hw.acpi.cpu.economy_speed: 4 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 30 hw.acpi.thermal.tz0.temperature: 3062 hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 3642 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3662 hw.acpi.thermal.tz0._ACx: 3512 3452 3402 3282 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz1.temperature: 3032 hw.acpi.thermal.tz1.active: -1 hw.acpi.thermal.tz1.thermal_flags: 0 hw.acpi.thermal.tz1._PSV: -1 hw.acpi.thermal.tz1._HOT: -1 hw.acpi.thermal.tz1._CRT: 3662 hw.acpi.thermal.tz1._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz2.temperature: 2892 hw.acpi.thermal.tz2.active: -1 hw.acpi.thermal.tz2.thermal_flags: 0 hw.acpi.thermal.tz2._PSV: 3262 hw.acpi.thermal.tz2._HOT: -1 hw.acpi.thermal.tz2._CRT: 3662 hw.acpi.thermal.tz2._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.battery.life: -1 hw.acpi.battery.time: -1 hw.acpi.battery.state: 7 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 hw.acpi.acline: 1 > > Ok. You can manually turn on the active cooling with: > sysctl hw.acpi.thermal.active=0 > (or 1,2,3, etc.) This is another way to trigger the panic. hunter# sync hunter# sysctl hw.acpi.thermal.active=0 sysctl: unknown oid 'hw.acpi.thermal.active' hunter# sysctl hw.acpi.thermal.tz0.active=0 hw.acpi.thermal.tz0.active: -1 -> 0 hunter# sysctl hw.acpi.thermal.tz0.active=1 hw.acpi.thermal.tz0.active: 0 -> 1 hunter# sysctl hw.acpi.thermal.tz0.active=2 hw.acpi.thermal.tz0.active: 1 -> 2 hunter# sysctl hw.acpi.thermal.tz0.active=3 hw.acpi.thermal.tz0.active: 2 -> 3 hunter# sysctl hw.acpi.thermal.tz0.active=4 hw.acpi.thermal.tz0.active: 3 -> 4 hunter# sysctl hw.acpi.thermal.tz0.active=-1 hw.acpi.thermal.tz0.active: 4 -> -1 hunter# The fan was running on low speed as I startet (see active was -1 above), then cycled through various speeds as I typed these commands. At the end, when I reset active to -1, the fan turned off. This is a bit strange, given that it usually stays on, low speed, while on AC. Anyway, will rebuild acpi.ko with debug and try more often or with the other tz's. Is there a way to see which tz was triggering from the dump? A final note: I get two error messages during boot: ... acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR ACPI-1287: *** Error: Method execution failed [\\_SB_.C047.C05A.C0E5.C0E9] (Node 0xc6141a80), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\\_SB_.C047.C05A.C0E5._INI] (Node 0xc6141280), AE_NOT_EXIST acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_tz1: on acpi0 acpi_tz2: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 ... Let me know if you'd like to see a verbose boot. -- Regards, Georg.