public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathias Kretschmer <psoting@blx4.net>
To: linux-kernel@vger.kernel.org
Subject: mISDN: WARNING: at kernel/softirq.c:124 local_bh_enable+0x8f/0xb0()
Date: Fri, 5 Jun 2009 00:07:12 +0200	[thread overview]
Message-ID: <200906050007.13507.psoting@blx4.net> (raw)
In-Reply-To: <20090604232610.GA16053@intel.com>

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]  [<ffffffff8025909a>] warn_slowpath+0xea/0x160
[88563.318149]  [<ffffffff8025ee0f>] local_bh_enable+0x8f/0xb0
[88563.318152]  [<ffffffff8065f284>] sk_filter+0x44/0xa0
[88563.318154]  [<ffffffff8064548d>] sock_queue_rcv_skb+0x5d/0x120
[88563.318156]  [<ffffffff8060410f>] mISDN_send+0x4f/0xa0
[88563.318159]  [<ffffffff8060790e>] l2up_create+0x7e/0x100
[88563.318161]  [<ffffffff8060b6e0>] l2_got_tei+0x0/0x90
[88563.318163]  [<ffffffff8060b722>] l2_got_tei+0x42/0x90
[88563.318164]  [<ffffffff80602d32>] mISDN_FsmEvent+0x82/0x100
[88563.318167]  [<ffffffff8060cb00>] tei_id_assign+0x0/0x120
[88563.318168]  [<ffffffff80602d32>] mISDN_FsmEvent+0x82/0x100
[88563.318170]  [<ffffffff8060e373>] mgr_send+0x4d3/0x660
[88563.318172]  [<ffffffff8061ac8e>] hfcpci_l2l1D+0x19e/0x2f0
[88563.318174]  [<ffffffff80606591>] mISDNStackd+0x431/0x680
[88563.318177]  [<ffffffff80270950>] autoremove_wake_function+0x0/0x30
[88563.318179]  [<ffffffff80606160>] mISDNStackd+0x0/0x680
[88563.318181]  [<ffffffff80270547>] kthread+0x47/0x80
[88563.318183]  [<ffffffff802226fa>] child_rip+0xa/0x20
[88563.318185]  [<ffffffff80270500>] kthread+0x0/0x80
[88563.318186]  [<ffffffff802226f0>] child_rip+0x0/0x20
[88563.318188] ---[ end trace 2a7bb9b2f669de5a ]---


  parent reply	other threads:[~2009-06-04 23:10 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03  9:09 linux-next: Tree for June 3 Stephen Rothwell
2009-06-03 15:22 ` linux-next: Tree for June 3 (rfkill) Randy Dunlap
2009-06-03 15:29   ` Johannes Berg
2009-06-03 15:47     ` Gábor Stefanik
2009-06-03 15:53       ` Johannes Berg
2009-06-03 16:27   ` Johannes Berg
2009-06-03 17:20   ` Randy Dunlap
2009-06-03 17:33     ` Johannes Berg
2009-06-03 22:48       ` Inaky Perez-Gonzalez
2009-06-03 15:24 ` linux-next: Tree for June 3 (staging) Randy Dunlap
2009-06-03 15:25   ` Greg KH
2009-06-03 15:40     ` Randy Dunlap
2009-06-03 23:11       ` Greg KH
2009-06-04  2:04         ` Gao, Yunpeng
2009-06-04 23:26         ` Yunpeng Gao
2009-06-04 16:00           ` Greg KH
2009-06-04 17:52           ` Greg KH
2009-06-05  3:31             ` Gao, Yunpeng
2009-06-05 18:58               ` Bartlomiej Zolnierkiewicz
2009-06-05 19:22                 ` Greg KH
2009-06-06 16:30                   ` Yunpeng Gao
2009-06-06  8:37                 ` Gao, Yunpeng
2009-06-04 22:07           ` Mathias Kretschmer [this message]
2009-06-05  2:59             ` mISDN: WARNING: at kernel/softirq.c:124 local_bh_enable+0x8f/0xb0() Andrew Morton
2009-06-05 10:01               ` Karsten Keil
2009-06-09 13:05                 ` Karsten Keil
2009-06-22 22:37                   ` Mathias Kretschmer
2009-06-05 18:45           ` linux-next: Tree for June 3 (staging) Bartlomiej Zolnierkiewicz
2009-06-05 20:15             ` Alan Cox
2009-06-06  8:35               ` Gao, Yunpeng
2009-06-03 15:44 ` linux-next: Tree for June 3 (staging++) Randy Dunlap
2009-06-03 15:50 ` linux-next: Tree for June 3 (driver core) Randy Dunlap
2009-06-03 21:22   ` Greg KH
2009-06-03 21:44     ` Eric W. Biederman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200906050007.13507.psoting@blx4.net \
    --to=psoting@blx4.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox