From owner-freebsd-questions@FreeBSD.ORG Tue May 5 01:29:44 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB6AE106564A for ; Tue, 5 May 2009 01:29:44 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from imedmobility.com (host-50.216-16-29.iw.net [216.16.29.50]) by mx1.freebsd.org (Postfix) with ESMTP id A22518FC08 for ; Tue, 5 May 2009 01:29:44 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from midco.net (host-67-54-107-208.midco.net [208.107.54.67]) by imedmobility.com (Postfix) with ESMTPA id 6F9351173C57 for ; Mon, 4 May 2009 20:29:43 -0500 (CDT) Message-ID: <49FF9680.3020800@gmail.com> Date: Mon, 04 May 2009 20:29:36 -0500 From: Adam Vande More User-Agent: Thunderbird 2.0.0.21 (X11/20090408) MIME-Version: 1.0 To: freebsd-questions References: <5e8ad96d0905041746o67c463e9t1297a0b3103557bf@mail.gmail.com> In-Reply-To: <5e8ad96d0905041746o67c463e9t1297a0b3103557bf@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Part II: Running SMP kernel but only one cpu X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 01:29:45 -0000 Duane wrote: > The bios in this old Micron dual PPro-180 full tower antique only > initializes the second CPU if the machine is cold-booted. A simple > 'reboot' results in a single processor machine regardless of the > kernel that is launched. This fact -- unknown to me before last night > -- was the source of a great deal of lost time! > Good you found a work around. You might try ensuring your running latest avail bios as well. > My 6.4 SMP kernel (now customized) runs just fine, with both cpus > active, *except* for this message streaming constantly up the boot > console. > > (from /var/log/messages:) > > May 4 20:20:33 poobah kernel: interrupt storm detected on "irq15:"; > throttling interrupt source > May 4 20:21:02 poobah last message repeated 42 times > May 4 20:21:03 poobah login: ROOT LOGIN (root) ON ttyv1 > May 4 20:21:03 poobah kernel: interrupt storm detected on "irq15:"; > throttling interrupt source > May 4 20:21:33 poobah last message repeated 30 times > May 4 20:23:33 poobah last message repeated 120 times > May 4 20:33:33 poobah last message repeated 599 times > May 4 20:40:01 poobah last message repeated 387 times > etc etc ad repetitum infinitum > > Question1: Is this something I should go to some lengths to eliminate? > Yes, it's probably something you should eliminate. > Question2: What the heck is it? > A poor explanation is the devices are fighting over an IRQ. Generally, simplest fix is to find what devs are on that IRQ, and manually reassign one dev to a different IRQ. > > Best regards, > >