From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754203AbZFEKBU (ORCPT ); Fri, 5 Jun 2009 06:01:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751433AbZFEKBJ (ORCPT ); Fri, 5 Jun 2009 06:01:09 -0400 Received: from moutng.kundenserver.de ([212.227.126.177]:65501 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750984AbZFEKBI (ORCPT ); Fri, 5 Jun 2009 06:01:08 -0400 From: Karsten Keil Reply-To: isdn@linux-pingi.de To: Andrew Morton Subject: Re: mISDN: WARNING: at kernel/softirq.c:124 local_bh_enable+0x8f/0xb0() Date: Fri, 5 Jun 2009 12:01:03 +0200 User-Agent: KMail/1.11.1 (Linux/2.6.27.21-0.1-default; KDE/4.2.1; x86_64; ; ) Cc: Mathias Kretschmer , linux-kernel@vger.kernel.org, netdev@vger.kernel.org References: <20090603190952.2dd0cc70.sfr@canb.auug.org.au> <200906050007.13507.psoting@blx4.net> <20090604195948.9c7af254.akpm@linux-foundation.org> In-Reply-To: <20090604195948.9c7af254.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906051201.04185.isdn@linux-pingi.de> X-Provags-ID: V01U2FsdGVkX18t3vDP0mkkiKg2qoVQSd6NM1LMHnQgL25KHTQ 0oiV16li2oF1M274THIBE5w8ViMcnTDOGjItAeLBoaMMdxXEzE YeNjuE+1BopOYnTVkicnIZvAtSksQzM Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, I'm currently see this too from time to time, but have no idea about it. On Freitag, 5. Juni 2009 04:59:48 Andrew Morton wrote: > (cc's added) > > On Fri, 5 Jun 2009 00:07:12 +0200 Mathias Kretschmer wrote: > > Hi *, > > > > the following pops up from time to time when I place a call (might also > > happened on incoming calls). > > > > machine is an AMD K8 dual core running a x86_64 2.6.29.4-grsec kernel. > > > > please, let me know if you need more details. > > > > cheers, > > > > Mathias > > > > [88563.318126] ------------[ cut here ]------------ > > [88563.318129] WARNING: at kernel/softirq.c:124 > > local_bh_enable+0x8f/0xb0() [88563.318130] Hardware name: empty > > [88563.318132] Modules linked in: usbtouchscreen dvb_usb_cinergyT2 dummy > > bonding snd_emu10k1 snd_rawmidi snd_ac97_codec ath9k ac97_bus snd_pcm > > snd_page_alloc snd_util_mem forcedeth snd_hwdep > > [88563.318141] Pid: 826, comm: mISDN_hfc-pci.1 Not tainted 2.6.29.4-grsec > > #13 [88563.318142] Call Trace: > > [88563.318147] [] warn_slowpath+0xea/0x160 > > [88563.318149] [] local_bh_enable+0x8f/0xb0 > > [88563.318152] [] sk_filter+0x44/0xa0 > > [88563.318154] [] sock_queue_rcv_skb+0x5d/0x120 > > [88563.318156] [] mISDN_send+0x4f/0xa0 > > [88563.318159] [] l2up_create+0x7e/0x100 > > [88563.318161] [] l2_got_tei+0x0/0x90 > > [88563.318163] [] l2_got_tei+0x42/0x90 > > [88563.318164] [] mISDN_FsmEvent+0x82/0x100 > > [88563.318167] [] tei_id_assign+0x0/0x120 > > [88563.318168] [] mISDN_FsmEvent+0x82/0x100 > > [88563.318170] [] mgr_send+0x4d3/0x660 > > [88563.318172] [] hfcpci_l2l1D+0x19e/0x2f0 > > [88563.318174] [] mISDNStackd+0x431/0x680 > > [88563.318177] [] autoremove_wake_function+0x0/0x30 > > [88563.318179] [] mISDNStackd+0x0/0x680 > > [88563.318181] [] kthread+0x47/0x80 > > [88563.318183] [] child_rip+0xa/0x20 > > [88563.318185] [] kthread+0x0/0x80 > > [88563.318186] [] child_rip+0x0/0x20 > > [88563.318188] ---[ end trace 2a7bb9b2f669de5a ]--- > > hm, tricky, who disabled interrupts? Yes, indeed I have no idea what exactely is going on. > It could be > > spin_lock_irqsave(&hc->lock, flags); > > in hfcpci_l2l1D(). I do not think that this function is really in the call trace, in my dumps I see also traces without hfcpci_l2l1D in it. And I see no way back to mgr_send from hfcpci_l2l1D from the design the HW functions are decoupled from the stack thread via queues, so here should be no direct callback. The common part is, that it seems always happen on successful TEI assign. Karsten