From owner-freebsd-current@FreeBSD.ORG Tue May 25 05:31:02 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 E7DC416A4CE for ; Tue, 25 May 2004 05:31:02 -0700 (PDT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEBA543D1F for ; Tue, 25 May 2004 05:31:02 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 28362 invoked from network); 25 May 2004 12:30:48 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 25 May 2004 12:30:48 -0000 Received: from slimer.baldwin.cx (slimer.baldwin.cx [192.168.0.16]) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i4PCUbwt005452; Tue, 25 May 2004 08:30:42 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Tue, 25 May 2004 08:31:20 -0400 User-Agent: KMail/1.6 References: <40A43E86.6040504@sbcglobal.net> <200405241147.20382.jhb@FreeBSD.org> <40B2CE33.6090700@sbcglobal.net> In-Reply-To: <40B2CE33.6090700@sbcglobal.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200405250831.20795.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Jason King Subject: Re: lockups 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: Tue, 25 May 2004 12:31:03 -0000 On Tuesday 25 May 2004 12:40 am, Jason King wrote: > John Baldwin wrote: > >On Sunday 23 May 2004 12:30 am, Jason King wrote: > >>John Baldwin wrote: > >>>On Friday 14 May 2004 08:54 pm, Jason King wrote: > >>>>ok i'm a dumbass... in my haste this morning, i commented out the wrong > >>>>line in my config file, so when i tried disabling mixed mode, apic > >>>>support wasn't even compiled in the kernel. So to make extra sure, I > >>>>went back and explicitly tried it with the 5.2.1-RELEASE cd (disabling > >>>>apic worked, disabling mixed mode did not), so its really something > >>>>related to apic support. So next question, what can I do to track down > >>>>the problem? Any suggestions for resources to understand how the apic > >>>>stuff works? Might there be a way to grab the kernel messages even > >>>>after a reboot since the lockups don't even my to drop to the debugger? > >>>>Doing a boot -v generated a bunch of text that I couldn't read as it > >>>>scrolled by too fast, and I'm wondering if it might possibly help shed > >>>>some light as to what's going on... > >>> > >>>Note that you can't disable mixed mode via a tunable on 5.2.1, so you > >>>might want to retest disabling mixed mode. However, the first steps are > >>>to work on the non-ACPI case as that is easiest. I'll need 'mptable' > >>>output and dmesg output from a verbose boot with APIC enabled and ACPI > >>>disabled if you can get that. Thanks. > >> > >>Unfortunately, booting with ACPI disabled and apic enabled still caused > >>the system to hang. So anytime apic is enabled, the system locks up. > >>(i've tried just the kernel with no modules loaded as well as with the > >>normal modules I use loaded, locks up, but in a different place). I was > >>able to pull off the output from a boot -v using a serial console. I've > >>attached that. Hopefully that helps... > > > >Can you provide mptable output? > > Here is the mptable output. Hmm, your box has lots of issues. :-/ The $PIR table doesn't include entries for several devices on PCI bus 0, and the mptable doesn't include entries for almost all of your PCI devices. I would first look for a BIOS upgrade. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org