From owner-freebsd-stable@FreeBSD.ORG Thu Dec 10 13:59:28 2009 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 9FABB1065676 for ; Thu, 10 Dec 2009 13:59:28 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 5C9338FC13 for ; Thu, 10 Dec 2009 13:59:28 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id E83C646B2E; Thu, 10 Dec 2009 08:59:27 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 2E6528A01D; Thu, 10 Dec 2009 08:59:27 -0500 (EST) From: John Baldwin To: freebsd-stable@freebsd.org Date: Thu, 10 Dec 2009 08:48:31 -0500 User-Agent: KMail/1.12.1 (FreeBSD/7.2-CBSD-20091103; KDE/4.3.1; amd64; ; ) References: <30f6a6b39e2bdbf45c8ce69ee593831a.HRCIM@webmail.1command.com> <200912090950.37686.jhb@freebsd.org> <101228207f5fbe0513b5b034d15b8ab7.HRCIM@webmail.1command.com> In-Reply-To: <101228207f5fbe0513b5b034d15b8ab7.HRCIM@webmail.1command.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <200912100848.31916.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Thu, 10 Dec 2009 08:59:27 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Chris H Subject: Re: ACPI Error: A valid RSDP was not found 20090521 tbxfroot-309 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Dec 2009 13:59:28 -0000 On Wednesday 09 December 2009 8:52:06 pm Chris H wrote: > On Wed, December 9, 2009 6:50 am, John Baldwin wrote: > > On Tuesday 08 December 2009 7:06:18 pm Chris H wrote: > > > >> Greetings, > >> I am receiving the following in dmesg (verbose) during boot in 8-RELEASE > >> (GENERIC) > >> cvsuped 2009-12-08 @1am: ACPI Error: A valid RSDP was not found 20090521 > >> tbxfroot-309 > >> > >> As I create the KERNCONF for this machine, I want to confirm that this > >> message is caused by the fact that APM is shut off in the BIOS, and won't > >> cause any averse problems. We're having issues with "timeout" errors on some > >> 50 TYAN server MB's > >> since 7-RELEASE regarding the disk media (no matter how many different drives > >> we use). So as I attempt to create a STABLE - in the sense that the servers > >> are reliable, I want to eliminate any potential issues. > >> > >> more (informational) "noise" follows: > > > > You can ignore the message, I do think it is due to disabling ACPI in your > > BIOS. Do you have problems when ACPI is enabled? ACPI is generally going to > > be more reliable than !ACPI in the future as it seems many BIOS vendors no longer > > test the !ACPI case as much (e.g. I've seen Intel motherboards with incomplete > > or incorrect MP Tables because no commercial OS uses the MP Table anymore). > > Hello, and thank you very much for your reply. > So the message is simply "informative" - good to know. > As to the ACPI. Closer examination seemed to indicate the BIOS was incomplete. > While I could have flashed it, assuming that it 1) would have all current updates > 2) it would then also be complete > I opted to simply take another new board off the shelf and try again. This time, > taking your advice, and /enabling/ full ACPI. I performed an install, and just > now cvsupped src && ports. It's in the process of building world/kernel as I > write this reply. Hope all turns out well - "Fingers crossed". :) Ok. > If you (or anyone else) can tell me... > I have had issues with periodic "timeouts" with disks (SCSI,ATA && CD/DVD ROMS) > ever since late 6. After experimenting with /many/ kernels. I'm left with the > suspicion the it has to do with SCHED_4BSD vs. SCHED_ULE. In other words, ever > since SCHED_ULE became default/preferred most of the PIII based boards have > exhibited this anomaly. Often the "retries" aren't exhausted, and they recover. > But many times they don't which will lead to freeze that requires "bouncing" the > machine, and performing FSCK(8). I haven't seen anything in UPDATING. But wonder; > should I assume that anything in the PIII category /requires/ SCHED_4BSD. Or > would it be better to tune a kernel via SYSCTL(8)? Hmmm, there isn't anything CPU-specific in ULE vs 4BSD, and I would expect ULE to work fine on a PIII. I would generally expect device timeouts to be more of a driver issue than a scheduler issue. -- John Baldwin