From: Jasper Spaans <jasper@vs19.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Pavel Machek <pavel@ucw.cz>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.11-rc2 complains badly aboud badness in local_bh_enable
Date: Sun, 23 Jan 2005 23:41:33 +0100 [thread overview]
Message-ID: <20050123224133.GA4301@spaans.vs19.net> (raw)
In-Reply-To: <1106492276.9269.14.camel@pegasus>
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
Hoi,
On Sun, Jan 23, 2005 at 03:57:56PM +0100, Marcel Holtmann wrote:
> > -rc1 worked fine here. -rc2 complains a lot:
> >
> > Jan 23 12:59:50 amd kernel: Badness in local_bh_enable at kernel/softirq.c:140
[snip]
> the problem is the PPP code (not Bluetooth btw.) like others reported so
> far. I also see the same problem with the external MadWiFi driver.
I'm seeing a similar problem on my machine - one that does not know what ppp
is. Main suspect is the network bridging code in combination with iptables;
the first lines of the message:
Jan 23 07:50:56 spaans kernel: [local_bh_enable+42/109] local_bh_enable+0x2a/0x6d
Jan 23 07:50:56 spaans kernel: [pg0+979444471/1068110848] ipt_do_table+0x2db/0x310 [ip_tables]
Jan 23 07:50:56 spaans kernel: [pg0+942403693/1068110848] ipt_local_out_hook+0x51/0x58 [iptable_filter]
Jan 23 07:50:56 spaans kernel: [nf_iterate+64/137] nf_iterate+0x40/0x89
Jan 23 07:50:56 spaans kernel: [pg0+979631787/1068110848] br_nf_local_out_finish+0x0/0x77 [bridge]
(Btw, this kernel is enhanced with hostap and swsusp2 support, if needed I
can compile a vanilla -rc2)
Groet,
--
Jasper Spaans http://jsp.vs19.net/
23:34:43 up 10203 days, 15:21, 0 users, load average: 6.00 6.06 6.20
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-01-23 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-23 12:01 2.6.11-rc2 complains badly aboud badness in local_bh_enable Pavel Machek
2005-01-23 14:57 ` Marcel Holtmann
2005-01-23 22:41 ` Jasper Spaans [this message]
2005-01-24 0:42 ` Patrick McHardy
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=20050123224133.GA4301@spaans.vs19.net \
--to=jasper@vs19.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=pavel@ucw.cz \
/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