This is no longer an issue for me. Not because I was able to track down the
issue and fix it, but because this machine has been repurposed and the
replacement machine (very different hardware) doesn't exhibit the symptoms.
Thanks to those that tried to help!
-Nick
On Feb 1, 2012 6:20 PM, Nick
Anybody else have any suggestions as to what I can do to further
troubleshoot this? After a recent upgrade the issue still exists (I've
provided the latest dmesg). I've taken to adding a periodic reboot to
my cron jobs so that I don't get stuck without network access while
I'm away from the
Okay, so finally I got around to disabling the vether/tun/bridge
interfaces and mbuf usage still seems to be climbing. Here's the
output from 'netstat -m' and 'systat mbuf' from the morning of Jan.
3rd (an hour or so after a reboot):
79 mbufs in use:
47 mbufs allocated to data
24
I'll give it a shot.
On Dec 19, 2011 4:27 AM, Stuart Henderson s...@spacehopper.org wrote:
I just noticed the vether/tun/bridge in your systat output.
To try and narrow things down, are you able to disable these
to see if there's any improvement?
On 2011-12-08, Nick Templeton
I just noticed the vether/tun/bridge in your systat output.
To try and narrow things down, are you able to disable these
to see if there's any improvement?
On 2011-12-08, Nick Templeton n...@nicktempleton.com wrote:
I think you're right Stuart, raising kern.maxclusters is only buying me time.
I think you're right Stuart, raising kern.maxclusters is only buying me time.
The only sysctl values I've modified are:
net.inet.ip.forwarding=1
ddb.panic=0
kern.maxclusters=8192
netstat -m shows increasing values over time, here's the output from
this morning:
3510 mbufs in use:
3479
Have you adjusted any other sysctl values?
What does netstat -m say? Run it once, then again after 30 mins or so.
What does systat mbuf say?
Did you update the kernel at the same time as changing bios settings?
If so, what did you run before? (check /var/log/messages*)
I doubt there's a
You're right that I had an outdated BIOS, which I've now updated, but
upon further review I don't think that is/was the culprit. I've since
had the issue re-surface and this time I noticed many lines like this
in the dmesg (not sure how I missed it before):
WARNING: mclpools limit reached;
You should try upgrading BIOS. As far as I can tell, it would be version
2.4 as of 8/7/2007.
http://www.dell.com/support/drivers/us/en/19/DriverDetails/DriverFileFormats?DriverId=HY9F0FileId=2731098639
(I was recently given an Dell Optiplex 755, also intel Core 2 Duo, and I
installed OpenBSD 5.0
9 matches
Mail list logo
