From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 15 21:23:39 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 748D5106566C for ; Mon, 15 Aug 2011 21:23:39 +0000 (UTC) (envelope-from joesuf4@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2A9AB8FC08 for ; Mon, 15 Aug 2011 21:23:38 +0000 (UTC) Received: by vws18 with SMTP id 18so5623232vws.13 for ; Mon, 15 Aug 2011 14:23:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=rH0bT/H477qOplf98yjEn+9ZSlE+iG7cwpUJiu7u6A4=; b=cbBxwrv6ZZt6uBtqXfFJk7WsWlsR3vw0Ns2IRL7X5go9Gx5/t3YpgnzGOJB0F9Pfav AG9gpvmkBP4gTNzNbOIlg1WKEtBJiRLB4xcu8c8o/FsxYwg820Cl1OSgkahAWZ2uD+PH +/NirRZAYBIa55fvBdPOoC7gs538K28Uj4VVw= MIME-Version: 1.0 Received: by 10.220.96.129 with SMTP id h1mr1107276vcn.104.1313441866079; Mon, 15 Aug 2011 13:57:46 -0700 (PDT) Received: by 10.220.190.7 with HTTP; Mon, 15 Aug 2011 13:57:46 -0700 (PDT) In-Reply-To: <4E498326.2060308@FreeBSD.org> References: <4E498326.2060308@FreeBSD.org> Date: Mon, 15 Aug 2011 16:57:46 -0400 Message-ID: From: Joe Schaefer To: Alexander Motin Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: hackers@freebsd.org Subject: Re: Clock stalls on Sabertooth 990FX X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Aug 2011 21:23:39 -0000 On Mon, Aug 15, 2011 at 4:35 PM, Alexander Motin wrote: > On 15.08.2011 22:18, Joe Schaefer wrote: >> >> On Mon, Aug 15, 2011 at 9:31 AM, Joe Schaefer =C2=A0w= rote: >>> >>> On Mon, Aug 15, 2011 at 8:32 AM, Andriy Gapon =C2=A0wr= ote: >>>> >>>> on 13/08/2011 20:16 Joe Schaefer said the following: >>>>> >>>>> Brand new machine with a Phenom II X6 1100T and under chronic load >>>>> the clock will stop running periodically until the machine eventually >>>>> completely >>>>> freezes. =C2=A0Note: during these stalls the kernel is still running,= the >>>>> machine is still >>>>> mostly responsive, it's just that the clock is frozen in time. >>>>> >>>>> I've disabled Turbo mode in the bios and toyed with just about every >>>>> other setting but nothing seems to resolve this problem. =C2=A0Based = on the >>>>> behavior >>>>> of the machine (just making buildworld will eventually kill it, uppin= g >>>>> the -j flag >>>>> just kills it faster), I'm guessing it has something to do with the >>>>> Digi+ VRM features >>>>> but again nothing I've tried modifying in the bios seems to help. >>>>> >>>>> I've tried both 8.2-RELEASE and FreeBSD 9 (head). =C2=A0Running head = now >>>>> with >>>>> a dtrace enabled kernel. >>>>> >>>>> Suggestions? >>>> >>>> On head, start with checking what source is used for driving clocks: >>>> sysctl kern.eventtimer >>> >>> % sysctl kern.eventtimer =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[m= aster] >>> kern.eventtimer.choice: HPET(450) HPET1(450) HPET2(450) LAPIC(400) >>> i8254(100) RTC(0) >>> kern.eventtimer.et.LAPIC.flags: 15 >>> kern.eventtimer.et.LAPIC.frequency: 0 >>> kern.eventtimer.et.LAPIC.quality: 400 >>> kern.eventtimer.et.HPET.flags: 3 >>> kern.eventtimer.et.HPET.frequency: 14318180 >>> kern.eventtimer.et.HPET.quality: 450 >>> kern.eventtimer.et.HPET1.flags: 3 >>> kern.eventtimer.et.HPET1.frequency: 14318180 >>> kern.eventtimer.et.HPET1.quality: 450 >>> kern.eventtimer.et.HPET2.flags: 3 >>> kern.eventtimer.et.HPET2.frequency: 14318180 >>> kern.eventtimer.et.HPET2.quality: 450 >>> kern.eventtimer.et.i8254.flags: 1 >>> kern.eventtimer.et.i8254.frequency: 1193182 >>> kern.eventtimer.et.i8254.quality: 100 >>> kern.eventtimer.et.RTC.flags: 17 >>> kern.eventtimer.et.RTC.frequency: 32768 >>> kern.eventtimer.et.RTC.quality: 0 >>> kern.eventtimer.periodic: 0 >>> kern.eventtimer.timer: HPET >> >> =C2=A0 =C2=A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> Changing this to "i8254" seems to have resolved the stalls. >> I'm running buildworld -j12 without issue. =C2=A0More than willing >> to test out a patch or two against head if anyone's still >> interested, otherwise I've thrown the change into loader.conf >> and will move along quietly. > > 8.2-RELEASE you've mentioned doesn't have event timers subsystem and HPET > timer driver. That makes me think it is strange at least. Can you try als= o > LAPIC timer and do alike experiments with kern.timeocunter? My problems with 8.2-RELEASE may have been network based. I don't recall precisely if the clock was stalling there, my guess is no based on what you wrote. I'll test LAPIC next ... so far so good. Just so I'm clear, you'd like me to tweak kern.timecounter.hardware as well? (Currently it's HPET). > > Also, please check whether kern.timecounter.tc.X.counter value changes fo= r > the selected timercounter and whether you are receiving timer interrupts = in > `vmstat -i` > > -- > Alexander Motin >