From owner-freebsd-current@FreeBSD.ORG Mon Nov 1 21:04:27 2004 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 ECAEB16A4CE for ; Mon, 1 Nov 2004 21:04:26 +0000 (GMT) Received: from ms-smtp-01-eri0.socal.rr.com (ms-smtp-01-qfe0.socal.rr.com [66.75.162.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9DD443D3F for ; Mon, 1 Nov 2004 21:04:26 +0000 (GMT) (envelope-from freebsd@teknoir.com) Received: from sg1.teknoir.com (dt054n4e.san.rr.com [24.30.152.78]) iA1L4MkM029082 for ; Mon, 1 Nov 2004 13:04:22 -0800 (PST) Received: from [10.2.4.204] (h-68-164-222-118.sndacagl.covad.net [68.164.222.118]) (authenticated bits=0) by sg1.teknoir.com (8.12.9p2/8.12.9) with ESMTP id iA1L3wf7030584 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 1 Nov 2004 13:04:18 -0800 (PST) (envelope-from freebsd@teknoir.com) Message-ID: <4186A4B7.9070205@teknoir.com> Date: Mon, 01 Nov 2004 13:03:51 -0800 From: Michael Knittle User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Virus-Scanned: by amavisd-new Subject: Problems rebooting/ACPI problem with HT in RC2 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: Mon, 01 Nov 2004 21:04:27 -0000 In 5.3 Beta7, RC1, and RC2 I've been having a problem with ACPI on a system I'm building. When I try to reboot the system or to do a shutdown -p with SMP and ACPI enabled as soon as it gets to "Shutting down ACPI" it crashes and fills part of the screen with garbage characters. If I select APCI disabled at the boot screen it will be able to reboot and shutdown/powerdown just fine, but then again SMP obviously doesn't work either. The generic kernel in Beta7 and RC1 which had SMP enabled by default did this as well, so I dont think its the result of anything in my customer kernels. If ACPI is enabled but SMP is not, it will also reboot fine so I'm pretty sure this is a SMP/Hyperthreading issue but it is definitely a show stopper for me. I dont have any other systems which are multi-processor or hyperthreading enabled to test to see if it's specific to my hardware though. In RC1 (I think I had KDB, DDB, WITNESS, and INVARIANTS enabled in the kernel for this one) this shows up in /var/log/messages: Oct 31 12:47:55 synapscape kernel: Shutting down ACPI Oct 31 12:47:55 synapscape kernel: ke Oct 31 12:47:55 synapscape kernel: <18446744072652783764>kkernel trap 1 with interrupts disabled Oct 31 12:47:55 synapscape kernel: Oct 31 12:47:55 synapscape kernel: Oct 31 12:47:55 synapscape kernel: Fatal trap 1: privileged instruction fault while in kernel mode Oct 31 12:47:55 synapscape kernel: cpuid = 0; apic id = 00 Oct 31 12:47:55 synapscape kernel: instruction pointer = 0x8:0xc2c32003 Oct 31 12:47:55 synapscape kernel: stack pointer = 0x10:0xeb41c777 Oct 31 12:47:55 synapscape kernel: frame pointer = 0x10:0xeb41c838 Oct 31 12:47:55 synapscape kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Oct 31 12:47:55 synapscape kernel: = DPL 0, pres 1, def32 1, gran 1 Oct 31 12:47:55 synapscape kernel: processor eflags = resume, IOPL = 0 Oct 31 12:47:55 synapscape kernel: current process = 37 (swi5: clock sio) Oct 31 12:47:55 synapscape kernel: trap number = 1 Oct 31 12:47:55 synapscape kernel: panic: privileged instruction fault Oct 31 12:47:55 synapscape kernel: cpuid = 0 Oct 31 12:47:55 synapscape kernel: boot() called on cpu#0 In RC2 this shows up in /var/log/messages: Oct 31 15:44:04 synapscape kernel: Shutting down ACPI Oct 31 15:44:04 synapscape kernel: