From owner-freebsd-stable Sun Oct 14 10:53:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gigi.excite.com (gigi.excite.com [199.172.152.110]) by hub.freebsd.org (Postfix) with ESMTP id C219037B408; Sun, 14 Oct 2001 10:53:42 -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 <20011014175342.UKXH17391.gigi.excite.com@patti.excite.com>; Sun, 14 Oct 2001 10:53:42 -0700 Message-ID: <12199010.1003082022454.JavaMail.imail@patti.excite.com> Date: Sun, 14 Oct 2001 10:53:41 -0700 (PDT) From: Matt Sykes To: John Hay 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-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 11 Oct 2001 08:12:58 +0200 (SAT), John Hay wrote: > > > > kernel: 4.4-STABLE motherboard: P2L97-DS, dual Pentium II 300MHZ > > > > top shows 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% > > idle > > > > WCPU and CPU show 0.00% for all processes in top and ps. > > > > Go and look in the old freebsd-smp archives for this message: > > Message-Id: <199906151902.VAA96921@midten.fast.no> > > It is message by Tor Egge and describes the problem. I have the > same motherboard and that patch did the job. I'm running -current > nowadays and the code does not look like that anymore so i have > changed the patch for current, but I do not have new patches for > -stable, so if that doesn't aplly anymore you will have to tweak > them by hand. Thanks to everyone who responded. It's good to know at least I'm not going crazy; that however meticulously I was following the instructions for kernel config and install, it was still broken because I needed this patch. Unfortunately the patch cannot be applied even manually (I happen to be a programmer) to 4.4-STABLE. The patch expects pcici_t types, whereas the -stable source needs device_t types (maybe they are just typedefs of one another, I did a grep -r but couldn't find the definition). Much more importantly, though ... why isn't this patch included in 4.4-STABLE? When you say you changed the patch for -current, does this mean it is IN -current, or that you have a patch which you re-apply every time you cvsup? If the latter, why isn't it in -current as well? The number of hours I've spent on this problem is now embarassingly long --- looking through google, looking through mail archives, disabling apm on/off with flags on/off with patch (the one that didn't work) applied/not-applied then rebuilding world and kernel each time according to /usr/src/UPDATING, then testing with bios 1.005/1.008 and kern.timecounter.method=0/1. What can I do to assure that nobody has to do this again? And, since I still have a broken FreeBSD kernel, how do I to fix it? Am I just out of luck with this motherboard? --Matt _______________________________________________________ Send a cool gift with your E-Card http://www.bluemountain.com/giftcenter/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message