From owner-freebsd-hackers@FreeBSD.ORG Thu May 11 21:37:31 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 945AD16A581 for ; Thu, 11 May 2006 21:37:26 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E0D044594 for ; Thu, 11 May 2006 21:14:48 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k4BLEf10046069; Thu, 11 May 2006 17:14:44 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Eric Anderson Date: Thu, 11 May 2006 16:45:12 -0400 User-Agent: KMail/1.9.1 References: <4460FCE8.9020703@centtech.com> <200605101714.34683.jhb@freebsd.org> <446322D4.7020708@centtech.com> In-Reply-To: <446322D4.7020708@centtech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605111645.13941.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1459/Thu May 11 16:46:49 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-hackers@freebsd.org Subject: Re: Exiting Xorg panics Core Duo laptop X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 May 2006 21:37:50 -0000 On Thursday 11 May 2006 07:41, Eric Anderson wrote: > John Baldwin wrote: > > On Tuesday 09 May 2006 16:34, Eric Anderson wrote: > >> I have a Core Duo system (2 2GHz CPUs), that continually locks up (I > >> believe it panics) when exiting xorg with both CPU's enabled. If I > >> have: > >> > >> hint.apic.0.disabled="1" > >> > >> in device.hints, I only use one CPU, however it exits from xorg just > >> fine. When the system locks, I still have some keyboard control (num > >> lock lights, etc), but I can't seem to do anything else. I can't see > >> the screen, it goes black during that time. All my system > >> configs/dmesg/etc are here: > >> > >> Booted with apic not disabled: > >> http://www.googlebit.com/freebsd/200605090613/ > >> > >> Booted with apic disabled: > >> http://www.googlebit.com/freebsd/200605091117/ > >> > >> How can I debug (or help debug) this? > > > > What if you disable just SMP but leave APIC enabled > > (kern.smp.disabled=1)? > > If I disable only SMP and leave APIC enabled, everything seems to work > fine. What other info can I give you? Ok, that helps to narrow it down. Can you hook up a serial console and obtain the panic messages along with a stack trace as described in the handbook? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org