From owner-freebsd-questions Mon Oct 15 8:28:44 2001 Delivered-To: freebsd-questions@freebsd.org Received: from ewey.excite.com (ewey-rwcmta.excite.com [198.3.99.191]) by hub.freebsd.org (Postfix) with ESMTP id 72E4B37B403; Mon, 15 Oct 2001 08:28:37 -0700 (PDT) Received: from patti.excite.com ([199.172.148.159]) by ewey.excite.com (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <20011015152836.EOBY16702.ewey.excite.com@patti.excite.com>; Mon, 15 Oct 2001 08:28:36 -0700 Message-ID: <29848144.1003159716498.JavaMail.imail@patti.excite.com> Date: Mon, 15 Oct 2001 08:28:33 -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-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 08:26:17 +0200 (SAT), John Hay wrote: > Ok, I have tried to port my -current version to stable. It does > compile, but I don't know what it will do when you run it > though. :-) I have added it to the end. > > 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? > Well it isn't part of -current either. At that time the feeling was > that it shouldn't become part of FreeBSD, so I have just kept it as > a local patch and fixed it everytime it broke when I upgraded to a > new -current. > > What can I do to assure that nobody has to do this again? > 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)? Thanks again. --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-questions" in the body of the message