From owner-freebsd-hardware@FreeBSD.ORG Mon Apr 19 09:33:13 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02E2316A4CE for ; Mon, 19 Apr 2004 09:33:13 -0700 (PDT) Received: from myn.rcast.u-tokyo.ac.jp (spam003.ecc.u-tokyo.ac.jp [133.11.50.196]) by mx1.FreeBSD.org (Postfix) with SMTP id 4F42B43D4C for ; Mon, 19 Apr 2004 09:33:07 -0700 (PDT) (envelope-from tamaru@myn.rcast.u-tokyo.ac.jp) Received: from md002.ecc.u-tokyo.ac.jp ( [133.11.50.202]) by spam003.ecc.u-tokyo.ac.jp (SpamBlock.pst 3.4.5) with ESMTP id for ; Tue, 20 Apr 2004 01:33:05 +0900 Received: from amulet.amuletic.net (YahooBB219001110002.bbtec.net [219.1.110.2]) by md002.ecc.u-tokyo.ac.jp (MOS 3.4.5-GR) with ESMTP id ACP48898 (AUTH via LOGINBEFORESMTP); Tue, 20 Apr 2004 01:33:04 +0900 (JST) Date: Tue, 20 Apr 2004 01:32:50 +0900 Message-ID: From: Hiroharu Tamaru To: "Artem Koutchine" In-Reply-To: <00c201c4260c$6acf2580$0c00a8c0@artem> References: <001801c425e5$9f3a19a0$0c00a8c0@artem> <003c01c425f7$3a3d6b30$0c00a8c0@artem> <00c201c4260c$6acf2580$0c00a8c0@artem> User-Agent: User-Agent: Wanderlust/2.10.0 (Venus) Emacs/21.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII X-IP: 133.11.50.202 X-FROM-DOMAIN: myn.rcast.u-tokyo.ac.jp X-FROM-EMAIL: tamaru@myn.rcast.u-tokyo.ac.jp cc: freebsd-hardware@freebsd.org Subject: Re: Escalde 7506-4LP PCI parity error on Asustek p2b-ds X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2004 16:33:13 -0000 At Mon, 19 Apr 2004 16:46:59 +0400, Artem Koutchine wrote: > > > > > > twe0: PCI parity error: Reseat card, move card or buggy device present. > > > > > (this line is repeated many times). > > > > This is the original message I wrote back then: > > > > > > > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+archive/2002/freebsd-hardware/20020623.freebsd-hardware > > > > > > > > I couldn't confirm if it were safe to ignore the message or > > > > not, but I never had any trouble with it for the 1+ year > > > > that I ran the system. That includes mail alarting and > > > > rebuilding the array through the 3dmd utility. I use to run > > > > JBOD, mirroring and RAID5 on that card. > > > > > > Thank you for replying. I just installed FreeBSD on > > > that dual P2B-DS MB with 2 P3 550Mhz CPUs and > > > run top. What i saw scred me. I saw 50% CPU LOAD on > > > interupts. Nothing really was running, The system is just > > > installed and it was my first login (as root). I thinj this > > > 50% interupts load is somehow related to the error message. > > > But this is just a guess. Is there any way to be make it sure? > > > > I can't remember well, but PRINTING warnings could well had > > been the reason. Try my patch, and see if suppressing the > > printf's themselves could save the CPU. If not, well, it > > could be scheduler related, and you might want to try > > 4-stable instead. > > Did the patch. The message are gone now. However, i still have > about 50% of cpu power wasted on interupts and i have not idea > what is going on and how to figure out what is geenrated so many > interupts and why. Maybe i should first do CVSup to 5-CURRENT > (i am running 5.2-RC2). > And which BIOS version have you? I'd try differrent BIOS versions before cvsup'ing, since BIOS did change the interrupt rates in my case. Have a look at the counter and see how fast you are getting the PE interrupts. sysctl hw.twe.twe_pe ; sleep 10 ; sysctl hw.twe.twe_pe Then flash some other BIOS (maybe the latest one :) ), and see if the rates change. Since, in my case, it was 20/sec -> 0.9/sec, that certainly would give you more CPU cycles to spare... -- Hiroharu Tamaru