From owner-freebsd-hackers@FreeBSD.ORG Wed May 10 02:06:32 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 5A82516A409 for ; Wed, 10 May 2006 02:06:32 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id D235E43D48 for ; Wed, 10 May 2006 02:06:31 +0000 (GMT) (envelope-from minimarmot@gmail.com) Received: by nz-out-0102.google.com with SMTP id 9so1574346nzo for ; Tue, 09 May 2006 19:06:31 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=G0KHSMuscvkBF9TLYjbbWmmJkS1B0J6uBuEqi5I+eLT2Qc/juXxKdl1Tjyqrnd3seNLs8F/+Iz1v+8ZAnnOI77BO4L4l1EL6qiWzkkFJtcymdM721Uzgk7ctOLGP8rN1CoCl+pPNvFo3XpEnWqFPBfC2YAfC7HJ/H538rEPsdno= Received: by 10.36.220.18 with SMTP id s18mr5918116nzg; Tue, 09 May 2006 19:06:31 -0700 (PDT) Received: by 10.36.80.9 with HTTP; Tue, 9 May 2006 19:06:31 -0700 (PDT) Message-ID: <47d0403c0605091906ldac37c1pe601c280865beabe@mail.gmail.com> Date: Wed, 10 May 2006 02:06:31 +0000 From: "Ben Kaduk" To: "Eric Anderson" In-Reply-To: <446148E7.3090205@centtech.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4460FCE8.9020703@centtech.com> <47d0403c0605091432x4b19ad0drc90d96b123c07d6a@mail.gmail.com> <446148E7.3090205@centtech.com> 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: Wed, 10 May 2006 02:06:32 -0000 On 5/10/06, Eric Anderson wrote: > Ben Kaduk wrote: > > On 5/9/06, 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 ha= ve: > >> > >> hint.apic.0.disabled=3D"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? > >> > >> Eric > >> > >> > >> -- > >> ----------------------------------------------------------------------= -- > >> Eric Anderson Sr. Systems Administrator Centaur Technolo= gy > >> Anything that works is better than anything that doesn't. > >> ----------------------------------------------------------------------= -- > >> _______________________________________________ > >> freebsd-hackers@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > >> To unsubscribe, send any mail to > >> "freebsd-hackers-unsubscribe@freebsd.org" > >> > > > > Eric, > > > > Does your laptop by any chance have a serial or firewire port with > > which to set up a remote console? > > It has both. I can set up a serial console on it - what's the best way > to do this? > > > Eric > > > > -- > ------------------------------------------------------------------------ > Eric Anderson Sr. Systems Administrator Centaur Technology > Anything that works is better than anything that doesn't. > ------------------------------------------------------------------------ > I am told that there are instructions in the handbook at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-set= up.html but I personally have not gotten it to work (though I only tried when my laptop was panic-ing on boot. . .) If your freeze truly is a panic, the trace should show up on the serial console and illuminate what is going wrong. -Ben Kaduk