Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760592AbZJKLvg (ORCPT ); Sun, 11 Oct 2009 07:51:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757056AbZJKLvf (ORCPT ); Sun, 11 Oct 2009 07:51:35 -0400 Received: from posthamster.phnxsoft.com ([195.227.45.4]:2283 "EHLO posthamster.phnxsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757037AbZJKLvf (ORCPT ); Sun, 11 Oct 2009 07:51:35 -0400 X-Greylist: delayed 1929 seconds by postgrey-1.27 at vger.kernel.org; Sun, 11 Oct 2009 07:51:34 EDT Message-ID: <4AD1BF06.3050103@phoenixsoftware.de> Date: Sun, 11 Oct 2009 13:18:30 +0200 From: Tilman Schmidt User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Johannes Berg CC: Dave Young , linux-kernel@vger.kernel.org, tglx@linutronix.de, linux-wireless , "David S. Miller" Subject: Re: NOHZ: local_softirq_pending 08 References: <20091011095217.GA2200@darkstar> <1255255735.4095.53.camel@johannes.local> In-Reply-To: <1255255735.4095.53.camel@johannes.local> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Score: -0.414 () AWL,BAYES_50,RDNS_NONE Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1123 Lines: 31 On Sun, 11 Oct 2009 12:08:55 +0200, Johannes Berg wrote: > On Sun, 2009-10-11 at 17:52 +0800, Dave Young wrote: > >> With kernel 2.6.32-rc3-00052-g0eca52a I got following KERN_ERR >> messages just while using firefox: >> >> [ 130.527399] NOHZ: local_softirq_pending 08 > >> Any idea? or known issue? > > Are you using b43 (or wl12x1)? If so, it's a known issue, but the driver > was recently left without an active maintainer in a brouhaha about a bug > fix. > > Cf. http://thread.gmane.org/gmane.linux.kernel.wireless.general/39440 Can you explain a bit more what that message is about? I am encountering it in a completely different context (PPP over ISDN) and I would like to know where to start looking for the cause and developing a fix. The thread on linux.kernel.wireless.general only seems to address the specific situation in the wireless stack. Thanks, Tilman -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/