From owner-freebsd-current Sat Dec 28 9: 4:17 2002 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 0611C37B401 for ; Sat, 28 Dec 2002 09:04:04 -0800 (PST) Received: from baraca.united.net.ua (ns.united.net.ua [193.111.8.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8520A43EB2 for ; Sat, 28 Dec 2002 09:03:57 -0800 (PST) (envelope-from max@vega.com) Received: from vega.vega.com (root@xDSL-2-2.united.net.ua [193.111.9.226]) by baraca.united.net.ua (8.12.6/8.12.6) with ESMTP id gBSH3nhm088774; Sat, 28 Dec 2002 19:03:50 +0200 (EET) (envelope-from max@vega.com) Received: from vega.vega.com (max@localhost.vega.com [127.0.0.1]) by vega.vega.com (8.12.6/8.12.5) with ESMTP id gBSH3knN047392; Sat, 28 Dec 2002 19:03:46 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: (from max@localhost) by vega.vega.com (8.12.6/8.12.5/Submit) id gBSH3YBt047391; Sat, 28 Dec 2002 19:03:34 +0200 (EET) Date: Sat, 28 Dec 2002 19:03:34 +0200 From: Maxim Sobolev To: Mark Evenson Cc: Nate Lawson , freebsd-current@FreeBSD.ORG Subject: Re: DP2 won't stay powered off Message-ID: <20021228170334.GC47156@vega.vega.com> References: <20021205114733.R77878@cnd.mcgill.ca> <20021227181604.GA46110@anastasia.lan.barfoos.de> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The same ("automatic" power on after power off ) is here - IBM ThinkPad 600E. -Maxim On Sat, Dec 28, 2002 at 08:31:53AM -0500, Mark Evenson wrote: > Jens Trzaska writes: > > > On Thu, Dec 05, 2002 at 10:37:49AM -0800, Nate Lawson wrote: > > > > Can everyone with the auto power on problem report the output of "sysctl > > > hw.acpi"? > > > > I'm seeing the same problem on my T20. It powers on again after some > > time. But I don't use the DP2! > > I am getting the same sort of symptom here with a IBM ThinkPad X20: if I > leave the system attached to the AC adapator "overnight" it will have "powered > itself up" in the morning. I have never been able to successfully log onto the > system after these events, as the screen is not active in any state, but > certainly the system logs show activity at this time. > > This system in general is a little weird with respect to power manangement > issues in general, which is one of the reasons I made the leap to CURRENT > about a month ago from STABLE in order to see if the ACPI code would help > anything. Most notably, the system has never reliably transitioned to and > from sleep in any consistent manner. > > In addition, I get the following errors reliably upon boot: > > Dec 28 14:19:24 quid kernel: ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR > Dec 28 14:19:24 quid kernel: ACPI-1287: *** Error: Method execution failed, AE_ERROR > Dec 28 14:19:26 quid kernel: acpi_acad0: On Line > Dec 28 14:19:58 quid kernel: system power profile changed to 'economy' > Dec 28 14:19:58 quid kernel: acpi_cpu0: set speed to 50.0% > Dec 28 14:19:58 quid kernel: acpi_acad0: Off Line > Dec 28 14:19:59 quid kernel: system power profile changed to 'performance' > Dec 28 14:20:00 quid kernel: acpi_cpu0: set speed to 100.0% > Dec 28 14:20:00 quid kernel: acpi_acad0: On Line > > During the economy/perfomance transition, the AC remains attached. > > Furthermore, with the battery inserted in the X20 will sometimes get system > freezes with message about a "ACPI lid event" without corresponding > physical action. During these system freezes, DDB is never entered, > meaning the power must be removed from the system before I can do anything > additional. Gotta love RELENG_5's async fsck here. . . > > I have been holding off reporting my problems with ACPI while I try to > educate myself more both about what is present in CURRENT and what exactly > ACPI is trying to do, but at this point at least I can give a "me too" > report here for the auto power problem, to show that it is apparently more > wide spread. > > -- > > I am using a CURRENT cvsup from Dec 25 with a GENERIC kernel: > > FreeBSD quid 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Dec 25 > 23:06:22 CET 2002 realtime@quid:/usr/obj/usr/src/sys/GENERIC i386 > > Attached are the demsg-boot and the ouput of "systcl hw.acpi". > > Content-Description: dmesg output > @\^D\^PCopyright (c) 1992-2002 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 #0: Wed Dec 25 23:06:22 CET 2002 > realtime@quid:/usr/obj/usr/src/sys/GENERIC > Preloaded elf kernel "/boot/kernel/kernel" at 0xc06bd000. > Preloaded userconfig_script "/boot/kernel.conf" at 0xc06bd0a8. > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc06bd0f8. > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 597407176 Hz > CPU: Pentium III/Pentium III Xeon/Celeron (597.41-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x683 Stepping = 3 > Features=0x383f9ff > real memory = 335478784 (319 MB) > avail memory = 318681088 (303 MB) > Initializing GEOMetry subsystem > Pentium Pro MTRR support enabled > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > Using $PIR table, 11 entries at 0xc00fdee0 > ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 > ACPI-1287: *** Error: Method execution failed, AE_AML_NO_RETURN_VALUE > acpi0: power button is handled as a fixed feature programming model. > Timecounter "ACPI-safe" 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_lid0: on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > agp0: mem 0xf8000000-0xfbffffff at device 0.0 on pci0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pci1: at device 0.0 (no driver attached) > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port 0x1800-0x180f at device 7.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > uhci0: port 0x1820-0x183f irq 11 at device 7.2 on pci0 > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > pci0: at device 7.3 (no driver attached) > cbb0: mem 0x50000000-0x50000fff irq 11 at device 8.0 on pci0 > cardbus0: on cbb0 > pccard0: <16-bit PCCard bus> on cbb0 > cbb1: mem 0x50100000-0x50100fff irq 11 at device 8.1 on pci0 > cardbus1: on cbb1 > pccard1: <16-bit PCCard bus> on cbb1 > fxp0: port 0x1840-0x187f mem 0xf4020000-0xf403ffff,0xf4010000-0xf4010fff irq 11 at device 10.0 on pci0 > fxp0: Ethernet address 00:10:a4:a6:52:85 > inphy0: on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > pci0: at device 10.1 (no driver attached) > pci0: at device 11.0 (no driver attached) > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0 > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > ppc0 port 0x3bc-0x3c3 irq 7 on acpi0 > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > acpi_ec0: port 0x66,0x62 on acpi0 > acpi_cmbat0: on acpi0 > acpi_acad0: on acpi0 > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > orm0: