From owner-freebsd-stable@FreeBSD.ORG Mon Nov 17 05:47:26 2003 Return-Path: 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 E5E7116A4CE for ; Mon, 17 Nov 2003 05:47:26 -0800 (PST) Received: from ene.asda.gr (ene.asda.gr [193.92.118.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CA3943F3F for ; Mon, 17 Nov 2003 05:47:25 -0800 (PST) (envelope-from lefty@ene.asda.gr) Received: from ene.asda.gr (lefty.ene.asda.gr [193.92.118.162]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (Client CN "Lefteris Tsintjelis", Issuer "E 'n' E CA" (verified OK)) by ene.asda.gr (Postfix) with ESMTP id C6F29170; Mon, 17 Nov 2003 15:47:30 +0200 (EET) Message-ID: <3FB8D15C.947E52B1@ene.asda.gr> Date: Mon, 17 Nov 2003 15:47:08 +0200 From: Lefteris Tsintjelis Organization: ASDA X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en,el MIME-Version: 1.0 To: Doug White References: <3FAE5958.6B162FAF@ene.asda.gr> <20031111180355.A66327@carver.gumbysoft.com> Content-Type: text/plain; charset=iso-8859-7 Content-Transfer-Encoding: 7bit cc: stable@freebsd.org Subject: Re: Machine Freezes with SMP+APIC enabled. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Nov 2003 13:47:27 -0000 Doug White wrote: > > On Sun, 9 Nov 2003, Lefteris Tsintjelis wrote: > > > I have been experiencing random machine freezes when using SMP (Hyper > > threading) the past week. There are no core dumps or error messages > > displayed anywhere. Load is very minimum. When SMP/Hyperthreading is > > disabled machine works with no problems at full load. > > Hm, smells like Giant deadlock. > Hi Doug, and thank you for all the info. The motherboard of the PC decided to finally die on me last week so it looks like it was a hardware deadlock. I got it replaced and cvsup to the latest STABLE. It has been working very STABLE the past couple of days. Best Regards, Lefteris Tsintjelis > dwhite's Form Letter on Debugging Giant Deadlocks > > If you are experiencing problems with CURRENT locking up hard, it may be > due to a deadlock against the Giant mutex, which controls large parts of > the kernel. Symptoms include: > > . No response to any input > . System video console > . Network (ping) > > To debug this, you will need to set up a serial console with some special > kernel options. Instructions for booting with serial console are in the > Handbook, but you will have to compile with the following kernel options: > > options DDB > options BREAK_TO_DEBUGGER > options WITNESS > options INVARIANTS > options INVARIANTS_SUPPORT > > Make sure your serial console is capable of sending a Break signal. If > not, use "ALT_BREAK_TO_DEBUGGER" instead of "BREAK_TO_DEBUGGER". > > Enable the serial console and boot the system. Turn on terminal logging. > In loader, stop the boot and type "boot -v" at the OK prompt to get > additional info during the boot process. > > Once the system is up, trigger the hang. When the system hangs, issue the > Break signal (or if you have used ALT_BREAK_TO_DEBUGGER, press Enter ~ ^E > b (tilde, Ctrl-E, b)). > > If you get the db> prompt, then your hang is probably due to a Giant > deadlock. If not, then something else may be at fault. > > Once in db>, run the following two commands and capture their output using > your terminal's logging capability: > > show locks > tr > > Take these and the boot -v output, put them on a webpage, and send a > message to current@freebsd.org carefully explaining what you did to > trigger the hang. > > Good luck! > > > > > Best, > > Lefteris Tsintjelis