From owner-freebsd-stable@FreeBSD.ORG Wed Aug 16 21:49:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15C5316A4DF for ; Wed, 16 Aug 2006 21:49:00 +0000 (UTC) (envelope-from android@oberon.pfi.lt) Received: from oberon.pfi.lt (oberon.pfi.lt [193.219.52.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D44A43D46 for ; Wed, 16 Aug 2006 21:48:59 +0000 (GMT) (envelope-from android@oberon.pfi.lt) Received: from [10.10.10.1] (82-135-145-2.ip.rygveda.lt [82.135.145.2]) by oberon.pfi.lt (8.13.3/8.13.3) with ESMTP id k7GM4Mww060394; Thu, 17 Aug 2006 01:04:23 +0300 (EEST) (envelope-from android@oberon.pfi.lt) Message-ID: <44E392C3.2000605@oberon.pfi.lt> Date: Thu, 17 Aug 2006 00:48:51 +0300 From: "Android Andrew [:]" User-Agent: Thunderbird 1.5.0.5 (X11/20060731) MIME-Version: 1.0 To: Ian Smith References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Christian Walther Subject: Re: FreeBSD 6.1-STABLE: Unexplained power off X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Aug 2006 21:49:00 -0000 Thank you for answers! Yesterday the last iteration of high load testing finished with just another power off. There are two ways of problem-solving have been outlined in this thread. One way - hardware problem, e.g. PSU. Another way - software, e.g. APM/ACPI problem. I could not find any PSU for replacement at this moment. So, I've been playing with BIOS and kernel options. I disabled "dynamic overclocking", hyperthreading options in BIOS. There's no "Disable APM" (or something like this) or "Disable ACPI" in my BIOS. I can only disable some ACPI functions or extensions (like "Enable ACPI 2 extensions"). I've recompiled kernel without apm/acpi options and without SMP support. I was typing "After recompilation system is still working without crashing" when system just turned off.... :) my loader.conf: loader_logo="beastie" if_myk_load="YES" nvidia_load="YES" sysctl.conf: net.inet.tcp.msl=7500 net.inet.udp.blackhole=1 net.inet.ip.random_id=1 kern.ipc.somaxconn=4096 net.inet.icmp.icmplim=100 last dmesg: Copyright (c) 1992-2006 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 6.1-STABLE #8: Wed Aug 16 21:11:42 EEST 2006 root@callisto:/usr/obj/usr/src/sys/callisto Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (3010.67-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf43 Stepping = 3 Features=0xbfebfbff Features2=0x649d> AMD Features=0x20100000 real memory = 2147090432 (2047 MB) avail memory = 2092273664 (1995 MB) kbd1 at kbdmux0 ichwd module loaded 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 acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 ACPI-1304: *** Error: Method execution failed [\\_PR_.CPU1._PDC] (Node 0xc5c81c60), AE_BAD_HEADER acpi_throttle0: on cpu0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 11 at device 1.0 on pci0 pci4: on pcib1 nvidia0: mem 0xd4000000-0xd7ffffff,0xd8000000-0xdfffffff,0xd3000000-0xd3ffffff irq 11 at device 0.0 on pci4 nvidia0: [GIANT-LOCKED] pci0: at device 27.0 (no driver attached) pcib2: irq 11 at device 28.0 on pci0 pci3: on pcib2 pcib3: irq 10 at device 28.3 on pci0 pci2: on pcib3 myk0: port 0xc800-0xc8ff mem 0xd2efc000-0xd2efffff irq 10 at device 0.0 on pci2 myk0: Ethernet address: 00:13:d4:d0:31:e5 uhci0: port 0x8000-0x801f irq 5 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] 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 uhci1: port 0x8400-0x841f irq 11 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x8800-0x881f irq 3 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0x9000-0x901f irq 10 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xd2dff800-0xd2dffbff irq 5 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered uhub4: device problem (IOERROR), disabling port 7 pcib4: at device 30.0 on pci0 pci1: on pcib4 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0xa800-0xa807,0xa400-0xa403,0xa000-0xa007,0x9800-0x9803,0x9400-0x940f mem 0xd2dffc00-0xd2dfffff irq 11 at device 31.2 on pci0 ata2: on atapci1 ata3: on atapci1 ata4: on atapci1 ata5: on atapci1 ichsmb0: port 0x400-0x41f irq 11 at device 31.3 on pci0 ichsmb0: [GIANT-LOCKED] smbus0: on ichsmb0 smb0: on smbus0 acpi_button0: on acpi0 speaker0: port 0x61 on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ichwd0: on isa0 orm0: at iomem 0xc0000-0xcefff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0 at vga0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ukbd0: Key Tronic Keytronic USB Keyboard, rev 1.10/1.02, addr 2, iclass 3/1 kbd2 at ukbd0 ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/20.00, addr 3, iclass 3/1 ums0: 4 buttons and Z dir. Timecounter "TSC" frequency 3010671825 Hz quality 800 Timecounters tick every 1.000 msec ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default acd0: DVDR at ata0-master UDMA66 ad4: 114473MB at ata2-master SATA300 ad6: 114473MB at ata3-master SATA300 ar0: 228942MB status: READY ar0: disk0 READY using ad4 at ata2-master ar0: disk1 READY using ad6 at ata3-master cd0 at ata0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 66.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from ufs:/dev/ar0s1a myk0: link up oss: Out of mixer extensions for device 0 Ian Smith wrote: > On Tue, 15 Aug 2006, Christian Walther wrote: > > > This is just a wild, uneducated guess, because I'm not a long FreeBSD > > user, but from my point of view this error could really be related to > > ACPI/APM, as already has been suggested. > > It smells a bit that way to me too. I've just read the whole thread, > but going back to the original post's kernel conf, android had APM and > apm_saver in there, but the dmesg confirmed an ACPI boot, complete with > a complaint by apm_saver refusing to load because APM wasn't loaded. As > it never is if ACPI is loaded, as I understand it. (caveat: 5.5-STABLE) > > android also mentioned trying to do things with APM settings in BIOS. I > suspect APM should be _disabled_ in BIOS, and ACPI enabled, with ACPI > power (etc) management used instead .. someone correct me if I'm wrong; > I'm really unsure how much APM functional emulation remains in ACPI? > > > Maybe the machine is trying to go to suspend, but fails while doing > > so, which in the end would mean that it can't recover from the > > suspend, but has to reboot completely, resulting in dirty file > > systems. It wouldn't reach the suspend state correctly, which could > > leave everything depending on ACPI/APM in a undefined state, including > > the hardware. This would explain why the machine has to be turned off > > properly by pressing toe power button for such a long time. > > Maybe. If APM is enabled in BIOS, but not loaded, could spell trouble. > > > I'd try to use the machine without ACPI/APM enabled. If possible, > > compile a new kernel without it being enabled. This might not be > > possible because you're on a SMP-system, thou, but you might want to > > check your configuration files for suspend or hibernation -- and turn > > them of. > > Well it won't likely work with _neither_ enabled, and I suspect you're > right about SMP needing ACPI. android suggested failure to boot with > neither enabled, which sounds likely. What's in /boot/loader.conf? > > Cheers, Ian > > > With ACPI/APM turned on, leave the machine idle for some time and see > > if it shows the same behaviour. When it shuts down cleanly it's likely > > that suspend/hibernation fails due to the high load introduced by the > > build process. > > > > I've seen and experienced similar problems on other platforms, such as > > OS X and (sorry) Linux. > >