From owner-freebsd-current@FreeBSD.ORG Sat Aug 21 14:00:03 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 07D3F106564A for ; Sat, 21 Aug 2010 14:00:03 +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 79F958FC1E for ; Sat, 21 Aug 2010 14:00:02 +0000 (UTC) Received: by wwi18 with SMTP id 18so1421494wwi.31 for ; Sat, 21 Aug 2010 07:00:01 -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:cc :content-type; bh=BsZW+huqhwUkYEv0K48lCrTXEmmsZh0zKu8Hcl/h69c=; b=CE9jml217KK+ACb7QfuSlEBUzWvfZYiF4f/jI60SxeD0Fk3lnI5vd9q3WON1VCL6Fj besrn4IW/hi24hCyKWe8r6MiY9n2dHZm35j1TQ/MSGHDM8w6NwPGDjBd6F8l7YFrx3ee ce1MLybpe7B6EV6w417CxIb0vk45mm6e9NZp8= 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:cc:content-type; b=vYsAgHtpBpPowh8576rGsbdOQBiT3mz3OYgZtU1THn6U/aGO45FLZUZAnQRPD5vHJw pLOrURZ/DN3fsqwsBHaKwR13rOC1f0HFUbHGVIVRMnbJSdGyzMU6mKjfGxdX/U1sthsi eLc2pUhfCLaL5zqsxtQhqOo/qwISQ6JFCqd+8= MIME-Version: 1.0 Received: by 10.227.133.18 with SMTP id d18mr2572321wbt.33.1282399201392; Sat, 21 Aug 2010 07:00:01 -0700 (PDT) Received: by 10.216.183.212 with HTTP; Sat, 21 Aug 2010 07:00:01 -0700 (PDT) In-Reply-To: <4C6FD562.1030700@icyb.net.ua> References: <4C6FD562.1030700@icyb.net.ua> Date: Sat, 21 Aug 2010 14:00:01 +0000 Message-ID: From: "b. f." To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: 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 14:00:03 -0000 On 8/21/10, Andriy Gapon wrote: > on 21/08/2010 16:04 b. f. said the following: >> Andriy Gapon wrote: >>> on 21/08/2010 12:35 Andriy Gapon said the following: > Well, let's try to not muddy the waters prematurely. It's not premature to say that his machine has some peculiar clock-related features, that should be kept in mind while testing. This came up earlier: http://lists.freebsd.org/pipermail/freebsd-current/2010-June/018179.html and is partly why I recommended some of the settings below. > >> 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" > > Well, I don't see much point in doing the above in this situation. We suspected clock problems as well, and were trying to isolate the problem taking other clocks completely out of consideration. Probably the legacy_route could have been discarded, but in that case the second eventtimer would have to be emulated with NONE. > >> machdep.disable_rtc_set="1" >> kern.eventtimer.timer2="HPET" >> kern.eventtimer.timer1="NONE" (Or, if available, HPET1, ...) > > So, what was actually used here? > I don't think that NONE is a good idea. Doug will have to answer that -- he wasn't specific in his reply. >> 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? > > Right. > Still I would prefer that Doug would do the cleaner experiment(s) that I > suggested. And if the problem persists then elimination of LAPIC timer > would > make the picture clearer (for me). Sure, let's see if restraining the C-states yields any results. > > P.S. > I still think that KTR+schedgraph would be the best tool here. Attilio recommended that originally, then (reportedly) changed his mind and said to try dtrace. I brought it up again earlier, and Doug said that he would make some experiments. b.