Re: "Badness in local_bh_enable" - a reasonable fix?
From: Steve Snyder
Date: Wed Oct 26 2005 - 15:01:44 EST
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.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/