From owner-freebsd-questions@FreeBSD.ORG Tue May 5 03:45:48 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 5E1FA106564A for ; Tue, 5 May 2009 03:45:48 +0000 (UTC) (envelope-from tajudd@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.24]) by mx1.freebsd.org (Postfix) with ESMTP id 154F68FC1D for ; Tue, 5 May 2009 03:45:47 +0000 (UTC) (envelope-from tajudd@gmail.com) Received: by qw-out-2122.google.com with SMTP id 3so3239941qwe.7 for ; Mon, 04 May 2009 20:45:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type; bh=gCtJ82f9jbUsKhsVUyesO22R4izDjYgsPwnLljgLxOM=; b=tBQv4fJX50U2fDtf26M8FCW499lxeOwdBI4Ny6gz0AJn8N5CDGi7LdEOrkPMJj15sZ fODK/d48gRnN+xdLiJVWa1hRoJX2YxJwSCXMR/2vojmCEdAkOPPkeH2HNa+7kPVs2I+V kpjc4xQgqtdSmi3in/MnOiJSJGqoXGOlZOufM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=I/uASh/W0CU6flyQceyBIRgesyuoRD+YEmcHmoCUBGL/vt2wtxOKlWrWv273NCzePj bWZAKSfH61DaxrkMUPAhAxudiXJVa0L5nkDmtdRWHcLc0HqjzYdfiUOKNSpoJQxzV7f9 ci3ntFu5QD9In9FAebRcGMae1vUgKm9lmyFA8= MIME-Version: 1.0 Received: by 10.220.45.203 with SMTP id g11mr10769275vcf.70.1241495147315; Mon, 04 May 2009 20:45:47 -0700 (PDT) In-Reply-To: <5e8ad96d0905041746o67c463e9t1297a0b3103557bf@mail.gmail.com> References: <5e8ad96d0905041746o67c463e9t1297a0b3103557bf@mail.gmail.com> From: Tim Judd Date: Mon, 4 May 2009 21:45:32 -0600 Message-ID: To: Duane Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-questions 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 03:45:48 -0000 On Mon, May 4, 2009 at 6:46 PM, 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! > > 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? > > Question2: What the heck is it? > > > Best regards, > > -- > Duane > IRQ15 is typically your secondary IDE controller; but due to PCI (or E-ISA) plug&play, including the PnP the BIOS may setup, lots of others can be on that bus too. Likely candidates are PCI devices, such as modems, NICs, sound cards, etc I think you'd be able to find what's on IRQ15 by a simple: # grep -i irq15 /var/run/dmesg.boot You will probably not be able to pull your secondary IDE controller off 15. The possible other device that's been configured for irq15 might stop if you disable PnP OS in the BIOS (if it exists), or setting irq15 to the equivelant of 'reserved' in the BIOS might aleviate the problem. Good luck.