From owner-freebsd-questions Mon Oct 15 15:27:58 2001 Delivered-To: freebsd-questions@freebsd.org Received: from gigi.excite.com (gigi.excite.com [199.172.152.110]) by hub.freebsd.org (Postfix) with ESMTP id 2230137B401; Mon, 15 Oct 2001 15:27:48 -0700 (PDT) Received: from patti.excite.com ([199.172.148.159]) by gigi.excite.com (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <20011015222747.FQLM17391.gigi.excite.com@patti.excite.com>; Mon, 15 Oct 2001 15:27:47 -0700 Message-ID: <19663931.1003184867692.JavaMail.imail@patti.excite.com> Date: Mon, 15 Oct 2001 15:27:47 -0700 (PDT) From: Matt Sykes To: Jason Andresen Subject: Re: 0.00% CPU for all processes Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Excite Inbox X-Sender-Ip: 66.3.230.250 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 15 Oct 2001 17:23:48 -0400, Jason Andresen wrote: > Matt Sykes wrote: > > > > On Mon, 15 Oct 2001 18:06:17 +0200 (SAT), John Hay wrote: > > > > > > > I don't know. If this patch ever do go in, it will probably > > > > > have to be protected with a "#ifdef BROKEN_P2L97-DS" or > > > > > something similar. > > > > > > > > And, since I still have a broken FreeBSD kernel, how do I to > > > > > > fix it? Am I just out of luck with this motherboard? > > > > > > > Well if you are brave enough, you can try my patch. :-) If you > > > > > see the message "Disabled Device 13 trap SMI for access to RTC > > > > > chip" during the boot phase, you will know that it did execute > > > > > the code in the patch. > > > > > > Hey thanks alot, I'll give it a try. > > > > > > Before I do, a few questions: can you give me the exact line of > > > > your kernel config file for device apm0 (which flags enabled or > > > > disabled)? Or do you not use device apm0 in kernel config? Is > > > > apm enabled or disabled in the bios? What is your > > > > kern.timecounter.method? Which bios revision (I only have access > > > > to 1.005 and 1.008)? > > > > > I don't have physical access to the machine at the moment, it is at > > > work, but IIRC the bios is ver 1.008 and apm was disabled. I don't > > > have apm in the kernel and it is using the PIIX timecounter and I > > > set it to 3580676. > > > > Looks like it works! > > > > In top, cvsup gradually comes up to about 40%, stays there a while, > > then disappears (I couldn't think of another longish process to test > > with). I guess that's correct. Before it would start at 2% then > > quickly go back to 0%. > > > > dmesg says "Timecounter 'PIIX' frequency 3579545"; I guess that's > > alright. > > > > One thing which surprises me, though --- all other processes are zero. > > Is this normal? This is my first time seeing FreeBSD run. I have an > > identical box here running linux (and each box runs a minimum of > > services), where at least top will show nonzero CPU percentage in top, > > usually around 0.5%. Does linux have more fine-grained timing, or is > > it cheating, or does the margin of error render this test essentially > > meaningless anyway? > > It's not unusual to see most of your processes at 0.00% in FreeBSD. > From the answers I've recieved, seems I wasn't clear enough. I know that most of idle processes should be zero --- my point is that top should show up in top, and since it does in linux and with other FreeBSD top outputs I've seen, this leads me to believe my kernel timer is still broken (and it works on this same box running linux). _______________________________________________________ Send a cool gift with your E-Card http://www.bluemountain.com/giftcenter/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message