From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755698AbZBPJV2 (ORCPT ); Mon, 16 Feb 2009 04:21:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752738AbZBPJVT (ORCPT ); Mon, 16 Feb 2009 04:21:19 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:39761 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751764AbZBPJVS (ORCPT ); Mon, 16 Feb 2009 04:21:18 -0500 Date: Mon, 16 Feb 2009 10:21:00 +0100 From: Ingo Molnar To: Damien Wyart Cc: Peter Zijlstra , Mike Galbraith , =?iso-8859-1?Q?Fr=E9d=E9ric?= Weisbecker , "Rafael J. Wysocki" , Linux Kernel Mailing List , Kernel Testers List Subject: Re: [Bug #12650] Strange load average and ksoftirqd behavior with 2.6.29-rc2-git1 Message-ID: <20090216092100.GH6182@elte.hu> References: <20090215080941.GA2295@localhost.localdomain> <20090215090026.GA31147@elte.hu> <20090215095128.GA3234@localhost.localdomain> <20090215101351.GA23274@elte.hu> <20090215103445.GA2335@localhost.localdomain> <20090215110104.GB31351@elte.hu> <20090215180355.GA2273@localhost.localdomain> <20090215193102.GA16873@elte.hu> <20090216084223.GA2641@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090216084223.GA2641@localhost.localdomain> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Damien Wyart wrote: > > Does it find any TSC time warps? > > Seems not. ok, it's indeed pretty conclusive: | 2 CPUs, running 2 parallel test-tasks. | checking for time-warps via: | - read time stamp counter (RDTSC) instruction (cycle resolution) | | | TSC: 0.32us, fail:0 | i suspect you ran it for at least a couple of minutes, and the ksoftirqd anomaly occured during it, right? Ingo