From owner-freebsd-stable@FreeBSD.ORG Wed Mar 19 21:08:35 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1F38106566B for ; Wed, 19 Mar 2008 21:08:35 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from virtual.micronet.sk (smtp.micronet.sk [84.16.32.237]) by mx1.freebsd.org (Postfix) with ESMTP id 6894B8FC12 for ; Wed, 19 Mar 2008 21:08:35 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by virtual.micronet.sk (Postfix) with ESMTP id 74C9D10E624; Wed, 19 Mar 2008 22:07:14 +0100 (CET) X-Virus-Scanned: by amavisd-new at virtual.micronet.sk Received: from virtual.micronet.sk ([127.0.0.1]) by localhost (virtual.micronet.sk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HW4Qs+QbqyjZ; Wed, 19 Mar 2008 22:07:12 +0100 (CET) Received: from DANGER-PC (danger.mcrn.sk [84.16.37.254]) by virtual.micronet.sk (Postfix) with ESMTP id CCC6410E647; Wed, 19 Mar 2008 22:07:12 +0100 (CET) Date: Wed, 19 Mar 2008 22:08:25 +0100 From: Daniel Gerzo X-Mailer: The Bat! (v3.99.3) Professional Organization: The FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1839488629.20080319220825@rulez.sk> To: Mike Tancsa In-Reply-To: <200803192034.m2JKYFmL087217@lava.sentex.ca> References: <669936444.20080319100148@rulez.sk> <200803191753.m2JHraI5092556@lurza.secnetix.de> <20080319180629.GA29308@eos.sc1.parodius.com> <200803192034.m2JKYFmL087217@lava.sentex.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Jeremy Chadwick , freebsd-stable@freebsd.org Subject: Re[2]: Weird system cpu usage X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Gerzo List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Mar 2008 21:08:36 -0000 Hello Mike, Wednesday, March 19, 2008, 9:32:13 PM, you wrote: >>Also, I believe there was a report from another user who saw similar >>issues with em(4), and found that disabling MSI fixed the storm in >>question. I believe you can disable MSI/MSIX by placing the following >>in /boot/loader.conf, then reboot: >> >>hw.pci.enable_msi="0" >>hw.pci.enable_msix="0" > When MSI is enabled, the irq will be a strangely high number. e.g. Interesting, I have disabled MSI and MSIX support, but they still share the same irq. However, I don't know yet if the interrupt storm is going to be resolved, it needs some time (It always used to take some time until it has showed up). > If anything, I found enabling MSI helped matters where I saw strange > IRQ issues. However, not sure if the original poster's hardware > supports it. One thing it does remind me of is some strange IRQ > issues I had on an AMD board where a USB setting for "legacy handoff" > (something like that) would really slow down the machine with an in > inordinate amount of IRQs firing. I forget if I had to enable it or > disable it to fix the problem. If anything, I would try disabling > USB all together if its not being used even though its not figuring > in the above really high rate of IRQs. The USB isn't indeed used, I will think about disabling it, and also about trying to move around the em(4) NICs to the other slots. Unfortunately I don't have a physical access to the given maschine. -- Best regards, Daniel mailto:danger@FreeBSD.org