From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752470AbYIVH0T (ORCPT ); Mon, 22 Sep 2008 03:26:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751757AbYIVH0I (ORCPT ); Mon, 22 Sep 2008 03:26:08 -0400 Received: from nf-out-0910.google.com ([64.233.182.185]:62611 "EHLO nf-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751749AbYIVH0H (ORCPT ); Mon, 22 Sep 2008 03:26:07 -0400 Message-ID: Date: Mon, 22 Sep 2008 00:26:02 -0700 From: "Steven Noonan" To: "Luis R. Rodriguez" Subject: Re: [ath9k-devel] ath9k: massive unexplained latency in 2.6.27 (rc5, rc6, probably others) Cc: "Luis Rodriguez" , linux-wireless , LKML , "Senthilkumar Balasubramanian" , "ath9k-devel@lists.ath9k.org" , "Johannes Berg" , "Ingo Molnar" In-Reply-To: <20080922065453.GD19580@tesla> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <43e72e890809191813n95579f5h83e92b0ba1f95a44@mail.gmail.com> <43e72e890809201357y1413a151r85aad7cc16440cf4@mail.gmail.com> <1221944338.3023.8.camel@johannes.berg> <43e72e890809201403w2c4511fdv2fe26bbcf49ccdd7@mail.gmail.com> <43e72e890809201426x61c94bfej2dcda1c178be81b@mail.gmail.com> <20080922065453.GD19580@tesla> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Sep 21, 2008 at 11:54 PM, Luis R. Rodriguez wrote: > On Sat, Sep 20, 2008 at 06:48:05PM -0700, Steven Noonan wrote: >> >> OK, here's the time index at which it b0rked: >> >> 18:28:42 sum 1155.00 >> 18:28:43 sum 1339.00 >> 18:28:44 sum 18355.00 >> 18:28:45 sum 17845.45 >> >> And the entire log of the minute 18:28 is here: >> http://www.uplinklabs.net/~tycho/linux/18.28.00-59.log.gz >> >> It looks pretty crazy. > > Thanks, I'll take a look when I get a chance (remember aggretion > is in the queue too) unless someone beats me to it. > You may want to take a quick look at it now. I certainly don't mean you should push aggregation aside, but the log looks kind of screwy at 18:28:43 (look at line 4972 to see what I mean). It looks as though it did printk()s from multiple threads with no locking mechanism. It's possible I will need to re-capture the error, and I'd like to know if this log will help or not. - Steven