The only issue that I've had that remotely resembles that involes CPU usage, not memory. Assuming your statistics are from top(1), can you try 'top -S' to display what system process resources are also? I'm betting it's some system task, since your killing user processes has had no effect. (btw my issue is the "irq10:" task seemingly locked in *Giant state and sucking -- Anthony Jenkins
To Unsubscribe: send mail to with "unsubscribe freebsd-current" in the body of the message
Tried this, nothing was showing huge memory consumption. I had to reboot the machine anyway, so while it was down I put in another 256MB of memory and manually ran the expire. No huge cpu/swap spike, and no increase in wired memory after the expire. Looks like the wired memory problem is tied to the swapping in some way, based on empirical data.
- brian
+++ He rides a cycle of mighty days, and \ Wm Brian and Lori McCane represents the last great schizm among\ McCane Consulting the gods. Evil though he obviously is, \ he is a mighty figure, this father of \ # my spirit, and I respect him as the sons \ # of old did the fathers of their bodies. \ # Roger Zelazny - "Lord of Light" \ # +++
To Unsubscribe: send mail to with "unsubscribe freebsd-current" in the body of the message
Was this solution helpful? Show your Appreciation by rating it: