bce0: Error mapping mbuf into TX chain!

Bucky Jordan bjordan at lumeta.com
Tue Aug 22 20:36:21 UTC 2006


Sam,

I'm also running the stock RELEASE kernel config- haven't had a chance
to do a rebuild yet.

But, I just noticed something interesting- the box has been running fine
for several days with multiple ssh connections, and several large remote
data loads (by way of postgres copy on port 5432). However, I just
installed webmin, set it up to run HTTPS on port 9090, and as soon as I
tried to connect- got the error. It does that every subsequent time too.


I will try the latest from 6-stable, but if you're thinking a big src
download from ports is high network io, well, lets just say the datasets
I'm copying around tend to dwarf the bsd source tree ;) (typically
they're several gb per dataset). So if that's still a problem I may be
jumping out of the proverbial frying pan and into the fire..

Thanks,

Bucky

-----Original Message-----
From: owner-freebsd-stable at freebsd.org
[mailto:owner-freebsd-stable at freebsd.org] On Behalf Of Sam Eaton
Sent: Tuesday, August 22, 2006 3:29 PM
To: stable at freebsd.org
Subject: Re: bce0: Error mapping mbuf into TX chain!

On Tue, Aug 22, 2006 at 02:46:04PM -0400, Bucky Jordan wrote:
> Sam,
> 
> I've got a PowerEdge 2950 with a DRAC 5 card, and I'm having what
> appears to be the same set of issues. I'm running 6.1 amd64 RELEASE.
> 
> I've only gotten the " bce0: Error mapping mbuf into TX chain!" error
a
> few times now. Although the box isn't in production at the moment,
we've
> been sending quite a bit of data (several GB) across the interface
> without a hitch (basically remote COPY statements for postgresql). It
> sounds like your 1950 is/was having the issue more frequently (our
2950
> stays up for days at a time).

The 'error mapping mbuf' error seems to have been fixed by the latest
set of changes to if_bce.c - after upgrading to the latest stable, that
problem stopped happening.  

However, instead of that, under rather higher load, we now get the
watchdog timer error instead.  This is not good :)  I can get it within
minutes with something like building something big from ports, during
the initial source download.

> However, the fact that I do get the error every now and then is still
a
> concern, so I plan to rebuild world and kernel when I get the chance.
> 
> Please keep us posted on your findings, and if it'd be useful to have
> another box to run tests on, I'd be happy to give it a go.

I think moving to stable will fix the mbuf error for you, as that's what
others report.  You, and all the other reports I've seen have been
running amd64, which I haven't been (I didn't build the box originally).
I'll know tommorow if amd64 makes much of a difference or not.

Oh, other info - I'm running the standard SMP kernel config with no
modifications.

Sam.
-- 
"Fortified with Essential Bitterness and Sarcasm"
    Matt Groening, "Binky's Guide to Love".
_______________________________________________
freebsd-stable at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
"freebsd-stable-unsubscribe at freebsd.org"


More information about the freebsd-stable mailing list