From: Mathias Kretschmer <posting@blx4.net>
To: linux-kernel@vger.kernel.org
Subject: WARNING: at kernel/softirq.c:141 local_bh_enable+0x8b/0xc0()
Date: Thu, 10 Sep 2009 21:39:09 +0200 [thread overview]
Message-ID: <200909102139.09735.posting@blx4.net> (raw)
I reported this before. I'm still seeing this on 2.6.30.6+grsec:
[ 526.823652] ------------[ cut here ]------------
[ 526.823671] WARNING: at kernel/softirq.c:141 local_bh_enable+0x8b/0xc0()
[ 526.823676] Hardware name: empty
[ 526.823680] Modules linked in: iscsi_trgt dummy bonding dvb_usb_cinergyT2
usbtouchscreen forcedeth
[ 526.823697] Pid: 904, comm: mISDN_hfc-pci.1 Not tainted 2.6.30.6-grsec #3
[ 526.823702] Call Trace:
[ 526.823711] [<ffffffff81064a0b>] ? local_bh_enable+0x8b/0xc0
[ 526.823718] [<ffffffff81064a0b>] ? local_bh_enable+0x8b/0xc0
[ 526.823727] [<ffffffff8105ea39>] ? warn_slowpath_common+0x79/0xd0
[ 526.823734] [<ffffffff81064a0b>] ? local_bh_enable+0x8b/0xc0
[ 526.823743] [<ffffffff8151af41>] ? sk_filter+0x41/0xa0
[ 526.823753] [<ffffffff8150002d>] ? sock_queue_rcv_skb+0x5d/0x140
[ 526.823762] [<ffffffff8148fe9f>] ? mISDN_send+0x4f/0xa0
[ 526.823769] [<ffffffff81495250>] ? l2_got_ui+0x0/0x70
[ 526.823775] [<ffffffff81493437>] ? l2up+0x27/0x50
[ 526.823782] [<ffffffff8148eac2>] ? mISDN_FsmEvent+0x82/0x100
[ 526.823788] [<ffffffff814973ba>] ? l2_send+0x6fa/0x980
[ 526.823795] [<ffffffff814993b3>] ? mgr_bcast+0x83/0x160
[ 526.823803] [<ffffffff81492459>] ? mISDNStackd+0x439/0x680
[ 526.823811] [<ffffffff81077730>] ? autoremove_wake_function+0x0/0x30
[ 526.823818] [<ffffffff81492020>] ? mISDNStackd+0x0/0x680
[ 526.823825] [<ffffffff81492020>] ? mISDNStackd+0x0/0x680
[ 526.823831] [<ffffffff81077224>] ? kthread+0x54/0x90
[ 526.823838] [<ffffffff8105bb72>] ? schedule_tail+0x32/0x80
[ 526.823845] [<ffffffff81025baa>] ? child_rip+0xa/0x20
[ 526.823851] [<ffffffff810771d0>] ? kthread+0x0/0x90
[ 526.823857] [<ffffffff81025ba0>] ? child_rip+0x0/0x20
[ 526.823862] ---[ end trace a4fad34479a16c5d ]---
reply other threads:[~2009-09-10 19:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200909102139.09735.posting@blx4.net \
--to=posting@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.