From owner-freebsd-current@FreeBSD.ORG Sat Aug 21 13:18:22 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EDAE210656A4 for ; Sat, 21 Aug 2010 13:18:22 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 866AC8FC1F for ; Sat, 21 Aug 2010 13:18:22 +0000 (UTC) Received: by wwi18 with SMTP id 18so1382642wwi.31 for ; Sat, 21 Aug 2010 06:18:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to :in-reply-to:references:date:message-id:subject:from:to:content-type; bh=DxjiBAntRF2mpJ22AEmqY+SNKd6pa79KUg/m21/Hx1o=; b=tii7iH/EXbS3vS9Lwzkc+8bQhlVjJglh9TpIqoyv6HHfUbbVelSbp7A5LIeYYIEZZd GB9iZK7iY1B/mXL3aGPdj+A2iUM5o567X8yUKBDUjjEd2PBsQyZMyswN4McZR2IZhL9j s2TMhewdMVm20/sAXnNLoB1la4uLBI9HBL0Po= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; b=ohQu3up3GpMr3nsKBwC3jgCgTJqfaqzMJT7fzgIh4yQxNZhSxRIT0szbC6TrM5eUfV /JcObX0Ek/K1oYMHuO2QYjr3DJ22xaR1Pkc359Pp/3IUiYiScWcR8BcHd97Mb7H9iy7W YdXH/SJYdPoS4ANgO84ONq/eYAFG7/H8qzs90= MIME-Version: 1.0 Received: by 10.216.178.130 with SMTP id f2mr2436325wem.101.1282396701437; Sat, 21 Aug 2010 06:18:21 -0700 (PDT) Received: by 10.216.183.212 with HTTP; Sat, 21 Aug 2010 06:18:21 -0700 (PDT) In-Reply-To: References: Date: Sat, 21 Aug 2010 13:18:21 +0000 Message-ID: From: "b. f." To: freebsd-current@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Fwd: Latest intr problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bf1783@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Aug 2010 13:18:23 -0000 Andriy Gapon wrote: >on 21/08/2010 12:35 Andriy Gapon said the following: >> I feel like you might be having a problem with clocks... > >FWIW, I am reading this document http://edc.intel.com/Link.aspx?id=1484 >and I see this sentence: "All of the clocks in the processor core are >stopped in the C3 state". > >I see that you have C3 state enabled and it's regularly entered: >dev.cpu.0.cx_usage: 0.00% 5.51% 94.48% last 305us I don't think this accounts for all of his problems, unless his machine has an unusual configuration. Alexander and I recommended that he try different clocks, and just recently, for example, he wrote that he had used: loader.conf hint.apic.0.clock="0" hint.atrtc.0.clock="0" hint.attimer.0.clock="0" hint.hpet.0.legacy_route="1" machdep.disable_rtc_set="1" kern.eventtimer.timer2="HPET" kern.eventtimer.timer1="NONE" (Or, if available, HPET1, ...) kern.eventtimer.singlemul="1" sysctl.conf: kern.timecounter.hardware=HPET and reported that it did not help. The HPET doesn't usually suffer from the problem that you are describing, right? b.