From: Steve Snyder <R00020C@freescale.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: "Badness in local_bh_enable" - a reasonable fix?
Date: Wed, 26 Oct 2005 16:01:19 -0400 [thread overview]
Message-ID: <200510261601.19369.R00020C@freescale.com> (raw)
In-Reply-To: <1130355615.3339.10.camel@laptopd505.fenrus.org>
On Wednesday 26 October 2005 15:40, Arjan van de Ven wrote:
> On Wed, 2005-10-26 at 15:34 -0400, Steve Snyder wrote:
> > [ I observed the following on a Fedora Core 3 system, running kernel
> > 2.6.12-1.1380_FC3. I am posting this here because a quick Googling
> > indicates that the problem is not specific to this environment. ]
> >
> > Today I found my system log filled with the error shown below.
> > Reading a 366MB file across a NFS mount results in over 6300
> > occurrences of the error being written to the system log of the NFS
> > server.
> >
> > I have 2 network interfaces in the NFS server machine, a standard
> > kernel Ethernet device driver and my own Ultra-Wide Band (UWB) device
> > driver. (In the error shown below the references to "fsuwbpci" are my
> > driver.) This problem is not seen when using the Ethernet interface,
> > but is perfectly consistent when reading a NFS-mounted file across the
> > UWB interface. Therefore there is a problem with my code.
> >
> > I quickly established that the error came from within this routine:
> >
>
> > -------------------------------------------
> >
> > kernel: Badness in local_bh_enable at kernel/softirq.c:140 (Tainted: P )
>
>
>
> hmmm binary module? please try without.
What, you mean the driver? No, it is built from source against the
installed & running Fedora Core 3 kernel version 2.6.12-1.1380_FC3.
next prev parent reply other threads:[~2005-10-26 20:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 19:34 Steve Snyder
2005-10-26 19:40 ` Arjan van de Ven
2005-10-26 20:01 ` Steve Snyder [this message]
2005-10-26 20:24 ` Lee Revell
2005-10-26 21:20 ` Steve Snyder
2005-10-26 22:00 ` Lee Revell
2005-10-26 20:44 ` Stephen Hemminger
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=200510261601.19369.R00020C@freescale.com \
--to=r00020c@freescale.com \
--cc=arjan@infradead.org \
--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
Powered by JetHome