From owner-freebsd-stable@FreeBSD.ORG Thu Oct 9 05:00:33 2008 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 2BC2910656A5 for ; Thu, 9 Oct 2008 05:00:33 +0000 (UTC) (envelope-from bf2006a@yahoo.com) Received: from web39105.mail.mud.yahoo.com (web39105.mail.mud.yahoo.com [209.191.87.224]) by mx1.freebsd.org (Postfix) with SMTP id F35A88FC21 for ; Thu, 9 Oct 2008 05:00:32 +0000 (UTC) (envelope-from bf2006a@yahoo.com) Received: (qmail 35434 invoked by uid 60001); 9 Oct 2008 05:00:32 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Message-ID; b=RXRTnkNtlXfN/cfMY2EKOiawMGRKEHfjI6sazidcXvY7mOYY6OLhZ52aTrvRU4prA9JGUd22NSC4BpwLkjWpMSi7nZ3KKZNGuJWiCGvCM3l7ViDGT+x9bN9NlSSLyycoqCRRSn19Ali+gELCoCpD0E2r+ZMR/IACLTVQw173CHM=; X-YMail-OSG: adIJWGcVM1l_LwFj5_NfQzsXealUHshlI8h8yRCrGeL9olT2ToEmqUleBxxYQRf72g-- Received: from [81.169.137.209] by web39105.mail.mud.yahoo.com via HTTP; Wed, 08 Oct 2008 22:00:32 PDT X-Mailer: YahooMailWebService/0.7.218.2 Date: Wed, 8 Oct 2008 22:00:32 -0700 (PDT) From: bf To: Jeremy Chadwick , freebsd-stable@freebsd.org In-Reply-To: <20081008183652.GA83351@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <501797.33750.qm@web39105.mail.mud.yahoo.com> Cc: Subject: Re: Recent Problems with RELENG_7 i386 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bf2006a@yahoo.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Oct 2008 05:00:33 -0000 --- On Wed, 10/8/08, Jeremy Chadwick wrote: > From: Jeremy Chadwick > Subject: Re: Recent Problems with RELENG_7 i386 > To: "bf" > Cc: freebsd-stable@freebsd.org > Date: Wednesday, October 8, 2008, 2:36 PM > On Wed, Oct 08, 2008 at 10:19:47AM -0700, bf wrote: > > After updating to RELENG_7 i386 of this weekend, I > have been having problems > > with my machine. When booting normally, the system > slows or hangs at the > > login prompt. If I am able to continue past the > prompt, I sometimes experience > > erratic mouse behavior, and a subsequent hang, after > varying lengths of time, > > even under light workloads. The same problem does not > seem to occur in > > single-user mode, and did not occur with the RELENG_7 > i386 of just over a > > week ago. I have been unable to obtain crashdumps so > far, and the only > > log messages I can find that weren't present > before are notices like those > > recorded below: > > > > Oct 8 11:00:40 myhost kernel: t_delta > 15.fd80bdcb75b60200 too short > > This comes from src/sys/kern/kern_tc.c, around line 908. > I'm not > familiar with the kernel, but two ideas come to mind: > > 1) If you have Intel SpeedStep (EIST) or AMD > Cool'n'Quiet enabled in > your BIOS, try disabling it, > > 2) If you're using powerd, disable it (I don't see > it enabled), > > 3) Try keeping HZ at 1000 (the default). > Thanks, Jeremy, for taking the time to consider my question and reply. My CPU is pre-Cool'n'Quiet, and as far as I can tell I had disabled all forms of power management that may affect the clock speeds. I have found that by raising kern.hz to 250, or by using the default, I no longer receive the t_delta is too short messages, and the other problems are no longer apparent. My question is: why did this occur now? I have been using a similar configuration for months now without any apparent problems. My original goal in using a lower kern.hz was to avoid burdening my machine with excessive context switching. I saw the relevant section of kern_tc.c before I wrote my first message, but when skimming through the changes in RELENG_7 over the past week or two, I couldn't see any commit that may have directly affected kernel timekeeping. Has some new workload been imposed on the system by recent changes, that may have made a kern.hz of 100 insufficient? Is this tuneable setting properly implemented, so that all parts of the base system are using it's current value rather than the default? Could some of my hardware, such as my RTC, be malfunctioning? Regards, b. > -- > | Jeremy Chadwick jdc at > parodius.com | > | Parodius Networking > http://www.parodius.com/ | > | UNIX Systems Administrator Mountain > View, CA, USA | > | Making life hard for others since 1977. PGP: > 4BD6C0CB |